https://launchpad.net/ubuntu/+source/python-django/3:3.2.19-1ubuntu3/+build/26344941 RUN: /usr/share/launchpad-buildd/bin/builder-prep Kernel version: Linux lcy02-amd64-004 5.4.0-152-generic #169-Ubuntu SMP Tue Jun 6 22:23:09 UTC 2023 x86_64 Buildd toolchain package versions: launchpad-buildd_233~634~ubuntu20.04.1 python3-lpbuildd_233~634~ubuntu20.04.1 sbuild_0.79.0-1ubuntu1 git-build-recipe_0.3.6 git_1:2.25.1-1ubuntu3.11 dpkg-dev_1.19.7ubuntu3.2 python3-debian_0.1.36ubuntu1. Syncing the system clock with the buildd NTP service... 28 Jun 11:30:51 ntpdate[1884]: adjust time server 10.131.248.1 offset -0.008673 sec RUN: /usr/share/launchpad-buildd/bin/in-target unpack-chroot --backend=chroot --series=mantic --arch=amd64 PACKAGEBUILD-26344941 --image-type chroot /home/buildd/filecache-default/1fc1752c0976ad9eb0e621fd063fde252dab04e3 Creating target for build PACKAGEBUILD-26344941 RUN: /usr/share/launchpad-buildd/bin/in-target mount-chroot --backend=chroot --series=mantic --arch=amd64 PACKAGEBUILD-26344941 Starting target for build PACKAGEBUILD-26344941 RUN: /usr/share/launchpad-buildd/bin/in-target override-sources-list --backend=chroot --series=mantic --arch=amd64 PACKAGEBUILD-26344941 'deb http://ftpmaster.internal/ubuntu mantic main universe' 'deb http://ftpmaster.internal/ubuntu mantic-security main universe' 'deb http://ftpmaster.internal/ubuntu mantic-updates main universe' 'deb http://ftpmaster.internal/ubuntu mantic-proposed main universe' Overriding sources.list in build-PACKAGEBUILD-26344941 RUN: /usr/share/launchpad-buildd/bin/in-target update-debian-chroot --backend=chroot --series=mantic --arch=amd64 PACKAGEBUILD-26344941 Updating target for build PACKAGEBUILD-26344941 Get:1 http://ftpmaster.internal/ubuntu mantic InRelease [255 kB] Get:2 http://ftpmaster.internal/ubuntu mantic-security InRelease [90.7 kB] Get:3 http://ftpmaster.internal/ubuntu mantic-updates InRelease [90.7 kB] Get:4 http://ftpmaster.internal/ubuntu mantic-proposed InRelease [118 kB] Get:5 http://ftpmaster.internal/ubuntu mantic/main amd64 Packages [1400 kB] Get:6 http://ftpmaster.internal/ubuntu mantic/main Translation-en [515 kB] Get:7 http://ftpmaster.internal/ubuntu mantic/universe amd64 Packages [14.7 MB] Get:8 http://ftpmaster.internal/ubuntu mantic/universe Translation-en [5940 kB] Get:9 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 Packages [65.3 kB] Get:10 http://ftpmaster.internal/ubuntu mantic-proposed/main Translation-en [20.7 kB] Get:11 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 Packages [359 kB] Get:12 http://ftpmaster.internal/ubuntu mantic-proposed/universe Translation-en [139 kB] Fetched 23.7 MB in 2s (9623 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... The following NEW packages will be installed: gcc-13-base libproc2-0 The following packages will be upgraded: adduser advancecomp apt base-files bash binutils binutils-common binutils-x86-64-linux-gnu bsdutils ca-certificates coreutils cpp cpp-12 dash debconf diffutils dpkg dpkg-dev e2fsprogs fakeroot findutils g++ g++-12 gcc gcc-12 gcc-12-base gpg gpg-agent gpgconf gpgv grep hostname libacl1 libapparmor1 libapt-pkg6.0 libargon2-1 libasan8 libatomic1 libattr1 libaudit-common libaudit1 libbinutils libblkid1 libc-bin libc-dev-bin libc6 libc6-dev libcap-ng0 libcap2 libcc1-0 libcom-err2 libcrypt-dev libcrypt1 libcryptsetup12 libctf-nobfd0 libctf0 libdb5.3 libdebconfclient0 libdevmapper1.02.1 libdpkg-perl libext2fs2 libfakeroot libfdisk1 libgcc-12-dev libgcc-s1 libgcrypt20 libgnutls30 libgomp1 libgprofng0 libgssapi-krb5-2 libisl23 libitm1 libk5crypto3 libkmod2 libkrb5-3 libkrb5support0 liblsan0 liblzma5 libmd0 libmount1 libmpfr6 libncurses6 libncursesw6 libp11-kit0 libpam-modules libpam-modules-bin libpam-runtime libpam0g libpcre2-8-0 libperl5.36 libpng16-16 libquadmath0 libreadline8 libseccomp2 libselinux1 libsemanage-common libsemanage2 libsepol2 libsmartcols1 libsqlite3-0 libss2 libssl3 libstdc++-12-dev libstdc++6 libsystemd-shared libsystemd0 libtinfo6 libtsan2 libubsan1 libudev1 libuuid1 libzstd1 linux-libc-dev logsave lsb-base lto-disabled-list mawk mount ncurses-base ncurses-bin openssl perl perl-base perl-modules-5.36 pkgbinarymangler procps readline-common sed sensible-utils systemd systemd-sysv sysvinit-utils tar tzdata usrmerge util-linux util-linux-extra xz-utils zlib1g 139 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 111 MB of archives. After this operation, 286 kB disk space will be freed. Get:1 http://ftpmaster.internal/ubuntu mantic/main amd64 libcrypt-dev amd64 1:4.4.35-1 [112 kB] Get:2 http://ftpmaster.internal/ubuntu mantic/main amd64 libc6-dev amd64 2.37-0ubuntu2 [2092 kB] Get:3 http://ftpmaster.internal/ubuntu mantic/main amd64 libc-dev-bin amd64 2.37-0ubuntu2 [20.0 kB] Get:4 http://ftpmaster.internal/ubuntu mantic/main amd64 libcrypt1 amd64 1:4.4.35-1 [82.1 kB] Get:5 http://ftpmaster.internal/ubuntu mantic/main amd64 linux-libc-dev amd64 6.3.0-7.7 [1544 kB] Get:6 http://ftpmaster.internal/ubuntu mantic/main amd64 libc6 amd64 2.37-0ubuntu2 [3179 kB] Get:7 http://ftpmaster.internal/ubuntu mantic/main amd64 libc-bin amd64 2.37-0ubuntu2 [669 kB] Get:8 http://ftpmaster.internal/ubuntu mantic/main amd64 gcc-13-base amd64 13.1.0-6ubuntu1 [42.0 kB] Get:9 http://ftpmaster.internal/ubuntu mantic/main amd64 libgcc-s1 amd64 13.1.0-6ubuntu1 [62.5 kB] Get:10 http://ftpmaster.internal/ubuntu mantic/main amd64 base-files amd64 13ubuntu1 [74.0 kB] Get:11 http://ftpmaster.internal/ubuntu mantic/main amd64 bash amd64 5.2.15-2ubuntu1 [795 kB] Get:12 http://ftpmaster.internal/ubuntu mantic/main amd64 bsdutils amd64 1:2.38.1-5ubuntu2 [91.5 kB] Get:13 http://ftpmaster.internal/ubuntu mantic/main amd64 coreutils amd64 9.1-1ubuntu2 [1407 kB] Get:14 http://ftpmaster.internal/ubuntu mantic/main amd64 liblzma5 amd64 5.4.1-0.2 [125 kB] Get:15 http://ftpmaster.internal/ubuntu mantic/main amd64 libgcrypt20 amd64 1.10.1-3ubuntu1 [529 kB] Get:16 http://ftpmaster.internal/ubuntu mantic/main amd64 libstdc++6 amd64 13.1.0-6ubuntu1 [772 kB] Get:17 http://ftpmaster.internal/ubuntu mantic/main amd64 libacl1 amd64 2.3.1-3 [16.4 kB] Get:18 http://ftpmaster.internal/ubuntu mantic/main amd64 libapparmor1 amd64 3.0.8-1ubuntu3 [46.3 kB] Get:19 http://ftpmaster.internal/ubuntu mantic/main amd64 libaudit-common all 1:3.0.9-1 [5142 B] Get:20 http://ftpmaster.internal/ubuntu mantic/main amd64 libcap-ng0 amd64 0.8.3-1build2 [15.3 kB] Get:21 http://ftpmaster.internal/ubuntu mantic/main amd64 libaudit1 amd64 1:3.0.9-1 [46.0 kB] Get:22 http://ftpmaster.internal/ubuntu mantic/main amd64 libblkid1 amd64 2.38.1-5ubuntu2 [111 kB] Get:23 http://ftpmaster.internal/ubuntu mantic/main amd64 libcap2 amd64 1:2.66-4ubuntu1 [29.4 kB] Get:24 http://ftpmaster.internal/ubuntu mantic/main amd64 libperl5.36 amd64 5.36.0-7ubuntu1 [4834 kB] Get:25 http://ftpmaster.internal/ubuntu mantic/main amd64 perl amd64 5.36.0-7ubuntu1 [235 kB] Get:26 http://ftpmaster.internal/ubuntu mantic/main amd64 perl-base amd64 5.36.0-7ubuntu1 [1784 kB] Get:27 http://ftpmaster.internal/ubuntu mantic/main amd64 perl-modules-5.36 all 5.36.0-7ubuntu1 [2984 kB] Get:28 http://ftpmaster.internal/ubuntu mantic/main amd64 libdb5.3 amd64 5.3.28+dfsg2-1 [742 kB] Get:29 http://ftpmaster.internal/ubuntu mantic/main amd64 zlib1g amd64 1:1.2.13.dfsg-1ubuntu4 [61.2 kB] Get:30 http://ftpmaster.internal/ubuntu mantic/main amd64 debconf all 1.5.82 [125 kB] Get:31 http://ftpmaster.internal/ubuntu mantic/main amd64 libssl3 amd64 3.0.9-1ubuntu1 [1901 kB] Get:32 http://ftpmaster.internal/ubuntu mantic/main amd64 libzstd1 amd64 1.5.4+dfsg2-5 [292 kB] Get:33 http://ftpmaster.internal/ubuntu mantic/main amd64 libkmod2 amd64 30+20221128-1ubuntu1 [49.5 kB] Get:34 http://ftpmaster.internal/ubuntu mantic/main amd64 libpcre2-8-0 amd64 10.42-1 [228 kB] Get:35 http://ftpmaster.internal/ubuntu mantic/main amd64 libselinux1 amd64 3.4-1build4 [78.1 kB] Get:36 http://ftpmaster.internal/ubuntu mantic/main amd64 libmount1 amd64 2.38.1-5ubuntu2 [121 kB] Get:37 http://ftpmaster.internal/ubuntu mantic/main amd64 libpam0g amd64 1.5.2-6ubuntu1 [65.9 kB] Get:38 http://ftpmaster.internal/ubuntu mantic/main amd64 libseccomp2 amd64 2.5.4-1ubuntu3 [49.1 kB] Get:39 http://ftpmaster.internal/ubuntu mantic/main amd64 systemd-sysv amd64 252.5-2ubuntu3 [11.5 kB] Get:40 http://ftpmaster.internal/ubuntu mantic/main amd64 systemd amd64 252.5-2ubuntu3 [3002 kB] Get:41 http://ftpmaster.internal/ubuntu mantic/main amd64 libsystemd-shared amd64 252.5-2ubuntu3 [1832 kB] Get:42 http://ftpmaster.internal/ubuntu mantic/main amd64 libargon2-1 amd64 0~20190702+dfsg-3 [20.3 kB] Get:43 http://ftpmaster.internal/ubuntu mantic/main amd64 libudev1 amd64 252.5-2ubuntu3 [150 kB] Get:44 http://ftpmaster.internal/ubuntu mantic/main amd64 libdevmapper1.02.1 amd64 2:1.02.185-2ubuntu1 [139 kB] Get:45 http://ftpmaster.internal/ubuntu mantic/main amd64 libuuid1 amd64 2.38.1-5ubuntu2 [32.7 kB] Get:46 http://ftpmaster.internal/ubuntu mantic/main amd64 libcryptsetup12 amd64 2:2.6.1-4ubuntu1 [243 kB] Get:47 http://ftpmaster.internal/ubuntu mantic/main amd64 libfdisk1 amd64 2.38.1-5ubuntu2 [144 kB] Get:48 http://ftpmaster.internal/ubuntu mantic/main amd64 libp11-kit0 amd64 0.24.1-2ubuntu1 [248 kB] Get:49 http://ftpmaster.internal/ubuntu mantic/main amd64 mount amd64 2.38.1-5ubuntu2 [114 kB] Get:50 http://ftpmaster.internal/ubuntu mantic/main amd64 libsystemd0 amd64 252.5-2ubuntu3 [389 kB] Get:51 http://ftpmaster.internal/ubuntu mantic/main amd64 libapt-pkg6.0 amd64 2.7.1 [930 kB] Get:52 http://ftpmaster.internal/ubuntu mantic/main amd64 tar amd64 1.34+dfsg-1.2ubuntu1 [293 kB] Get:53 http://ftpmaster.internal/ubuntu mantic/main amd64 dpkg amd64 1.21.22ubuntu1 [1393 kB] Get:54 http://ftpmaster.internal/ubuntu mantic/main amd64 dash amd64 0.5.12-2ubuntu1 [88.2 kB] Get:55 http://ftpmaster.internal/ubuntu mantic/main amd64 diffutils amd64 1:3.8-4 [176 kB] Get:56 http://ftpmaster.internal/ubuntu mantic/main amd64 findutils amd64 4.9.0-4ubuntu1 [299 kB] Get:57 http://ftpmaster.internal/ubuntu mantic/main amd64 grep amd64 3.8-5 [160 kB] Get:58 http://ftpmaster.internal/ubuntu mantic/main amd64 hostname amd64 3.23+nmu1ubuntu1 [11.0 kB] Get:59 http://ftpmaster.internal/ubuntu mantic/main amd64 ncurses-bin amd64 6.4-4 [185 kB] Get:60 http://ftpmaster.internal/ubuntu mantic/main amd64 sed amd64 4.9-1 [193 kB] Get:61 http://ftpmaster.internal/ubuntu mantic/main amd64 libsmartcols1 amd64 2.38.1-5ubuntu2 [59.5 kB] Get:62 http://ftpmaster.internal/ubuntu mantic/main amd64 util-linux-extra amd64 2.38.1-5ubuntu2 [83.8 kB] Get:63 http://ftpmaster.internal/ubuntu mantic/main amd64 util-linux amd64 2.38.1-5ubuntu2 [1075 kB] Get:64 http://ftpmaster.internal/ubuntu mantic/main amd64 ncurses-base all 6.4-4 [23.3 kB] Get:65 http://ftpmaster.internal/ubuntu mantic/main amd64 sysvinit-utils amd64 3.06-4ubuntu1 [33.0 kB] Get:66 http://ftpmaster.internal/ubuntu mantic/main amd64 lsb-base all 11.6 [4606 B] Get:67 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 adduser all 3.134ubuntu1 [136 kB] Get:68 http://ftpmaster.internal/ubuntu mantic/main amd64 gpgv amd64 2.2.40-1.1ubuntu1 [140 kB] Get:69 http://ftpmaster.internal/ubuntu mantic/main amd64 libgnutls30 amd64 3.7.9-2ubuntu1 [999 kB] Get:70 http://ftpmaster.internal/ubuntu mantic/main amd64 apt amd64 2.7.1 [1359 kB] Get:71 http://ftpmaster.internal/ubuntu mantic/main amd64 libpam-modules-bin amd64 1.5.2-6ubuntu1 [47.3 kB] Get:72 http://ftpmaster.internal/ubuntu mantic/main amd64 libpam-modules amd64 1.5.2-6ubuntu1 [284 kB] Get:73 http://ftpmaster.internal/ubuntu mantic/main amd64 logsave amd64 1.47.0-1ubuntu1 [14.2 kB] Get:74 http://ftpmaster.internal/ubuntu mantic/main amd64 libext2fs2 amd64 1.47.0-1ubuntu1 [212 kB] Get:75 http://ftpmaster.internal/ubuntu mantic/main amd64 e2fsprogs amd64 1.47.0-1ubuntu1 [598 kB] Get:76 http://ftpmaster.internal/ubuntu mantic/main amd64 libattr1 amd64 1:2.5.1-4 [12.4 kB] Get:77 http://ftpmaster.internal/ubuntu mantic/main amd64 libdebconfclient0 amd64 0.267ubuntu1 [7892 B] Get:78 http://ftpmaster.internal/ubuntu mantic/main amd64 libmd0 amd64 1.1.0-1 [26.9 kB] Get:79 http://ftpmaster.internal/ubuntu mantic/main amd64 libpam-runtime all 1.5.2-6ubuntu1 [41.5 kB] Get:80 http://ftpmaster.internal/ubuntu mantic/main amd64 libsemanage-common all 3.4-1build4 [9852 B] Get:81 http://ftpmaster.internal/ubuntu mantic/main amd64 libsepol2 amd64 3.4-2.1 [301 kB] Get:82 http://ftpmaster.internal/ubuntu mantic/main amd64 libsemanage2 amd64 3.4-1build4 [92.7 kB] Get:83 http://ftpmaster.internal/ubuntu mantic/main amd64 libncurses6 amd64 6.4-4 [112 kB] Get:84 http://ftpmaster.internal/ubuntu mantic/main amd64 libncursesw6 amd64 6.4-4 [147 kB] Get:85 http://ftpmaster.internal/ubuntu mantic/main amd64 libtinfo6 amd64 6.4-4 [103 kB] Get:86 http://ftpmaster.internal/ubuntu mantic/main amd64 usrmerge all 35ubuntu1 [58.2 kB] Get:87 http://ftpmaster.internal/ubuntu mantic/main amd64 libcom-err2 amd64 1.47.0-1ubuntu1 [14.5 kB] Get:88 http://ftpmaster.internal/ubuntu mantic/main amd64 libproc2-0 amd64 2:4.0.3-1ubuntu1 [55.9 kB] Get:89 http://ftpmaster.internal/ubuntu mantic/main amd64 libss2 amd64 1.47.0-1ubuntu1 [16.8 kB] Get:90 http://ftpmaster.internal/ubuntu mantic/main amd64 mawk amd64 1.3.4.20230525-1 [113 kB] Get:91 http://ftpmaster.internal/ubuntu mantic/main amd64 procps amd64 2:4.0.3-1ubuntu1 [609 kB] Get:92 http://ftpmaster.internal/ubuntu mantic/main amd64 sensible-utils all 0.0.20 [19.6 kB] Get:93 http://ftpmaster.internal/ubuntu mantic/main amd64 openssl amd64 3.0.9-1ubuntu1 [1189 kB] Get:94 http://ftpmaster.internal/ubuntu mantic/main amd64 ca-certificates all 20230311ubuntu1 [152 kB] Get:95 http://ftpmaster.internal/ubuntu mantic/main amd64 libgssapi-krb5-2 amd64 1.20.1-2 [142 kB] Get:96 http://ftpmaster.internal/ubuntu mantic/main amd64 libkrb5-3 amd64 1.20.1-2 [346 kB] Get:97 http://ftpmaster.internal/ubuntu mantic/main amd64 libkrb5support0 amd64 1.20.1-2 [32.7 kB] Get:98 http://ftpmaster.internal/ubuntu mantic/main amd64 libk5crypto3 amd64 1.20.1-2 [81.1 kB] Get:99 http://ftpmaster.internal/ubuntu mantic/main amd64 readline-common all 8.2-1.3 [55.7 kB] Get:100 http://ftpmaster.internal/ubuntu mantic/main amd64 libreadline8 amd64 8.2-1.3 [151 kB] Get:101 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 libsqlite3-0 amd64 3.42.0-1 [668 kB] Get:102 http://ftpmaster.internal/ubuntu mantic/main amd64 tzdata all 2023c-4exp1ubuntu1 [271 kB] Get:103 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 libpng16-16 amd64 1.6.40-1 [186 kB] Get:104 http://ftpmaster.internal/ubuntu mantic/main amd64 xz-utils amd64 5.4.1-0.2 [270 kB] Get:105 http://ftpmaster.internal/ubuntu mantic/main amd64 advancecomp amd64 2.5-1 [180 kB] Get:106 http://ftpmaster.internal/ubuntu mantic/main amd64 libgprofng0 amd64 2.40.50.20230622-1ubuntu1 [902 kB] Get:107 http://ftpmaster.internal/ubuntu mantic/main amd64 libctf0 amd64 2.40.50.20230622-1ubuntu1 [97.1 kB] Get:108 http://ftpmaster.internal/ubuntu mantic/main amd64 libctf-nobfd0 amd64 2.40.50.20230622-1ubuntu1 [99.7 kB] Get:109 http://ftpmaster.internal/ubuntu mantic/main amd64 binutils-x86-64-linux-gnu amd64 2.40.50.20230622-1ubuntu1 [2524 kB] Get:110 http://ftpmaster.internal/ubuntu mantic/main amd64 libbinutils amd64 2.40.50.20230622-1ubuntu1 [631 kB] Get:111 http://ftpmaster.internal/ubuntu mantic/main amd64 binutils amd64 2.40.50.20230622-1ubuntu1 [18.7 kB] Get:112 http://ftpmaster.internal/ubuntu mantic/main amd64 binutils-common amd64 2.40.50.20230622-1ubuntu1 [252 kB] Get:113 http://ftpmaster.internal/ubuntu mantic/main amd64 libisl23 amd64 0.26-3 [741 kB] Get:114 http://ftpmaster.internal/ubuntu mantic/main amd64 libmpfr6 amd64 4.2.0-1 [352 kB] Get:115 http://ftpmaster.internal/ubuntu mantic/main amd64 g++-12 amd64 12.3.0-3ubuntu1 [12.1 MB] Get:116 http://ftpmaster.internal/ubuntu mantic/main amd64 gcc-12 amd64 12.3.0-3ubuntu1 [21.6 MB] Get:117 http://ftpmaster.internal/ubuntu mantic/main amd64 cpp-12 amd64 12.3.0-3ubuntu1 [10.7 MB] Get:118 http://ftpmaster.internal/ubuntu mantic/main amd64 libubsan1 amd64 13.1.0-6ubuntu1 [1104 kB] Get:119 http://ftpmaster.internal/ubuntu mantic/main amd64 libstdc++-12-dev amd64 12.3.0-3ubuntu1 [2180 kB] Get:120 http://ftpmaster.internal/ubuntu mantic/main amd64 libgomp1 amd64 13.1.0-6ubuntu1 [142 kB] Get:121 http://ftpmaster.internal/ubuntu mantic/main amd64 libitm1 amd64 13.1.0-6ubuntu1 [29.5 kB] Get:122 http://ftpmaster.internal/ubuntu mantic/main amd64 libatomic1 amd64 13.1.0-6ubuntu1 [10.4 kB] Get:123 http://ftpmaster.internal/ubuntu mantic/main amd64 libasan8 amd64 13.1.0-6ubuntu1 [2827 kB] Get:124 http://ftpmaster.internal/ubuntu mantic/main amd64 liblsan0 amd64 13.1.0-6ubuntu1 [1203 kB] Get:125 http://ftpmaster.internal/ubuntu mantic/main amd64 libquadmath0 amd64 13.1.0-6ubuntu1 [153 kB] Get:126 http://ftpmaster.internal/ubuntu mantic/main amd64 libgcc-12-dev amd64 12.3.0-3ubuntu1 [2575 kB] Get:127 http://ftpmaster.internal/ubuntu mantic/main amd64 libtsan2 amd64 13.1.0-6ubuntu1 [2599 kB] Get:128 http://ftpmaster.internal/ubuntu mantic/main amd64 libcc1-0 amd64 13.1.0-6ubuntu1 [48.1 kB] Get:129 http://ftpmaster.internal/ubuntu mantic/main amd64 gcc-12-base amd64 12.3.0-3ubuntu1 [42.7 kB] Get:130 http://ftpmaster.internal/ubuntu mantic/main amd64 g++ amd64 4:12.2.0-3ubuntu1 [1120 B] Get:131 http://ftpmaster.internal/ubuntu mantic/main amd64 gcc amd64 4:12.2.0-3ubuntu1 [5160 B] Get:132 http://ftpmaster.internal/ubuntu mantic/main amd64 cpp amd64 4:12.2.0-3ubuntu1 [27.8 kB] Get:133 http://ftpmaster.internal/ubuntu mantic/main amd64 dpkg-dev all 1.21.22ubuntu1 [1118 kB] Get:134 http://ftpmaster.internal/ubuntu mantic/main amd64 libdpkg-perl all 1.21.22ubuntu1 [247 kB] Get:135 http://ftpmaster.internal/ubuntu mantic/main amd64 lto-disabled-list all 41 [12.4 kB] Get:136 http://ftpmaster.internal/ubuntu mantic/main amd64 libfakeroot amd64 1.31-1.2 [32.0 kB] Get:137 http://ftpmaster.internal/ubuntu mantic/main amd64 fakeroot amd64 1.31-1.2 [60.1 kB] Get:138 http://ftpmaster.internal/ubuntu mantic/main amd64 gpg amd64 2.2.40-1.1ubuntu1 [523 kB] Get:139 http://ftpmaster.internal/ubuntu mantic/main amd64 gpgconf amd64 2.2.40-1.1ubuntu1 [96.3 kB] Get:140 http://ftpmaster.internal/ubuntu mantic/main amd64 gpg-agent amd64 2.2.40-1.1ubuntu1 [216 kB] Get:141 http://ftpmaster.internal/ubuntu mantic/main amd64 pkgbinarymangler all 153 [16.3 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 111 MB in 1s (127 MB/s) (Reading database ... 13093 files and directories currently installed.) Preparing to unpack .../libcrypt-dev_1%3a4.4.35-1_amd64.deb ... Unpacking libcrypt-dev:amd64 (1:4.4.35-1) over (1:4.4.33-1) ... Preparing to unpack .../libc6-dev_2.37-0ubuntu2_amd64.deb ... Unpacking libc6-dev:amd64 (2.37-0ubuntu2) over (2.36-0ubuntu4) ... Preparing to unpack .../libc-dev-bin_2.37-0ubuntu2_amd64.deb ... Unpacking libc-dev-bin (2.37-0ubuntu2) over (2.36-0ubuntu4) ... Preparing to unpack .../libcrypt1_1%3a4.4.35-1_amd64.deb ... Unpacking libcrypt1:amd64 (1:4.4.35-1) over (1:4.4.33-1) ... Setting up libcrypt1:amd64 (1:4.4.35-1) ... (Reading database ... 13093 files and directories currently installed.) Preparing to unpack .../linux-libc-dev_6.3.0-7.7_amd64.deb ... Unpacking linux-libc-dev:amd64 (6.3.0-7.7) over (5.19.0-21.21) ... Preparing to unpack .../libc6_2.37-0ubuntu2_amd64.deb ... Unpacking libc6:amd64 (2.37-0ubuntu2) over (2.36-0ubuntu4) ... Setting up libc6:amd64 (2.37-0ubuntu2) ... (Reading database ... 13096 files and directories currently installed.) Preparing to unpack .../libc-bin_2.37-0ubuntu2_amd64.deb ... Unpacking libc-bin (2.37-0ubuntu2) over (2.36-0ubuntu4) ... Setting up libc-bin (2.37-0ubuntu2) ... Selecting previously unselected package gcc-13-base:amd64. (Reading database ... 13096 files and directories currently installed.) Preparing to unpack .../gcc-13-base_13.1.0-6ubuntu1_amd64.deb ... Unpacking gcc-13-base:amd64 (13.1.0-6ubuntu1) ... Setting up gcc-13-base:amd64 (13.1.0-6ubuntu1) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libgcc-s1_13.1.0-6ubuntu1_amd64.deb ... Unpacking libgcc-s1:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Setting up libgcc-s1:amd64 (13.1.0-6ubuntu1) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../base-files_13ubuntu1_amd64.deb ... Unpacking base-files (13ubuntu1) over (12.3ubuntu1) ... Setting up base-files (13ubuntu1) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../bash_5.2.15-2ubuntu1_amd64.deb ... Unpacking bash (5.2.15-2ubuntu1) over (5.2-1ubuntu2) ... Setting up bash (5.2.15-2ubuntu1) ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../bsdutils_1%3a2.38.1-5ubuntu2_amd64.deb ... Unpacking bsdutils (1:2.38.1-5ubuntu2) over (1:2.38.1-4ubuntu1) ... Setting up bsdutils (1:2.38.1-5ubuntu2) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../coreutils_9.1-1ubuntu2_amd64.deb ... Unpacking coreutils (9.1-1ubuntu2) over (8.32-4.1ubuntu1) ... Setting up coreutils (9.1-1ubuntu2) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../liblzma5_5.4.1-0.2_amd64.deb ... Unpacking liblzma5:amd64 (5.4.1-0.2) over (5.2.9-0.0) ... Setting up liblzma5:amd64 (5.4.1-0.2) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libgcrypt20_1.10.1-3ubuntu1_amd64.deb ... Unpacking libgcrypt20:amd64 (1.10.1-3ubuntu1) over (1.10.1-2ubuntu1) ... Setting up libgcrypt20:amd64 (1.10.1-3ubuntu1) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libstdc++6_13.1.0-6ubuntu1_amd64.deb ... Unpacking libstdc++6:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Setting up libstdc++6:amd64 (13.1.0-6ubuntu1) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libacl1_2.3.1-3_amd64.deb ... Unpacking libacl1:amd64 (2.3.1-3) over (2.3.1-2) ... Setting up libacl1:amd64 (2.3.1-3) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libapparmor1_3.0.8-1ubuntu3_amd64.deb ... Unpacking libapparmor1:amd64 (3.0.8-1ubuntu3) over (3.0.8-1ubuntu1) ... Preparing to unpack .../libaudit-common_1%3a3.0.9-1_all.deb ... Unpacking libaudit-common (1:3.0.9-1) over (1:3.0.7-1ubuntu3) ... Setting up libaudit-common (1:3.0.9-1) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libcap-ng0_0.8.3-1build2_amd64.deb ... Unpacking libcap-ng0:amd64 (0.8.3-1build2) over (0.8.3-1build1) ... Setting up libcap-ng0:amd64 (0.8.3-1build2) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libaudit1_1%3a3.0.9-1_amd64.deb ... Unpacking libaudit1:amd64 (1:3.0.9-1) over (1:3.0.7-1ubuntu3) ... Setting up libaudit1:amd64 (1:3.0.9-1) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libblkid1_2.38.1-5ubuntu2_amd64.deb ... Unpacking libblkid1:amd64 (2.38.1-5ubuntu2) over (2.38.1-4ubuntu1) ... Setting up libblkid1:amd64 (2.38.1-5ubuntu2) ... (Reading database ... 13101 files and directories currently installed.) Preparing to unpack .../libcap2_1%3a2.66-4ubuntu1_amd64.deb ... Unpacking libcap2:amd64 (1:2.66-4ubuntu1) over (1:2.44-1build3) ... Setting up libcap2:amd64 (1:2.66-4ubuntu1) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../libperl5.36_5.36.0-7ubuntu1_amd64.deb ... Unpacking libperl5.36:amd64 (5.36.0-7ubuntu1) over (5.36.0-4ubuntu2) ... Preparing to unpack .../perl_5.36.0-7ubuntu1_amd64.deb ... Unpacking perl (5.36.0-7ubuntu1) over (5.36.0-4ubuntu2) ... Preparing to unpack .../perl-base_5.36.0-7ubuntu1_amd64.deb ... Unpacking perl-base (5.36.0-7ubuntu1) over (5.36.0-4ubuntu2) ... Setting up perl-base (5.36.0-7ubuntu1) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../perl-modules-5.36_5.36.0-7ubuntu1_all.deb ... Unpacking perl-modules-5.36 (5.36.0-7ubuntu1) over (5.36.0-4ubuntu2) ... Preparing to unpack .../libdb5.3_5.3.28+dfsg2-1_amd64.deb ... Unpacking libdb5.3:amd64 (5.3.28+dfsg2-1) over (5.3.28+dfsg1-0.10) ... Setting up libdb5.3:amd64 (5.3.28+dfsg2-1) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../zlib1g_1%3a1.2.13.dfsg-1ubuntu4_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.13.dfsg-1ubuntu4) over (1:1.2.11.dfsg-4.1ubuntu1) ... Setting up zlib1g:amd64 (1:1.2.13.dfsg-1ubuntu4) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../debconf_1.5.82_all.deb ... Unpacking debconf (1.5.82) over (1.5.79ubuntu1) ... Setting up debconf (1.5.82) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../libssl3_3.0.9-1ubuntu1_amd64.deb ... Unpacking libssl3:amd64 (3.0.9-1ubuntu1) over (3.0.5-2ubuntu2) ... Preparing to unpack .../libzstd1_1.5.4+dfsg2-5_amd64.deb ... Unpacking libzstd1:amd64 (1.5.4+dfsg2-5) over (1.5.2+dfsg-1) ... Setting up libzstd1:amd64 (1.5.4+dfsg2-5) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../libkmod2_30+20221128-1ubuntu1_amd64.deb ... Unpacking libkmod2:amd64 (30+20221128-1ubuntu1) over (30+20220905-1ubuntu1) ... Preparing to unpack .../libpcre2-8-0_10.42-1_amd64.deb ... Unpacking libpcre2-8-0:amd64 (10.42-1) over (10.40-1ubuntu1) ... Setting up libpcre2-8-0:amd64 (10.42-1) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../libselinux1_3.4-1build4_amd64.deb ... Unpacking libselinux1:amd64 (3.4-1build4) over (3.4-1build1) ... Setting up libselinux1:amd64 (3.4-1build4) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../libmount1_2.38.1-5ubuntu2_amd64.deb ... Unpacking libmount1:amd64 (2.38.1-5ubuntu2) over (2.38.1-4ubuntu1) ... Setting up libmount1:amd64 (2.38.1-5ubuntu2) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../libpam0g_1.5.2-6ubuntu1_amd64.deb ... Unpacking libpam0g:amd64 (1.5.2-6ubuntu1) over (1.5.2-5ubuntu1) ... Setting up libpam0g:amd64 (1.5.2-6ubuntu1) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../libseccomp2_2.5.4-1ubuntu3_amd64.deb ... Unpacking libseccomp2:amd64 (2.5.4-1ubuntu3) over (2.5.4-1ubuntu2) ... Setting up libseccomp2:amd64 (2.5.4-1ubuntu3) ... (Reading database ... 13103 files and directories currently installed.) Preparing to unpack .../systemd-sysv_252.5-2ubuntu3_amd64.deb ... Unpacking systemd-sysv (252.5-2ubuntu3) over (251.4-1ubuntu7) ... Setting up libssl3:amd64 (3.0.9-1ubuntu1) ... (Reading database ... 13104 files and directories currently installed.) Preparing to unpack .../systemd_252.5-2ubuntu3_amd64.deb ... Unpacking systemd (252.5-2ubuntu3) over (251.4-1ubuntu7) ... Preparing to unpack .../libsystemd-shared_252.5-2ubuntu3_amd64.deb ... Unpacking libsystemd-shared:amd64 (252.5-2ubuntu3) over (251.4-1ubuntu7) ... Preparing to unpack .../libargon2-1_0~20190702+dfsg-3_amd64.deb ... Unpacking libargon2-1:amd64 (0~20190702+dfsg-3) over (0~20171227-0.3) ... Preparing to unpack .../libudev1_252.5-2ubuntu3_amd64.deb ... Unpacking libudev1:amd64 (252.5-2ubuntu3) over (251.4-1ubuntu7) ... Setting up libudev1:amd64 (252.5-2ubuntu3) ... (Reading database ... 13135 files and directories currently installed.) Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.185-2ubuntu1_amd64.deb ... Unpacking libdevmapper1.02.1:amd64 (2:1.02.185-2ubuntu1) over (2:1.02.185-1ubuntu1) ... Preparing to unpack .../libuuid1_2.38.1-5ubuntu2_amd64.deb ... Unpacking libuuid1:amd64 (2.38.1-5ubuntu2) over (2.38.1-4ubuntu1) ... Setting up libuuid1:amd64 (2.38.1-5ubuntu2) ... (Reading database ... 13135 files and directories currently installed.) Preparing to unpack .../libcryptsetup12_2%3a2.6.1-4ubuntu1_amd64.deb ... Unpacking libcryptsetup12:amd64 (2:2.6.1-4ubuntu1) over (2:2.5.0-6ubuntu3) ... Preparing to unpack .../libfdisk1_2.38.1-5ubuntu2_amd64.deb ... Unpacking libfdisk1:amd64 (2.38.1-5ubuntu2) over (2.38.1-4ubuntu1) ... Preparing to unpack .../libp11-kit0_0.24.1-2ubuntu1_amd64.deb ... Unpacking libp11-kit0:amd64 (0.24.1-2ubuntu1) over (0.24.1-1ubuntu2) ... Setting up libp11-kit0:amd64 (0.24.1-2ubuntu1) ... (Reading database ... 13135 files and directories currently installed.) Preparing to unpack .../mount_2.38.1-5ubuntu2_amd64.deb ... Unpacking mount (2.38.1-5ubuntu2) over (2.38.1-4ubuntu1) ... Preparing to unpack .../libsystemd0_252.5-2ubuntu3_amd64.deb ... Unpacking libsystemd0:amd64 (252.5-2ubuntu3) over (251.4-1ubuntu7) ... Setting up libsystemd0:amd64 (252.5-2ubuntu3) ... (Reading database ... 13136 files and directories currently installed.) Preparing to unpack .../libapt-pkg6.0_2.7.1_amd64.deb ... Unpacking libapt-pkg6.0:amd64 (2.7.1) over (2.5.4) ... Setting up libapt-pkg6.0:amd64 (2.7.1) ... (Reading database ... 13136 files and directories currently installed.) Preparing to unpack .../tar_1.34+dfsg-1.2ubuntu1_amd64.deb ... Unpacking tar (1.34+dfsg-1.2ubuntu1) over (1.34+dfsg-1.1) ... Setting up tar (1.34+dfsg-1.2ubuntu1) ... (Reading database ... 13136 files and directories currently installed.) Preparing to unpack .../dpkg_1.21.22ubuntu1_amd64.deb ... Unpacking dpkg (1.21.22ubuntu1) over (1.21.11ubuntu2) ... Setting up dpkg (1.21.22ubuntu1) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../dash_0.5.12-2ubuntu1_amd64.deb ... Unpacking dash (0.5.12-2ubuntu1) over (0.5.11+git20210903+057cd650a4ed-9ubuntu1) ... Setting up dash (0.5.12-2ubuntu1) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../diffutils_1%3a3.8-4_amd64.deb ... Unpacking diffutils (1:3.8-4) over (1:3.8-1) ... Setting up diffutils (1:3.8-4) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../findutils_4.9.0-4ubuntu1_amd64.deb ... Unpacking findutils (4.9.0-4ubuntu1) over (4.9.0-3ubuntu1) ... Setting up findutils (4.9.0-4ubuntu1) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../archives/grep_3.8-5_amd64.deb ... Unpacking grep (3.8-5) over (3.8-3) ... Setting up grep (3.8-5) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../hostname_3.23+nmu1ubuntu1_amd64.deb ... Unpacking hostname (3.23+nmu1ubuntu1) over (3.23ubuntu2) ... Setting up hostname (3.23+nmu1ubuntu1) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../ncurses-bin_6.4-4_amd64.deb ... Unpacking ncurses-bin (6.4-4) over (6.3+20220423-2) ... Setting up ncurses-bin (6.4-4) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../archives/sed_4.9-1_amd64.deb ... Unpacking sed (4.9-1) over (4.8-1ubuntu2) ... Setting up sed (4.9-1) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../libsmartcols1_2.38.1-5ubuntu2_amd64.deb ... Unpacking libsmartcols1:amd64 (2.38.1-5ubuntu2) over (2.38.1-4ubuntu1) ... Setting up libsmartcols1:amd64 (2.38.1-5ubuntu2) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../util-linux-extra_2.38.1-5ubuntu2_amd64.deb ... Unpacking util-linux-extra (2.38.1-5ubuntu2) over (2.38.1-4ubuntu1) ... Setting up util-linux-extra (2.38.1-5ubuntu2) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../util-linux_2.38.1-5ubuntu2_amd64.deb ... Unpacking util-linux (2.38.1-5ubuntu2) over (2.38.1-4ubuntu1) ... Setting up util-linux (2.38.1-5ubuntu2) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../ncurses-base_6.4-4_all.deb ... Unpacking ncurses-base (6.4-4) over (6.3+20220423-2) ... Setting up ncurses-base (6.4-4) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../archives/lsb-base_11.6_all.deb ... Unpacking lsb-base (11.6) over (11.2ubuntu1) ... Preparing to unpack .../sysvinit-utils_3.06-4ubuntu1_amd64.deb ... Unpacking sysvinit-utils (3.06-4ubuntu1) over (3.04-1ubuntu1) ... Setting up sysvinit-utils (3.06-4ubuntu1) ... (Reading database ... 13139 files and directories currently installed.) Preparing to unpack .../adduser_3.134ubuntu1_all.deb ... moving unchanged adduser.conf to adduser.conf.update-old. New dpkg-conffile will come from the package. Unpacking adduser (3.134ubuntu1) over (3.121ubuntu1) ... Setting up adduser (3.134ubuntu1) ... Installing new version of config file /etc/deluser.conf ... (Reading database ... 13109 files and directories currently installed.) Preparing to unpack .../gpgv_2.2.40-1.1ubuntu1_amd64.deb ... Unpacking gpgv (2.2.40-1.1ubuntu1) over (2.2.40-1ubuntu1) ... Setting up gpgv (2.2.40-1.1ubuntu1) ... (Reading database ... 13109 files and directories currently installed.) Preparing to unpack .../libgnutls30_3.7.9-2ubuntu1_amd64.deb ... Unpacking libgnutls30:amd64 (3.7.9-2ubuntu1) over (3.7.7-2ubuntu2) ... Setting up libgnutls30:amd64 (3.7.9-2ubuntu1) ... (Reading database ... 13109 files and directories currently installed.) Preparing to unpack .../archives/apt_2.7.1_amd64.deb ... Unpacking apt (2.7.1) over (2.5.4) ... Setting up apt (2.7.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libpam-modules-bin_1.5.2-6ubuntu1_amd64.deb ... Unpacking libpam-modules-bin (1.5.2-6ubuntu1) over (1.5.2-5ubuntu1) ... Setting up libpam-modules-bin (1.5.2-6ubuntu1) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.5.2-6ubuntu1_amd64.deb ... Unpacking libpam-modules:amd64 (1.5.2-6ubuntu1) over (1.5.2-5ubuntu1) ... Setting up libpam-modules:amd64 (1.5.2-6ubuntu1) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../logsave_1.47.0-1ubuntu1_amd64.deb ... Unpacking logsave (1.47.0-1ubuntu1) over (1.46.6~rc1-1ubuntu1) ... Preparing to unpack .../libext2fs2_1.47.0-1ubuntu1_amd64.deb ... Unpacking libext2fs2:amd64 (1.47.0-1ubuntu1) over (1.46.6~rc1-1ubuntu1) ... Setting up libext2fs2:amd64 (1.47.0-1ubuntu1) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../e2fsprogs_1.47.0-1ubuntu1_amd64.deb ... Unpacking e2fsprogs (1.47.0-1ubuntu1) over (1.46.6~rc1-1ubuntu1) ... Preparing to unpack .../libattr1_1%3a2.5.1-4_amd64.deb ... Unpacking libattr1:amd64 (1:2.5.1-4) over (1:2.5.1-3) ... Setting up libattr1:amd64 (1:2.5.1-4) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libdebconfclient0_0.267ubuntu1_amd64.deb ... Unpacking libdebconfclient0:amd64 (0.267ubuntu1) over (0.264ubuntu1) ... Setting up libdebconfclient0:amd64 (0.267ubuntu1) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libmd0_1.1.0-1_amd64.deb ... Unpacking libmd0:amd64 (1.1.0-1) over (1.0.4-2) ... Setting up libmd0:amd64 (1.1.0-1) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libpam-runtime_1.5.2-6ubuntu1_all.deb ... Unpacking libpam-runtime (1.5.2-6ubuntu1) over (1.5.2-5ubuntu1) ... Setting up libpam-runtime (1.5.2-6ubuntu1) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libsemanage-common_3.4-1build4_all.deb ... Unpacking libsemanage-common (3.4-1build4) over (3.4-1build1) ... Setting up libsemanage-common (3.4-1build4) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libsepol2_3.4-2.1_amd64.deb ... Unpacking libsepol2:amd64 (3.4-2.1) over (3.4-2) ... Setting up libsepol2:amd64 (3.4-2.1) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libsemanage2_3.4-1build4_amd64.deb ... Unpacking libsemanage2:amd64 (3.4-1build4) over (3.4-1build1) ... Setting up libsemanage2:amd64 (3.4-1build4) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../libncurses6_6.4-4_amd64.deb ... Unpacking libncurses6:amd64 (6.4-4) over (6.3+20220423-2) ... Preparing to unpack .../libncursesw6_6.4-4_amd64.deb ... Unpacking libncursesw6:amd64 (6.4-4) over (6.3+20220423-2) ... Preparing to unpack .../libtinfo6_6.4-4_amd64.deb ... Unpacking libtinfo6:amd64 (6.4-4) over (6.3+20220423-2) ... Setting up libtinfo6:amd64 (6.4-4) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../usrmerge_35ubuntu1_all.deb ... Unpacking usrmerge (35ubuntu1) over (33ubuntu1) ... Setting up usrmerge (35ubuntu1) ... (Reading database ... 13106 files and directories currently installed.) Preparing to unpack .../00-libcom-err2_1.47.0-1ubuntu1_amd64.deb ... Unpacking libcom-err2:amd64 (1.47.0-1ubuntu1) over (1.46.6~rc1-1ubuntu1) ... Selecting previously unselected package libproc2-0:amd64. Preparing to unpack .../01-libproc2-0_2%3a4.0.3-1ubuntu1_amd64.deb ... Unpacking libproc2-0:amd64 (2:4.0.3-1ubuntu1) ... Preparing to unpack .../02-libss2_1.47.0-1ubuntu1_amd64.deb ... Unpacking libss2:amd64 (1.47.0-1ubuntu1) over (1.46.6~rc1-1ubuntu1) ... Preparing to unpack .../03-mawk_1.3.4.20230525-1_amd64.deb ... Unpacking mawk (1.3.4.20230525-1) over (1.3.4.20200120-3.1) ... Preparing to unpack .../04-procps_2%3a4.0.3-1ubuntu1_amd64.deb ... Unpacking procps (2:4.0.3-1ubuntu1) over (2:3.3.17-7ubuntu1) ... Preparing to unpack .../05-sensible-utils_0.0.20_all.deb ... Unpacking sensible-utils (0.0.20) over (0.0.17) ... Preparing to unpack .../06-openssl_3.0.9-1ubuntu1_amd64.deb ... Unpacking openssl (3.0.9-1ubuntu1) over (3.0.5-2ubuntu2) ... Preparing to unpack .../07-ca-certificates_20230311ubuntu1_all.deb ... Unpacking ca-certificates (20230311ubuntu1) over (20211016ubuntu1) ... Preparing to unpack .../08-libgssapi-krb5-2_1.20.1-2_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.20.1-2) over (1.20.1-1build1) ... Preparing to unpack .../09-libkrb5-3_1.20.1-2_amd64.deb ... Unpacking libkrb5-3:amd64 (1.20.1-2) over (1.20.1-1build1) ... Preparing to unpack .../10-libkrb5support0_1.20.1-2_amd64.deb ... Unpacking libkrb5support0:amd64 (1.20.1-2) over (1.20.1-1build1) ... Preparing to unpack .../11-libk5crypto3_1.20.1-2_amd64.deb ... Unpacking libk5crypto3:amd64 (1.20.1-2) over (1.20.1-1build1) ... Preparing to unpack .../12-readline-common_8.2-1.3_all.deb ... Unpacking readline-common (8.2-1.3) over (8.2-1.2) ... Preparing to unpack .../13-libreadline8_8.2-1.3_amd64.deb ... Unpacking libreadline8:amd64 (8.2-1.3) over (8.2-1.2) ... Preparing to unpack .../14-libsqlite3-0_3.42.0-1_amd64.deb ... Unpacking libsqlite3-0:amd64 (3.42.0-1) over (3.40.0-1) ... Preparing to unpack .../15-tzdata_2023c-4exp1ubuntu1_all.deb ... Unpacking tzdata (2023c-4exp1ubuntu1) over (2022g-1ubuntu1) ... Preparing to unpack .../16-libpng16-16_1.6.40-1_amd64.deb ... Unpacking libpng16-16:amd64 (1.6.40-1) over (1.6.39-2) ... Preparing to unpack .../17-xz-utils_5.4.1-0.2_amd64.deb ... Unpacking xz-utils (5.4.1-0.2) over (5.2.9-0.0) ... Preparing to unpack .../18-advancecomp_2.5-1_amd64.deb ... Unpacking advancecomp (2.5-1) over (2.4-1) ... Preparing to unpack .../19-libgprofng0_2.40.50.20230622-1ubuntu1_amd64.deb ... Unpacking libgprofng0:amd64 (2.40.50.20230622-1ubuntu1) over (2.39.50.20221224-1ubuntu1) ... Preparing to unpack .../20-libctf0_2.40.50.20230622-1ubuntu1_amd64.deb ... Unpacking libctf0:amd64 (2.40.50.20230622-1ubuntu1) over (2.39.50.20221224-1ubuntu1) ... Preparing to unpack .../21-libctf-nobfd0_2.40.50.20230622-1ubuntu1_amd64.deb ... Unpacking libctf-nobfd0:amd64 (2.40.50.20230622-1ubuntu1) over (2.39.50.20221224-1ubuntu1) ... Preparing to unpack .../22-binutils-x86-64-linux-gnu_2.40.50.20230622-1ubuntu1_amd64.deb ... Unpacking binutils-x86-64-linux-gnu (2.40.50.20230622-1ubuntu1) over (2.39.50.20221224-1ubuntu1) ... Preparing to unpack .../23-libbinutils_2.40.50.20230622-1ubuntu1_amd64.deb ... Unpacking libbinutils:amd64 (2.40.50.20230622-1ubuntu1) over (2.39.50.20221224-1ubuntu1) ... Preparing to unpack .../24-binutils_2.40.50.20230622-1ubuntu1_amd64.deb ... Unpacking binutils (2.40.50.20230622-1ubuntu1) over (2.39.50.20221224-1ubuntu1) ... Preparing to unpack .../25-binutils-common_2.40.50.20230622-1ubuntu1_amd64.deb ... Unpacking binutils-common:amd64 (2.40.50.20230622-1ubuntu1) over (2.39.50.20221224-1ubuntu1) ... Preparing to unpack .../26-libisl23_0.26-3_amd64.deb ... Unpacking libisl23:amd64 (0.26-3) over (0.25-1) ... Preparing to unpack .../27-libmpfr6_4.2.0-1_amd64.deb ... Unpacking libmpfr6:amd64 (4.2.0-1) over (4.1.0-3build3) ... Preparing to unpack .../28-g++-12_12.3.0-3ubuntu1_amd64.deb ... Unpacking g++-12 (12.3.0-3ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../29-gcc-12_12.3.0-3ubuntu1_amd64.deb ... Unpacking gcc-12 (12.3.0-3ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../30-cpp-12_12.3.0-3ubuntu1_amd64.deb ... Unpacking cpp-12 (12.3.0-3ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../31-libubsan1_13.1.0-6ubuntu1_amd64.deb ... Unpacking libubsan1:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../32-libstdc++-12-dev_12.3.0-3ubuntu1_amd64.deb ... Unpacking libstdc++-12-dev:amd64 (12.3.0-3ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../33-libgomp1_13.1.0-6ubuntu1_amd64.deb ... Unpacking libgomp1:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../34-libitm1_13.1.0-6ubuntu1_amd64.deb ... Unpacking libitm1:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../35-libatomic1_13.1.0-6ubuntu1_amd64.deb ... Unpacking libatomic1:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../36-libasan8_13.1.0-6ubuntu1_amd64.deb ... Unpacking libasan8:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../37-liblsan0_13.1.0-6ubuntu1_amd64.deb ... Unpacking liblsan0:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../38-libquadmath0_13.1.0-6ubuntu1_amd64.deb ... Unpacking libquadmath0:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../39-libgcc-12-dev_12.3.0-3ubuntu1_amd64.deb ... Unpacking libgcc-12-dev:amd64 (12.3.0-3ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../40-libtsan2_13.1.0-6ubuntu1_amd64.deb ... Unpacking libtsan2:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../41-libcc1-0_13.1.0-6ubuntu1_amd64.deb ... Unpacking libcc1-0:amd64 (13.1.0-6ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../42-gcc-12-base_12.3.0-3ubuntu1_amd64.deb ... Unpacking gcc-12-base:amd64 (12.3.0-3ubuntu1) over (12.2.0-10ubuntu1) ... Preparing to unpack .../43-g++_4%3a12.2.0-3ubuntu1_amd64.deb ... Unpacking g++ (4:12.2.0-3ubuntu1) over (4:12.2.0-1ubuntu1) ... Preparing to unpack .../44-gcc_4%3a12.2.0-3ubuntu1_amd64.deb ... Unpacking gcc (4:12.2.0-3ubuntu1) over (4:12.2.0-1ubuntu1) ... Preparing to unpack .../45-cpp_4%3a12.2.0-3ubuntu1_amd64.deb ... Unpacking cpp (4:12.2.0-3ubuntu1) over (4:12.2.0-1ubuntu1) ... Preparing to unpack .../46-dpkg-dev_1.21.22ubuntu1_all.deb ... Unpacking dpkg-dev (1.21.22ubuntu1) over (1.21.11ubuntu2) ... Preparing to unpack .../47-libdpkg-perl_1.21.22ubuntu1_all.deb ... Unpacking libdpkg-perl (1.21.22ubuntu1) over (1.21.11ubuntu2) ... Preparing to unpack .../48-lto-disabled-list_41_all.deb ... Unpacking lto-disabled-list (41) over (37) ... Preparing to unpack .../49-libfakeroot_1.31-1.2_amd64.deb ... Unpacking libfakeroot:amd64 (1.31-1.2) over (1.30.1-1ubuntu1) ... Preparing to unpack .../50-fakeroot_1.31-1.2_amd64.deb ... Unpacking fakeroot (1.31-1.2) over (1.30.1-1ubuntu1) ... Preparing to unpack .../51-gpg_2.2.40-1.1ubuntu1_amd64.deb ... Unpacking gpg (2.2.40-1.1ubuntu1) over (2.2.40-1ubuntu1) ... Preparing to unpack .../52-gpgconf_2.2.40-1.1ubuntu1_amd64.deb ... Unpacking gpgconf (2.2.40-1.1ubuntu1) over (2.2.40-1ubuntu1) ... Preparing to unpack .../53-gpg-agent_2.2.40-1.1ubuntu1_amd64.deb ... Unpacking gpg-agent (2.2.40-1.1ubuntu1) over (2.2.40-1ubuntu1) ... Preparing to unpack .../54-pkgbinarymangler_153_all.deb ... Unpacking pkgbinarymangler (153) over (149) ... Setting up lsb-base (11.6) ... Setting up lto-disabled-list (41) ... Setting up libapparmor1:amd64 (3.0.8-1ubuntu3) ... Setting up libargon2-1:amd64 (0~20190702+dfsg-3) ... Setting up libsqlite3-0:amd64 (3.42.0-1) ... Setting up binutils-common:amd64 (2.40.50.20230622-1ubuntu1) ... Installing new version of config file /etc/gprofng.rc ... Setting up linux-libc-dev:amd64 (6.3.0-7.7) ... Setting up libctf-nobfd0:amd64 (2.40.50.20230622-1ubuntu1) ... Setting up libcom-err2:amd64 (1.47.0-1ubuntu1) ... Setting up libgomp1:amd64 (13.1.0-6ubuntu1) ... Setting up libfakeroot:amd64 (1.31-1.2) ... Setting up libkrb5support0:amd64 (1.20.1-2) ... Setting up gcc-12-base:amd64 (12.3.0-3ubuntu1) ... Setting up tzdata (2023c-4exp1ubuntu1) ... Current default time zone: 'Etc/UTC' Local time is now: Wed Jun 28 11:31:13 UTC 2023. Universal Time is now: Wed Jun 28 11:31:13 UTC 2023. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up fakeroot (1.31-1.2) ... Setting up perl-modules-5.36 (5.36.0-7ubuntu1) ... Setting up libmpfr6:amd64 (4.2.0-1) ... Setting up libncurses6:amd64 (6.4-4) ... Setting up xz-utils (5.4.1-0.2) ... Setting up libquadmath0:amd64 (13.1.0-6ubuntu1) ... Setting up libproc2-0:amd64 (2:4.0.3-1ubuntu1) ... Setting up libpng16-16:amd64 (1.6.40-1) ... Setting up libatomic1:amd64 (13.1.0-6ubuntu1) ... Setting up libss2:amd64 (1.47.0-1ubuntu1) ... Setting up libncursesw6:amd64 (6.4-4) ... Setting up libk5crypto3:amd64 (1.20.1-2) ... Setting up logsave (1.47.0-1ubuntu1) ... Setting up libfdisk1:amd64 (2.38.1-5ubuntu2) ... Setting up libubsan1:amd64 (13.1.0-6ubuntu1) ... Setting up advancecomp (2.5-1) ... Setting up libdevmapper1.02.1:amd64 (2:1.02.185-2ubuntu1) ... Setting up mount (2.38.1-5ubuntu2) ... Setting up sensible-utils (0.0.20) ... Setting up libcrypt-dev:amd64 (1:4.4.35-1) ... Setting up libasan8:amd64 (13.1.0-6ubuntu1) ... Setting up procps (2:4.0.3-1ubuntu1) ... Setting up libcryptsetup12:amd64 (2:2.6.1-4ubuntu1) ... Setting up mawk (1.3.4.20230525-1) ... Setting up libkrb5-3:amd64 (1.20.1-2) ... Setting up libtsan2:amd64 (13.1.0-6ubuntu1) ... Setting up libbinutils:amd64 (2.40.50.20230622-1ubuntu1) ... Setting up libisl23:amd64 (0.26-3) ... Setting up libc-dev-bin (2.37-0ubuntu2) ... Setting up openssl (3.0.9-1ubuntu1) ... Installing new version of config file /etc/ssl/openssl.cnf ... Setting up readline-common (8.2-1.3) ... Setting up libcc1-0:amd64 (13.1.0-6ubuntu1) ... Setting up libperl5.36:amd64 (5.36.0-7ubuntu1) ... Setting up liblsan0:amd64 (13.1.0-6ubuntu1) ... Setting up libitm1:amd64 (13.1.0-6ubuntu1) ... Setting up libkmod2:amd64 (30+20221128-1ubuntu1) ... Setting up libctf0:amd64 (2.40.50.20230622-1ubuntu1) ... Setting up cpp-12 (12.3.0-3ubuntu1) ... Setting up pkgbinarymangler (153) ... Setting up libreadline8:amd64 (8.2-1.3) ... Setting up e2fsprogs (1.47.0-1ubuntu1) ... Installing new version of config file /etc/mke2fs.conf ... Setting up ca-certificates (20230311ubuntu1) ... Updating certificates in /etc/ssl/certs... rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL 19 added, 6 removed; done. Setting up perl (5.36.0-7ubuntu1) ... Setting up libgprofng0:amd64 (2.40.50.20230622-1ubuntu1) ... Setting up libgcc-12-dev:amd64 (12.3.0-3ubuntu1) ... Setting up libgssapi-krb5-2:amd64 (1.20.1-2) ... Setting up libsystemd-shared:amd64 (252.5-2ubuntu3) ... Setting up libdpkg-perl (1.21.22ubuntu1) ... Setting up cpp (4:12.2.0-3ubuntu1) ... Setting up gpgconf (2.2.40-1.1ubuntu1) ... Setting up libc6-dev:amd64 (2.37-0ubuntu2) ... Setting up gpg (2.2.40-1.1ubuntu1) ... Setting up binutils-x86-64-linux-gnu (2.40.50.20230622-1ubuntu1) ... Setting up gpg-agent (2.2.40-1.1ubuntu1) ... Setting up libstdc++-12-dev:amd64 (12.3.0-3ubuntu1) ... Setting up systemd (252.5-2ubuntu3) ... Installing new version of config file /etc/systemd/logind.conf ... Installing new version of config file /etc/systemd/system.conf ... Installing new version of config file /etc/systemd/user.conf ... Initializing machine ID from random generator. Setting up binutils (2.40.50.20230622-1ubuntu1) ... Setting up dpkg-dev (1.21.22ubuntu1) ... Setting up gcc-12 (12.3.0-3ubuntu1) ... Setting up g++-12 (12.3.0-3ubuntu1) ... Setting up systemd-sysv (252.5-2ubuntu3) ... Setting up gcc (4:12.2.0-3ubuntu1) ... Setting up g++ (4:12.2.0-3ubuntu1) ... Processing triggers for libc-bin (2.37-0ubuntu2) ... Processing triggers for debianutils (5.7-0.4) ... Processing triggers for ca-certificates (20230311ubuntu1) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. RUN: /usr/share/launchpad-buildd/bin/sbuild-package PACKAGEBUILD-26344941 amd64 mantic-proposed -c chroot:build-PACKAGEBUILD-26344941 --arch=amd64 --dist=mantic-proposed --nolog -A python-django_3.2.19-1ubuntu3.dsc Initiating build PACKAGEBUILD-26344941 with 4 jobs across 4 processor cores. Kernel reported to sbuild: 5.4.0-152-generic #169-Ubuntu SMP Tue Jun 6 22:23:09 UTC 2023 x86_64 sbuild (Debian sbuild) 0.79.0 (05 February 2020) on lcy02-amd64-004.buildd +==============================================================================+ | python-django 3:3.2.19-1ubuntu3 (amd64) Wed, 28 Jun 2023 11:31:16 +0000 | +==============================================================================+ Package: python-django Version: 3:3.2.19-1ubuntu3 Source Version: 3:3.2.19-1ubuntu3 Distribution: mantic-proposed Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'home/buildd/build-PACKAGEBUILD-26344941/chroot-autobuild' with '<>' I: NOTICE: Log filtering will replace 'build/python-django-mX9le4/resolver-RMcKq1' with '<>' +------------------------------------------------------------------------------+ | Fetch source files | +------------------------------------------------------------------------------+ Local sources ------------- python-django_3.2.19-1ubuntu3.dsc exists in .; copying to chroot I: NOTICE: Log filtering will replace 'build/python-django-mX9le4/python-django-3.2.19' with '<>' I: NOTICE: Log filtering will replace 'build/python-django-mX9le4' with '<>' +------------------------------------------------------------------------------+ | Install package build dependencies | +------------------------------------------------------------------------------+ Setup apt archive ----------------- Merged Build-Depends: debhelper-compat (= 13), dh-python, dpkg-dev (>= 1.17.14), libgdal-dev, libsqlite3-mod-spatialite, python-django-formtools-doc, python-psycopg2-doc, python3-all, python3-asgiref, python3-bcrypt, python3-doc, python3-docutils, python3-jinja2, python3-mock, python3-numpy, python3-pil, python3-selenium, python3-setuptools, python3-sphinx, python3-sqlparse, python3-tblib, python3-tz, python3-yaml, sphinx-doc, build-essential, fakeroot, libjs-jquery Filtered Build-Depends: debhelper-compat (= 13), dh-python, dpkg-dev (>= 1.17.14), libgdal-dev, libsqlite3-mod-spatialite, python-django-formtools-doc, python-psycopg2-doc, python3-all, python3-asgiref, python3-bcrypt, python3-doc, python3-docutils, python3-jinja2, python3-mock, python3-numpy, python3-pil, python3-selenium, python3-setuptools, python3-sphinx, python3-sqlparse, python3-tblib, python3-tz, python3-yaml, sphinx-doc, build-essential, fakeroot, libjs-jquery dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. Ign:1 copy:/<>/apt_archive ./ InRelease Get:2 copy:/<>/apt_archive ./ Release [963 B] Ign:3 copy:/<>/apt_archive ./ Release.gpg Get:4 copy:/<>/apt_archive ./ Sources [568 B] Get:5 copy:/<>/apt_archive ./ Packages [620 B] Fetched 2151 B in 0s (0 B/s) Reading package lists... Reading package lists... Install main build dependencies (apt-based resolver) ---------------------------------------------------- Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: autoconf automake autopoint autotools-dev bsdextrautils debhelper debugedit default-libmysqlclient-dev dh-autoreconf dh-python dh-strip-nondeterminism docutils-common docutils-doc dwz file fontconfig-config fonts-dejavu-core fonts-mathjax gdal-data gdal-plugins gettext gettext-base groff-base hdf5-helpers icu-devtools intltool-debian libaec-dev libaec0 libaom-dev libaom3 libarchive-zip-perl libarmadillo-dev libarmadillo11 libarpack2 libarpack2-dev libblas-dev libblas3 libblosc-dev libblosc1 libboost-dev libboost1.74-dev libbrotli1 libbsd0 libcfitsio-dev libcfitsio10 libcurl3-gnutls libcurl4 libcurl4-openssl-dev libdav1d-dev libdav1d6 libde265-0 libde265-dev libdebhelper-perl libdeflate-dev libdeflate0 libdw1 libelf1 libexpat1 libexpat1-dev libfile-stripnondeterminism-perl libfontconfig1 libfreetype6 libfreexl-dev libfreexl1 libfribidi0 libfyba-dev libfyba0 libgdal-dev libgdal33 libgeos-c1v5 libgeos-dev libgeos3.12.0 libgeotiff-dev libgeotiff5 libgfortran5 libgif-dev libgif7 libglib2.0-0 libgraphite2-3 libharfbuzz0b libhdf4-0-alt libhdf4-alt-dev libhdf5-103-1 libhdf5-cpp-103-1 libhdf5-dev libhdf5-fortran-102 libhdf5-hl-100 libhdf5-hl-cpp-100 libhdf5-hl-fortran-100 libheif-dev libheif1 libicu-dev libicu72 libimagequant0 libjbig-dev libjbig0 libjpeg-dev libjpeg-turbo8 libjpeg-turbo8-dev libjpeg8 libjpeg8-dev libjs-jquery libjs-mathjax libjs-sphinxdoc libjs-underscore libjson-c-dev libjson-perl libkml-dev libkmlbase1 libkmlconvenience1 libkmldom1 libkmlengine1 libkmlregionator1 libkmlxsd1 liblapack-dev liblapack3 liblcms2-2 libldap2 liblerc-dev liblerc4 libltdl-dev libltdl7 liblz4-dev liblzma-dev libmagic-mgc libmagic1 libminizip-dev libminizip1 libmysqlclient-dev libmysqlclient21 libnetcdf-dev libnetcdf19 libnghttp2-14 libnspr4 libnss3 libnuma1 libodbc2 libodbccr2 libodbcinst2 libogdi-dev libogdi4.1 libopenjp2-7 libopenjp2-7-dev libpcre2-16-0 libpcre2-32-0 libpcre2-dev libpcre2-posix3 libpipeline1 libpng-dev libpoppler-dev libpoppler-private-dev libpoppler126 libpq-dev libpq5 libproj-dev libproj25 libpsl5 libpython3-stdlib libpython3.11-minimal libpython3.11-stdlib libqhull-dev libqhull-r8.0 libqhull8.0 libqhullcpp8.0 libraqm0 librtmp1 librttopo-dev librttopo1 libsasl2-2 libsasl2-modules-db libsnappy1v5 libspatialite-dev libspatialite7 libsqlite3-dev libsqlite3-mod-spatialite libssh-4 libssl-dev libsub-override-perl libsuperlu-dev libsuperlu5 libsz2 libtiff-dev libtiff6 libtiffxx6 libtool libuchardet0 liburiparser-dev liburiparser1 libwebp-dev libwebp7 libwebpdemux2 libwebpmux3 libx265-199 libx265-dev libxau6 libxcb1 libxdmcp6 libxerces-c-dev libxerces-c3.2 libxml2 libxml2-dev libyaml-0-2 libzstd-dev m4 mailcap man-db media-types mime-support mysql-common po-debconf proj-data python-babel-localedata python-django-formtools-doc python-psycopg2-doc python-requests-doc python3 python3-alabaster python3-all python3-asgiref python3-async-generator python3-attr python3-babel python3-bcrypt python3-certifi python3-cffi-backend python3-chardet python3-distutils python3-doc python3-docutils python3-exceptiongroup python3-h11 python3-idna python3-imagesize python3-jinja2 python3-lib2to3 python3-markupsafe python3-minimal python3-mock python3-numpy python3-outcome python3-packaging python3-pbr python3-pil python3-pkg-resources python3-pygments python3-requests python3-roman python3-selenium python3-setuptools python3-six python3-sniffio python3-snowballstemmer python3-sortedcontainers python3-sphinx python3-sqlparse python3-tblib python3-trio python3-trio-websocket python3-tz python3-urllib3 python3-wsproto python3-yaml python3.11 python3.11-doc python3.11-minimal sgml-base sphinx-common sphinx-doc unixodbc-common unixodbc-dev xml-core zlib1g-dev Suggested packages: autoconf-archive gnu-standards autoconf-doc dh-make flit python3-build python3-installer python3-wheel gettext-doc libasprintf-dev libgettextpo-dev groff libitpp-dev liblapack-doc libboost-doc libboost1.74-doc libboost-atomic1.74-dev libboost-chrono1.74-dev libboost-container1.74-dev libboost-context1.74-dev libboost-contract1.74-dev libboost-coroutine1.74-dev libboost-date-time1.74-dev libboost-exception1.74-dev libboost-fiber1.74-dev libboost-filesystem1.74-dev libboost-graph1.74-dev libboost-graph-parallel1.74-dev libboost-iostreams1.74-dev libboost-locale1.74-dev libboost-log1.74-dev libboost-math1.74-dev libboost-mpi1.74-dev libboost-mpi-python1.74-dev libboost-numpy1.74-dev libboost-program-options1.74-dev libboost-python1.74-dev libboost-random1.74-dev libboost-regex1.74-dev libboost-serialization1.74-dev libboost-stacktrace1.74-dev libboost-system1.74-dev libboost-test1.74-dev libboost-thread1.74-dev libboost-timer1.74-dev libboost-type-erasure1.74-dev libboost-wave1.74-dev libboost1.74-tools-dev libmpfrc++-dev libntl-dev libboost-nowide1.74-dev libcurl4-doc libidn-dev libkrb5-dev libldap2-dev librtmp-dev libssh2-1-dev pkg-config libgdal-doc libgeotiff-epsg geotiff-bin gdal-bin low-memory-monitor libhdf4-doc hdf4-tools libhdf5-doc icu-doc fonts-mathjax-extras fonts-stix libjs-mathjax-doc liblcms2-utils libtool-doc liblzma-doc netcdf-bin netcdf-doc odbc-postgresql tdsodbc ogdi-bin libfreetype6-dev postgresql-doc-15 proj-bin sqlite3-doc libssl-doc libsuperlu-doc gfortran | fortran95-compiler gcj-jdk libx265-doc libxerces-c-doc m4-doc apparmor less www-browser libmail-box-perl python3-psycopg2 python3-tk python3-venv python-attr-doc python3-examples fonts-linuxlibertine | ttf-linux-libertine texlive-lang-french texlive-latex-base texlive-latex-recommended python-jinja2-doc python-mock-doc gfortran python3-dev python3-pytest python-pil-doc python-pygments-doc ttf-bitstream-vera python3-cryptography python3-openssl python3-socks python-setuptools-doc python3-stemmer python-sortedcontainers-doc dvipng fonts-freefont-otf imagemagick-6.q16 latexmk python3-sphinx-rtd-theme tex-gyre texlive-fonts-recommended texlive-latex-extra texlive-plain-generic python-sqlparse-doc python3-brotli python3.11-venv binfmt-support sgml-base-doc Recommended packages: curl | wget | lynx libcfitsio-doc libarchive-cpio-perl proj-bin libglib2.0-data shared-mime-info xdg-user-dirs javascript-common libjson-xs-perl libldap-common pkg-config libpng-tools poppler-data publicsuffix libsasl2-modules libmail-sendmail-perl libpaper-utils python3-olefile chromium-driver The following NEW packages will be installed: autoconf automake autopoint autotools-dev bsdextrautils debhelper debugedit default-libmysqlclient-dev dh-autoreconf dh-python dh-strip-nondeterminism docutils-common docutils-doc dwz file fontconfig-config fonts-dejavu-core fonts-mathjax gdal-data gdal-plugins gettext gettext-base groff-base hdf5-helpers icu-devtools intltool-debian libaec-dev libaec0 libaom-dev libaom3 libarchive-zip-perl libarmadillo-dev libarmadillo11 libarpack2 libarpack2-dev libblas-dev libblas3 libblosc-dev libblosc1 libboost-dev libboost1.74-dev libbrotli1 libbsd0 libcfitsio-dev libcfitsio10 libcurl3-gnutls libcurl4 libcurl4-openssl-dev libdav1d-dev libdav1d6 libde265-0 libde265-dev libdebhelper-perl libdeflate-dev libdeflate0 libdw1 libelf1 libexpat1 libexpat1-dev libfile-stripnondeterminism-perl libfontconfig1 libfreetype6 libfreexl-dev libfreexl1 libfribidi0 libfyba-dev libfyba0 libgdal-dev libgdal33 libgeos-c1v5 libgeos-dev libgeos3.12.0 libgeotiff-dev libgeotiff5 libgfortran5 libgif-dev libgif7 libglib2.0-0 libgraphite2-3 libharfbuzz0b libhdf4-0-alt libhdf4-alt-dev libhdf5-103-1 libhdf5-cpp-103-1 libhdf5-dev libhdf5-fortran-102 libhdf5-hl-100 libhdf5-hl-cpp-100 libhdf5-hl-fortran-100 libheif-dev libheif1 libicu-dev libicu72 libimagequant0 libjbig-dev libjbig0 libjpeg-dev libjpeg-turbo8 libjpeg-turbo8-dev libjpeg8 libjpeg8-dev libjs-jquery libjs-mathjax libjs-sphinxdoc libjs-underscore libjson-c-dev libjson-perl libkml-dev libkmlbase1 libkmlconvenience1 libkmldom1 libkmlengine1 libkmlregionator1 libkmlxsd1 liblapack-dev liblapack3 liblcms2-2 libldap2 liblerc-dev liblerc4 libltdl-dev libltdl7 liblz4-dev liblzma-dev libmagic-mgc libmagic1 libminizip-dev libminizip1 libmysqlclient-dev libmysqlclient21 libnetcdf-dev libnetcdf19 libnghttp2-14 libnspr4 libnss3 libnuma1 libodbc2 libodbccr2 libodbcinst2 libogdi-dev libogdi4.1 libopenjp2-7 libopenjp2-7-dev libpcre2-16-0 libpcre2-32-0 libpcre2-dev libpcre2-posix3 libpipeline1 libpng-dev libpoppler-dev libpoppler-private-dev libpoppler126 libpq-dev libpq5 libproj-dev libproj25 libpsl5 libpython3-stdlib libpython3.11-minimal libpython3.11-stdlib libqhull-dev libqhull-r8.0 libqhull8.0 libqhullcpp8.0 libraqm0 librtmp1 librttopo-dev librttopo1 libsasl2-2 libsasl2-modules-db libsnappy1v5 libspatialite-dev libspatialite7 libsqlite3-dev libsqlite3-mod-spatialite libssh-4 libssl-dev libsub-override-perl libsuperlu-dev libsuperlu5 libsz2 libtiff-dev libtiff6 libtiffxx6 libtool libuchardet0 liburiparser-dev liburiparser1 libwebp-dev libwebp7 libwebpdemux2 libwebpmux3 libx265-199 libx265-dev libxau6 libxcb1 libxdmcp6 libxerces-c-dev libxerces-c3.2 libxml2 libxml2-dev libyaml-0-2 libzstd-dev m4 mailcap man-db media-types mime-support mysql-common po-debconf proj-data python-babel-localedata python-django-formtools-doc python-psycopg2-doc python-requests-doc python3 python3-alabaster python3-all python3-asgiref python3-async-generator python3-attr python3-babel python3-bcrypt python3-certifi python3-cffi-backend python3-chardet python3-distutils python3-doc python3-docutils python3-exceptiongroup python3-h11 python3-idna python3-imagesize python3-jinja2 python3-lib2to3 python3-markupsafe python3-minimal python3-mock python3-numpy python3-outcome python3-packaging python3-pbr python3-pil python3-pkg-resources python3-pygments python3-requests python3-roman python3-selenium python3-setuptools python3-six python3-sniffio python3-snowballstemmer python3-sortedcontainers python3-sphinx python3-sqlparse python3-tblib python3-trio python3-trio-websocket python3-tz python3-urllib3 python3-wsproto python3-yaml python3.11 python3.11-doc python3.11-minimal sbuild-build-depends-main-dummy sgml-base sphinx-common sphinx-doc unixodbc-common unixodbc-dev xml-core zlib1g-dev 0 upgraded, 273 newly installed, 0 to remove and 0 not upgraded. Need to get 166 MB of archives. After this operation, 859 MB of additional disk space will be used. Get:1 copy:/<>/apt_archive ./ sbuild-build-depends-main-dummy 0.invalid.0 [842 B] Get:2 http://ftpmaster.internal/ubuntu mantic/main amd64 libpython3.11-minimal amd64 3.11.4-1 [839 kB] Get:3 http://ftpmaster.internal/ubuntu mantic/main amd64 libexpat1 amd64 2.5.0-2 [85.2 kB] Get:4 http://ftpmaster.internal/ubuntu mantic/main amd64 python3.11-minimal amd64 3.11.4-1 [2228 kB] Get:5 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 python3-minimal amd64 3.11.4-1 [26.6 kB] Get:6 http://ftpmaster.internal/ubuntu mantic/main amd64 media-types all 10.0.0 [25.8 kB] Get:7 http://ftpmaster.internal/ubuntu mantic/main amd64 mailcap all 3.70+nmu1ubuntu1 [23.8 kB] Get:8 http://ftpmaster.internal/ubuntu mantic/main amd64 mime-support all 3.66 [3696 B] Get:9 http://ftpmaster.internal/ubuntu mantic/main amd64 libpython3.11-stdlib amd64 3.11.4-1 [1908 kB] Get:10 http://ftpmaster.internal/ubuntu mantic/main amd64 python3.11 amd64 3.11.4-1 [572 kB] Get:11 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 libpython3-stdlib amd64 3.11.4-1 [9326 B] Get:12 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 python3 amd64 3.11.4-1 [22.9 kB] Get:13 http://ftpmaster.internal/ubuntu mantic/main amd64 sgml-base all 1.31 [11.4 kB] Get:14 http://ftpmaster.internal/ubuntu mantic/main amd64 libbsd0 amd64 0.11.7-4 [41.4 kB] Get:15 http://ftpmaster.internal/ubuntu mantic/main amd64 libelf1 amd64 0.188-2.1 [53.4 kB] Get:16 http://ftpmaster.internal/ubuntu mantic/main amd64 libfribidi0 amd64 1.0.13-3 [26.1 kB] Get:17 http://ftpmaster.internal/ubuntu mantic/main amd64 libglib2.0-0 amd64 2.76.3-1ubuntu1 [1517 kB] Get:18 http://ftpmaster.internal/ubuntu mantic/main amd64 libicu72 amd64 72.1-3ubuntu2 [10.8 MB] Get:19 http://ftpmaster.internal/ubuntu mantic/main amd64 libxml2 amd64 2.9.14+dfsg-1.2 [764 kB] Get:20 http://ftpmaster.internal/ubuntu mantic/main amd64 libyaml-0-2 amd64 0.2.5-1 [52.8 kB] Get:21 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-pkg-resources all 67.8.0-1 [161 kB] Get:22 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-pygments all 2.15.1+dfsg-1 [820 kB] Get:23 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-yaml amd64 6.0-3build1 [121 kB] Get:24 http://ftpmaster.internal/ubuntu mantic/main amd64 bsdextrautils amd64 2.38.1-5ubuntu2 [71.0 kB] Get:25 http://ftpmaster.internal/ubuntu mantic/main amd64 libmagic-mgc amd64 1:5.44-3 [293 kB] Get:26 http://ftpmaster.internal/ubuntu mantic/main amd64 libmagic1 amd64 1:5.44-3 [85.6 kB] Get:27 http://ftpmaster.internal/ubuntu mantic/main amd64 file amd64 1:5.44-3 [21.8 kB] Get:28 http://ftpmaster.internal/ubuntu mantic/main amd64 gettext-base amd64 0.21-12 [38.0 kB] Get:29 http://ftpmaster.internal/ubuntu mantic/main amd64 libuchardet0 amd64 0.0.7-1build2 [76.9 kB] Get:30 http://ftpmaster.internal/ubuntu mantic/main amd64 groff-base amd64 1.22.4-10 [937 kB] Get:31 http://ftpmaster.internal/ubuntu mantic/main amd64 libnghttp2-14 amd64 1.54.0-1 [72.7 kB] Get:32 http://ftpmaster.internal/ubuntu mantic/main amd64 libnuma1 amd64 2.0.16-1 [22.6 kB] Get:33 http://ftpmaster.internal/ubuntu mantic/main amd64 libpipeline1 amd64 1.5.7-1 [23.3 kB] Get:34 http://ftpmaster.internal/ubuntu mantic/main amd64 libpsl5 amd64 0.21.2-1 [59.0 kB] Get:35 http://ftpmaster.internal/ubuntu mantic/main amd64 libxau6 amd64 1:1.0.9-1build5 [7634 B] Get:36 http://ftpmaster.internal/ubuntu mantic/main amd64 libxdmcp6 amd64 1:1.1.3-0ubuntu5 [10.9 kB] Get:37 http://ftpmaster.internal/ubuntu mantic/main amd64 libxcb1 amd64 1.15-1 [48.0 kB] Get:38 http://ftpmaster.internal/ubuntu mantic/main amd64 man-db amd64 2.11.2-2 [1220 kB] Get:39 http://ftpmaster.internal/ubuntu mantic/main amd64 m4 amd64 1.4.19-3 [243 kB] Get:40 http://ftpmaster.internal/ubuntu mantic/main amd64 autoconf all 2.71-3 [339 kB] Get:41 http://ftpmaster.internal/ubuntu mantic/main amd64 autotools-dev all 20220109.1 [44.9 kB] Get:42 http://ftpmaster.internal/ubuntu mantic/main amd64 automake all 1:1.16.5-1.3 [558 kB] Get:43 http://ftpmaster.internal/ubuntu mantic/main amd64 autopoint all 0.21-12 [422 kB] Get:44 http://ftpmaster.internal/ubuntu mantic/main amd64 libdebhelper-perl all 13.11.4ubuntu3 [66.1 kB] Get:45 http://ftpmaster.internal/ubuntu mantic/main amd64 libtool all 2.4.7-5 [166 kB] Get:46 http://ftpmaster.internal/ubuntu mantic/main amd64 dh-autoreconf all 20 [16.1 kB] Get:47 http://ftpmaster.internal/ubuntu mantic/main amd64 libarchive-zip-perl all 1.68-1 [90.2 kB] Get:48 http://ftpmaster.internal/ubuntu mantic/main amd64 libsub-override-perl all 0.09-4 [8706 B] Get:49 http://ftpmaster.internal/ubuntu mantic/main amd64 libfile-stripnondeterminism-perl all 1.13.1-1 [18.1 kB] Get:50 http://ftpmaster.internal/ubuntu mantic/main amd64 dh-strip-nondeterminism all 1.13.1-1 [5362 B] Get:51 http://ftpmaster.internal/ubuntu mantic/main amd64 libdw1 amd64 0.188-2.1 [251 kB] Get:52 http://ftpmaster.internal/ubuntu mantic/main amd64 debugedit amd64 1:5.0-5 [46.1 kB] Get:53 http://ftpmaster.internal/ubuntu mantic/main amd64 dwz amd64 0.15-1 [112 kB] Get:54 http://ftpmaster.internal/ubuntu mantic/main amd64 gettext amd64 0.21-12 [866 kB] Get:55 http://ftpmaster.internal/ubuntu mantic/main amd64 intltool-debian all 0.35.0+20060710.6 [23.2 kB] Get:56 http://ftpmaster.internal/ubuntu mantic/main amd64 po-debconf all 1.0.21+nmu1 [233 kB] Get:57 http://ftpmaster.internal/ubuntu mantic/main amd64 debhelper all 13.11.4ubuntu3 [925 kB] Get:58 http://ftpmaster.internal/ubuntu mantic/main amd64 mysql-common all 5.8+1.1.0 [6626 B] Get:59 http://ftpmaster.internal/ubuntu mantic/main amd64 libmysqlclient21 amd64 8.0.33-2 [1284 kB] Get:60 http://ftpmaster.internal/ubuntu mantic/main amd64 libssl-dev amd64 3.0.9-1ubuntu1 [2375 kB] Get:61 http://ftpmaster.internal/ubuntu mantic/main amd64 libzstd-dev amd64 1.5.4+dfsg2-5 [361 kB] Get:62 http://ftpmaster.internal/ubuntu mantic/main amd64 zlib1g-dev amd64 1:1.2.13.dfsg-1ubuntu4 [895 kB] Get:63 http://ftpmaster.internal/ubuntu mantic/main amd64 libmysqlclient-dev amd64 8.0.33-2 [1621 kB] Get:64 http://ftpmaster.internal/ubuntu mantic/main amd64 default-libmysqlclient-dev amd64 1.1.0 [3014 B] Get:65 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-lib2to3 all 3.11.4-1 [79.0 kB] Get:66 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-distutils all 3.11.4-1 [131 kB] Get:67 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 dh-python all 6.20230603 [107 kB] Get:68 http://ftpmaster.internal/ubuntu mantic/main amd64 xml-core all 0.18+nmu1 [21.6 kB] Get:69 http://ftpmaster.internal/ubuntu mantic/main amd64 docutils-common all 0.19+dfsg-6 [129 kB] Get:70 http://ftpmaster.internal/ubuntu mantic/main amd64 docutils-doc all 0.19+dfsg-6 [1116 kB] Get:71 http://ftpmaster.internal/ubuntu mantic/main amd64 fonts-dejavu-core all 2.37-6 [1137 kB] Get:72 http://ftpmaster.internal/ubuntu mantic/main amd64 fontconfig-config amd64 2.14.1-4ubuntu1 [35.1 kB] Get:73 http://ftpmaster.internal/ubuntu mantic/main amd64 fonts-mathjax all 2.7.9+dfsg-1 [2208 kB] Get:74 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 gdal-data all 3.7.0+dfsg-1 [255 kB] Get:75 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 gdal-plugins amd64 3.7.0+dfsg-1 [23.7 kB] Get:76 http://ftpmaster.internal/ubuntu mantic/universe amd64 hdf5-helpers amd64 1.10.8+repack1-1ubuntu1 [13.9 kB] Get:77 http://ftpmaster.internal/ubuntu mantic/main amd64 icu-devtools amd64 72.1-3ubuntu2 [210 kB] Get:78 http://ftpmaster.internal/ubuntu mantic/universe amd64 libaec0 amd64 1.0.6-1 [20.1 kB] Get:79 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 libaom3 amd64 3.6.1-1 [1917 kB] Get:80 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 libaom-dev amd64 3.6.1-1 [2261 kB] Get:81 http://ftpmaster.internal/ubuntu mantic/main amd64 libblas3 amd64 3.11.0-2 [244 kB] Get:82 http://ftpmaster.internal/ubuntu mantic/main amd64 libgfortran5 amd64 13.1.0-6ubuntu1 [891 kB] Get:83 http://ftpmaster.internal/ubuntu mantic/main amd64 liblapack3 amd64 3.11.0-2 [2659 kB] Get:84 http://ftpmaster.internal/ubuntu mantic/universe amd64 libarpack2 amd64 3.8.0-3 [106 kB] Get:85 http://ftpmaster.internal/ubuntu mantic/universe amd64 libsuperlu5 amd64 5.3.0+dfsg1-2 [183 kB] Get:86 http://ftpmaster.internal/ubuntu mantic/universe amd64 libarmadillo11 amd64 1:11.4.2+dfsg-1 [102 kB] Get:87 http://ftpmaster.internal/ubuntu mantic/main amd64 libblas-dev amd64 3.11.0-2 [170 kB] Get:88 http://ftpmaster.internal/ubuntu mantic/main amd64 liblapack-dev amd64 3.11.0-2 [5073 kB] Get:89 http://ftpmaster.internal/ubuntu mantic/universe amd64 libarpack2-dev amd64 3.8.0-3 [122 kB] Get:90 http://ftpmaster.internal/ubuntu mantic/main amd64 libbrotli1 amd64 1.0.9-2build8 [309 kB] Get:91 http://ftpmaster.internal/ubuntu mantic/main amd64 libsasl2-modules-db amd64 2.1.28+dfsg1-1 [20.0 kB] Get:92 http://ftpmaster.internal/ubuntu mantic/main amd64 libsasl2-2 amd64 2.1.28+dfsg1-1 [55.6 kB] Get:93 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 libldap2 amd64 2.6.4+dfsg-1~exp1ubuntu1 [193 kB] Get:94 http://ftpmaster.internal/ubuntu mantic/main amd64 librtmp1 amd64 2.4+20151223.gitfa8646d.1-2build4 [58.2 kB] Get:95 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 libssh-4 amd64 0.10.5-2 [187 kB] Get:96 http://ftpmaster.internal/ubuntu mantic/main amd64 libcurl4 amd64 7.88.1-10ubuntu1 [307 kB] Get:97 http://ftpmaster.internal/ubuntu mantic/universe amd64 libsz2 amd64 1.0.6-1 [5354 B] Get:98 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf5-103-1 amd64 1.10.8+repack1-1ubuntu1 [1301 kB] Get:99 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf5-fortran-102 amd64 1.10.8+repack1-1ubuntu1 [85.4 kB] Get:100 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf5-hl-100 amd64 1.10.8+repack1-1ubuntu1 [56.0 kB] Get:101 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf5-hl-fortran-100 amd64 1.10.8+repack1-1ubuntu1 [32.0 kB] Get:102 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf5-cpp-103-1 amd64 1.10.8+repack1-1ubuntu1 [122 kB] Get:103 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf5-hl-cpp-100 amd64 1.10.8+repack1-1ubuntu1 [10.8 kB] Get:104 http://ftpmaster.internal/ubuntu mantic/main amd64 libjpeg-turbo8 amd64 2.1.5-2ubuntu1 [147 kB] Get:105 http://ftpmaster.internal/ubuntu mantic/main amd64 libjpeg-turbo8-dev amd64 2.1.5-2ubuntu1 [294 kB] Get:106 http://ftpmaster.internal/ubuntu mantic/main amd64 libjpeg8 amd64 8c-2ubuntu11 [2148 B] Get:107 http://ftpmaster.internal/ubuntu mantic/main amd64 libjpeg8-dev amd64 8c-2ubuntu11 [1484 B] Get:108 http://ftpmaster.internal/ubuntu mantic/main amd64 libjpeg-dev amd64 8c-2ubuntu11 [1482 B] Get:109 http://ftpmaster.internal/ubuntu mantic/universe amd64 libaec-dev amd64 1.0.6-1 [17.9 kB] Get:110 http://ftpmaster.internal/ubuntu mantic/main amd64 libcurl4-openssl-dev amd64 7.88.1-10ubuntu1 [408 kB] Get:111 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf5-dev amd64 1.10.8+repack1-1ubuntu1 [2801 kB] Get:112 http://ftpmaster.internal/ubuntu mantic/universe amd64 libsuperlu-dev amd64 5.3.0+dfsg1-2 [20.0 kB] Get:113 http://ftpmaster.internal/ubuntu mantic/universe amd64 libarmadillo-dev amd64 1:11.4.2+dfsg-1 [403 kB] Get:114 http://ftpmaster.internal/ubuntu mantic/main amd64 libsnappy1v5 amd64 1.1.9-3 [27.9 kB] Get:115 http://ftpmaster.internal/ubuntu mantic/universe amd64 libblosc1 amd64 1.21.3+ds-1 [31.5 kB] Get:116 http://ftpmaster.internal/ubuntu mantic/universe amd64 libblosc-dev amd64 1.21.3+ds-1 [44.0 kB] Get:117 http://ftpmaster.internal/ubuntu mantic/main amd64 libboost1.74-dev amd64 1.74.0+ds1-21.1ubuntu1 [9586 kB] Get:118 http://ftpmaster.internal/ubuntu mantic/main amd64 libboost-dev amd64 1.74.0.3ubuntu7 [3490 B] Get:119 http://ftpmaster.internal/ubuntu mantic/main amd64 libcurl3-gnutls amd64 7.88.1-10ubuntu1 [301 kB] Get:120 http://ftpmaster.internal/ubuntu mantic/universe amd64 libcfitsio10 amd64 4.2.0-3 [529 kB] Get:121 http://ftpmaster.internal/ubuntu mantic/universe amd64 libcfitsio-dev amd64 4.2.0-3 [598 kB] Get:122 http://ftpmaster.internal/ubuntu mantic/universe amd64 libdav1d6 amd64 1.2.1-2 [602 kB] Get:123 http://ftpmaster.internal/ubuntu mantic/universe amd64 libdav1d-dev amd64 1.2.1-2 [25.1 kB] Get:124 http://ftpmaster.internal/ubuntu mantic/universe amd64 libde265-0 amd64 1.0.12-1 [164 kB] Get:125 http://ftpmaster.internal/ubuntu mantic/universe amd64 libde265-dev amd64 1.0.12-1 [12.4 kB] Get:126 http://ftpmaster.internal/ubuntu mantic/main amd64 libdeflate0 amd64 1.15-1 [41.9 kB] Get:127 http://ftpmaster.internal/ubuntu mantic/main amd64 libdeflate-dev amd64 1.15-1 [49.3 kB] Get:128 http://ftpmaster.internal/ubuntu mantic/main amd64 libexpat1-dev amd64 2.5.0-2 [137 kB] Get:129 http://ftpmaster.internal/ubuntu mantic/main amd64 libfreetype6 amd64 2.12.1+dfsg-5 [392 kB] Get:130 http://ftpmaster.internal/ubuntu mantic/main amd64 libfontconfig1 amd64 2.14.1-4ubuntu1 [136 kB] Get:131 http://ftpmaster.internal/ubuntu mantic/universe amd64 libfyba0 amd64 4.1.1-8 [119 kB] Get:132 http://ftpmaster.internal/ubuntu mantic/universe amd64 libfyba-dev amd64 4.1.1-8 [178 kB] Get:133 http://ftpmaster.internal/ubuntu mantic/universe amd64 libfreexl1 amd64 1.0.6-2 [30.8 kB] Get:134 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 libgeos3.12.0 amd64 3.12.0-1 [842 kB] Get:135 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 libgeos-c1v5 amd64 3.12.0-1 [94.0 kB] Get:136 http://ftpmaster.internal/ubuntu mantic/universe amd64 proj-data all 9.2.1-1 [7847 kB] Get:137 http://ftpmaster.internal/ubuntu mantic/main amd64 libjbig0 amd64 2.1-6.1ubuntu1 [29.3 kB] Get:138 http://ftpmaster.internal/ubuntu mantic/main amd64 liblerc4 amd64 4.0.0+ds-2ubuntu2 [185 kB] Get:139 http://ftpmaster.internal/ubuntu mantic/main amd64 libwebp7 amd64 1.2.4-0.2 [212 kB] Get:140 http://ftpmaster.internal/ubuntu mantic/main amd64 libtiff6 amd64 4.5.0-6ubuntu1 [198 kB] Get:141 http://ftpmaster.internal/ubuntu mantic/universe amd64 libproj25 amd64 9.2.1-1 [1351 kB] Get:142 http://ftpmaster.internal/ubuntu mantic/universe amd64 libgeotiff5 amd64 1.7.1-2build1 [62.7 kB] Get:143 http://ftpmaster.internal/ubuntu mantic/main amd64 libgif7 amd64 5.2.1-2.5 [34.0 kB] Get:144 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf4-0-alt amd64 4.2.16-3 [282 kB] Get:145 http://ftpmaster.internal/ubuntu mantic/universe amd64 libx265-199 amd64 3.5-2 [1170 kB] Get:146 http://ftpmaster.internal/ubuntu mantic/universe amd64 libheif1 amd64 1.15.1-1 [220 kB] Get:147 http://ftpmaster.internal/ubuntu mantic/universe amd64 libminizip1 amd64 1.1-8build1 [20.2 kB] Get:148 http://ftpmaster.internal/ubuntu mantic/universe amd64 liburiparser1 amd64 0.9.7+dfsg-2 [35.9 kB] Get:149 http://ftpmaster.internal/ubuntu mantic/universe amd64 libkmlbase1 amd64 1.3.0-10 [47.4 kB] Get:150 http://ftpmaster.internal/ubuntu mantic/universe amd64 libkmldom1 amd64 1.3.0-10 [151 kB] Get:151 http://ftpmaster.internal/ubuntu mantic/universe amd64 libkmlengine1 amd64 1.3.0-10 [69.3 kB] Get:152 http://ftpmaster.internal/ubuntu mantic/universe amd64 libnetcdf19 amd64 1:4.9.2-1 [469 kB] Get:153 http://ftpmaster.internal/ubuntu mantic/main amd64 libltdl7 amd64 2.4.7-5 [40.3 kB] Get:154 http://ftpmaster.internal/ubuntu mantic/main amd64 libodbc2 amd64 2.3.11-4 [159 kB] Get:155 http://ftpmaster.internal/ubuntu mantic/main amd64 unixodbc-common all 2.3.11-4 [8474 B] Get:156 http://ftpmaster.internal/ubuntu mantic/main amd64 libodbcinst2 amd64 2.3.11-4 [30.8 kB] Get:157 http://ftpmaster.internal/ubuntu mantic/universe amd64 libogdi4.1 amd64 4.1.0+ds-6 [228 kB] Get:158 http://ftpmaster.internal/ubuntu mantic/main amd64 libopenjp2-7 amd64 2.5.0-2 [174 kB] Get:159 http://ftpmaster.internal/ubuntu mantic/main amd64 liblcms2-2 amd64 2.14-2 [161 kB] Get:160 http://ftpmaster.internal/ubuntu mantic/main amd64 libnspr4 amd64 2:4.35-1.1 [117 kB] Get:161 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 libnss3 amd64 2:3.90-3 [1395 kB] Get:162 http://ftpmaster.internal/ubuntu mantic/main amd64 libpoppler126 amd64 22.12.0-2ubuntu1 [1100 kB] Get:163 http://ftpmaster.internal/ubuntu mantic/main amd64 libpq5 amd64 15.3-1 [134 kB] Get:164 http://ftpmaster.internal/ubuntu mantic/universe amd64 libqhull-r8.0 amd64 2020.2-5 [194 kB] Get:165 http://ftpmaster.internal/ubuntu mantic/universe amd64 librttopo1 amd64 1.1.0-3 [191 kB] Get:166 http://ftpmaster.internal/ubuntu mantic/universe amd64 libspatialite7 amd64 5.0.1-3 [1992 kB] Get:167 http://ftpmaster.internal/ubuntu mantic/universe amd64 libxerces-c3.2 amd64 3.2.4+debian-1build1 [914 kB] Get:168 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 libgdal33 amd64 3.7.0+dfsg-1 [8134 kB] Get:169 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 libgeos-dev amd64 3.12.0-1 [54.2 kB] Get:170 http://ftpmaster.internal/ubuntu mantic/main amd64 libgif-dev amd64 5.2.1-2.5 [22.7 kB] Get:171 http://ftpmaster.internal/ubuntu mantic/main amd64 libgraphite2-3 amd64 1.3.14-1build2 [71.3 kB] Get:172 http://ftpmaster.internal/ubuntu mantic/main amd64 libharfbuzz0b amd64 6.0.0+dfsg-3build1 [411 kB] Get:173 http://ftpmaster.internal/ubuntu mantic/universe amd64 libx265-dev amd64 3.5-2 [1374 kB] Get:174 http://ftpmaster.internal/ubuntu mantic/universe amd64 libheif-dev amd64 1.15.1-1 [32.5 kB] Get:175 http://ftpmaster.internal/ubuntu mantic/main amd64 libicu-dev amd64 72.1-3ubuntu2 [11.8 MB] Get:176 http://ftpmaster.internal/ubuntu mantic/main amd64 libimagequant0 amd64 2.17.0-1 [34.6 kB] Get:177 http://ftpmaster.internal/ubuntu mantic/main amd64 libjs-jquery all 3.6.1+dfsg+~3.5.14-1 [328 kB] Get:178 http://ftpmaster.internal/ubuntu mantic/main amd64 libjs-underscore all 1.13.4~dfsg+~1.11.4-3 [118 kB] Get:179 http://ftpmaster.internal/ubuntu mantic/main amd64 libjs-sphinxdoc all 5.3.0-4 [130 kB] Get:180 http://ftpmaster.internal/ubuntu mantic/main amd64 libjson-perl all 4.10000-1 [81.9 kB] Get:181 http://ftpmaster.internal/ubuntu mantic/universe amd64 libkmlconvenience1 amd64 1.3.0-10 [47.6 kB] Get:182 http://ftpmaster.internal/ubuntu mantic/universe amd64 libkmlregionator1 amd64 1.3.0-10 [20.9 kB] Get:183 http://ftpmaster.internal/ubuntu mantic/universe amd64 libkmlxsd1 amd64 1.3.0-10 [27.7 kB] Get:184 http://ftpmaster.internal/ubuntu mantic/main amd64 liblerc-dev amd64 4.0.0+ds-2ubuntu2 [188 kB] Get:185 http://ftpmaster.internal/ubuntu mantic/main amd64 libltdl-dev amd64 2.4.7-5 [169 kB] Get:186 http://ftpmaster.internal/ubuntu mantic/universe amd64 libminizip-dev amd64 1.1-8build1 [26.7 kB] Get:187 http://ftpmaster.internal/ubuntu mantic/main amd64 libxml2-dev amd64 2.9.14+dfsg-1.2 [786 kB] Get:188 http://ftpmaster.internal/ubuntu mantic/universe amd64 libnetcdf-dev amd64 1:4.9.2-1 [57.9 kB] Get:189 http://ftpmaster.internal/ubuntu mantic/main amd64 libodbccr2 amd64 2.3.11-4 [16.3 kB] Get:190 http://ftpmaster.internal/ubuntu mantic/universe amd64 libogdi-dev amd64 4.1.0+ds-6 [22.6 kB] Get:191 http://ftpmaster.internal/ubuntu mantic/main amd64 libpcre2-16-0 amd64 10.42-1 [211 kB] Get:192 http://ftpmaster.internal/ubuntu mantic/main amd64 libpcre2-32-0 amd64 10.42-1 [198 kB] Get:193 http://ftpmaster.internal/ubuntu mantic/main amd64 libpcre2-posix3 amd64 10.42-1 [6744 B] Get:194 http://ftpmaster.internal/ubuntu mantic/main amd64 libpcre2-dev amd64 10.42-1 [744 kB] Get:195 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 libpng-dev amd64 1.6.40-1 [264 kB] Get:196 http://ftpmaster.internal/ubuntu mantic/main amd64 libpoppler-dev amd64 22.12.0-2ubuntu1 [5192 B] Get:197 http://ftpmaster.internal/ubuntu mantic/main amd64 libpoppler-private-dev amd64 22.12.0-2ubuntu1 [195 kB] Get:198 http://ftpmaster.internal/ubuntu mantic/main amd64 libpq-dev amd64 15.3-1 [148 kB] Get:199 http://ftpmaster.internal/ubuntu mantic/universe amd64 libqhull8.0 amd64 2020.2-5 [192 kB] Get:200 http://ftpmaster.internal/ubuntu mantic/universe amd64 libqhullcpp8.0 amd64 2020.2-5 [50.3 kB] Get:201 http://ftpmaster.internal/ubuntu mantic/universe amd64 libqhull-dev amd64 2020.2-5 [497 kB] Get:202 http://ftpmaster.internal/ubuntu mantic/main amd64 libraqm0 amd64 0.10.1-1 [14.6 kB] Get:203 http://ftpmaster.internal/ubuntu mantic/universe amd64 librttopo-dev amd64 1.1.0-3 [239 kB] Get:204 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 libsqlite3-dev amd64 3.42.0-1 [882 kB] Get:205 http://ftpmaster.internal/ubuntu mantic/universe amd64 libsqlite3-mod-spatialite amd64 5.0.1-3 [1996 kB] Get:206 http://ftpmaster.internal/ubuntu mantic/main amd64 libjbig-dev amd64 2.1-6.1ubuntu1 [27.8 kB] Get:207 http://ftpmaster.internal/ubuntu mantic/main amd64 liblzma-dev amd64 5.4.1-0.2 [177 kB] Get:208 http://ftpmaster.internal/ubuntu mantic/main amd64 libwebpmux3 amd64 1.2.4-0.2 [20.8 kB] Get:209 http://ftpmaster.internal/ubuntu mantic/main amd64 libwebpdemux2 amd64 1.2.4-0.2 [9874 B] Get:210 http://ftpmaster.internal/ubuntu mantic/main amd64 libwebp-dev amd64 1.2.4-0.2 [334 kB] Get:211 http://ftpmaster.internal/ubuntu mantic/main amd64 libtiffxx6 amd64 4.5.0-6ubuntu1 [5808 B] Get:212 http://ftpmaster.internal/ubuntu mantic/main amd64 libtiff-dev amd64 4.5.0-6ubuntu1 [337 kB] Get:213 http://ftpmaster.internal/ubuntu mantic/universe amd64 liburiparser-dev amd64 0.9.7+dfsg-2 [15.1 kB] Get:214 http://ftpmaster.internal/ubuntu mantic/universe amd64 libxerces-c-dev amd64 3.2.4+debian-1build1 [1820 kB] Get:215 http://ftpmaster.internal/ubuntu mantic/main amd64 python-babel-localedata all 2.10.3-1 [6357 kB] Get:216 http://ftpmaster.internal/ubuntu mantic/universe amd64 python-django-formtools-doc all 2.3-3 [45.0 kB] Get:217 http://ftpmaster.internal/ubuntu mantic/main amd64 python-psycopg2-doc all 2.9.5-1build1 [313 kB] Get:218 http://ftpmaster.internal/ubuntu mantic/main amd64 python-requests-doc all 2.28.1+dfsg-1ubuntu2 [169 kB] Get:219 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 python3-all amd64 3.11.4-1 [896 B] Get:220 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-asgiref all 3.7.2-1 [24.8 kB] Get:221 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-async-generator all 1.10-4 [17.5 kB] Get:222 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 python3-attr all 23.1.0-1 [50.4 kB] Get:223 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 python3-tz all 2023.3-3 [31.2 kB] Get:224 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-babel all 2.10.3-1 [87.5 kB] Get:225 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-certifi all 2022.9.24-1 [155 kB] Get:226 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-cffi-backend amd64 1.15.1-5build1 [76.0 kB] Get:227 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-chardet all 5.1.0+dfsg-2 [119 kB] Get:228 http://ftpmaster.internal/ubuntu mantic/main amd64 python3.11-doc all 3.11.4-1 [11.9 MB] Get:229 http://ftpmaster.internal/ubuntu mantic-proposed/main amd64 python3-doc all 3.11.4-1 [9554 B] Get:230 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-roman all 3.3-3 [9632 B] Get:231 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-docutils all 0.19+dfsg-6 [386 kB] Get:232 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-exceptiongroup all 1.1.0-1 [16.3 kB] Get:233 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-h11 all 0.14.0-1 [51.1 kB] Get:234 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-idna all 3.3-1 [49.3 kB] Get:235 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-imagesize all 1.4.1-1 [6844 B] Get:236 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-markupsafe amd64 2.1.3-1 [12.4 kB] Get:237 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-jinja2 all 3.1.2-1 [107 kB] Get:238 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-numpy amd64 1:1.24.2-1 [5573 kB] Get:239 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-outcome all 1.2.0-1 [5922 B] Get:240 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-packaging all 23.1-1 [38.1 kB] Get:241 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-setuptools all 67.8.0-1 [392 kB] Get:242 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-six all 1.16.0-4 [12.4 kB] Get:243 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-pbr all 5.11.1-0ubuntu1 [66.5 kB] Get:244 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-pil amd64 9.5.0-1 [435 kB] Get:245 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-urllib3 all 1.26.12-1 [99.7 kB] Get:246 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-requests all 2.28.1+dfsg-1ubuntu2 [50.7 kB] Get:247 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-sniffio all 1.2.0-1 [6438 B] Get:248 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-sortedcontainers all 2.4.0-2 [27.6 kB] Get:249 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-trio all 0.22.0-0.2 [259 kB] Get:250 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-wsproto all 1.2.0-1 [23.6 kB] Get:251 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-trio-websocket all 0.10.3-1 [20.6 kB] Get:252 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-selenium all 4.10.0+dfsg-1 [99.7 kB] Get:253 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-snowballstemmer all 2.2.0-4 [59.7 kB] Get:254 http://ftpmaster.internal/ubuntu mantic/main amd64 sphinx-common all 5.3.0-4 [691 kB] Get:255 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-alabaster all 0.7.12-1 [17.8 kB] Get:256 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-sphinx all 5.3.0-4 [556 kB] Get:257 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-sqlparse all 0.4.2-1ubuntu1 [30.5 kB] Get:258 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-tblib all 1.7.0-3 [12.5 kB] Get:259 http://ftpmaster.internal/ubuntu mantic/main amd64 libjs-mathjax all 2.7.9+dfsg-1 [5665 kB] Get:260 http://ftpmaster.internal/ubuntu mantic/main amd64 sphinx-doc all 5.3.0-4 [2292 kB] Get:261 http://ftpmaster.internal/ubuntu mantic/universe amd64 libfreexl-dev amd64 1.0.6-2 [32.5 kB] Get:262 http://ftpmaster.internal/ubuntu mantic/universe amd64 libproj-dev amd64 9.2.1-1 [75.4 kB] Get:263 http://ftpmaster.internal/ubuntu mantic/universe amd64 libgeotiff-dev amd64 1.7.1-2build1 [89.2 kB] Get:264 http://ftpmaster.internal/ubuntu mantic/universe amd64 libhdf4-alt-dev amd64 4.2.16-3 [388 kB] Get:265 http://ftpmaster.internal/ubuntu mantic/main amd64 libjson-c-dev amd64 0.16-2 [60.6 kB] Get:266 http://ftpmaster.internal/ubuntu mantic/universe amd64 libkml-dev amd64 1.3.0-10 [659 kB] Get:267 http://ftpmaster.internal/ubuntu mantic/main amd64 liblz4-dev amd64 1.9.4-1 [87.6 kB] Get:268 http://ftpmaster.internal/ubuntu mantic/main amd64 libopenjp2-7-dev amd64 2.5.0-2 [258 kB] Get:269 http://ftpmaster.internal/ubuntu mantic/universe amd64 libspatialite-dev amd64 5.0.1-3 [2267 kB] Get:270 http://ftpmaster.internal/ubuntu mantic/main amd64 unixodbc-dev amd64 2.3.11-4 [251 kB] Get:271 http://ftpmaster.internal/ubuntu mantic-proposed/universe amd64 libgdal-dev amd64 3.7.0+dfsg-1 [208 kB] Get:272 http://ftpmaster.internal/ubuntu mantic/main amd64 python3-bcrypt amd64 3.2.2-1 [32.5 kB] Get:273 http://ftpmaster.internal/ubuntu mantic/universe amd64 python3-mock all 4.0.3-4 [59.5 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 166 MB in 1s (140 MB/s) Selecting previously unselected package libpython3.11-minimal:amd64. (Reading database ... 12590 files and directories currently installed.) Preparing to unpack .../libpython3.11-minimal_3.11.4-1_amd64.deb ... Unpacking libpython3.11-minimal:amd64 (3.11.4-1) ... Selecting previously unselected package libexpat1:amd64. Preparing to unpack .../libexpat1_2.5.0-2_amd64.deb ... Unpacking libexpat1:amd64 (2.5.0-2) ... Selecting previously unselected package python3.11-minimal. Preparing to unpack .../python3.11-minimal_3.11.4-1_amd64.deb ... Unpacking python3.11-minimal (3.11.4-1) ... Setting up libpython3.11-minimal:amd64 (3.11.4-1) ... Setting up libexpat1:amd64 (2.5.0-2) ... Setting up python3.11-minimal (3.11.4-1) ... Selecting previously unselected package python3-minimal. (Reading database ... 12904 files and directories currently installed.) Preparing to unpack .../0-python3-minimal_3.11.4-1_amd64.deb ... Unpacking python3-minimal (3.11.4-1) ... Selecting previously unselected package media-types. Preparing to unpack .../1-media-types_10.0.0_all.deb ... Unpacking media-types (10.0.0) ... Selecting previously unselected package mailcap. Preparing to unpack .../2-mailcap_3.70+nmu1ubuntu1_all.deb ... Unpacking mailcap (3.70+nmu1ubuntu1) ... Selecting previously unselected package mime-support. Preparing to unpack .../3-mime-support_3.66_all.deb ... Unpacking mime-support (3.66) ... Selecting previously unselected package libpython3.11-stdlib:amd64. Preparing to unpack .../4-libpython3.11-stdlib_3.11.4-1_amd64.deb ... Unpacking libpython3.11-stdlib:amd64 (3.11.4-1) ... Selecting previously unselected package python3.11. Preparing to unpack .../5-python3.11_3.11.4-1_amd64.deb ... Unpacking python3.11 (3.11.4-1) ... Selecting previously unselected package libpython3-stdlib:amd64. Preparing to unpack .../6-libpython3-stdlib_3.11.4-1_amd64.deb ... Unpacking libpython3-stdlib:amd64 (3.11.4-1) ... Setting up python3-minimal (3.11.4-1) ... Selecting previously unselected package python3. (Reading database ... 13337 files and directories currently installed.) Preparing to unpack .../000-python3_3.11.4-1_amd64.deb ... Unpacking python3 (3.11.4-1) ... Selecting previously unselected package sgml-base. Preparing to unpack .../001-sgml-base_1.31_all.deb ... Unpacking sgml-base (1.31) ... Selecting previously unselected package libbsd0:amd64. Preparing to unpack .../002-libbsd0_0.11.7-4_amd64.deb ... Unpacking libbsd0:amd64 (0.11.7-4) ... Selecting previously unselected package libelf1:amd64. Preparing to unpack .../003-libelf1_0.188-2.1_amd64.deb ... Unpacking libelf1:amd64 (0.188-2.1) ... Selecting previously unselected package libfribidi0:amd64. Preparing to unpack .../004-libfribidi0_1.0.13-3_amd64.deb ... Unpacking libfribidi0:amd64 (1.0.13-3) ... Selecting previously unselected package libglib2.0-0:amd64. Preparing to unpack .../005-libglib2.0-0_2.76.3-1ubuntu1_amd64.deb ... Unpacking libglib2.0-0:amd64 (2.76.3-1ubuntu1) ... Selecting previously unselected package libicu72:amd64. Preparing to unpack .../006-libicu72_72.1-3ubuntu2_amd64.deb ... Unpacking libicu72:amd64 (72.1-3ubuntu2) ... Selecting previously unselected package libxml2:amd64. Preparing to unpack .../007-libxml2_2.9.14+dfsg-1.2_amd64.deb ... Unpacking libxml2:amd64 (2.9.14+dfsg-1.2) ... Selecting previously unselected package libyaml-0-2:amd64. Preparing to unpack .../008-libyaml-0-2_0.2.5-1_amd64.deb ... Unpacking libyaml-0-2:amd64 (0.2.5-1) ... Selecting previously unselected package python3-pkg-resources. Preparing to unpack .../009-python3-pkg-resources_67.8.0-1_all.deb ... Unpacking python3-pkg-resources (67.8.0-1) ... Selecting previously unselected package python3-pygments. Preparing to unpack .../010-python3-pygments_2.15.1+dfsg-1_all.deb ... Unpacking python3-pygments (2.15.1+dfsg-1) ... Selecting previously unselected package python3-yaml. Preparing to unpack .../011-python3-yaml_6.0-3build1_amd64.deb ... Unpacking python3-yaml (6.0-3build1) ... Selecting previously unselected package bsdextrautils. Preparing to unpack .../012-bsdextrautils_2.38.1-5ubuntu2_amd64.deb ... Unpacking bsdextrautils (2.38.1-5ubuntu2) ... Selecting previously unselected package libmagic-mgc. Preparing to unpack .../013-libmagic-mgc_1%3a5.44-3_amd64.deb ... Unpacking libmagic-mgc (1:5.44-3) ... Selecting previously unselected package libmagic1:amd64. Preparing to unpack .../014-libmagic1_1%3a5.44-3_amd64.deb ... Unpacking libmagic1:amd64 (1:5.44-3) ... Selecting previously unselected package file. Preparing to unpack .../015-file_1%3a5.44-3_amd64.deb ... Unpacking file (1:5.44-3) ... Selecting previously unselected package gettext-base. Preparing to unpack .../016-gettext-base_0.21-12_amd64.deb ... Unpacking gettext-base (0.21-12) ... Selecting previously unselected package libuchardet0:amd64. Preparing to unpack .../017-libuchardet0_0.0.7-1build2_amd64.deb ... Unpacking libuchardet0:amd64 (0.0.7-1build2) ... Selecting previously unselected package groff-base. Preparing to unpack .../018-groff-base_1.22.4-10_amd64.deb ... Unpacking groff-base (1.22.4-10) ... Selecting previously unselected package libnghttp2-14:amd64. Preparing to unpack .../019-libnghttp2-14_1.54.0-1_amd64.deb ... Unpacking libnghttp2-14:amd64 (1.54.0-1) ... Selecting previously unselected package libnuma1:amd64. Preparing to unpack .../020-libnuma1_2.0.16-1_amd64.deb ... Unpacking libnuma1:amd64 (2.0.16-1) ... Selecting previously unselected package libpipeline1:amd64. Preparing to unpack .../021-libpipeline1_1.5.7-1_amd64.deb ... Unpacking libpipeline1:amd64 (1.5.7-1) ... Selecting previously unselected package libpsl5:amd64. Preparing to unpack .../022-libpsl5_0.21.2-1_amd64.deb ... Unpacking libpsl5:amd64 (0.21.2-1) ... Selecting previously unselected package libxau6:amd64. Preparing to unpack .../023-libxau6_1%3a1.0.9-1build5_amd64.deb ... Unpacking libxau6:amd64 (1:1.0.9-1build5) ... Selecting previously unselected package libxdmcp6:amd64. Preparing to unpack .../024-libxdmcp6_1%3a1.1.3-0ubuntu5_amd64.deb ... Unpacking libxdmcp6:amd64 (1:1.1.3-0ubuntu5) ... Selecting previously unselected package libxcb1:amd64. Preparing to unpack .../025-libxcb1_1.15-1_amd64.deb ... Unpacking libxcb1:amd64 (1.15-1) ... Selecting previously unselected package man-db. Preparing to unpack .../026-man-db_2.11.2-2_amd64.deb ... Unpacking man-db (2.11.2-2) ... Selecting previously unselected package m4. Preparing to unpack .../027-m4_1.4.19-3_amd64.deb ... Unpacking m4 (1.4.19-3) ... Selecting previously unselected package autoconf. Preparing to unpack .../028-autoconf_2.71-3_all.deb ... Unpacking autoconf (2.71-3) ... Selecting previously unselected package autotools-dev. Preparing to unpack .../029-autotools-dev_20220109.1_all.deb ... Unpacking autotools-dev (20220109.1) ... Selecting previously unselected package automake. Preparing to unpack .../030-automake_1%3a1.16.5-1.3_all.deb ... Unpacking automake (1:1.16.5-1.3) ... Selecting previously unselected package autopoint. Preparing to unpack .../031-autopoint_0.21-12_all.deb ... Unpacking autopoint (0.21-12) ... Selecting previously unselected package libdebhelper-perl. Preparing to unpack .../032-libdebhelper-perl_13.11.4ubuntu3_all.deb ... Unpacking libdebhelper-perl (13.11.4ubuntu3) ... Selecting previously unselected package libtool. Preparing to unpack .../033-libtool_2.4.7-5_all.deb ... Unpacking libtool (2.4.7-5) ... Selecting previously unselected package dh-autoreconf. Preparing to unpack .../034-dh-autoreconf_20_all.deb ... Unpacking dh-autoreconf (20) ... Selecting previously unselected package libarchive-zip-perl. Preparing to unpack .../035-libarchive-zip-perl_1.68-1_all.deb ... Unpacking libarchive-zip-perl (1.68-1) ... Selecting previously unselected package libsub-override-perl. Preparing to unpack .../036-libsub-override-perl_0.09-4_all.deb ... Unpacking libsub-override-perl (0.09-4) ... Selecting previously unselected package libfile-stripnondeterminism-perl. Preparing to unpack .../037-libfile-stripnondeterminism-perl_1.13.1-1_all.deb ... Unpacking libfile-stripnondeterminism-perl (1.13.1-1) ... Selecting previously unselected package dh-strip-nondeterminism. Preparing to unpack .../038-dh-strip-nondeterminism_1.13.1-1_all.deb ... Unpacking dh-strip-nondeterminism (1.13.1-1) ... Selecting previously unselected package libdw1:amd64. Preparing to unpack .../039-libdw1_0.188-2.1_amd64.deb ... Unpacking libdw1:amd64 (0.188-2.1) ... Selecting previously unselected package debugedit. Preparing to unpack .../040-debugedit_1%3a5.0-5_amd64.deb ... Unpacking debugedit (1:5.0-5) ... Selecting previously unselected package dwz. Preparing to unpack .../041-dwz_0.15-1_amd64.deb ... Unpacking dwz (0.15-1) ... Selecting previously unselected package gettext. Preparing to unpack .../042-gettext_0.21-12_amd64.deb ... Unpacking gettext (0.21-12) ... Selecting previously unselected package intltool-debian. Preparing to unpack .../043-intltool-debian_0.35.0+20060710.6_all.deb ... Unpacking intltool-debian (0.35.0+20060710.6) ... Selecting previously unselected package po-debconf. Preparing to unpack .../044-po-debconf_1.0.21+nmu1_all.deb ... Unpacking po-debconf (1.0.21+nmu1) ... Selecting previously unselected package debhelper. Preparing to unpack .../045-debhelper_13.11.4ubuntu3_all.deb ... Unpacking debhelper (13.11.4ubuntu3) ... Selecting previously unselected package mysql-common. Preparing to unpack .../046-mysql-common_5.8+1.1.0_all.deb ... Unpacking mysql-common (5.8+1.1.0) ... Selecting previously unselected package libmysqlclient21:amd64. Preparing to unpack .../047-libmysqlclient21_8.0.33-2_amd64.deb ... Unpacking libmysqlclient21:amd64 (8.0.33-2) ... Selecting previously unselected package libssl-dev:amd64. Preparing to unpack .../048-libssl-dev_3.0.9-1ubuntu1_amd64.deb ... Unpacking libssl-dev:amd64 (3.0.9-1ubuntu1) ... Selecting previously unselected package libzstd-dev:amd64. Preparing to unpack .../049-libzstd-dev_1.5.4+dfsg2-5_amd64.deb ... Unpacking libzstd-dev:amd64 (1.5.4+dfsg2-5) ... Selecting previously unselected package zlib1g-dev:amd64. Preparing to unpack .../050-zlib1g-dev_1%3a1.2.13.dfsg-1ubuntu4_amd64.deb ... Unpacking zlib1g-dev:amd64 (1:1.2.13.dfsg-1ubuntu4) ... Selecting previously unselected package libmysqlclient-dev. Preparing to unpack .../051-libmysqlclient-dev_8.0.33-2_amd64.deb ... Unpacking libmysqlclient-dev (8.0.33-2) ... Selecting previously unselected package default-libmysqlclient-dev:amd64. Preparing to unpack .../052-default-libmysqlclient-dev_1.1.0_amd64.deb ... Unpacking default-libmysqlclient-dev:amd64 (1.1.0) ... Selecting previously unselected package python3-lib2to3. Preparing to unpack .../053-python3-lib2to3_3.11.4-1_all.deb ... Unpacking python3-lib2to3 (3.11.4-1) ... Selecting previously unselected package python3-distutils. Preparing to unpack .../054-python3-distutils_3.11.4-1_all.deb ... Unpacking python3-distutils (3.11.4-1) ... Selecting previously unselected package dh-python. Preparing to unpack .../055-dh-python_6.20230603_all.deb ... Unpacking dh-python (6.20230603) ... Selecting previously unselected package xml-core. Preparing to unpack .../056-xml-core_0.18+nmu1_all.deb ... Unpacking xml-core (0.18+nmu1) ... Selecting previously unselected package docutils-common. Preparing to unpack .../057-docutils-common_0.19+dfsg-6_all.deb ... Unpacking docutils-common (0.19+dfsg-6) ... Selecting previously unselected package docutils-doc. Preparing to unpack .../058-docutils-doc_0.19+dfsg-6_all.deb ... Unpacking docutils-doc (0.19+dfsg-6) ... Selecting previously unselected package fonts-dejavu-core. Preparing to unpack .../059-fonts-dejavu-core_2.37-6_all.deb ... Unpacking fonts-dejavu-core (2.37-6) ... Selecting previously unselected package fontconfig-config. Preparing to unpack .../060-fontconfig-config_2.14.1-4ubuntu1_amd64.deb ... Unpacking fontconfig-config (2.14.1-4ubuntu1) ... Selecting previously unselected package fonts-mathjax. Preparing to unpack .../061-fonts-mathjax_2.7.9+dfsg-1_all.deb ... Unpacking fonts-mathjax (2.7.9+dfsg-1) ... Selecting previously unselected package gdal-data. Preparing to unpack .../062-gdal-data_3.7.0+dfsg-1_all.deb ... Unpacking gdal-data (3.7.0+dfsg-1) ... Selecting previously unselected package gdal-plugins. Preparing to unpack .../063-gdal-plugins_3.7.0+dfsg-1_amd64.deb ... Unpacking gdal-plugins (3.7.0+dfsg-1) ... Selecting previously unselected package hdf5-helpers. Preparing to unpack .../064-hdf5-helpers_1.10.8+repack1-1ubuntu1_amd64.deb ... Unpacking hdf5-helpers (1.10.8+repack1-1ubuntu1) ... Selecting previously unselected package icu-devtools. Preparing to unpack .../065-icu-devtools_72.1-3ubuntu2_amd64.deb ... Unpacking icu-devtools (72.1-3ubuntu2) ... Selecting previously unselected package libaec0:amd64. Preparing to unpack .../066-libaec0_1.0.6-1_amd64.deb ... Unpacking libaec0:amd64 (1.0.6-1) ... Selecting previously unselected package libaom3:amd64. Preparing to unpack .../067-libaom3_3.6.1-1_amd64.deb ... Unpacking libaom3:amd64 (3.6.1-1) ... Selecting previously unselected package libaom-dev:amd64. Preparing to unpack .../068-libaom-dev_3.6.1-1_amd64.deb ... Unpacking libaom-dev:amd64 (3.6.1-1) ... Selecting previously unselected package libblas3:amd64. Preparing to unpack .../069-libblas3_3.11.0-2_amd64.deb ... Unpacking libblas3:amd64 (3.11.0-2) ... Selecting previously unselected package libgfortran5:amd64. Preparing to unpack .../070-libgfortran5_13.1.0-6ubuntu1_amd64.deb ... Unpacking libgfortran5:amd64 (13.1.0-6ubuntu1) ... Selecting previously unselected package liblapack3:amd64. Preparing to unpack .../071-liblapack3_3.11.0-2_amd64.deb ... Unpacking liblapack3:amd64 (3.11.0-2) ... Selecting previously unselected package libarpack2:amd64. Preparing to unpack .../072-libarpack2_3.8.0-3_amd64.deb ... Unpacking libarpack2:amd64 (3.8.0-3) ... Selecting previously unselected package libsuperlu5:amd64. Preparing to unpack .../073-libsuperlu5_5.3.0+dfsg1-2_amd64.deb ... Unpacking libsuperlu5:amd64 (5.3.0+dfsg1-2) ... Selecting previously unselected package libarmadillo11. Preparing to unpack .../074-libarmadillo11_1%3a11.4.2+dfsg-1_amd64.deb ... Unpacking libarmadillo11 (1:11.4.2+dfsg-1) ... Selecting previously unselected package libblas-dev:amd64. Preparing to unpack .../075-libblas-dev_3.11.0-2_amd64.deb ... Unpacking libblas-dev:amd64 (3.11.0-2) ... Selecting previously unselected package liblapack-dev:amd64. Preparing to unpack .../076-liblapack-dev_3.11.0-2_amd64.deb ... Unpacking liblapack-dev:amd64 (3.11.0-2) ... Selecting previously unselected package libarpack2-dev:amd64. Preparing to unpack .../077-libarpack2-dev_3.8.0-3_amd64.deb ... Unpacking libarpack2-dev:amd64 (3.8.0-3) ... Selecting previously unselected package libbrotli1:amd64. Preparing to unpack .../078-libbrotli1_1.0.9-2build8_amd64.deb ... Unpacking libbrotli1:amd64 (1.0.9-2build8) ... Selecting previously unselected package libsasl2-modules-db:amd64. Preparing to unpack .../079-libsasl2-modules-db_2.1.28+dfsg1-1_amd64.deb ... Unpacking libsasl2-modules-db:amd64 (2.1.28+dfsg1-1) ... Selecting previously unselected package libsasl2-2:amd64. Preparing to unpack .../080-libsasl2-2_2.1.28+dfsg1-1_amd64.deb ... Unpacking libsasl2-2:amd64 (2.1.28+dfsg1-1) ... Selecting previously unselected package libldap2:amd64. Preparing to unpack .../081-libldap2_2.6.4+dfsg-1~exp1ubuntu1_amd64.deb ... Unpacking libldap2:amd64 (2.6.4+dfsg-1~exp1ubuntu1) ... Selecting previously unselected package librtmp1:amd64. Preparing to unpack .../082-librtmp1_2.4+20151223.gitfa8646d.1-2build4_amd64.deb ... Unpacking librtmp1:amd64 (2.4+20151223.gitfa8646d.1-2build4) ... Selecting previously unselected package libssh-4:amd64. Preparing to unpack .../083-libssh-4_0.10.5-2_amd64.deb ... Unpacking libssh-4:amd64 (0.10.5-2) ... Selecting previously unselected package libcurl4:amd64. Preparing to unpack .../084-libcurl4_7.88.1-10ubuntu1_amd64.deb ... Unpacking libcurl4:amd64 (7.88.1-10ubuntu1) ... Selecting previously unselected package libsz2:amd64. Preparing to unpack .../085-libsz2_1.0.6-1_amd64.deb ... Unpacking libsz2:amd64 (1.0.6-1) ... Selecting previously unselected package libhdf5-103-1:amd64. Preparing to unpack .../086-libhdf5-103-1_1.10.8+repack1-1ubuntu1_amd64.deb ... Unpacking libhdf5-103-1:amd64 (1.10.8+repack1-1ubuntu1) ... Selecting previously unselected package libhdf5-fortran-102:amd64. Preparing to unpack .../087-libhdf5-fortran-102_1.10.8+repack1-1ubuntu1_amd64.deb ... Unpacking libhdf5-fortran-102:amd64 (1.10.8+repack1-1ubuntu1) ... Selecting previously unselected package libhdf5-hl-100:amd64. Preparing to unpack .../088-libhdf5-hl-100_1.10.8+repack1-1ubuntu1_amd64.deb ... Unpacking libhdf5-hl-100:amd64 (1.10.8+repack1-1ubuntu1) ... Selecting previously unselected package libhdf5-hl-fortran-100:amd64. Preparing to unpack .../089-libhdf5-hl-fortran-100_1.10.8+repack1-1ubuntu1_amd64.deb ... Unpacking libhdf5-hl-fortran-100:amd64 (1.10.8+repack1-1ubuntu1) ... Selecting previously unselected package libhdf5-cpp-103-1:amd64. Preparing to unpack .../090-libhdf5-cpp-103-1_1.10.8+repack1-1ubuntu1_amd64.deb ... Unpacking libhdf5-cpp-103-1:amd64 (1.10.8+repack1-1ubuntu1) ... Selecting previously unselected package libhdf5-hl-cpp-100:amd64. Preparing to unpack .../091-libhdf5-hl-cpp-100_1.10.8+repack1-1ubuntu1_amd64.deb ... Unpacking libhdf5-hl-cpp-100:amd64 (1.10.8+repack1-1ubuntu1) ... Selecting previously unselected package libjpeg-turbo8:amd64. Preparing to unpack .../092-libjpeg-turbo8_2.1.5-2ubuntu1_amd64.deb ... Unpacking libjpeg-turbo8:amd64 (2.1.5-2ubuntu1) ... Selecting previously unselected package libjpeg-turbo8-dev:amd64. Preparing to unpack .../093-libjpeg-turbo8-dev_2.1.5-2ubuntu1_amd64.deb ... Unpacking libjpeg-turbo8-dev:amd64 (2.1.5-2ubuntu1) ... Selecting previously unselected package libjpeg8:amd64. Preparing to unpack .../094-libjpeg8_8c-2ubuntu11_amd64.deb ... Unpacking libjpeg8:amd64 (8c-2ubuntu11) ... Selecting previously unselected package libjpeg8-dev:amd64. Preparing to unpack .../095-libjpeg8-dev_8c-2ubuntu11_amd64.deb ... Unpacking libjpeg8-dev:amd64 (8c-2ubuntu11) ... Selecting previously unselected package libjpeg-dev:amd64. Preparing to unpack .../096-libjpeg-dev_8c-2ubuntu11_amd64.deb ... Unpacking libjpeg-dev:amd64 (8c-2ubuntu11) ... Selecting previously unselected package libaec-dev:amd64. Preparing to unpack .../097-libaec-dev_1.0.6-1_amd64.deb ... Unpacking libaec-dev:amd64 (1.0.6-1) ... Selecting previously unselected package libcurl4-openssl-dev:amd64. Preparing to unpack .../098-libcurl4-openssl-dev_7.88.1-10ubuntu1_amd64.deb ... Unpacking libcurl4-openssl-dev:amd64 (7.88.1-10ubuntu1) ... Selecting previously unselected package libhdf5-dev. Preparing to unpack .../099-libhdf5-dev_1.10.8+repack1-1ubuntu1_amd64.deb ... Unpacking libhdf5-dev (1.10.8+repack1-1ubuntu1) ... Selecting previously unselected package libsuperlu-dev:amd64. Preparing to unpack .../100-libsuperlu-dev_5.3.0+dfsg1-2_amd64.deb ... Unpacking libsuperlu-dev:amd64 (5.3.0+dfsg1-2) ... Selecting previously unselected package libarmadillo-dev. Preparing to unpack .../101-libarmadillo-dev_1%3a11.4.2+dfsg-1_amd64.deb ... Unpacking libarmadillo-dev (1:11.4.2+dfsg-1) ... Selecting previously unselected package libsnappy1v5:amd64. Preparing to unpack .../102-libsnappy1v5_1.1.9-3_amd64.deb ... Unpacking libsnappy1v5:amd64 (1.1.9-3) ... Selecting previously unselected package libblosc1:amd64. Preparing to unpack .../103-libblosc1_1.21.3+ds-1_amd64.deb ... Unpacking libblosc1:amd64 (1.21.3+ds-1) ... Selecting previously unselected package libblosc-dev:amd64. Preparing to unpack .../104-libblosc-dev_1.21.3+ds-1_amd64.deb ... Unpacking libblosc-dev:amd64 (1.21.3+ds-1) ... Selecting previously unselected package libboost1.74-dev:amd64. Preparing to unpack .../105-libboost1.74-dev_1.74.0+ds1-21.1ubuntu1_amd64.deb ... Unpacking libboost1.74-dev:amd64 (1.74.0+ds1-21.1ubuntu1) ... Selecting previously unselected package libboost-dev:amd64. Preparing to unpack .../106-libboost-dev_1.74.0.3ubuntu7_amd64.deb ... Unpacking libboost-dev:amd64 (1.74.0.3ubuntu7) ... Selecting previously unselected package libcurl3-gnutls:amd64. Preparing to unpack .../107-libcurl3-gnutls_7.88.1-10ubuntu1_amd64.deb ... Unpacking libcurl3-gnutls:amd64 (7.88.1-10ubuntu1) ... Selecting previously unselected package libcfitsio10:amd64. Preparing to unpack .../108-libcfitsio10_4.2.0-3_amd64.deb ... Unpacking libcfitsio10:amd64 (4.2.0-3) ... Selecting previously unselected package libcfitsio-dev:amd64. Preparing to unpack .../109-libcfitsio-dev_4.2.0-3_amd64.deb ... Unpacking libcfitsio-dev:amd64 (4.2.0-3) ... Selecting previously unselected package libdav1d6:amd64. Preparing to unpack .../110-libdav1d6_1.2.1-2_amd64.deb ... Unpacking libdav1d6:amd64 (1.2.1-2) ... Selecting previously unselected package libdav1d-dev:amd64. Preparing to unpack .../111-libdav1d-dev_1.2.1-2_amd64.deb ... Unpacking libdav1d-dev:amd64 (1.2.1-2) ... Selecting previously unselected package libde265-0:amd64. Preparing to unpack .../112-libde265-0_1.0.12-1_amd64.deb ... Unpacking libde265-0:amd64 (1.0.12-1) ... Selecting previously unselected package libde265-dev:amd64. Preparing to unpack .../113-libde265-dev_1.0.12-1_amd64.deb ... Unpacking libde265-dev:amd64 (1.0.12-1) ... Selecting previously unselected package libdeflate0:amd64. Preparing to unpack .../114-libdeflate0_1.15-1_amd64.deb ... Unpacking libdeflate0:amd64 (1.15-1) ... Selecting previously unselected package libdeflate-dev:amd64. Preparing to unpack .../115-libdeflate-dev_1.15-1_amd64.deb ... Unpacking libdeflate-dev:amd64 (1.15-1) ... Selecting previously unselected package libexpat1-dev:amd64. Preparing to unpack .../116-libexpat1-dev_2.5.0-2_amd64.deb ... Unpacking libexpat1-dev:amd64 (2.5.0-2) ... Selecting previously unselected package libfreetype6:amd64. Preparing to unpack .../117-libfreetype6_2.12.1+dfsg-5_amd64.deb ... Unpacking libfreetype6:amd64 (2.12.1+dfsg-5) ... Selecting previously unselected package libfontconfig1:amd64. Preparing to unpack .../118-libfontconfig1_2.14.1-4ubuntu1_amd64.deb ... Unpacking libfontconfig1:amd64 (2.14.1-4ubuntu1) ... Selecting previously unselected package libfyba0:amd64. Preparing to unpack .../119-libfyba0_4.1.1-8_amd64.deb ... Unpacking libfyba0:amd64 (4.1.1-8) ... Selecting previously unselected package libfyba-dev:amd64. Preparing to unpack .../120-libfyba-dev_4.1.1-8_amd64.deb ... Unpacking libfyba-dev:amd64 (4.1.1-8) ... Selecting previously unselected package libfreexl1:amd64. Preparing to unpack .../121-libfreexl1_1.0.6-2_amd64.deb ... Unpacking libfreexl1:amd64 (1.0.6-2) ... Selecting previously unselected package libgeos3.12.0:amd64. Preparing to unpack .../122-libgeos3.12.0_3.12.0-1_amd64.deb ... Unpacking libgeos3.12.0:amd64 (3.12.0-1) ... Selecting previously unselected package libgeos-c1v5:amd64. Preparing to unpack .../123-libgeos-c1v5_3.12.0-1_amd64.deb ... Unpacking libgeos-c1v5:amd64 (3.12.0-1) ... Selecting previously unselected package proj-data. Preparing to unpack .../124-proj-data_9.2.1-1_all.deb ... Unpacking proj-data (9.2.1-1) ... Selecting previously unselected package libjbig0:amd64. Preparing to unpack .../125-libjbig0_2.1-6.1ubuntu1_amd64.deb ... Unpacking libjbig0:amd64 (2.1-6.1ubuntu1) ... Selecting previously unselected package liblerc4:amd64. Preparing to unpack .../126-liblerc4_4.0.0+ds-2ubuntu2_amd64.deb ... Unpacking liblerc4:amd64 (4.0.0+ds-2ubuntu2) ... Selecting previously unselected package libwebp7:amd64. Preparing to unpack .../127-libwebp7_1.2.4-0.2_amd64.deb ... Unpacking libwebp7:amd64 (1.2.4-0.2) ... Selecting previously unselected package libtiff6:amd64. Preparing to unpack .../128-libtiff6_4.5.0-6ubuntu1_amd64.deb ... Unpacking libtiff6:amd64 (4.5.0-6ubuntu1) ... Selecting previously unselected package libproj25:amd64. Preparing to unpack .../129-libproj25_9.2.1-1_amd64.deb ... Unpacking libproj25:amd64 (9.2.1-1) ... Selecting previously unselected package libgeotiff5:amd64. Preparing to unpack .../130-libgeotiff5_1.7.1-2build1_amd64.deb ... Unpacking libgeotiff5:amd64 (1.7.1-2build1) ... Selecting previously unselected package libgif7:amd64. Preparing to unpack .../131-libgif7_5.2.1-2.5_amd64.deb ... Unpacking libgif7:amd64 (5.2.1-2.5) ... Selecting previously unselected package libhdf4-0-alt. Preparing to unpack .../132-libhdf4-0-alt_4.2.16-3_amd64.deb ... Unpacking libhdf4-0-alt (4.2.16-3) ... Selecting previously unselected package libx265-199:amd64. Preparing to unpack .../133-libx265-199_3.5-2_amd64.deb ... Unpacking libx265-199:amd64 (3.5-2) ... Selecting previously unselected package libheif1:amd64. Preparing to unpack .../134-libheif1_1.15.1-1_amd64.deb ... Unpacking libheif1:amd64 (1.15.1-1) ... Selecting previously unselected package libminizip1:amd64. Preparing to unpack .../135-libminizip1_1.1-8build1_amd64.deb ... Unpacking libminizip1:amd64 (1.1-8build1) ... Selecting previously unselected package liburiparser1:amd64. Preparing to unpack .../136-liburiparser1_0.9.7+dfsg-2_amd64.deb ... Unpacking liburiparser1:amd64 (0.9.7+dfsg-2) ... Selecting previously unselected package libkmlbase1:amd64. Preparing to unpack .../137-libkmlbase1_1.3.0-10_amd64.deb ... Unpacking libkmlbase1:amd64 (1.3.0-10) ... Selecting previously unselected package libkmldom1:amd64. Preparing to unpack .../138-libkmldom1_1.3.0-10_amd64.deb ... Unpacking libkmldom1:amd64 (1.3.0-10) ... Selecting previously unselected package libkmlengine1:amd64. Preparing to unpack .../139-libkmlengine1_1.3.0-10_amd64.deb ... Unpacking libkmlengine1:amd64 (1.3.0-10) ... Selecting previously unselected package libnetcdf19:amd64. Preparing to unpack .../140-libnetcdf19_1%3a4.9.2-1_amd64.deb ... Unpacking libnetcdf19:amd64 (1:4.9.2-1) ... Selecting previously unselected package libltdl7:amd64. Preparing to unpack .../141-libltdl7_2.4.7-5_amd64.deb ... Unpacking libltdl7:amd64 (2.4.7-5) ... Selecting previously unselected package libodbc2:amd64. Preparing to unpack .../142-libodbc2_2.3.11-4_amd64.deb ... Unpacking libodbc2:amd64 (2.3.11-4) ... Selecting previously unselected package unixodbc-common. Preparing to unpack .../143-unixodbc-common_2.3.11-4_all.deb ... Unpacking unixodbc-common (2.3.11-4) ... Selecting previously unselected package libodbcinst2:amd64. Preparing to unpack .../144-libodbcinst2_2.3.11-4_amd64.deb ... Unpacking libodbcinst2:amd64 (2.3.11-4) ... Selecting previously unselected package libogdi4.1. Preparing to unpack .../145-libogdi4.1_4.1.0+ds-6_amd64.deb ... Unpacking libogdi4.1 (4.1.0+ds-6) ... Selecting previously unselected package libopenjp2-7:amd64. Preparing to unpack .../146-libopenjp2-7_2.5.0-2_amd64.deb ... Unpacking libopenjp2-7:amd64 (2.5.0-2) ... Selecting previously unselected package liblcms2-2:amd64. Preparing to unpack .../147-liblcms2-2_2.14-2_amd64.deb ... Unpacking liblcms2-2:amd64 (2.14-2) ... Selecting previously unselected package libnspr4:amd64. Preparing to unpack .../148-libnspr4_2%3a4.35-1.1_amd64.deb ... Unpacking libnspr4:amd64 (2:4.35-1.1) ... Selecting previously unselected package libnss3:amd64. Preparing to unpack .../149-libnss3_2%3a3.90-3_amd64.deb ... Unpacking libnss3:amd64 (2:3.90-3) ... Selecting previously unselected package libpoppler126:amd64. Preparing to unpack .../150-libpoppler126_22.12.0-2ubuntu1_amd64.deb ... Unpacking libpoppler126:amd64 (22.12.0-2ubuntu1) ... Selecting previously unselected package libpq5:amd64. Preparing to unpack .../151-libpq5_15.3-1_amd64.deb ... Unpacking libpq5:amd64 (15.3-1) ... Selecting previously unselected package libqhull-r8.0:amd64. Preparing to unpack .../152-libqhull-r8.0_2020.2-5_amd64.deb ... Unpacking libqhull-r8.0:amd64 (2020.2-5) ... Selecting previously unselected package librttopo1:amd64. Preparing to unpack .../153-librttopo1_1.1.0-3_amd64.deb ... Unpacking librttopo1:amd64 (1.1.0-3) ... Selecting previously unselected package libspatialite7:amd64. Preparing to unpack .../154-libspatialite7_5.0.1-3_amd64.deb ... Unpacking libspatialite7:amd64 (5.0.1-3) ... Selecting previously unselected package libxerces-c3.2:amd64. Preparing to unpack .../155-libxerces-c3.2_3.2.4+debian-1build1_amd64.deb ... Unpacking libxerces-c3.2:amd64 (3.2.4+debian-1build1) ... Selecting previously unselected package libgdal33. Preparing to unpack .../156-libgdal33_3.7.0+dfsg-1_amd64.deb ... Unpacking libgdal33 (3.7.0+dfsg-1) ... Selecting previously unselected package libgeos-dev. Preparing to unpack .../157-libgeos-dev_3.12.0-1_amd64.deb ... Unpacking libgeos-dev (3.12.0-1) ... Selecting previously unselected package libgif-dev:amd64. Preparing to unpack .../158-libgif-dev_5.2.1-2.5_amd64.deb ... Unpacking libgif-dev:amd64 (5.2.1-2.5) ... Selecting previously unselected package libgraphite2-3:amd64. Preparing to unpack .../159-libgraphite2-3_1.3.14-1build2_amd64.deb ... Unpacking libgraphite2-3:amd64 (1.3.14-1build2) ... Selecting previously unselected package libharfbuzz0b:amd64. Preparing to unpack .../160-libharfbuzz0b_6.0.0+dfsg-3build1_amd64.deb ... Unpacking libharfbuzz0b:amd64 (6.0.0+dfsg-3build1) ... Selecting previously unselected package libx265-dev:amd64. Preparing to unpack .../161-libx265-dev_3.5-2_amd64.deb ... Unpacking libx265-dev:amd64 (3.5-2) ... Selecting previously unselected package libheif-dev:amd64. Preparing to unpack .../162-libheif-dev_1.15.1-1_amd64.deb ... Unpacking libheif-dev:amd64 (1.15.1-1) ... Selecting previously unselected package libicu-dev:amd64. Preparing to unpack .../163-libicu-dev_72.1-3ubuntu2_amd64.deb ... Unpacking libicu-dev:amd64 (72.1-3ubuntu2) ... Selecting previously unselected package libimagequant0:amd64. Preparing to unpack .../164-libimagequant0_2.17.0-1_amd64.deb ... Unpacking libimagequant0:amd64 (2.17.0-1) ... Selecting previously unselected package libjs-jquery. Preparing to unpack .../165-libjs-jquery_3.6.1+dfsg+~3.5.14-1_all.deb ... Unpacking libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Selecting previously unselected package libjs-underscore. Preparing to unpack .../166-libjs-underscore_1.13.4~dfsg+~1.11.4-3_all.deb ... Unpacking libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Selecting previously unselected package libjs-sphinxdoc. Preparing to unpack .../167-libjs-sphinxdoc_5.3.0-4_all.deb ... Unpacking libjs-sphinxdoc (5.3.0-4) ... Selecting previously unselected package libjson-perl. Preparing to unpack .../168-libjson-perl_4.10000-1_all.deb ... Unpacking libjson-perl (4.10000-1) ... Selecting previously unselected package libkmlconvenience1:amd64. Preparing to unpack .../169-libkmlconvenience1_1.3.0-10_amd64.deb ... Unpacking libkmlconvenience1:amd64 (1.3.0-10) ... Selecting previously unselected package libkmlregionator1:amd64. Preparing to unpack .../170-libkmlregionator1_1.3.0-10_amd64.deb ... Unpacking libkmlregionator1:amd64 (1.3.0-10) ... Selecting previously unselected package libkmlxsd1:amd64. Preparing to unpack .../171-libkmlxsd1_1.3.0-10_amd64.deb ... Unpacking libkmlxsd1:amd64 (1.3.0-10) ... Selecting previously unselected package liblerc-dev:amd64. Preparing to unpack .../172-liblerc-dev_4.0.0+ds-2ubuntu2_amd64.deb ... Unpacking liblerc-dev:amd64 (4.0.0+ds-2ubuntu2) ... Selecting previously unselected package libltdl-dev:amd64. Preparing to unpack .../173-libltdl-dev_2.4.7-5_amd64.deb ... Unpacking libltdl-dev:amd64 (2.4.7-5) ... Selecting previously unselected package libminizip-dev:amd64. Preparing to unpack .../174-libminizip-dev_1.1-8build1_amd64.deb ... Unpacking libminizip-dev:amd64 (1.1-8build1) ... Selecting previously unselected package libxml2-dev:amd64. Preparing to unpack .../175-libxml2-dev_2.9.14+dfsg-1.2_amd64.deb ... Unpacking libxml2-dev:amd64 (2.9.14+dfsg-1.2) ... Selecting previously unselected package libnetcdf-dev. Preparing to unpack .../176-libnetcdf-dev_1%3a4.9.2-1_amd64.deb ... Unpacking libnetcdf-dev (1:4.9.2-1) ... Selecting previously unselected package libodbccr2:amd64. Preparing to unpack .../177-libodbccr2_2.3.11-4_amd64.deb ... Unpacking libodbccr2:amd64 (2.3.11-4) ... Selecting previously unselected package libogdi-dev. Preparing to unpack .../178-libogdi-dev_4.1.0+ds-6_amd64.deb ... Unpacking libogdi-dev (4.1.0+ds-6) ... Selecting previously unselected package libpcre2-16-0:amd64. Preparing to unpack .../179-libpcre2-16-0_10.42-1_amd64.deb ... Unpacking libpcre2-16-0:amd64 (10.42-1) ... Selecting previously unselected package libpcre2-32-0:amd64. Preparing to unpack .../180-libpcre2-32-0_10.42-1_amd64.deb ... Unpacking libpcre2-32-0:amd64 (10.42-1) ... Selecting previously unselected package libpcre2-posix3:amd64. Preparing to unpack .../181-libpcre2-posix3_10.42-1_amd64.deb ... Unpacking libpcre2-posix3:amd64 (10.42-1) ... Selecting previously unselected package libpcre2-dev:amd64. Preparing to unpack .../182-libpcre2-dev_10.42-1_amd64.deb ... Unpacking libpcre2-dev:amd64 (10.42-1) ... Selecting previously unselected package libpng-dev:amd64. Preparing to unpack .../183-libpng-dev_1.6.40-1_amd64.deb ... Unpacking libpng-dev:amd64 (1.6.40-1) ... Selecting previously unselected package libpoppler-dev:amd64. Preparing to unpack .../184-libpoppler-dev_22.12.0-2ubuntu1_amd64.deb ... Unpacking libpoppler-dev:amd64 (22.12.0-2ubuntu1) ... Selecting previously unselected package libpoppler-private-dev:amd64. Preparing to unpack .../185-libpoppler-private-dev_22.12.0-2ubuntu1_amd64.deb ... Unpacking libpoppler-private-dev:amd64 (22.12.0-2ubuntu1) ... Selecting previously unselected package libpq-dev. Preparing to unpack .../186-libpq-dev_15.3-1_amd64.deb ... Unpacking libpq-dev (15.3-1) ... Selecting previously unselected package libqhull8.0:amd64. Preparing to unpack .../187-libqhull8.0_2020.2-5_amd64.deb ... Unpacking libqhull8.0:amd64 (2020.2-5) ... Selecting previously unselected package libqhullcpp8.0:amd64. Preparing to unpack .../188-libqhullcpp8.0_2020.2-5_amd64.deb ... Unpacking libqhullcpp8.0:amd64 (2020.2-5) ... Selecting previously unselected package libqhull-dev:amd64. Preparing to unpack .../189-libqhull-dev_2020.2-5_amd64.deb ... Unpacking libqhull-dev:amd64 (2020.2-5) ... Selecting previously unselected package libraqm0:amd64. Preparing to unpack .../190-libraqm0_0.10.1-1_amd64.deb ... Unpacking libraqm0:amd64 (0.10.1-1) ... Selecting previously unselected package librttopo-dev:amd64. Preparing to unpack .../191-librttopo-dev_1.1.0-3_amd64.deb ... Unpacking librttopo-dev:amd64 (1.1.0-3) ... Selecting previously unselected package libsqlite3-dev:amd64. Preparing to unpack .../192-libsqlite3-dev_3.42.0-1_amd64.deb ... Unpacking libsqlite3-dev:amd64 (3.42.0-1) ... Selecting previously unselected package libsqlite3-mod-spatialite:amd64. Preparing to unpack .../193-libsqlite3-mod-spatialite_5.0.1-3_amd64.deb ... Unpacking libsqlite3-mod-spatialite:amd64 (5.0.1-3) ... Selecting previously unselected package libjbig-dev:amd64. Preparing to unpack .../194-libjbig-dev_2.1-6.1ubuntu1_amd64.deb ... Unpacking libjbig-dev:amd64 (2.1-6.1ubuntu1) ... Selecting previously unselected package liblzma-dev:amd64. Preparing to unpack .../195-liblzma-dev_5.4.1-0.2_amd64.deb ... Unpacking liblzma-dev:amd64 (5.4.1-0.2) ... Selecting previously unselected package libwebpmux3:amd64. Preparing to unpack .../196-libwebpmux3_1.2.4-0.2_amd64.deb ... Unpacking libwebpmux3:amd64 (1.2.4-0.2) ... Selecting previously unselected package libwebpdemux2:amd64. Preparing to unpack .../197-libwebpdemux2_1.2.4-0.2_amd64.deb ... Unpacking libwebpdemux2:amd64 (1.2.4-0.2) ... Selecting previously unselected package libwebp-dev:amd64. Preparing to unpack .../198-libwebp-dev_1.2.4-0.2_amd64.deb ... Unpacking libwebp-dev:amd64 (1.2.4-0.2) ... Selecting previously unselected package libtiffxx6:amd64. Preparing to unpack .../199-libtiffxx6_4.5.0-6ubuntu1_amd64.deb ... Unpacking libtiffxx6:amd64 (4.5.0-6ubuntu1) ... Selecting previously unselected package libtiff-dev:amd64. Preparing to unpack .../200-libtiff-dev_4.5.0-6ubuntu1_amd64.deb ... Unpacking libtiff-dev:amd64 (4.5.0-6ubuntu1) ... Selecting previously unselected package liburiparser-dev. Preparing to unpack .../201-liburiparser-dev_0.9.7+dfsg-2_amd64.deb ... Unpacking liburiparser-dev (0.9.7+dfsg-2) ... Selecting previously unselected package libxerces-c-dev:amd64. Preparing to unpack .../202-libxerces-c-dev_3.2.4+debian-1build1_amd64.deb ... Unpacking libxerces-c-dev:amd64 (3.2.4+debian-1build1) ... Selecting previously unselected package python-babel-localedata. Preparing to unpack .../203-python-babel-localedata_2.10.3-1_all.deb ... Unpacking python-babel-localedata (2.10.3-1) ... Selecting previously unselected package python-django-formtools-doc. Preparing to unpack .../204-python-django-formtools-doc_2.3-3_all.deb ... Unpacking python-django-formtools-doc (2.3-3) ... Selecting previously unselected package python-psycopg2-doc. Preparing to unpack .../205-python-psycopg2-doc_2.9.5-1build1_all.deb ... Unpacking python-psycopg2-doc (2.9.5-1build1) ... Selecting previously unselected package python-requests-doc. Preparing to unpack .../206-python-requests-doc_2.28.1+dfsg-1ubuntu2_all.deb ... Unpacking python-requests-doc (2.28.1+dfsg-1ubuntu2) ... Selecting previously unselected package python3-all. Preparing to unpack .../207-python3-all_3.11.4-1_amd64.deb ... Unpacking python3-all (3.11.4-1) ... Selecting previously unselected package python3-asgiref. Preparing to unpack .../208-python3-asgiref_3.7.2-1_all.deb ... Unpacking python3-asgiref (3.7.2-1) ... Selecting previously unselected package python3-async-generator. Preparing to unpack .../209-python3-async-generator_1.10-4_all.deb ... Unpacking python3-async-generator (1.10-4) ... Selecting previously unselected package python3-attr. Preparing to unpack .../210-python3-attr_23.1.0-1_all.deb ... Unpacking python3-attr (23.1.0-1) ... Selecting previously unselected package python3-tz. Preparing to unpack .../211-python3-tz_2023.3-3_all.deb ... Unpacking python3-tz (2023.3-3) ... Selecting previously unselected package python3-babel. Preparing to unpack .../212-python3-babel_2.10.3-1_all.deb ... Unpacking python3-babel (2.10.3-1) ... Selecting previously unselected package python3-certifi. Preparing to unpack .../213-python3-certifi_2022.9.24-1_all.deb ... Unpacking python3-certifi (2022.9.24-1) ... Selecting previously unselected package python3-cffi-backend:amd64. Preparing to unpack .../214-python3-cffi-backend_1.15.1-5build1_amd64.deb ... Unpacking python3-cffi-backend:amd64 (1.15.1-5build1) ... Selecting previously unselected package python3-chardet. Preparing to unpack .../215-python3-chardet_5.1.0+dfsg-2_all.deb ... Unpacking python3-chardet (5.1.0+dfsg-2) ... Selecting previously unselected package python3.11-doc. Preparing to unpack .../216-python3.11-doc_3.11.4-1_all.deb ... Unpacking python3.11-doc (3.11.4-1) ... Selecting previously unselected package python3-doc. Preparing to unpack .../217-python3-doc_3.11.4-1_all.deb ... Unpacking python3-doc (3.11.4-1) ... Selecting previously unselected package python3-roman. Preparing to unpack .../218-python3-roman_3.3-3_all.deb ... Unpacking python3-roman (3.3-3) ... Selecting previously unselected package python3-docutils. Preparing to unpack .../219-python3-docutils_0.19+dfsg-6_all.deb ... Unpacking python3-docutils (0.19+dfsg-6) ... Selecting previously unselected package python3-exceptiongroup. Preparing to unpack .../220-python3-exceptiongroup_1.1.0-1_all.deb ... Unpacking python3-exceptiongroup (1.1.0-1) ... Selecting previously unselected package python3-h11. Preparing to unpack .../221-python3-h11_0.14.0-1_all.deb ... Unpacking python3-h11 (0.14.0-1) ... Selecting previously unselected package python3-idna. Preparing to unpack .../222-python3-idna_3.3-1_all.deb ... Unpacking python3-idna (3.3-1) ... Selecting previously unselected package python3-imagesize. Preparing to unpack .../223-python3-imagesize_1.4.1-1_all.deb ... Unpacking python3-imagesize (1.4.1-1) ... Selecting previously unselected package python3-markupsafe. Preparing to unpack .../224-python3-markupsafe_2.1.3-1_amd64.deb ... Unpacking python3-markupsafe (2.1.3-1) ... Selecting previously unselected package python3-jinja2. Preparing to unpack .../225-python3-jinja2_3.1.2-1_all.deb ... Unpacking python3-jinja2 (3.1.2-1) ... Selecting previously unselected package python3-numpy. Preparing to unpack .../226-python3-numpy_1%3a1.24.2-1_amd64.deb ... Unpacking python3-numpy (1:1.24.2-1) ... Selecting previously unselected package python3-outcome. Preparing to unpack .../227-python3-outcome_1.2.0-1_all.deb ... Unpacking python3-outcome (1.2.0-1) ... Selecting previously unselected package python3-packaging. Preparing to unpack .../228-python3-packaging_23.1-1_all.deb ... Unpacking python3-packaging (23.1-1) ... Selecting previously unselected package python3-setuptools. Preparing to unpack .../229-python3-setuptools_67.8.0-1_all.deb ... Unpacking python3-setuptools (67.8.0-1) ... Selecting previously unselected package python3-six. Preparing to unpack .../230-python3-six_1.16.0-4_all.deb ... Unpacking python3-six (1.16.0-4) ... Selecting previously unselected package python3-pbr. Preparing to unpack .../231-python3-pbr_5.11.1-0ubuntu1_all.deb ... Unpacking python3-pbr (5.11.1-0ubuntu1) ... Selecting previously unselected package python3-pil:amd64. Preparing to unpack .../232-python3-pil_9.5.0-1_amd64.deb ... Unpacking python3-pil:amd64 (9.5.0-1) ... Selecting previously unselected package python3-urllib3. Preparing to unpack .../233-python3-urllib3_1.26.12-1_all.deb ... Unpacking python3-urllib3 (1.26.12-1) ... Selecting previously unselected package python3-requests. Preparing to unpack .../234-python3-requests_2.28.1+dfsg-1ubuntu2_all.deb ... Unpacking python3-requests (2.28.1+dfsg-1ubuntu2) ... Selecting previously unselected package python3-sniffio. Preparing to unpack .../235-python3-sniffio_1.2.0-1_all.deb ... Unpacking python3-sniffio (1.2.0-1) ... Selecting previously unselected package python3-sortedcontainers. Preparing to unpack .../236-python3-sortedcontainers_2.4.0-2_all.deb ... Unpacking python3-sortedcontainers (2.4.0-2) ... Selecting previously unselected package python3-trio. Preparing to unpack .../237-python3-trio_0.22.0-0.2_all.deb ... Unpacking python3-trio (0.22.0-0.2) ... Selecting previously unselected package python3-wsproto. Preparing to unpack .../238-python3-wsproto_1.2.0-1_all.deb ... Unpacking python3-wsproto (1.2.0-1) ... Selecting previously unselected package python3-trio-websocket. Preparing to unpack .../239-python3-trio-websocket_0.10.3-1_all.deb ... Unpacking python3-trio-websocket (0.10.3-1) ... Selecting previously unselected package python3-selenium. Preparing to unpack .../240-python3-selenium_4.10.0+dfsg-1_all.deb ... Unpacking python3-selenium (4.10.0+dfsg-1) ... Selecting previously unselected package python3-snowballstemmer. Preparing to unpack .../241-python3-snowballstemmer_2.2.0-4_all.deb ... Unpacking python3-snowballstemmer (2.2.0-4) ... Selecting previously unselected package sphinx-common. Preparing to unpack .../242-sphinx-common_5.3.0-4_all.deb ... Unpacking sphinx-common (5.3.0-4) ... Selecting previously unselected package python3-alabaster. Preparing to unpack .../243-python3-alabaster_0.7.12-1_all.deb ... Unpacking python3-alabaster (0.7.12-1) ... Selecting previously unselected package python3-sphinx. Preparing to unpack .../244-python3-sphinx_5.3.0-4_all.deb ... Unpacking python3-sphinx (5.3.0-4) ... Selecting previously unselected package python3-sqlparse. Preparing to unpack .../245-python3-sqlparse_0.4.2-1ubuntu1_all.deb ... Unpacking python3-sqlparse (0.4.2-1ubuntu1) ... Selecting previously unselected package python3-tblib. Preparing to unpack .../246-python3-tblib_1.7.0-3_all.deb ... Unpacking python3-tblib (1.7.0-3) ... Selecting previously unselected package libjs-mathjax. Preparing to unpack .../247-libjs-mathjax_2.7.9+dfsg-1_all.deb ... Unpacking libjs-mathjax (2.7.9+dfsg-1) ... Selecting previously unselected package sphinx-doc. Preparing to unpack .../248-sphinx-doc_5.3.0-4_all.deb ... Unpacking sphinx-doc (5.3.0-4) ... Selecting previously unselected package libfreexl-dev:amd64. Preparing to unpack .../249-libfreexl-dev_1.0.6-2_amd64.deb ... Unpacking libfreexl-dev:amd64 (1.0.6-2) ... Selecting previously unselected package libproj-dev:amd64. Preparing to unpack .../250-libproj-dev_9.2.1-1_amd64.deb ... Unpacking libproj-dev:amd64 (9.2.1-1) ... Selecting previously unselected package libgeotiff-dev:amd64. Preparing to unpack .../251-libgeotiff-dev_1.7.1-2build1_amd64.deb ... Unpacking libgeotiff-dev:amd64 (1.7.1-2build1) ... Selecting previously unselected package libhdf4-alt-dev. Preparing to unpack .../252-libhdf4-alt-dev_4.2.16-3_amd64.deb ... Unpacking libhdf4-alt-dev (4.2.16-3) ... Selecting previously unselected package libjson-c-dev:amd64. Preparing to unpack .../253-libjson-c-dev_0.16-2_amd64.deb ... Unpacking libjson-c-dev:amd64 (0.16-2) ... Selecting previously unselected package libkml-dev:amd64. Preparing to unpack .../254-libkml-dev_1.3.0-10_amd64.deb ... Unpacking libkml-dev:amd64 (1.3.0-10) ... Selecting previously unselected package liblz4-dev:amd64. Preparing to unpack .../255-liblz4-dev_1.9.4-1_amd64.deb ... Unpacking liblz4-dev:amd64 (1.9.4-1) ... Selecting previously unselected package libopenjp2-7-dev:amd64. Preparing to unpack .../256-libopenjp2-7-dev_2.5.0-2_amd64.deb ... Unpacking libopenjp2-7-dev:amd64 (2.5.0-2) ... Selecting previously unselected package libspatialite-dev:amd64. Preparing to unpack .../257-libspatialite-dev_5.0.1-3_amd64.deb ... Unpacking libspatialite-dev:amd64 (5.0.1-3) ... Selecting previously unselected package unixodbc-dev:amd64. Preparing to unpack .../258-unixodbc-dev_2.3.11-4_amd64.deb ... Unpacking unixodbc-dev:amd64 (2.3.11-4) ... Selecting previously unselected package libgdal-dev. Preparing to unpack .../259-libgdal-dev_3.7.0+dfsg-1_amd64.deb ... Unpacking libgdal-dev (3.7.0+dfsg-1) ... Selecting previously unselected package python3-bcrypt. Preparing to unpack .../260-python3-bcrypt_3.2.2-1_amd64.deb ... Unpacking python3-bcrypt (3.2.2-1) ... Selecting previously unselected package python3-mock. Preparing to unpack .../261-python3-mock_4.0.3-4_all.deb ... Unpacking python3-mock (4.0.3-4) ... Selecting previously unselected package sbuild-build-depends-main-dummy. Preparing to unpack .../262-sbuild-build-depends-main-dummy_0.invalid.0_amd64.deb ... Unpacking sbuild-build-depends-main-dummy (0.invalid.0) ... Setting up media-types (10.0.0) ... Setting up libpipeline1:amd64 (1.5.7-1) ... Setting up libgraphite2-3:amd64 (1.3.14-1build2) ... Setting up liblcms2-2:amd64 (2.14-2) ... Setting up libaom3:amd64 (3.6.1-1) ... Setting up mysql-common (5.8+1.1.0) ... update-alternatives: using /etc/mysql/my.cnf.fallback to provide /etc/mysql/my.cnf (my.cnf) in auto mode Setting up libmysqlclient21:amd64 (8.0.33-2) ... Setting up libxau6:amd64 (1:1.0.9-1build5) ... Setting up libpsl5:amd64 (0.21.2-1) ... Setting up libboost1.74-dev:amd64 (1.74.0+ds1-21.1ubuntu1) ... Setting up fonts-mathjax (2.7.9+dfsg-1) ... Setting up libicu72:amd64 (72.1-3ubuntu2) ... Setting up docutils-doc (0.19+dfsg-6) ... Setting up libzstd-dev:amd64 (1.5.4+dfsg2-5) ... Setting up liblerc4:amd64 (4.0.0+ds-2ubuntu2) ... Setting up proj-data (9.2.1-1) ... Setting up bsdextrautils (2.38.1-5ubuntu2) ... Setting up hdf5-helpers (1.10.8+repack1-1ubuntu1) ... Setting up libjs-mathjax (2.7.9+dfsg-1) ... Setting up libmagic-mgc (1:5.44-3) ... Setting up libogdi4.1 (4.1.0+ds-6) ... Setting up libqhull8.0:amd64 (2020.2-5) ... Setting up libminizip1:amd64 (1.1-8build1) ... Setting up libarchive-zip-perl (1.68-1) ... Setting up libyaml-0-2:amd64 (0.2.5-1) ... Setting up libglib2.0-0:amd64 (2.76.3-1ubuntu1) ... No schema files found: doing nothing. Setting up libjson-c-dev:amd64 (0.16-2) ... Setting up libpython3.11-stdlib:amd64 (3.11.4-1) ... Setting up libdebhelper-perl (13.11.4ubuntu3) ... Setting up libbrotli1:amd64 (1.0.9-2build8) ... Setting up libnghttp2-14:amd64 (1.54.0-1) ... Setting up libmagic1:amd64 (1:5.44-3) ... Setting up libdeflate0:amd64 (1.15-1) ... Setting up gettext-base (0.21-12) ... Setting up m4 (1.4.19-3) ... Setting up libqhull-r8.0:amd64 (2020.2-5) ... Setting up file (1:5.44-3) ... Setting up libgeos3.12.0:amd64 (3.12.0-1) ... Setting up libjbig0:amd64 (2.1-6.1ubuntu1) ... Setting up libpcre2-16-0:amd64 (10.42-1) ... Setting up libaec0:amd64 (1.0.6-1) ... Setting up gdal-data (3.7.0+dfsg-1) ... Setting up python-babel-localedata (2.10.3-1) ... Setting up libsnappy1v5:amd64 (1.1.9-3) ... Setting up libaom-dev:amd64 (3.6.1-1) ... Setting up libsasl2-modules-db:amd64 (2.1.28+dfsg1-1) ... Setting up libminizip-dev:amd64 (1.1-8build1) ... Setting up autotools-dev (20220109.1) ... Setting up libpcre2-32-0:amd64 (10.42-1) ... Setting up libblas3:amd64 (3.11.0-2) ... update-alternatives: using /usr/lib/x86_64-linux-gnu/blas/libblas.so.3 to provide /usr/lib/x86_64-linux-gnu/libblas.so.3 (libblas.so.3-x86_64-linux-gnu) in auto mode Setting up libexpat1-dev:amd64 (2.5.0-2) ... Setting up libsqlite3-dev:amd64 (3.42.0-1) ... Setting up libfreetype6:amd64 (2.12.1+dfsg-5) ... Setting up libnspr4:amd64 (2:4.35-1.1) ... Setting up librtmp1:amd64 (2.4+20151223.gitfa8646d.1-2build4) ... Setting up libfribidi0:amd64 (1.0.13-3) ... Setting up libimagequant0:amd64 (2.17.0-1) ... Setting up libssl-dev:amd64 (3.0.9-1ubuntu1) ... Setting up autopoint (0.21-12) ... Setting up icu-devtools (72.1-3ubuntu2) ... Setting up liblz4-dev:amd64 (1.9.4-1) ... Setting up libgeos-c1v5:amd64 (3.12.0-1) ... Setting up fonts-dejavu-core (2.37-6) ... Setting up unixodbc-common (2.3.11-4) ... Setting up libqhullcpp8.0:amd64 (2020.2-5) ... Setting up liblerc-dev:amd64 (4.0.0+ds-2ubuntu2) ... Setting up libjpeg-turbo8:amd64 (2.1.5-2ubuntu1) ... Setting up libdav1d6:amd64 (1.2.1-2) ... Setting up libltdl7:amd64 (2.4.7-5) ... Setting up libqhull-dev:amd64 (2020.2-5) ... Setting up libsasl2-2:amd64 (2.1.28+dfsg1-1) ... Setting up libssh-4:amd64 (0.10.5-2) ... Setting up libgfortran5:amd64 (13.1.0-6ubuntu1) ... Setting up autoconf (2.71-3) ... Setting up libwebp7:amd64 (1.2.4-0.2) ... Setting up liblzma-dev:amd64 (5.4.1-0.2) ... Setting up libgif7:amd64 (5.2.1-2.5) ... Setting up zlib1g-dev:amd64 (1:1.2.13.dfsg-1ubuntu4) ... Setting up libodbc2:amd64 (2.3.11-4) ... Setting up liburiparser1:amd64 (0.9.7+dfsg-2) ... Setting up libnuma1:amd64 (2.0.16-1) ... Setting up libpcre2-posix3:amd64 (10.42-1) ... Setting up librttopo1:amd64 (1.1.0-3) ... Setting up libfreexl1:amd64 (1.0.6-2) ... Setting up libgif-dev:amd64 (5.2.1-2.5) ... Setting up libfyba0:amd64 (4.1.1-8) ... Setting up libuchardet0:amd64 (0.0.7-1build2) ... Setting up libjson-perl (4.10000-1) ... Setting up libkmlbase1:amd64 (1.3.0-10) ... Setting up libblosc1:amd64 (1.21.3+ds-1) ... Setting up libopenjp2-7:amd64 (2.5.0-2) ... Setting up libsub-override-perl (0.09-4) ... Setting up libharfbuzz0b:amd64 (6.0.0+dfsg-3build1) ... Setting up sgml-base (1.31) ... Setting up libboost-dev:amd64 (1.74.0.3ubuntu7) ... Setting up libjs-jquery (3.6.1+dfsg+~3.5.14-1) ... Setting up libde265-0:amd64 (1.0.12-1) ... Setting up libwebpmux3:amd64 (1.2.4-0.2) ... Setting up libbsd0:amd64 (0.11.7-4) ... Setting up libdeflate-dev:amd64 (1.15-1) ... Setting up mailcap (3.70+nmu1ubuntu1) ... Setting up libelf1:amd64 (0.188-2.1) ... Setting up libogdi-dev (4.1.0+ds-6) ... Setting up libicu-dev:amd64 (72.1-3ubuntu2) ... Setting up libxml2:amd64 (2.9.14+dfsg-1.2) ... Setting up libldap2:amd64 (2.6.4+dfsg-1~exp1ubuntu1) ... Setting up libblas-dev:amd64 (3.11.0-2) ... update-alternatives: using /usr/lib/x86_64-linux-gnu/blas/libblas.so to provide /usr/lib/x86_64-linux-gnu/libblas.so (libblas.so-x86_64-linux-gnu) in auto mode Setting up libsz2:amd64 (1.0.6-1) ... Setting up libmysqlclient-dev (8.0.33-2) ... Setting up libpython3-stdlib:amd64 (3.11.4-1) ... Setting up libkmlxsd1:amd64 (1.3.0-10) ... Setting up libjs-underscore (1.13.4~dfsg+~1.11.4-3) ... Setting up libodbccr2:amd64 (2.3.11-4) ... Setting up gdal-plugins (3.7.0+dfsg-1) ... Setting up libkmldom1:amd64 (1.3.0-10) ... Setting up libjpeg8:amd64 (8c-2ubuntu11) ... Setting up automake (1:1.16.5-1.3) ... update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake (automake) in auto mode Setting up default-libmysqlclient-dev:amd64 (1.1.0) ... Setting up libfile-stripnondeterminism-perl (1.13.1-1) ... Setting up librttopo-dev:amd64 (1.1.0-3) ... Setting up python3.11 (3.11.4-1) ... Setting up libdw1:amd64 (0.188-2.1) ... Setting up libodbcinst2:amd64 (2.3.11-4) ... Setting up libjpeg-turbo8-dev:amd64 (2.1.5-2ubuntu1) ... Setting up libxdmcp6:amd64 (1:1.1.3-0ubuntu5) ... Setting up liblapack3:amd64 (3.11.0-2) ... update-alternatives: using /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3 to provide /usr/lib/x86_64-linux-gnu/liblapack.so.3 (liblapack.so.3-x86_64-linux-gnu) in auto mode Setting up libxcb1:amd64 (1.15-1) ... Setting up gettext (0.21-12) ... Setting up libkmlengine1:amd64 (1.3.0-10) ... Setting up mime-support (3.66) ... Setting up libpcre2-dev:amd64 (10.42-1) ... Setting up libkmlconvenience1:amd64 (1.3.0-10) ... Setting up libtool (2.4.7-5) ... Setting up libblosc-dev:amd64 (1.21.3+ds-1) ... Setting up fontconfig-config (2.14.1-4ubuntu1) ... Setting up libfreexl-dev:amd64 (1.0.6-2) ... Setting up libfyba-dev:amd64 (4.1.1-8) ... Setting up libwebpdemux2:amd64 (1.2.4-0.2) ... Setting up libpng-dev:amd64 (1.6.40-1) ... Setting up libaec-dev:amd64 (1.0.6-1) ... Setting up libarpack2:amd64 (3.8.0-3) ... Setting up libpq5:amd64 (15.3-1) ... Setting up libjbig-dev:amd64 (2.1-6.1ubuntu1) ... Setting up libsuperlu5:amd64 (5.3.0+dfsg1-2) ... Setting up libpq-dev (15.3-1) ... Setting up libcurl3-gnutls:amd64 (7.88.1-10ubuntu1) ... Setting up python3 (3.11.4-1) ... Setting up libnss3:amd64 (2:3.90-3) ... Setting up python3-sortedcontainers (2.4.0-2) ... Setting up libcfitsio10:amd64 (4.2.0-3) ... Setting up python3-markupsafe (2.1.3-1) ... Setting up python3-tz (2023.3-3) ... Setting up intltool-debian (0.35.0+20060710.6) ... Setting up liburiparser-dev (0.9.7+dfsg-2) ... Setting up python3-six (1.16.0-4) ... Setting up dh-autoreconf (20) ... Setting up libltdl-dev:amd64 (2.4.7-5) ... Setting up python3-roman (3.3-3) ... Setting up python3-jinja2 (3.1.2-1) ... Setting up libxml2-dev:amd64 (2.9.14+dfsg-1.2) ... Setting up libwebp-dev:amd64 (1.2.4-0.2) ... Setting up python3-packaging (23.1-1) ... Setting up python3-sqlparse (0.4.2-1ubuntu1) ... Setting up python3-certifi (2022.9.24-1) ... Setting up libde265-dev:amd64 (1.0.12-1) ... Setting up libopenjp2-7-dev:amd64 (2.5.0-2) ... Setting up python3.11-doc (3.11.4-1) ... Setting up python3-snowballstemmer (2.2.0-4) ... Setting up libkmlregionator1:amd64 (1.3.0-10) ... Setting up libgeos-dev (3.12.0-1) ... Setting up libraqm0:amd64 (0.10.1-1) ... Setting up libdav1d-dev:amd64 (1.2.1-2) ... Setting up liblapack-dev:amd64 (3.11.0-2) ... update-alternatives: using /usr/lib/x86_64-linux-gnu/lapack/liblapack.so to provide /usr/lib/x86_64-linux-gnu/liblapack.so (liblapack.so-x86_64-linux-gnu) in auto mode Setting up python3-idna (3.3-1) ... Setting up python3-h11 (0.14.0-1) ... Setting up libjs-sphinxdoc (5.3.0-4) ... Setting up python-requests-doc (2.28.1+dfsg-1ubuntu2) ... Setting up python3-urllib3 (1.26.12-1) ... Setting up libhdf4-0-alt (4.2.16-3) ... Setting up libx265-199:amd64 (3.5-2) ... Setting up dh-strip-nondeterminism (1.13.1-1) ... Setting up dwz (0.15-1) ... Setting up groff-base (1.22.4-10) ... Setting up libtiff6:amd64 (4.5.0-6ubuntu1) ... Setting up xml-core (0.18+nmu1) ... Setting up python3-exceptiongroup (1.1.0-1) ... Setting up debugedit (1:5.0-5) ... Setting up libcurl4:amd64 (7.88.1-10ubuntu1) ... Setting up libfontconfig1:amd64 (2.14.1-4ubuntu1) ... Setting up libjpeg8-dev:amd64 (8c-2ubuntu11) ... Setting up libsuperlu-dev:amd64 (5.3.0+dfsg1-2) ... Setting up libtiffxx6:amd64 (4.5.0-6ubuntu1) ... Setting up python3-lib2to3 (3.11.4-1) ... Setting up unixodbc-dev:amd64 (2.3.11-4) ... Setting up python3-doc (3.11.4-1) ... Setting up python3-asgiref (3.7.2-1) ... Setting up python3-cffi-backend:amd64 (1.15.1-5build1) ... Setting up python3-imagesize (1.4.1-1) ... Setting up python3-pkg-resources (67.8.0-1) ... Setting up python3-distutils (3.11.4-1) ... Setting up dh-python (6.20230603) ... Setting up libkml-dev:amd64 (1.3.0-10) ... Setting up python3-sniffio (1.2.0-1) ... Setting up python3-attr (23.1.0-1) ... Setting up sphinx-doc (5.3.0-4) ... Setting up libarpack2-dev:amd64 (3.8.0-3) ... Setting up libcfitsio-dev:amd64 (4.2.0-3) ... Setting up libxerces-c3.2:amd64 (3.2.4+debian-1build1) ... Setting up python3-wsproto (1.2.0-1) ... Setting up python3-setuptools (67.8.0-1) ... Setting up python3-async-generator (1.10-4) ... Setting up libarmadillo11 (1:11.4.2+dfsg-1) ... Setting up python3-tblib (1.7.0-3) ... Setting up libproj25:amd64 (9.2.1-1) ... Setting up python3-babel (2.10.3-1) ... update-alternatives: using /usr/bin/pybabel-python3 to provide /usr/bin/pybabel (pybabel) in auto mode Setting up python3-pbr (5.11.1-0ubuntu1) ... Setting up libsqlite3-mod-spatialite:amd64 (5.0.1-3) ... Setting up python3-alabaster (0.7.12-1) ... Setting up po-debconf (1.0.21+nmu1) ... Setting up python3-bcrypt (3.2.2-1) ... Setting up libheif1:amd64 (1.15.1-1) ... Setting up libjpeg-dev:amd64 (8c-2ubuntu11) ... Setting up python3-all (3.11.4-1) ... Setting up python3-yaml (6.0-3build1) ... Setting up man-db (2.11.2-2) ... Not building database; man-db/auto-update is not 'true'. Created symlink /etc/systemd/system/timers.target.wants/man-db.timer → /lib/systemd/system/man-db.timer. Setting up libgeotiff5:amd64 (1.7.1-2build1) ... Setting up python3-mock (4.0.3-4) ... Setting up python3-pil:amd64 (9.5.0-1) ... Setting up python3-pygments (2.15.1+dfsg-1) ... Setting up python3-chardet (5.1.0+dfsg-2) ... Setting up libtiff-dev:amd64 (4.5.0-6ubuntu1) ... Setting up libcurl4-openssl-dev:amd64 (7.88.1-10ubuntu1) ... Setting up libxerces-c-dev:amd64 (3.2.4+debian-1build1) ... Setting up sphinx-common (5.3.0-4) ... Setting up libx265-dev:amd64 (3.5-2) ... Setting up python3-requests (2.28.1+dfsg-1ubuntu2) ... Setting up libproj-dev:amd64 (9.2.1-1) ... Setting up python-psycopg2-doc (2.9.5-1build1) ... Setting up python-django-formtools-doc (2.3-3) ... Setting up python3-numpy (1:1.24.2-1) ... Setting up libpoppler126:amd64 (22.12.0-2ubuntu1) ... Setting up libhdf5-103-1:amd64 (1.10.8+repack1-1ubuntu1) ... Setting up libhdf5-cpp-103-1:amd64 (1.10.8+repack1-1ubuntu1) ... Setting up libhdf5-hl-100:amd64 (1.10.8+repack1-1ubuntu1) ... Setting up libpoppler-dev:amd64 (22.12.0-2ubuntu1) ... Setting up libspatialite7:amd64 (5.0.1-3) ... Setting up python3-outcome (1.2.0-1) ... Setting up libgeotiff-dev:amd64 (1.7.1-2build1) ... Setting up libpoppler-private-dev:amd64 (22.12.0-2ubuntu1) ... Setting up libheif-dev:amd64 (1.15.1-1) ... Setting up debhelper (13.11.4ubuntu3) ... Setting up libhdf5-hl-cpp-100:amd64 (1.10.8+repack1-1ubuntu1) ... Setting up python3-trio (0.22.0-0.2) ... Setting up libhdf5-fortran-102:amd64 (1.10.8+repack1-1ubuntu1) ... Setting up libspatialite-dev:amd64 (5.0.1-3) ... Setting up libnetcdf19:amd64 (1:4.9.2-1) ... Setting up libhdf5-hl-fortran-100:amd64 (1.10.8+repack1-1ubuntu1) ... Setting up python3-trio-websocket (0.10.3-1) ... Setting up libgdal33 (3.7.0+dfsg-1) ... Setting up libhdf5-dev (1.10.8+repack1-1ubuntu1) ... update-alternatives: using /usr/lib/x86_64-linux-gnu/pkgconfig/hdf5-serial.pc to provide /usr/lib/x86_64-linux-gnu/pkgconfig/hdf5.pc (hdf5.pc) in auto mode Setting up libnetcdf-dev (1:4.9.2-1) ... Setting up python3-selenium (4.10.0+dfsg-1) ... Setting up libarmadillo-dev (1:11.4.2+dfsg-1) ... Setting up libhdf4-alt-dev (4.2.16-3) ... Setting up libgdal-dev (3.7.0+dfsg-1) ... Processing triggers for libc-bin (2.37-0ubuntu2) ... Processing triggers for systemd (252.5-2ubuntu3) ... Processing triggers for sgml-base (1.31) ... Setting up docutils-common (0.19+dfsg-6) ... Processing triggers for sgml-base (1.31) ... Setting up python3-docutils (0.19+dfsg-6) ... Setting up python3-sphinx (5.3.0-4) ... Setting up sbuild-build-depends-main-dummy (0.invalid.0) ... +------------------------------------------------------------------------------+ | Check architectures | +------------------------------------------------------------------------------+ Arch check ok (amd64 included in all) +------------------------------------------------------------------------------+ | Build environment | +------------------------------------------------------------------------------+ Kernel: Linux 5.4.0-152-generic #169-Ubuntu SMP Tue Jun 6 22:23:09 UTC 2023 amd64 (x86_64) Toolchain package versions: binutils_2.40.50.20230622-1ubuntu1 dpkg-dev_1.21.22ubuntu1 g++-12_12.3.0-3ubuntu1 gcc-12_12.3.0-3ubuntu1 libc6-dev_2.37-0ubuntu2 libstdc++-12-dev_12.3.0-3ubuntu1 libstdc++6_13.1.0-6ubuntu1 linux-libc-dev_6.3.0-7.7 Package versions: adduser_3.134ubuntu1 advancecomp_2.5-1 apt_2.7.1 autoconf_2.71-3 automake_1:1.16.5-1.3 autopoint_0.21-12 autotools-dev_20220109.1 base-files_13ubuntu1 base-passwd_3.6.1 bash_5.2.15-2ubuntu1 binutils_2.40.50.20230622-1ubuntu1 binutils-common_2.40.50.20230622-1ubuntu1 binutils-x86-64-linux-gnu_2.40.50.20230622-1ubuntu1 bsdextrautils_2.38.1-5ubuntu2 bsdutils_1:2.38.1-5ubuntu2 build-essential_12.9ubuntu3 bzip2_1.0.8-5build1 ca-certificates_20230311ubuntu1 coreutils_9.1-1ubuntu2 cpp_4:12.2.0-3ubuntu1 cpp-12_12.3.0-3ubuntu1 dash_0.5.12-2ubuntu1 debconf_1.5.82 debhelper_13.11.4ubuntu3 debianutils_5.7-0.4 debugedit_1:5.0-5 default-libmysqlclient-dev_1.1.0 dh-autoreconf_20 dh-python_6.20230603 dh-strip-nondeterminism_1.13.1-1 diffutils_1:3.8-4 docutils-common_0.19+dfsg-6 docutils-doc_0.19+dfsg-6 dpkg_1.21.22ubuntu1 dpkg-dev_1.21.22ubuntu1 dwz_0.15-1 e2fsprogs_1.47.0-1ubuntu1 fakeroot_1.31-1.2 file_1:5.44-3 findutils_4.9.0-4ubuntu1 fontconfig-config_2.14.1-4ubuntu1 fonts-dejavu-core_2.37-6 fonts-mathjax_2.7.9+dfsg-1 g++_4:12.2.0-3ubuntu1 g++-12_12.3.0-3ubuntu1 gcc_4:12.2.0-3ubuntu1 gcc-12_12.3.0-3ubuntu1 gcc-12-base_12.3.0-3ubuntu1 gcc-13-base_13.1.0-6ubuntu1 gdal-data_3.7.0+dfsg-1 gdal-plugins_3.7.0+dfsg-1 gettext_0.21-12 gettext-base_0.21-12 gpg_2.2.40-1.1ubuntu1 gpg-agent_2.2.40-1.1ubuntu1 gpgconf_2.2.40-1.1ubuntu1 gpgv_2.2.40-1.1ubuntu1 grep_3.8-5 groff-base_1.22.4-10 gzip_1.12-1ubuntu1 hdf5-helpers_1.10.8+repack1-1ubuntu1 hostname_3.23+nmu1ubuntu1 icu-devtools_72.1-3ubuntu2 init_1.65.2 init-system-helpers_1.65.2 intltool-debian_0.35.0+20060710.6 libacl1_2.3.1-3 libaec-dev_1.0.6-1 libaec0_1.0.6-1 libaom-dev_3.6.1-1 libaom3_3.6.1-1 libapparmor1_3.0.8-1ubuntu3 libapt-pkg6.0_2.7.1 libarchive-zip-perl_1.68-1 libargon2-1_0~20190702+dfsg-3 libarmadillo-dev_1:11.4.2+dfsg-1 libarmadillo11_1:11.4.2+dfsg-1 libarpack2_3.8.0-3 libarpack2-dev_3.8.0-3 libasan8_13.1.0-6ubuntu1 libassuan0_2.5.5-5 libatomic1_13.1.0-6ubuntu1 libattr1_1:2.5.1-4 libaudit-common_1:3.0.9-1 libaudit1_1:3.0.9-1 libbinutils_2.40.50.20230622-1ubuntu1 libblas-dev_3.11.0-2 libblas3_3.11.0-2 libblkid1_2.38.1-5ubuntu2 libblosc-dev_1.21.3+ds-1 libblosc1_1.21.3+ds-1 libboost-dev_1.74.0.3ubuntu7 libboost1.74-dev_1.74.0+ds1-21.1ubuntu1 libbrotli1_1.0.9-2build8 libbsd0_0.11.7-4 libbz2-1.0_1.0.8-5build1 libc-bin_2.37-0ubuntu2 libc-dev-bin_2.37-0ubuntu2 libc6_2.37-0ubuntu2 libc6-dev_2.37-0ubuntu2 libcap-ng0_0.8.3-1build2 libcap2_1:2.66-4ubuntu1 libcc1-0_13.1.0-6ubuntu1 libcfitsio-dev_4.2.0-3 libcfitsio10_4.2.0-3 libcom-err2_1.47.0-1ubuntu1 libcrypt-dev_1:4.4.35-1 libcrypt1_1:4.4.35-1 libcryptsetup12_2:2.6.1-4ubuntu1 libctf-nobfd0_2.40.50.20230622-1ubuntu1 libctf0_2.40.50.20230622-1ubuntu1 libcurl3-gnutls_7.88.1-10ubuntu1 libcurl4_7.88.1-10ubuntu1 libcurl4-openssl-dev_7.88.1-10ubuntu1 libdav1d-dev_1.2.1-2 libdav1d6_1.2.1-2 libdb5.3_5.3.28+dfsg2-1 libde265-0_1.0.12-1 libde265-dev_1.0.12-1 libdebconfclient0_0.267ubuntu1 libdebhelper-perl_13.11.4ubuntu3 libdeflate-dev_1.15-1 libdeflate0_1.15-1 libdevmapper1.02.1_2:1.02.185-2ubuntu1 libdpkg-perl_1.21.22ubuntu1 libdw1_0.188-2.1 libelf1_0.188-2.1 libexpat1_2.5.0-2 libexpat1-dev_2.5.0-2 libext2fs2_1.47.0-1ubuntu1 libfakeroot_1.31-1.2 libfdisk1_2.38.1-5ubuntu2 libffi8_3.4.4-1 libfile-stripnondeterminism-perl_1.13.1-1 libfontconfig1_2.14.1-4ubuntu1 libfreetype6_2.12.1+dfsg-5 libfreexl-dev_1.0.6-2 libfreexl1_1.0.6-2 libfribidi0_1.0.13-3 libfyba-dev_4.1.1-8 libfyba0_4.1.1-8 libgcc-12-dev_12.3.0-3ubuntu1 libgcc-s1_13.1.0-6ubuntu1 libgcrypt20_1.10.1-3ubuntu1 libgdal-dev_3.7.0+dfsg-1 libgdal33_3.7.0+dfsg-1 libgdbm-compat4_1.23-3 libgdbm6_1.23-3 libgeos-c1v5_3.12.0-1 libgeos-dev_3.12.0-1 libgeos3.12.0_3.12.0-1 libgeotiff-dev_1.7.1-2build1 libgeotiff5_1.7.1-2build1 libgfortran5_13.1.0-6ubuntu1 libgif-dev_5.2.1-2.5 libgif7_5.2.1-2.5 libglib2.0-0_2.76.3-1ubuntu1 libgmp10_2:6.2.1+dfsg1-1.1ubuntu1 libgnutls30_3.7.9-2ubuntu1 libgomp1_13.1.0-6ubuntu1 libgpg-error0_1.46-1 libgprofng0_2.40.50.20230622-1ubuntu1 libgraphite2-3_1.3.14-1build2 libgssapi-krb5-2_1.20.1-2 libharfbuzz0b_6.0.0+dfsg-3build1 libhdf4-0-alt_4.2.16-3 libhdf4-alt-dev_4.2.16-3 libhdf5-103-1_1.10.8+repack1-1ubuntu1 libhdf5-cpp-103-1_1.10.8+repack1-1ubuntu1 libhdf5-dev_1.10.8+repack1-1ubuntu1 libhdf5-fortran-102_1.10.8+repack1-1ubuntu1 libhdf5-hl-100_1.10.8+repack1-1ubuntu1 libhdf5-hl-cpp-100_1.10.8+repack1-1ubuntu1 libhdf5-hl-fortran-100_1.10.8+repack1-1ubuntu1 libheif-dev_1.15.1-1 libheif1_1.15.1-1 libhogweed6_3.8.1-2 libicu-dev_72.1-3ubuntu2 libicu72_72.1-3ubuntu2 libidn2-0_2.3.3-1build1 libimagequant0_2.17.0-1 libip4tc2_1.8.7-1ubuntu7 libisl23_0.26-3 libitm1_13.1.0-6ubuntu1 libjansson4_2.14-2 libjbig-dev_2.1-6.1ubuntu1 libjbig0_2.1-6.1ubuntu1 libjpeg-dev_8c-2ubuntu11 libjpeg-turbo8_2.1.5-2ubuntu1 libjpeg-turbo8-dev_2.1.5-2ubuntu1 libjpeg8_8c-2ubuntu11 libjpeg8-dev_8c-2ubuntu11 libjs-jquery_3.6.1+dfsg+~3.5.14-1 libjs-mathjax_2.7.9+dfsg-1 libjs-sphinxdoc_5.3.0-4 libjs-underscore_1.13.4~dfsg+~1.11.4-3 libjson-c-dev_0.16-2 libjson-c5_0.16-2 libjson-perl_4.10000-1 libk5crypto3_1.20.1-2 libkeyutils1_1.6.3-2 libkml-dev_1.3.0-10 libkmlbase1_1.3.0-10 libkmlconvenience1_1.3.0-10 libkmldom1_1.3.0-10 libkmlengine1_1.3.0-10 libkmlregionator1_1.3.0-10 libkmlxsd1_1.3.0-10 libkmod2_30+20221128-1ubuntu1 libkrb5-3_1.20.1-2 libkrb5support0_1.20.1-2 liblapack-dev_3.11.0-2 liblapack3_3.11.0-2 liblcms2-2_2.14-2 libldap2_2.6.4+dfsg-1~exp1ubuntu1 liblerc-dev_4.0.0+ds-2ubuntu2 liblerc4_4.0.0+ds-2ubuntu2 liblockfile-bin_1.17-1build2 liblockfile1_1.17-1build2 liblsan0_13.1.0-6ubuntu1 libltdl-dev_2.4.7-5 libltdl7_2.4.7-5 liblz4-1_1.9.4-1 liblz4-dev_1.9.4-1 liblzma-dev_5.4.1-0.2 liblzma5_5.4.1-0.2 libmagic-mgc_1:5.44-3 libmagic1_1:5.44-3 libmd0_1.1.0-1 libminizip-dev_1.1-8build1 libminizip1_1.1-8build1 libmount1_2.38.1-5ubuntu2 libmpc3_1.3.1-1 libmpfr6_4.2.0-1 libmysqlclient-dev_8.0.33-2 libmysqlclient21_8.0.33-2 libncurses6_6.4-4 libncursesw6_6.4-4 libnetcdf-dev_1:4.9.2-1 libnetcdf19_1:4.9.2-1 libnettle8_3.8.1-2 libnghttp2-14_1.54.0-1 libnpth0_1.6-3build2 libnsl-dev_1.3.0-2build2 libnsl2_1.3.0-2build2 libnspr4_2:4.35-1.1 libnss3_2:3.90-3 libnuma1_2.0.16-1 libodbc2_2.3.11-4 libodbccr2_2.3.11-4 libodbcinst2_2.3.11-4 libogdi-dev_4.1.0+ds-6 libogdi4.1_4.1.0+ds-6 libopenjp2-7_2.5.0-2 libopenjp2-7-dev_2.5.0-2 libp11-kit0_0.24.1-2ubuntu1 libpam-modules_1.5.2-6ubuntu1 libpam-modules-bin_1.5.2-6ubuntu1 libpam-runtime_1.5.2-6ubuntu1 libpam0g_1.5.2-6ubuntu1 libpcre2-16-0_10.42-1 libpcre2-32-0_10.42-1 libpcre2-8-0_10.42-1 libpcre2-dev_10.42-1 libpcre2-posix3_10.42-1 libperl5.36_5.36.0-7ubuntu1 libpipeline1_1.5.7-1 libpng-dev_1.6.40-1 libpng16-16_1.6.40-1 libpoppler-dev_22.12.0-2ubuntu1 libpoppler-private-dev_22.12.0-2ubuntu1 libpoppler126_22.12.0-2ubuntu1 libpq-dev_15.3-1 libpq5_15.3-1 libproc2-0_2:4.0.3-1ubuntu1 libprocps8_2:3.3.17-7ubuntu1 libproj-dev_9.2.1-1 libproj25_9.2.1-1 libpsl5_0.21.2-1 libpython3-stdlib_3.11.4-1 libpython3.11-minimal_3.11.4-1 libpython3.11-stdlib_3.11.4-1 libqhull-dev_2020.2-5 libqhull-r8.0_2020.2-5 libqhull8.0_2020.2-5 libqhullcpp8.0_2020.2-5 libquadmath0_13.1.0-6ubuntu1 libraqm0_0.10.1-1 libreadline8_8.2-1.3 librtmp1_2.4+20151223.gitfa8646d.1-2build4 librttopo-dev_1.1.0-3 librttopo1_1.1.0-3 libsasl2-2_2.1.28+dfsg1-1 libsasl2-modules-db_2.1.28+dfsg1-1 libseccomp2_2.5.4-1ubuntu3 libselinux1_3.4-1build4 libsemanage-common_3.4-1build4 libsemanage2_3.4-1build4 libsepol2_3.4-2.1 libsmartcols1_2.38.1-5ubuntu2 libsnappy1v5_1.1.9-3 libspatialite-dev_5.0.1-3 libspatialite7_5.0.1-3 libsqlite3-0_3.42.0-1 libsqlite3-dev_3.42.0-1 libsqlite3-mod-spatialite_5.0.1-3 libss2_1.47.0-1ubuntu1 libssh-4_0.10.5-2 libssl-dev_3.0.9-1ubuntu1 libssl3_3.0.9-1ubuntu1 libstdc++-12-dev_12.3.0-3ubuntu1 libstdc++6_13.1.0-6ubuntu1 libsub-override-perl_0.09-4 libsuperlu-dev_5.3.0+dfsg1-2 libsuperlu5_5.3.0+dfsg1-2 libsystemd-shared_252.5-2ubuntu3 libsystemd0_252.5-2ubuntu3 libsz2_1.0.6-1 libtasn1-6_4.19.0-2 libtiff-dev_4.5.0-6ubuntu1 libtiff6_4.5.0-6ubuntu1 libtiffxx6_4.5.0-6ubuntu1 libtinfo6_6.4-4 libtirpc-common_1.3.3+ds-1 libtirpc-dev_1.3.3+ds-1 libtirpc3_1.3.3+ds-1 libtool_2.4.7-5 libtsan2_13.1.0-6ubuntu1 libubsan1_13.1.0-6ubuntu1 libuchardet0_0.0.7-1build2 libudev1_252.5-2ubuntu3 libunistring2_1.0-2 liburiparser-dev_0.9.7+dfsg-2 liburiparser1_0.9.7+dfsg-2 libuuid1_2.38.1-5ubuntu2 libwebp-dev_1.2.4-0.2 libwebp7_1.2.4-0.2 libwebpdemux2_1.2.4-0.2 libwebpmux3_1.2.4-0.2 libx265-199_3.5-2 libx265-dev_3.5-2 libxau6_1:1.0.9-1build5 libxcb1_1.15-1 libxdmcp6_1:1.1.3-0ubuntu5 libxerces-c-dev_3.2.4+debian-1build1 libxerces-c3.2_3.2.4+debian-1build1 libxml2_2.9.14+dfsg-1.2 libxml2-dev_2.9.14+dfsg-1.2 libxxhash0_0.8.1-1 libyaml-0-2_0.2.5-1 libzstd-dev_1.5.4+dfsg2-5 libzstd1_1.5.4+dfsg2-5 linux-libc-dev_6.3.0-7.7 lockfile-progs_0.1.19build1 login_1:4.13+dfsg1-1ubuntu1 logsave_1.47.0-1ubuntu1 lsb-base_11.6 lto-disabled-list_41 m4_1.4.19-3 mailcap_3.70+nmu1ubuntu1 make_4.3-4.1build1 man-db_2.11.2-2 mawk_1.3.4.20230525-1 media-types_10.0.0 mime-support_3.66 mount_2.38.1-5ubuntu2 mysql-common_5.8+1.1.0 ncurses-base_6.4-4 ncurses-bin_6.4-4 openssl_3.0.9-1ubuntu1 optipng_0.7.7-2build1 passwd_1:4.13+dfsg1-1ubuntu1 patch_2.7.6-7build2 perl_5.36.0-7ubuntu1 perl-base_5.36.0-7ubuntu1 perl-modules-5.36_5.36.0-7ubuntu1 pinentry-curses_1.2.1-1ubuntu1 pkgbinarymangler_153 po-debconf_1.0.21+nmu1 policyrcd-script-zg2_0.1-3.1 procps_2:4.0.3-1ubuntu1 proj-data_9.2.1-1 python-babel-localedata_2.10.3-1 python-django-formtools-doc_2.3-3 python-psycopg2-doc_2.9.5-1build1 python-requests-doc_2.28.1+dfsg-1ubuntu2 python3_3.11.4-1 python3-alabaster_0.7.12-1 python3-all_3.11.4-1 python3-asgiref_3.7.2-1 python3-async-generator_1.10-4 python3-attr_23.1.0-1 python3-babel_2.10.3-1 python3-bcrypt_3.2.2-1 python3-certifi_2022.9.24-1 python3-cffi-backend_1.15.1-5build1 python3-chardet_5.1.0+dfsg-2 python3-distutils_3.11.4-1 python3-doc_3.11.4-1 python3-docutils_0.19+dfsg-6 python3-exceptiongroup_1.1.0-1 python3-h11_0.14.0-1 python3-idna_3.3-1 python3-imagesize_1.4.1-1 python3-jinja2_3.1.2-1 python3-lib2to3_3.11.4-1 python3-markupsafe_2.1.3-1 python3-minimal_3.11.4-1 python3-mock_4.0.3-4 python3-numpy_1:1.24.2-1 python3-outcome_1.2.0-1 python3-packaging_23.1-1 python3-pbr_5.11.1-0ubuntu1 python3-pil_9.5.0-1 python3-pkg-resources_67.8.0-1 python3-pygments_2.15.1+dfsg-1 python3-requests_2.28.1+dfsg-1ubuntu2 python3-roman_3.3-3 python3-selenium_4.10.0+dfsg-1 python3-setuptools_67.8.0-1 python3-six_1.16.0-4 python3-sniffio_1.2.0-1 python3-snowballstemmer_2.2.0-4 python3-sortedcontainers_2.4.0-2 python3-sphinx_5.3.0-4 python3-sqlparse_0.4.2-1ubuntu1 python3-tblib_1.7.0-3 python3-trio_0.22.0-0.2 python3-trio-websocket_0.10.3-1 python3-tz_2023.3-3 python3-urllib3_1.26.12-1 python3-wsproto_1.2.0-1 python3-yaml_6.0-3build1 python3.11_3.11.4-1 python3.11-doc_3.11.4-1 python3.11-minimal_3.11.4-1 readline-common_8.2-1.3 rpcsvc-proto_1.4.2-0ubuntu6 sbuild-build-depends-main-dummy_0.invalid.0 sed_4.9-1 sensible-utils_0.0.20 sgml-base_1.31 sphinx-common_5.3.0-4 sphinx-doc_5.3.0-4 systemd_252.5-2ubuntu3 systemd-sysv_252.5-2ubuntu3 sysvinit-utils_3.06-4ubuntu1 tar_1.34+dfsg-1.2ubuntu1 tzdata_2023c-4exp1ubuntu1 ubuntu-keyring_2021.03.26 unixodbc-common_2.3.11-4 unixodbc-dev_2.3.11-4 usrmerge_35ubuntu1 util-linux_2.38.1-5ubuntu2 util-linux-extra_2.38.1-5ubuntu2 xml-core_0.18+nmu1 xz-utils_5.4.1-0.2 zlib1g_1:1.2.13.dfsg-1ubuntu4 zlib1g-dev_1:1.2.13.dfsg-1ubuntu4 +------------------------------------------------------------------------------+ | Build | +------------------------------------------------------------------------------+ Unpack source ------------- -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 3.0 (quilt) Source: python-django Binary: python3-django, python-django-doc Architecture: all Version: 3:3.2.19-1ubuntu3 Maintainer: Ubuntu Developers Uploaders: Luke Faraone , Raphaël Hertzog , Brian May , Chris Lamb , Homepage: http://www.djangoproject.com/ Standards-Version: 4.6.2 Vcs-Browser: https://salsa.debian.org/python-team/packages/python-django Vcs-Git: https://salsa.debian.org/python-team/packages/python-django.git Testsuite: autopkgtest Testsuite-Triggers: @builddeps@ Build-Depends: debhelper-compat (= 13), dh-python, dpkg-dev (>= 1.17.14), libgdal-dev , libsqlite3-mod-spatialite , python-django-formtools-doc , python-psycopg2-doc , python3-all, python3-asgiref , python3-bcrypt , python3-doc , python3-docutils , python3-jinja2 , python3-mock , python3-numpy , python3-pil , python3-selenium , python3-setuptools, python3-sphinx, python3-sqlparse , python3-tblib , python3-tz , python3-yaml , sphinx-doc Build-Depends-Indep: libjs-jquery Package-List: python-django-doc deb doc optional arch=all python3-django deb python optional arch=all Checksums-Sha1: 42f62327acc78f37f69cba058232fbfd7d8c77cd 9832772 python-django_3.2.19.orig.tar.gz 0906229c9c159ff60f98c604784ebd202a01ebfc 38920 python-django_3.2.19-1ubuntu3.debian.tar.xz Checksums-Sha256: 031365bae96814da19c10706218c44dff3b654cc4de20a98bd2d29b9bde469f0 9832772 python-django_3.2.19.orig.tar.gz 34af3ec3dd9004173178b99dc8f5b2bbdb71380f60c460a2c8a7701392559a19 38920 python-django_3.2.19-1ubuntu3.debian.tar.xz Files: d84f0b8669678fea14579d7400a521e2 9832772 python-django_3.2.19.orig.tar.gz 61370fd142e9bf7ef89c92827996caf7 38920 python-django_3.2.19-1ubuntu3.debian.tar.xz Original-Maintainer: Debian Python Team -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmScGV8ACgkQr8/sjmac 4cIB2BAAjtFw8lg4X+MeIGVIYT0uG6idNGH77qsjZV7eVj89qmp0NHvYM+NbQLzl nUoGk5YCdIIpz3YSYG35iQu5xjHz2iDc4aeUqvvtML5DNHQa2/D2vwXUfS5Z7O+1 +7R8unrr5IFSpf7X8RRmoP1bzoZbbJK6RrqQmfGI2r/S0cU0lMyGmyw02+yL0M3U XcaY3oyr5YuA/yLI8639yYj2eKzJgr5HbtDXdlrXhrq5DtCSqBkiDuuKizlTb5As T6ITEXe3kXw7yAhE0i5arPGl8bhnsrrDvUm+0CBXMPf8E+x3vpxCi1Em+g2RBbV2 RlvDt7PGXCsqQ/WB0+yUQqtqESJqQ3t8nhkAeRU9jfiboHfrAWzFGlaDifXZo34o 4ZgPw3kDjvGdAlXoXUgfcEQYPYxPp4PwX/43I5Uy3NUPeRh2Xxtjd3GprwmEFU9z Y5v+W5VeZV8v7JvXmAllPf+dYeQzYoTuxp+ven7q03szf10eNhwX15auFZ3vomOC olVvv2z6h3nfnNbqWCZ8ZPRPfUhmDVA4nOMewm5d3gHER4Nu6pcKn4EtG6Iubqft lLgTGEGZ5XJkuzf5/fu1/KPUZtEdR21BrRAxiSe7Nv2eeu2INH3ryD1r4p6GQk/0 TH77uL+vrnuAtGDzMhKln3G3mvSgbfHIgP+W9rsjPz44yuBjHnM= =9SDx -----END PGP SIGNATURE----- gpgv: Signature made Wed Jun 28 11:28:31 2023 UTC gpgv: using RSA key 25E3FF2D7F469DBE7D0D4E50AFCFEC8E669CE1C2 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./python-django_3.2.19-1ubuntu3.dsc: no acceptable signature found dpkg-source: info: extracting python-django in /<> dpkg-source: info: unpacking python-django_3.2.19.orig.tar.gz dpkg-source: info: unpacking python-django_3.2.19-1ubuntu3.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying 0001-disable-sources-in-sphinxdoc.diff dpkg-source: info: applying 0002-use_debian_geoip_database_as_default.diff dpkg-source: info: applying 0004-Use-locally-installed-documentation-sources.patch dpkg-source: info: applying 0004-Set-the-default-shebang-to-new-projects-to-use-Pytho.patch dpkg-source: info: applying 0005-Use-usr-bin-env-python3-shebang-for-django-admin.py.patch dpkg-source: info: applying 0006-Fixed-32690-Fixed-__in-lookup-crash-when-combining-w.patch dpkg-source: info: applying 0007-Refs-32786-Made-Query.clear_ordering-not-to-cause-si.patch dpkg-source: info: applying 0008-Refs-32690-Altered-lookups-Query-rhs-alterations-dur.patch dpkg-source: info: applying 0009-Fixed-33282-Fixed-a-crash-when-OR-ing-subquery-and-a.patch dpkg-source: info: applying 0011-Moved-RequestSite-import-to-the-toplevel.patch dpkg-source: info: applying 0012-Add-Python-3.11-support-for-tests.patch dpkg-source: info: applying fix-url-validator.patch Check disk space ---------------- Sufficient free space for build User Environment ---------------- APT_CONFIG=/var/lib/sbuild/apt.conf DEB_BUILD_OPTIONS=parallel=4 HOME=/sbuild-nonexistent LANG=C.UTF-8 LC_ALL=C.UTF-8 LOGNAME=buildd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-26344941 SCHROOT_CHROOT_NAME=build-PACKAGEBUILD-26344941 SCHROOT_COMMAND=env SCHROOT_GID=2501 SCHROOT_GROUP=buildd SCHROOT_SESSION_ID=build-PACKAGEBUILD-26344941 SCHROOT_UID=2001 SCHROOT_USER=buildd SHELL=/bin/sh TERM=unknown USER=buildd V=1 dpkg-buildpackage ----------------- Command: dpkg-buildpackage -us -uc -mLaunchpad Build Daemon -b -rfakeroot dpkg-buildpackage: info: source package python-django dpkg-buildpackage: info: source version 3:3.2.19-1ubuntu3 dpkg-buildpackage: info: source distribution mantic dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 debian/rules clean dh clean --with sphinxdoc,python3 --buildsystem=pybuild debian/rules override_dh_auto_clean make[1]: Entering directory '/<>' dh_auto_clean I: pybuild base:275: python3.11 setup.py clean /usr/lib/python3/dist-packages/setuptools/dist.py:755: SetuptoolsDeprecationWarning: Invalid dash-separated options !! ******************************************************************************** Usage of dash-separated 'install-script' will not be supported in future versions. Please use the underscore name 'install_script' instead. By 2023-Sep-26, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! opt = self.warn_dash_deprecation(opt, section) running clean removing '/<>/.pybuild/cpython3_3.11_django/build' (and everything under it) 'build/bdist.linux-x86_64' does not exist -- can't clean it 'build/scripts-3.11' does not exist -- can't clean it make -C docs clean make[2]: Entering directory '/<>/docs' rm -rf _build/* make[2]: Leaving directory '/<>/docs' make[1]: Leaving directory '/<>' dh_autoreconf_clean -O--buildsystem=pybuild debian/rules override_dh_clean make[1]: Entering directory '/<>' # backup~ is used in tests dh_clean -Xbackup~ make[1]: Leaving directory '/<>' debian/rules binary dh binary --with sphinxdoc,python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:275: python3.11 setup.py config /usr/lib/python3/dist-packages/setuptools/dist.py:755: SetuptoolsDeprecationWarning: Invalid dash-separated options !! ******************************************************************************** Usage of dash-separated 'install-script' will not be supported in future versions. Please use the underscore name 'install_script' instead. By 2023-Sep-26, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! opt = self.warn_dash_deprecation(opt, section) running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build I: pybuild base:275: /usr/bin/python3 setup.py build /usr/lib/python3/dist-packages/setuptools/dist.py:755: SetuptoolsDeprecationWarning: Invalid dash-separated options !! ******************************************************************************** Usage of dash-separated 'install-script' will not be supported in future versions. Please use the underscore name 'install_script' instead. By 2023-Sep-26, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! opt = self.warn_dash_deprecation(opt, section) running build running build_py creating /<>/.pybuild/cpython3_3.11_django/build/django copying django/__main__.py -> /<>/.pybuild/cpython3_3.11_django/build/django copying django/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django copying django/shortcuts.py -> /<>/.pybuild/cpython3_3.11_django/build/django creating /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/security.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/locale.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/gzip.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/cache.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/http.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/clickjacking.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/common.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware copying django/middleware/csrf.py -> /<>/.pybuild/cpython3_3.11_django/build/django/middleware creating /<>/.pybuild/cpython3_3.11_django/build/django/http copying django/http/cookie.py -> /<>/.pybuild/cpython3_3.11_django/build/django/http copying django/http/request.py -> /<>/.pybuild/cpython3_3.11_django/build/django/http copying django/http/multipartparser.py -> /<>/.pybuild/cpython3_3.11_django/build/django/http copying django/http/response.py -> /<>/.pybuild/cpython3_3.11_django/build/django/http copying django/http/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/http creating /<>/.pybuild/cpython3_3.11_django/build/django/conf copying django/conf/global_settings.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf copying django/conf/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib copying django/contrib/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib creating /<>/.pybuild/cpython3_3.11_django/build/django/dispatch copying django/dispatch/dispatcher.py -> /<>/.pybuild/cpython3_3.11_django/build/django/dispatch copying django/dispatch/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/dispatch creating /<>/.pybuild/cpython3_3.11_django/build/django/test copying django/test/testcases.py -> /<>/.pybuild/cpython3_3.11_django/build/django/test copying django/test/signals.py -> /<>/.pybuild/cpython3_3.11_django/build/django/test copying django/test/runner.py -> /<>/.pybuild/cpython3_3.11_django/build/django/test copying django/test/selenium.py -> /<>/.pybuild/cpython3_3.11_django/build/django/test copying django/test/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/test copying django/test/html.py -> /<>/.pybuild/cpython3_3.11_django/build/django/test copying django/test/client.py -> /<>/.pybuild/cpython3_3.11_django/build/django/test copying django/test/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/test creating /<>/.pybuild/cpython3_3.11_django/build/django/urls copying django/urls/resolvers.py -> /<>/.pybuild/cpython3_3.11_django/build/django/urls copying django/urls/conf.py -> /<>/.pybuild/cpython3_3.11_django/build/django/urls copying django/urls/exceptions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/urls copying django/urls/converters.py -> /<>/.pybuild/cpython3_3.11_django/build/django/urls copying django/urls/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/urls copying django/urls/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/urls copying django/urls/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/urls creating /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/defaulttags.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/engine.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/autoreload.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/exceptions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/smartif.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/response.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/loader.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/defaultfilters.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/context.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/loader_tags.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/context_processors.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/library.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template copying django/template/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template creating /<>/.pybuild/cpython3_3.11_django/build/django/templatetags copying django/templatetags/static.py -> /<>/.pybuild/cpython3_3.11_django/build/django/templatetags copying django/templatetags/i18n.py -> /<>/.pybuild/cpython3_3.11_django/build/django/templatetags copying django/templatetags/cache.py -> /<>/.pybuild/cpython3_3.11_django/build/django/templatetags copying django/templatetags/l10n.py -> /<>/.pybuild/cpython3_3.11_django/build/django/templatetags copying django/templatetags/tz.py -> /<>/.pybuild/cpython3_3.11_django/build/django/templatetags copying django/templatetags/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/templatetags creating /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/renderers.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/fields.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/boundfield.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/formsets.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/widgets.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/forms.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms copying django/forms/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/forms creating /<>/.pybuild/cpython3_3.11_django/build/django/core copying django/core/validators.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core copying django/core/signals.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core copying django/core/paginator.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core copying django/core/exceptions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core copying django/core/asgi.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core copying django/core/wsgi.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core copying django/core/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core copying django/core/signing.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core creating /<>/.pybuild/cpython3_3.11_django/build/django/views copying django/views/static.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views copying django/views/i18n.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views copying django/views/debug.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views copying django/views/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views copying django/views/csrf.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views copying django/views/defaults.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views creating /<>/.pybuild/cpython3_3.11_django/build/django/db copying django/db/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db copying django/db/transaction.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db copying django/db/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db creating /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/safestring.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/crypto.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/functional.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/numberformat.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/duration.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/text.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/connection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/deconstruct.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/autoreload.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/datastructures.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/inspect.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/cache.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/asyncio.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/dateformat.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/decorators.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/version.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/datetime_safe.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/baseconv.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/http.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/jslex.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/log.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/archive.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/timezone.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/dateparse.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/feedgenerator.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/xmlutils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/ipv6.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/topological_sort.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/timesince.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/tree.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/itercompat.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/dates.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/encoding.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/module_loading.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/html.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/deprecation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/_os.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/hashable.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/regex_helper.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/lorem_ipsum.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils copying django/utils/termcolors.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils creating /<>/.pybuild/cpython3_3.11_django/build/django/apps copying django/apps/registry.py -> /<>/.pybuild/cpython3_3.11_django/build/django/apps copying django/apps/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/apps copying django/apps/config.py -> /<>/.pybuild/cpython3_3.11_django/build/django/apps creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale copying django/conf/locale/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/urls copying django/conf/urls/static.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/urls copying django/conf/urls/i18n.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/urls copying django/conf/urls/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/urls creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_NI copying django/conf/locale/es_NI/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_NI copying django/conf/locale/es_NI/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_NI creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/et copying django/conf/locale/et/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/et copying django/conf/locale/et/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hans copying django/conf/locale/zh_Hans/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hans copying django/conf/locale/zh_Hans/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fi copying django/conf/locale/fi/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fi copying django/conf/locale/fi/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt_BR copying django/conf/locale/pt_BR/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt_BR copying django/conf/locale/pt_BR/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ru copying django/conf/locale/ru/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ru copying django/conf/locale/ru/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bg copying django/conf/locale/bg/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bg copying django/conf/locale/bg/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_GB copying django/conf/locale/en_GB/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_GB copying django/conf/locale/en_GB/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr copying django/conf/locale/sr/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr copying django/conf/locale/sr/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/el copying django/conf/locale/el/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/el copying django/conf/locale/el/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kn copying django/conf/locale/kn/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kn copying django/conf/locale/kn/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/th copying django/conf/locale/th/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/th copying django/conf/locale/th/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eu copying django/conf/locale/eu/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eu copying django/conf/locale/eu/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar_DZ copying django/conf/locale/ar_DZ/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar_DZ copying django/conf/locale/ar_DZ/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uz copying django/conf/locale/uz/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uz copying django/conf/locale/uz/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uz creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cy copying django/conf/locale/cy/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cy copying django/conf/locale/cy/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pl copying django/conf/locale/pl/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pl copying django/conf/locale/pl/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar copying django/conf/locale/ar/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar copying django/conf/locale/ar/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fa copying django/conf/locale/fa/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fa copying django/conf/locale/fa/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/it copying django/conf/locale/it/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/it copying django/conf/locale/it/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/az copying django/conf/locale/az/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/az copying django/conf/locale/az/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_MX copying django/conf/locale/es_MX/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_MX copying django/conf/locale/es_MX/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mk copying django/conf/locale/mk/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mk copying django/conf/locale/mk/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ga copying django/conf/locale/ga/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ga copying django/conf/locale/ga/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tk copying django/conf/locale/tk/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tk copying django/conf/locale/tk/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tk creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/da copying django/conf/locale/da/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/da copying django/conf/locale/da/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tg copying django/conf/locale/tg/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tg copying django/conf/locale/tg/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sl copying django/conf/locale/sl/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sl copying django/conf/locale/sl/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ky copying django/conf/locale/ky/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ky copying django/conf/locale/ky/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nb copying django/conf/locale/nb/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nb copying django/conf/locale/nb/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fr copying django/conf/locale/fr/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fr copying django/conf/locale/fr/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gl copying django/conf/locale/gl/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gl copying django/conf/locale/gl/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tr copying django/conf/locale/tr/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tr copying django/conf/locale/tr/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ig copying django/conf/locale/ig/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ig copying django/conf/locale/ig/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ig creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lv copying django/conf/locale/lv/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lv copying django/conf/locale/lv/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_AU copying django/conf/locale/en_AU/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_AU copying django/conf/locale/en_AU/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es copying django/conf/locale/es/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es copying django/conf/locale/es/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hi copying django/conf/locale/hi/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hi copying django/conf/locale/hi/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/te copying django/conf/locale/te/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/te copying django/conf/locale/te/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/km copying django/conf/locale/km/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/km copying django/conf/locale/km/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fy copying django/conf/locale/fy/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fy copying django/conf/locale/fy/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_PR copying django/conf/locale/es_PR/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_PR copying django/conf/locale/es_PR/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_PR creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hr copying django/conf/locale/hr/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hr copying django/conf/locale/hr/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eo copying django/conf/locale/eo/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eo copying django/conf/locale/eo/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sv copying django/conf/locale/sv/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sv copying django/conf/locale/sv/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ka copying django/conf/locale/ka/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ka copying django/conf/locale/ka/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ro copying django/conf/locale/ro/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ro copying django/conf/locale/ro/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sq copying django/conf/locale/sq/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sq copying django/conf/locale/sq/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bs copying django/conf/locale/bs/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bs copying django/conf/locale/bs/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ca copying django/conf/locale/ca/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ca copying django/conf/locale/ca/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_CO copying django/conf/locale/es_CO/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_CO copying django/conf/locale/es_CO/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ta copying django/conf/locale/ta/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ta copying django/conf/locale/ta/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/he copying django/conf/locale/he/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/he copying django/conf/locale/he/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ko copying django/conf/locale/ko/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ko copying django/conf/locale/ko/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nl copying django/conf/locale/nl/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nl copying django/conf/locale/nl/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ja copying django/conf/locale/ja/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ja copying django/conf/locale/ja/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/is copying django/conf/locale/is/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/is copying django/conf/locale/is/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ml copying django/conf/locale/ml/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ml copying django/conf/locale/ml/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de_CH copying django/conf/locale/de_CH/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de_CH copying django/conf/locale/de_CH/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de_CH creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/id copying django/conf/locale/id/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/id copying django/conf/locale/id/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gd copying django/conf/locale/gd/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gd copying django/conf/locale/gd/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cs copying django/conf/locale/cs/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cs copying django/conf/locale/cs/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mn copying django/conf/locale/mn/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mn copying django/conf/locale/mn/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de copying django/conf/locale/de/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de copying django/conf/locale/de/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt copying django/conf/locale/pt/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt copying django/conf/locale/pt/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lt copying django/conf/locale/lt/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lt copying django/conf/locale/lt/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sk copying django/conf/locale/sk/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sk copying django/conf/locale/sk/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr_Latn copying django/conf/locale/sr_Latn/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr_Latn copying django/conf/locale/sr_Latn/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uk copying django/conf/locale/uk/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uk copying django/conf/locale/uk/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hant copying django/conf/locale/zh_Hant/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hant copying django/conf/locale/zh_Hant/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hu copying django/conf/locale/hu/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hu copying django/conf/locale/hu/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_AR copying django/conf/locale/es_AR/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_AR copying django/conf/locale/es_AR/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/vi copying django/conf/locale/vi/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/vi copying django/conf/locale/vi/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bn copying django/conf/locale/bn/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bn copying django/conf/locale/bn/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nn copying django/conf/locale/nn/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nn copying django/conf/locale/nn/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en copying django/conf/locale/en/formats.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en copying django/conf/locale/en/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis copying django/contrib/gis/geometry.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis copying django/contrib/gis/measure.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis copying django/contrib/gis/ptr.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis copying django/contrib/gis/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis copying django/contrib/gis/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis copying django/contrib/gis/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis copying django/contrib/gis/shortcuts.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis copying django/contrib/gis/feeds.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps copying django/contrib/sitemaps/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps copying django/contrib/sitemaps/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps copying django/contrib/sitemaps/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/indexes.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/search.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/validators.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/signals.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/functions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/lookups.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/constraints.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/serializers.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres copying django/contrib/postgres/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/actions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/checks.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/decorators.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/exceptions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/tests.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/sites.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/widgets.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/forms.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/options.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/helpers.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/filters.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin copying django/contrib/admin/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/requests.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/checks.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/admin.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/managers.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/management.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/shortcuts.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites copying django/contrib/sites/middleware.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs copying django/contrib/admindocs/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs copying django/contrib/admindocs/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs copying django/contrib/admindocs/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs copying django/contrib/admindocs/urls.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs copying django/contrib/admindocs/middleware.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs copying django/contrib/admindocs/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/finders.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/storage.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/checks.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/handlers.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/urls.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/testing.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles copying django/contrib/staticfiles/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions copying django/contrib/sessions/base_session.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions copying django/contrib/sessions/exceptions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions copying django/contrib/sessions/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions copying django/contrib/sessions/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions copying django/contrib/sessions/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions copying django/contrib/sessions/middleware.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions copying django/contrib/sessions/serializers.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/validators.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/tokens.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/signals.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/mixins.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/checks.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/admin.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/decorators.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/hashers.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/forms.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/base_user.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/password_validation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/backends.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/context_processors.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/urls.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth copying django/contrib/auth/middleware.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes copying django/contrib/contenttypes/fields.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes copying django/contrib/contenttypes/checks.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes copying django/contrib/contenttypes/admin.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes copying django/contrib/contenttypes/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes copying django/contrib/contenttypes/forms.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes copying django/contrib/contenttypes/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes copying django/contrib/contenttypes/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes copying django/contrib/contenttypes/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize copying django/contrib/humanize/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize copying django/contrib/humanize/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages copying django/contrib/messages/api.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages copying django/contrib/messages/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages copying django/contrib/messages/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages copying django/contrib/messages/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages copying django/contrib/messages/constants.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages copying django/contrib/messages/context_processors.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages copying django/contrib/messages/middleware.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages copying django/contrib/messages/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/admin.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/forms.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/sitemaps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/urls.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages copying django/contrib/flatpages/middleware.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects copying django/contrib/redirects/admin.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects copying django/contrib/redirects/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects copying django/contrib/redirects/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects copying django/contrib/redirects/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects copying django/contrib/redirects/middleware.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/syndication copying django/contrib/syndication/apps.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/syndication copying django/contrib/syndication/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/syndication copying django/contrib/syndication/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/syndication creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/feature.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/error.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/geometries.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/srs.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/envelope.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/driver.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/layer.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/field.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/geomtype.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/libgdal.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/gdal/datasource.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/serializers copying django/contrib/gis/serializers/geojson.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/serializers copying django/contrib/gis/serializers/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/serializers creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/sitemaps copying django/contrib/gis/sitemaps/kml.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/sitemaps copying django/contrib/gis/sitemaps/views.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/sitemaps copying django/contrib/gis/sitemaps/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/sitemaps creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/admin copying django/contrib/gis/admin/widgets.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/admin copying django/contrib/gis/admin/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/admin copying django/contrib/gis/admin/options.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/admin creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/error.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/geometry.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/factory.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/mutable_list.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/io.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/point.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/polygon.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/linestring.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/collections.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/libgeos.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/coordseq.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos copying django/contrib/gis/geos/prepared.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/forms copying django/contrib/gis/forms/fields.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/forms copying django/contrib/gis/forms/widgets.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/forms copying django/contrib/gis/forms/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/forms creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db copying django/contrib/gis/db/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/utils copying django/contrib/gis/utils/ogrinfo.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/utils copying django/contrib/gis/utils/layermapping.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/utils copying django/contrib/gis/utils/srs.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/utils copying django/contrib/gis/utils/ogrinspect.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/utils copying django/contrib/gis/utils/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/utils creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geoip2 copying django/contrib/gis/geoip2/resources.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geoip2 copying django/contrib/gis/geoip2/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geoip2 copying django/contrib/gis/geoip2/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geoip2 creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/management copying django/contrib/gis/management/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/management creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/geom.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/srs.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/errcheck.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/raster.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/ds.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/prototypes copying django/contrib/gis/gdal/prototypes/generation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/prototypes creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/source.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/band.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/const.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/raster copying django/contrib/gis/gdal/raster/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal/raster creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/topology.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/geom.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/predicates.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/errcheck.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/threadsafe.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/misc.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/io.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/coordseq.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes copying django/contrib/gis/geos/prototypes/prepared.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos/prototypes creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends copying django/contrib/gis/db/backends/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends copying django/contrib/gis/db/backends/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models copying django/contrib/gis/db/models/fields.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models copying django/contrib/gis/db/models/functions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models copying django/contrib/gis/db/models/lookups.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models copying django/contrib/gis/db/models/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models copying django/contrib/gis/db/models/aggregates.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models copying django/contrib/gis/db/models/proxy.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/adapter.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite copying django/contrib/gis/db/backends/spatialite/client.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/spatialite creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/mysql copying django/contrib/gis/db/backends/mysql/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/mysql creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/adapter.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle copying django/contrib/gis/db/backends/oracle/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/oracle creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/adapter.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/base copying django/contrib/gis/db/backends/base/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/base creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/pgraster.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/adapter.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/const.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis copying django/contrib/gis/db/backends/postgis/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/backends/postgis creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models/sql copying django/contrib/gis/db/models/sql/conversion.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models/sql copying django/contrib/gis/db/models/sql/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/db/models/sql creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/management/commands copying django/contrib/gis/management/commands/ogrinspect.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/management/commands copying django/contrib/gis/management/commands/inspectdb.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/management/commands copying django/contrib/gis/management/commands/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/management/commands creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps/management copying django/contrib/sitemaps/management/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps/management creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps/management/commands copying django/contrib/sitemaps/management/commands/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps/management/commands copying django/contrib/sitemaps/management/commands/ping_google.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps/management/commands creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/mixins.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/statistics.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/aggregates copying django/contrib/postgres/aggregates/general.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/aggregates creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/fields copying django/contrib/postgres/fields/hstore.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/fields copying django/contrib/postgres/fields/citext.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/fields copying django/contrib/postgres/fields/jsonb.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/fields copying django/contrib/postgres/fields/ranges.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/fields copying django/contrib/postgres/fields/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/fields copying django/contrib/postgres/fields/array.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/fields copying django/contrib/postgres/fields/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/fields creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/forms copying django/contrib/postgres/forms/hstore.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/forms copying django/contrib/postgres/forms/jsonb.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/forms copying django/contrib/postgres/forms/ranges.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/forms copying django/contrib/postgres/forms/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/forms copying django/contrib/postgres/forms/array.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/forms creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/migrations copying django/contrib/admin/migrations/0002_logentry_remove_auto_add.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/migrations copying django/contrib/admin/migrations/0003_logentry_add_action_flag_choices.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/migrations copying django/contrib/admin/migrations/0001_initial.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/migrations copying django/contrib/admin/migrations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/log.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/admin_list.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/admin_urls.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/admin_modify.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templatetags copying django/contrib/admin/templatetags/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templatetags creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/views copying django/contrib/admin/views/autocomplete.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/views copying django/contrib/admin/views/decorators.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/views copying django/contrib/admin/views/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/views copying django/contrib/admin/views/main.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/views creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/migrations copying django/contrib/sites/migrations/0001_initial.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/migrations copying django/contrib/sites/migrations/0002_alter_domain_unique.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/migrations copying django/contrib/sites/migrations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles/management copying django/contrib/staticfiles/management/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles/management creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/collectstatic.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/findstatic.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles/management/commands copying django/contrib/staticfiles/management/commands/runserver.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/staticfiles/management/commands creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/migrations copying django/contrib/sessions/migrations/0001_initial.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/migrations copying django/contrib/sessions/migrations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/backends copying django/contrib/sessions/backends/cache.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/backends copying django/contrib/sessions/backends/db.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/backends copying django/contrib/sessions/backends/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/backends copying django/contrib/sessions/backends/signed_cookies.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/backends copying django/contrib/sessions/backends/file.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/backends copying django/contrib/sessions/backends/cached_db.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/backends copying django/contrib/sessions/backends/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/backends creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/management copying django/contrib/sessions/management/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/management creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/management/commands copying django/contrib/sessions/management/commands/clearsessions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/management/commands copying django/contrib/sessions/management/commands/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/management/commands creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0009_alter_user_last_name_max_length.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0012_alter_user_first_name_max_length.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0002_alter_permission_name_max_length.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0007_alter_validators_add_error_messages.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0001_initial.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0010_alter_group_name_max_length.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0003_alter_user_email_max_length.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0011_update_proxy_permissions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0004_alter_user_username_opts.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0006_require_contenttypes_0002.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0008_alter_user_username_max_length.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations copying django/contrib/auth/migrations/0005_alter_user_last_login_null.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/handlers copying django/contrib/auth/handlers/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/handlers copying django/contrib/auth/handlers/modwsgi.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/handlers creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/management copying django/contrib/auth/management/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/management creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/management/commands copying django/contrib/auth/management/commands/createsuperuser.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/management/commands copying django/contrib/auth/management/commands/changepassword.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/management/commands copying django/contrib/auth/management/commands/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/management/commands creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/migrations copying django/contrib/contenttypes/migrations/0002_remove_content_type_name.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/migrations copying django/contrib/contenttypes/migrations/0001_initial.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/migrations copying django/contrib/contenttypes/migrations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/management copying django/contrib/contenttypes/management/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/management creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/management/commands copying django/contrib/contenttypes/management/commands/remove_stale_contenttypes.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/management/commands copying django/contrib/contenttypes/management/commands/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/management/commands creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/templatetags copying django/contrib/humanize/templatetags/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/templatetags copying django/contrib/humanize/templatetags/humanize.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/templatetags creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages/storage copying django/contrib/messages/storage/cookie.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages/storage copying django/contrib/messages/storage/session.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages/storage copying django/contrib/messages/storage/fallback.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages/storage copying django/contrib/messages/storage/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages/storage copying django/contrib/messages/storage/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/messages/storage creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/migrations copying django/contrib/flatpages/migrations/0001_initial.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/migrations copying django/contrib/flatpages/migrations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/templatetags copying django/contrib/flatpages/templatetags/flatpages.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/templatetags copying django/contrib/flatpages/templatetags/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/templatetags creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/migrations copying django/contrib/redirects/migrations/0001_initial.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/migrations copying django/contrib/redirects/migrations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/migrations copying django/contrib/redirects/migrations/0002_alter_redirect_new_path_help_text.py -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/template/loaders copying django/template/loaders/locmem.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/loaders copying django/template/loaders/app_directories.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/loaders copying django/template/loaders/filesystem.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/loaders copying django/template/loaders/cached.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/loaders copying django/template/loaders/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/loaders copying django/template/loaders/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/loaders creating /<>/.pybuild/cpython3_3.11_django/build/django/template/backends copying django/template/backends/jinja2.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/backends copying django/template/backends/dummy.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/backends copying django/template/backends/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/backends copying django/template/backends/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/backends copying django/template/backends/django.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/backends copying django/template/backends/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/template/backends creating /<>/.pybuild/cpython3_3.11_django/build/django/core/serializers copying django/core/serializers/xml_serializer.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/serializers copying django/core/serializers/python.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/serializers copying django/core/serializers/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/serializers copying django/core/serializers/jsonl.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/serializers copying django/core/serializers/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/serializers copying django/core/serializers/json.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/serializers copying django/core/serializers/pyyaml.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/serializers creating /<>/.pybuild/cpython3_3.11_django/build/django/core/servers copying django/core/servers/basehttp.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/servers copying django/core/servers/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/servers creating /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/translation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/messages.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/caches.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/database.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/async_checks.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/templates.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/registry.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/model_checks.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks copying django/core/checks/urls.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks creating /<>/.pybuild/cpython3_3.11_django/build/django/core/cache copying django/core/cache/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache copying django/core/cache/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache creating /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/storage.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/temp.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/images.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/locks.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/move.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/uploadedfile.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/uploadhandler.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files copying django/core/files/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/files creating /<>/.pybuild/cpython3_3.11_django/build/django/core/handlers copying django/core/handlers/asgi.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/handlers copying django/core/handlers/wsgi.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/handlers copying django/core/handlers/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/handlers copying django/core/handlers/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/handlers copying django/core/handlers/exception.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/handlers creating /<>/.pybuild/cpython3_3.11_django/build/django/core/mail copying django/core/mail/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail copying django/core/mail/message.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail copying django/core/mail/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail creating /<>/.pybuild/cpython3_3.11_django/build/django/core/management copying django/core/management/templates.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management copying django/core/management/sql.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management copying django/core/management/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management copying django/core/management/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management copying django/core/management/color.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management copying django/core/management/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management creating /<>/.pybuild/cpython3_3.11_django/build/django/core/checks/compatibility copying django/core/checks/compatibility/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks/compatibility creating /<>/.pybuild/cpython3_3.11_django/build/django/core/checks/security copying django/core/checks/security/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks/security copying django/core/checks/security/sessions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks/security copying django/core/checks/security/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks/security copying django/core/checks/security/csrf.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/checks/security creating /<>/.pybuild/cpython3_3.11_django/build/django/core/cache/backends copying django/core/cache/backends/memcached.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache/backends copying django/core/cache/backends/locmem.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache/backends copying django/core/cache/backends/filebased.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache/backends copying django/core/cache/backends/dummy.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache/backends copying django/core/cache/backends/db.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache/backends copying django/core/cache/backends/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache/backends copying django/core/cache/backends/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/cache/backends creating /<>/.pybuild/cpython3_3.11_django/build/django/core/mail/backends copying django/core/mail/backends/locmem.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail/backends copying django/core/mail/backends/filebased.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail/backends copying django/core/mail/backends/smtp.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail/backends copying django/core/mail/backends/console.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail/backends copying django/core/mail/backends/dummy.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail/backends copying django/core/mail/backends/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail/backends copying django/core/mail/backends/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/mail/backends creating /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/sqlsequencereset.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/sendtestemail.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/flush.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/test.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/migrate.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/compilemessages.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/dumpdata.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/startapp.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/testserver.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/startproject.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/squashmigrations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/sqlflush.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/createcachetable.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/check.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/sqlmigrate.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/inspectdb.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/diffsettings.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/makemigrations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/loaddata.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/dbshell.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/showmigrations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/makemessages.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/runserver.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands copying django/core/management/commands/shell.py -> /<>/.pybuild/cpython3_3.11_django/build/django/core/management/commands creating /<>/.pybuild/cpython3_3.11_django/build/django/views/generic copying django/views/generic/detail.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/generic copying django/views/generic/edit.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/generic copying django/views/generic/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/generic copying django/views/generic/dates.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/generic copying django/views/generic/list.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/generic copying django/views/generic/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/generic creating /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/gzip.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/cache.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/http.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/vary.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/clickjacking.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/debug.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/common.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators copying django/views/decorators/csrf.py -> /<>/.pybuild/cpython3_3.11_django/build/django/views/decorators creating /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/optimizer.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/state.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/migration.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/questioner.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/writer.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/autodetector.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/exceptions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/executor.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/serializer.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/recorder.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/loader.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/graph.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations copying django/db/migrations/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/db/backends copying django/db/backends/signals.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends copying django/db/backends/ddl_references.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends copying django/db/backends/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends copying django/db/backends/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends creating /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/query.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/indexes.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/enums.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/signals.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/lookups.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/manager.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/constraints.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/options.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/aggregates.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/query_utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/deletion.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/constants.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/expressions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models copying django/db/models/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models creating /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations/operations copying django/db/migrations/operations/fields.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations/operations copying django/db/migrations/operations/models.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations/operations copying django/db/migrations/operations/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations/operations copying django/db/migrations/operations/special.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations/operations copying django/db/migrations/operations/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations/operations copying django/db/migrations/operations/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/migrations/operations creating /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/creation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/compiler.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/validation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql copying django/db/backends/mysql/client.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/mysql creating /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 copying django/db/backends/sqlite3/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 copying django/db/backends/sqlite3/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 copying django/db/backends/sqlite3/creation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 copying django/db/backends/sqlite3/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 copying django/db/backends/sqlite3/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 copying django/db/backends/sqlite3/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 copying django/db/backends/sqlite3/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 copying django/db/backends/sqlite3/client.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/sqlite3 creating /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/creation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/functions.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/validation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/client.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle copying django/db/backends/oracle/utils.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/oracle creating /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/dummy copying django/db/backends/dummy/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/dummy copying django/db/backends/dummy/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/dummy copying django/db/backends/dummy/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/dummy creating /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/creation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/validation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base copying django/db/backends/base/client.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/base creating /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql copying django/db/backends/postgresql/operations.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql copying django/db/backends/postgresql/features.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql copying django/db/backends/postgresql/creation.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql copying django/db/backends/postgresql/introspection.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql copying django/db/backends/postgresql/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql copying django/db/backends/postgresql/base.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql copying django/db/backends/postgresql/schema.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql copying django/db/backends/postgresql/client.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/backends/postgresql creating /<>/.pybuild/cpython3_3.11_django/build/django/db/models/functions copying django/db/models/functions/text.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/functions copying django/db/models/functions/mixins.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/functions copying django/db/models/functions/math.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/functions copying django/db/models/functions/datetime.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/functions copying django/db/models/functions/window.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/functions copying django/db/models/functions/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/functions copying django/db/models/functions/comparison.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/functions creating /<>/.pybuild/cpython3_3.11_django/build/django/db/models/sql copying django/db/models/sql/query.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/sql copying django/db/models/sql/compiler.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/sql copying django/db/models/sql/datastructures.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/sql copying django/db/models/sql/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/sql copying django/db/models/sql/constants.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/sql copying django/db/models/sql/where.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/sql copying django/db/models/sql/subqueries.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/sql creating /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/files.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/mixins.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/related_lookups.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/related_descriptors.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/proxy.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/reverse_related.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/related.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields copying django/db/models/fields/json.py -> /<>/.pybuild/cpython3_3.11_django/build/django/db/models/fields creating /<>/.pybuild/cpython3_3.11_django/build/django/utils/translation copying django/utils/translation/trans_null.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils/translation copying django/utils/translation/template.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils/translation copying django/utils/translation/reloader.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils/translation copying django/utils/translation/trans_real.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils/translation copying django/utils/translation/__init__.py -> /<>/.pybuild/cpython3_3.11_django/build/django/utils/translation 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/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.bin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.bin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django.bin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django.bin' to be distributed and are already explicitly excluding 'django.bin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-packages/setuptools/command/build_py.py:201: _Warning: Package 'django.contrib.admin.static.admin.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django.contrib.admin.static.admin.fonts' as an importable package[^1], but it is absent 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.fonts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more 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.fonts' to be distributed and are already explicitly excluding 'django.contrib.admin.static.admin.fonts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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/dist-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 /<>/.pybuild/cpython3_3.11_django/build/django/bin copying django/bin/django-admin.py -> /<>/.pybuild/cpython3_3.11_django/build/django/bin creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template copying django/conf/app_template/__init__.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template copying django/conf/app_template/admin.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template copying django/conf/app_template/apps.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template copying django/conf/app_template/models.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template copying django/conf/app_template/tests.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template copying django/conf/app_template/views.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template/migrations copying django/conf/app_template/migrations/__init__.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/app_template/migrations creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/project_template copying django/conf/project_template/manage.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/project_template creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/project_template/project_name copying django/conf/project_template/project_name/__init__.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/project_template/project_name copying django/conf/project_template/project_name/asgi.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/project_template/project_name copying django/conf/project_template/project_name/settings.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/project_template/project_name copying django/conf/project_template/project_name/urls.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/project_template/project_name copying django/conf/project_template/project_name/wsgi.py-tpl -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/project_template/project_name copying django/dispatch/license.txt -> /<>/.pybuild/cpython3_3.11_django/build/django/dispatch creating /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2 creating /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django creating /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms creating /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/attrs.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/checkbox.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/checkbox_option.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/checkbox_select.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/clearable_file_input.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/date.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/datetime.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/email.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/file.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/hidden.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/input.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/input_option.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/multiple_hidden.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/multiple_input.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/multiwidget.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/number.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/password.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/radio.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/radio_option.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/select.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/select_date.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/select_option.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/splitdatetime.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/splithiddendatetime.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/text.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/textarea.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/time.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets copying django/forms/jinja2/django/forms/widgets/url.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/jinja2/django/forms/widgets creating /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates creating /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django creating /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms creating /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/attrs.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/checkbox.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/checkbox_option.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/checkbox_select.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/clearable_file_input.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/date.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/datetime.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/email.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/file.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/hidden.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/input.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/input_option.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/multiple_hidden.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/multiple_input.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/multiwidget.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/number.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/password.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/radio.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/radio_option.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/select.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/select_date.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/select_option.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/splitdatetime.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/splithiddendatetime.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/text.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/textarea.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/time.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets copying django/forms/templates/django/forms/widgets/url.html -> /<>/.pybuild/cpython3_3.11_django/build/django/forms/templates/django/forms/widgets creating /<>/.pybuild/cpython3_3.11_django/build/django/views/templates copying django/views/templates/default_urlconf.html -> /<>/.pybuild/cpython3_3.11_django/build/django/views/templates copying django/views/templates/technical_404.html -> /<>/.pybuild/cpython3_3.11_django/build/django/views/templates copying django/views/templates/technical_500.html -> /<>/.pybuild/cpython3_3.11_django/build/django/views/templates copying django/views/templates/technical_500.txt -> /<>/.pybuild/cpython3_3.11_django/build/django/views/templates creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/af/LC_MESSAGES copying django/conf/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/af/LC_MESSAGES copying django/conf/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ast/LC_MESSAGES copying django/conf/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ast/LC_MESSAGES copying django/conf/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/be/LC_MESSAGES copying django/conf/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/be/LC_MESSAGES copying django/conf/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/br/LC_MESSAGES copying django/conf/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/br/LC_MESSAGES copying django/conf/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/dsb/LC_MESSAGES copying django/conf/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/dsb/LC_MESSAGES copying django/conf/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_VE/LC_MESSAGES copying django/conf/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_VE/LC_MESSAGES copying django/conf/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hsb/LC_MESSAGES copying django/conf/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hsb/LC_MESSAGES copying django/conf/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hy/LC_MESSAGES copying django/conf/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hy/LC_MESSAGES copying django/conf/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ia/LC_MESSAGES copying django/conf/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ia/LC_MESSAGES copying django/conf/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/io/LC_MESSAGES copying django/conf/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/io/LC_MESSAGES copying django/conf/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kab creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kab/LC_MESSAGES copying django/conf/locale/kab/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kab/LC_MESSAGES copying django/conf/locale/kab/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kab/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kk/LC_MESSAGES copying django/conf/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kk/LC_MESSAGES copying django/conf/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lb/LC_MESSAGES copying django/conf/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lb/LC_MESSAGES copying django/conf/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mr/LC_MESSAGES copying django/conf/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mr/LC_MESSAGES copying django/conf/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/my/LC_MESSAGES copying django/conf/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/my/LC_MESSAGES copying django/conf/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ne/LC_MESSAGES copying django/conf/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ne/LC_MESSAGES copying django/conf/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/os/LC_MESSAGES copying django/conf/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/os/LC_MESSAGES copying django/conf/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pa/LC_MESSAGES copying django/conf/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pa/LC_MESSAGES copying django/conf/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sw/LC_MESSAGES copying django/conf/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sw/LC_MESSAGES copying django/conf/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tt/LC_MESSAGES copying django/conf/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tt/LC_MESSAGES copying django/conf/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/udm/LC_MESSAGES copying django/conf/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/udm/LC_MESSAGES copying django/conf/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ur/LC_MESSAGES copying django/conf/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ur/LC_MESSAGES copying django/conf/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/et/LC_MESSAGES copying django/conf/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/et/LC_MESSAGES copying django/conf/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hans/LC_MESSAGES copying django/conf/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hans/LC_MESSAGES copying django/conf/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fi/LC_MESSAGES copying django/conf/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fi/LC_MESSAGES copying django/conf/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt_BR/LC_MESSAGES copying django/conf/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt_BR/LC_MESSAGES copying django/conf/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ru/LC_MESSAGES copying django/conf/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ru/LC_MESSAGES copying django/conf/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bg/LC_MESSAGES copying django/conf/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bg/LC_MESSAGES copying django/conf/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_GB/LC_MESSAGES copying django/conf/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_GB/LC_MESSAGES copying django/conf/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr/LC_MESSAGES copying django/conf/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr/LC_MESSAGES copying django/conf/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/el/LC_MESSAGES copying django/conf/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/el/LC_MESSAGES copying django/conf/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kn/LC_MESSAGES copying django/conf/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kn/LC_MESSAGES copying django/conf/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/th/LC_MESSAGES copying django/conf/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/th/LC_MESSAGES copying django/conf/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eu/LC_MESSAGES copying django/conf/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eu/LC_MESSAGES copying django/conf/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar_DZ/LC_MESSAGES copying django/conf/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar_DZ/LC_MESSAGES copying django/conf/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uz/LC_MESSAGES copying django/conf/locale/uz/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uz/LC_MESSAGES copying django/conf/locale/uz/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uz/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cy/LC_MESSAGES copying django/conf/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cy/LC_MESSAGES copying django/conf/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pl/LC_MESSAGES copying django/conf/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pl/LC_MESSAGES copying django/conf/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar/LC_MESSAGES copying django/conf/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar/LC_MESSAGES copying django/conf/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fa/LC_MESSAGES copying django/conf/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fa/LC_MESSAGES copying django/conf/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/it/LC_MESSAGES copying django/conf/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/it/LC_MESSAGES copying django/conf/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/az/LC_MESSAGES copying django/conf/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/az/LC_MESSAGES copying django/conf/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_MX/LC_MESSAGES copying django/conf/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_MX/LC_MESSAGES copying django/conf/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mk/LC_MESSAGES copying django/conf/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mk/LC_MESSAGES copying django/conf/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ga/LC_MESSAGES copying django/conf/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ga/LC_MESSAGES copying django/conf/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tk/LC_MESSAGES copying django/conf/locale/tk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tk/LC_MESSAGES copying django/conf/locale/tk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/da/LC_MESSAGES copying django/conf/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/da/LC_MESSAGES copying django/conf/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tg/LC_MESSAGES copying django/conf/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tg/LC_MESSAGES copying django/conf/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sl/LC_MESSAGES copying django/conf/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sl/LC_MESSAGES copying django/conf/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ky/LC_MESSAGES copying django/conf/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ky/LC_MESSAGES copying django/conf/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nb/LC_MESSAGES copying django/conf/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nb/LC_MESSAGES copying django/conf/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fr/LC_MESSAGES copying django/conf/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fr/LC_MESSAGES copying django/conf/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gl/LC_MESSAGES copying django/conf/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gl/LC_MESSAGES copying django/conf/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tr/LC_MESSAGES copying django/conf/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tr/LC_MESSAGES copying django/conf/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ig/LC_MESSAGES copying django/conf/locale/ig/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ig/LC_MESSAGES copying django/conf/locale/ig/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ig/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lv/LC_MESSAGES copying django/conf/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lv/LC_MESSAGES copying django/conf/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_AU/LC_MESSAGES copying django/conf/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_AU/LC_MESSAGES copying django/conf/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es/LC_MESSAGES copying django/conf/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es/LC_MESSAGES copying django/conf/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hi/LC_MESSAGES copying django/conf/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hi/LC_MESSAGES copying django/conf/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/te/LC_MESSAGES copying django/conf/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/te/LC_MESSAGES copying django/conf/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/km/LC_MESSAGES copying django/conf/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/km/LC_MESSAGES copying django/conf/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fy/LC_MESSAGES copying django/conf/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fy/LC_MESSAGES copying django/conf/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hr/LC_MESSAGES copying django/conf/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hr/LC_MESSAGES copying django/conf/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eo/LC_MESSAGES copying django/conf/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eo/LC_MESSAGES copying django/conf/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sv/LC_MESSAGES copying django/conf/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sv/LC_MESSAGES copying django/conf/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ka/LC_MESSAGES copying django/conf/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ka/LC_MESSAGES copying django/conf/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ro/LC_MESSAGES copying django/conf/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ro/LC_MESSAGES copying django/conf/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sq/LC_MESSAGES copying django/conf/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sq/LC_MESSAGES copying django/conf/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bs/LC_MESSAGES copying django/conf/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bs/LC_MESSAGES copying django/conf/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ca/LC_MESSAGES copying django/conf/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ca/LC_MESSAGES copying django/conf/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_CO/LC_MESSAGES copying django/conf/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_CO/LC_MESSAGES copying django/conf/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ta/LC_MESSAGES copying django/conf/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ta/LC_MESSAGES copying django/conf/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/he/LC_MESSAGES copying django/conf/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/he/LC_MESSAGES copying django/conf/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ko/LC_MESSAGES copying django/conf/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ko/LC_MESSAGES copying django/conf/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nl/LC_MESSAGES copying django/conf/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nl/LC_MESSAGES copying django/conf/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ja/LC_MESSAGES copying django/conf/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ja/LC_MESSAGES copying django/conf/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/is/LC_MESSAGES copying django/conf/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/is/LC_MESSAGES copying django/conf/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ml/LC_MESSAGES copying django/conf/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ml/LC_MESSAGES copying django/conf/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/id/LC_MESSAGES copying django/conf/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/id/LC_MESSAGES copying django/conf/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gd/LC_MESSAGES copying django/conf/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gd/LC_MESSAGES copying django/conf/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cs/LC_MESSAGES copying django/conf/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cs/LC_MESSAGES copying django/conf/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mn/LC_MESSAGES copying django/conf/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mn/LC_MESSAGES copying django/conf/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de/LC_MESSAGES copying django/conf/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de/LC_MESSAGES copying django/conf/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt/LC_MESSAGES copying django/conf/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt/LC_MESSAGES copying django/conf/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lt/LC_MESSAGES copying django/conf/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lt/LC_MESSAGES copying django/conf/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sk/LC_MESSAGES copying django/conf/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sk/LC_MESSAGES copying django/conf/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr_Latn/LC_MESSAGES copying django/conf/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr_Latn/LC_MESSAGES copying django/conf/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uk/LC_MESSAGES copying django/conf/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uk/LC_MESSAGES copying django/conf/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hant/LC_MESSAGES copying django/conf/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hant/LC_MESSAGES copying django/conf/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hu/LC_MESSAGES copying django/conf/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hu/LC_MESSAGES copying django/conf/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_AR/LC_MESSAGES copying django/conf/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_AR/LC_MESSAGES copying django/conf/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/vi/LC_MESSAGES copying django/conf/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/vi/LC_MESSAGES copying django/conf/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bn/LC_MESSAGES copying django/conf/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bn/LC_MESSAGES copying django/conf/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nn/LC_MESSAGES copying django/conf/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nn/LC_MESSAGES copying django/conf/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en/LC_MESSAGES copying django/conf/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en/LC_MESSAGES copying django/conf/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/conf/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/af/LC_MESSAGES copying django/contrib/gis/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/af/LC_MESSAGES copying django/contrib/gis/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ar/LC_MESSAGES copying django/contrib/gis/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ar/LC_MESSAGES copying django/contrib/gis/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ar_DZ/LC_MESSAGES copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ar_DZ/LC_MESSAGES copying django/contrib/gis/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ast/LC_MESSAGES copying django/contrib/gis/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ast/LC_MESSAGES copying django/contrib/gis/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/az/LC_MESSAGES copying django/contrib/gis/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/az/LC_MESSAGES copying django/contrib/gis/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/be/LC_MESSAGES copying django/contrib/gis/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/be/LC_MESSAGES copying django/contrib/gis/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bg/LC_MESSAGES copying django/contrib/gis/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bg/LC_MESSAGES copying django/contrib/gis/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bn/LC_MESSAGES copying django/contrib/gis/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bn/LC_MESSAGES copying django/contrib/gis/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/br/LC_MESSAGES copying django/contrib/gis/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/br/LC_MESSAGES copying django/contrib/gis/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bs/LC_MESSAGES copying django/contrib/gis/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bs/LC_MESSAGES copying django/contrib/gis/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ca/LC_MESSAGES copying django/contrib/gis/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ca/LC_MESSAGES copying django/contrib/gis/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/cs/LC_MESSAGES copying django/contrib/gis/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/cs/LC_MESSAGES copying django/contrib/gis/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/cy/LC_MESSAGES copying django/contrib/gis/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/cy/LC_MESSAGES copying django/contrib/gis/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/da/LC_MESSAGES copying django/contrib/gis/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/da/LC_MESSAGES copying django/contrib/gis/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/de/LC_MESSAGES copying django/contrib/gis/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/de/LC_MESSAGES copying django/contrib/gis/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/dsb/LC_MESSAGES copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/dsb/LC_MESSAGES copying django/contrib/gis/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/el/LC_MESSAGES copying django/contrib/gis/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/el/LC_MESSAGES copying django/contrib/gis/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en/LC_MESSAGES copying django/contrib/gis/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en/LC_MESSAGES copying django/contrib/gis/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en_AU/LC_MESSAGES copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en_AU/LC_MESSAGES copying django/contrib/gis/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en_GB/LC_MESSAGES copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en_GB/LC_MESSAGES copying django/contrib/gis/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/eo/LC_MESSAGES copying django/contrib/gis/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/eo/LC_MESSAGES copying django/contrib/gis/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es/LC_MESSAGES copying django/contrib/gis/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es/LC_MESSAGES copying django/contrib/gis/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_AR/LC_MESSAGES copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_AR/LC_MESSAGES copying django/contrib/gis/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_CO/LC_MESSAGES copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_CO/LC_MESSAGES copying django/contrib/gis/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_MX/LC_MESSAGES copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_MX/LC_MESSAGES copying django/contrib/gis/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_VE/LC_MESSAGES copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_VE/LC_MESSAGES copying django/contrib/gis/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/et/LC_MESSAGES copying django/contrib/gis/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/et/LC_MESSAGES copying django/contrib/gis/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/eu/LC_MESSAGES copying django/contrib/gis/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/eu/LC_MESSAGES copying django/contrib/gis/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fa/LC_MESSAGES copying django/contrib/gis/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fa/LC_MESSAGES copying django/contrib/gis/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fi/LC_MESSAGES copying django/contrib/gis/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fi/LC_MESSAGES copying django/contrib/gis/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fr/LC_MESSAGES copying django/contrib/gis/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fr/LC_MESSAGES copying django/contrib/gis/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fy/LC_MESSAGES copying django/contrib/gis/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fy/LC_MESSAGES copying django/contrib/gis/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ga/LC_MESSAGES copying django/contrib/gis/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ga/LC_MESSAGES copying django/contrib/gis/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/gd/LC_MESSAGES copying django/contrib/gis/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/gd/LC_MESSAGES copying django/contrib/gis/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/gl/LC_MESSAGES copying django/contrib/gis/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/gl/LC_MESSAGES copying django/contrib/gis/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/he/LC_MESSAGES copying django/contrib/gis/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/he/LC_MESSAGES copying django/contrib/gis/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hi/LC_MESSAGES copying django/contrib/gis/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hi/LC_MESSAGES copying django/contrib/gis/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hr/LC_MESSAGES copying django/contrib/gis/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hr/LC_MESSAGES copying django/contrib/gis/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hsb/LC_MESSAGES copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hsb/LC_MESSAGES copying django/contrib/gis/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hu/LC_MESSAGES copying django/contrib/gis/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hu/LC_MESSAGES copying django/contrib/gis/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hy/LC_MESSAGES copying django/contrib/gis/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hy/LC_MESSAGES copying django/contrib/gis/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ia/LC_MESSAGES copying django/contrib/gis/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ia/LC_MESSAGES copying django/contrib/gis/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/id/LC_MESSAGES copying django/contrib/gis/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/id/LC_MESSAGES copying django/contrib/gis/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/io/LC_MESSAGES copying django/contrib/gis/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/io/LC_MESSAGES copying django/contrib/gis/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/is/LC_MESSAGES copying django/contrib/gis/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/is/LC_MESSAGES copying django/contrib/gis/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/it/LC_MESSAGES copying django/contrib/gis/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/it/LC_MESSAGES copying django/contrib/gis/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ja/LC_MESSAGES copying django/contrib/gis/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ja/LC_MESSAGES copying django/contrib/gis/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ka/LC_MESSAGES copying django/contrib/gis/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ka/LC_MESSAGES copying django/contrib/gis/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/kk/LC_MESSAGES copying django/contrib/gis/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/kk/LC_MESSAGES copying django/contrib/gis/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/km/LC_MESSAGES copying django/contrib/gis/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/km/LC_MESSAGES copying django/contrib/gis/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/kn/LC_MESSAGES copying django/contrib/gis/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/kn/LC_MESSAGES copying django/contrib/gis/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ko/LC_MESSAGES copying django/contrib/gis/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ko/LC_MESSAGES copying django/contrib/gis/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ky/LC_MESSAGES copying django/contrib/gis/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ky/LC_MESSAGES copying django/contrib/gis/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lb/LC_MESSAGES copying django/contrib/gis/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lb/LC_MESSAGES copying django/contrib/gis/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lt/LC_MESSAGES copying django/contrib/gis/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lt/LC_MESSAGES copying django/contrib/gis/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lv/LC_MESSAGES copying django/contrib/gis/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lv/LC_MESSAGES copying django/contrib/gis/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mk/LC_MESSAGES copying django/contrib/gis/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mk/LC_MESSAGES copying django/contrib/gis/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ml/LC_MESSAGES copying django/contrib/gis/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ml/LC_MESSAGES copying django/contrib/gis/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mn/LC_MESSAGES copying django/contrib/gis/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mn/LC_MESSAGES copying django/contrib/gis/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mr/LC_MESSAGES copying django/contrib/gis/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mr/LC_MESSAGES copying django/contrib/gis/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/my/LC_MESSAGES copying django/contrib/gis/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/my/LC_MESSAGES copying django/contrib/gis/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nb/LC_MESSAGES copying django/contrib/gis/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nb/LC_MESSAGES copying django/contrib/gis/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ne/LC_MESSAGES copying django/contrib/gis/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ne/LC_MESSAGES copying django/contrib/gis/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nl/LC_MESSAGES copying django/contrib/gis/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nl/LC_MESSAGES copying django/contrib/gis/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nn/LC_MESSAGES copying django/contrib/gis/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nn/LC_MESSAGES copying django/contrib/gis/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/os/LC_MESSAGES copying django/contrib/gis/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/os/LC_MESSAGES copying django/contrib/gis/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pa/LC_MESSAGES copying django/contrib/gis/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pa/LC_MESSAGES copying django/contrib/gis/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pl/LC_MESSAGES copying django/contrib/gis/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pl/LC_MESSAGES copying django/contrib/gis/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pt/LC_MESSAGES copying django/contrib/gis/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pt/LC_MESSAGES copying django/contrib/gis/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pt_BR/LC_MESSAGES copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pt_BR/LC_MESSAGES copying django/contrib/gis/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ro/LC_MESSAGES copying django/contrib/gis/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ro/LC_MESSAGES copying django/contrib/gis/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ru/LC_MESSAGES copying django/contrib/gis/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ru/LC_MESSAGES copying django/contrib/gis/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sk/LC_MESSAGES copying django/contrib/gis/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sk/LC_MESSAGES copying django/contrib/gis/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sl/LC_MESSAGES copying django/contrib/gis/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sl/LC_MESSAGES copying django/contrib/gis/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sq/LC_MESSAGES copying django/contrib/gis/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sq/LC_MESSAGES copying django/contrib/gis/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sr/LC_MESSAGES copying django/contrib/gis/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sr/LC_MESSAGES copying django/contrib/gis/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sr_Latn/LC_MESSAGES copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sr_Latn/LC_MESSAGES copying django/contrib/gis/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sv/LC_MESSAGES copying django/contrib/gis/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sv/LC_MESSAGES copying django/contrib/gis/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sw/LC_MESSAGES copying django/contrib/gis/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sw/LC_MESSAGES copying django/contrib/gis/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ta/LC_MESSAGES copying django/contrib/gis/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ta/LC_MESSAGES copying django/contrib/gis/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/te/LC_MESSAGES copying django/contrib/gis/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/te/LC_MESSAGES copying django/contrib/gis/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tg/LC_MESSAGES copying django/contrib/gis/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tg/LC_MESSAGES copying django/contrib/gis/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/th/LC_MESSAGES copying django/contrib/gis/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/th/LC_MESSAGES copying django/contrib/gis/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tr/LC_MESSAGES copying django/contrib/gis/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tr/LC_MESSAGES copying django/contrib/gis/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tt/LC_MESSAGES copying django/contrib/gis/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tt/LC_MESSAGES copying django/contrib/gis/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/udm/LC_MESSAGES copying django/contrib/gis/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/udm/LC_MESSAGES copying django/contrib/gis/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/uk/LC_MESSAGES copying django/contrib/gis/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/uk/LC_MESSAGES copying django/contrib/gis/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ur/LC_MESSAGES copying django/contrib/gis/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ur/LC_MESSAGES copying django/contrib/gis/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/vi/LC_MESSAGES copying django/contrib/gis/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/vi/LC_MESSAGES copying django/contrib/gis/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/zh_Hans/LC_MESSAGES copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/zh_Hans/LC_MESSAGES copying django/contrib/gis/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/zh_Hant/LC_MESSAGES copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/zh_Hant/LC_MESSAGES copying django/contrib/gis/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/css copying django/contrib/gis/static/gis/css/ol3.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/css creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_line_off.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_line_on.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_point_off.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_point_on.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_polygon_off.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/img copying django/contrib/gis/static/gis/img/draw_polygon_on.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/img creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/js copying django/contrib/gis/static/gis/js/OLMapWidget.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/static/gis/js creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis copying django/contrib/gis/templates/gis/openlayers-osm.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis copying django/contrib/gis/templates/gis/openlayers.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis/admin copying django/contrib/gis/templates/gis/admin/openlayers.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis/admin copying django/contrib/gis/templates/gis/admin/openlayers.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis/admin copying django/contrib/gis/templates/gis/admin/osm.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis/admin copying django/contrib/gis/templates/gis/admin/osm.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis/admin creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis/kml copying django/contrib/gis/templates/gis/kml/base.kml -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis/kml copying django/contrib/gis/templates/gis/kml/placemarks.kml -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/templates/gis/kml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps/templates copying django/contrib/sitemaps/templates/sitemap.xml -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps/templates copying django/contrib/sitemaps/templates/sitemap_index.xml -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sitemaps/templates creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/jinja2 creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/jinja2/postgres creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/jinja2/postgres/widgets copying django/contrib/postgres/jinja2/postgres/widgets/split_array.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/jinja2/postgres/widgets creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/af/LC_MESSAGES copying django/contrib/postgres/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/af/LC_MESSAGES copying django/contrib/postgres/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ar/LC_MESSAGES copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ar/LC_MESSAGES copying django/contrib/postgres/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES copying django/contrib/postgres/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/az/LC_MESSAGES copying django/contrib/postgres/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/az/LC_MESSAGES copying django/contrib/postgres/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/be/LC_MESSAGES copying django/contrib/postgres/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/be/LC_MESSAGES copying django/contrib/postgres/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/bg/LC_MESSAGES copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/bg/LC_MESSAGES copying django/contrib/postgres/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ca/LC_MESSAGES copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ca/LC_MESSAGES copying django/contrib/postgres/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/cs/LC_MESSAGES copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/cs/LC_MESSAGES copying django/contrib/postgres/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/da/LC_MESSAGES copying django/contrib/postgres/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/da/LC_MESSAGES copying django/contrib/postgres/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/de/LC_MESSAGES copying django/contrib/postgres/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/de/LC_MESSAGES copying django/contrib/postgres/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/dsb/LC_MESSAGES copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/dsb/LC_MESSAGES copying django/contrib/postgres/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/el/LC_MESSAGES copying django/contrib/postgres/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/el/LC_MESSAGES copying django/contrib/postgres/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/en/LC_MESSAGES copying django/contrib/postgres/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/en/LC_MESSAGES copying django/contrib/postgres/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/eo/LC_MESSAGES copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/eo/LC_MESSAGES copying django/contrib/postgres/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es/LC_MESSAGES copying django/contrib/postgres/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es/LC_MESSAGES copying django/contrib/postgres/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_AR/LC_MESSAGES copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_AR/LC_MESSAGES copying django/contrib/postgres/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_CO/LC_MESSAGES copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_CO/LC_MESSAGES copying django/contrib/postgres/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_MX/LC_MESSAGES copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_MX/LC_MESSAGES copying django/contrib/postgres/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/et/LC_MESSAGES copying django/contrib/postgres/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/et/LC_MESSAGES copying django/contrib/postgres/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/eu/LC_MESSAGES copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/eu/LC_MESSAGES copying django/contrib/postgres/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fa/LC_MESSAGES copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fa/LC_MESSAGES copying django/contrib/postgres/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fi/LC_MESSAGES copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fi/LC_MESSAGES copying django/contrib/postgres/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fr/LC_MESSAGES copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fr/LC_MESSAGES copying django/contrib/postgres/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/gd/LC_MESSAGES copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/gd/LC_MESSAGES copying django/contrib/postgres/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/gl/LC_MESSAGES copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/gl/LC_MESSAGES copying django/contrib/postgres/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/he/LC_MESSAGES copying django/contrib/postgres/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/he/LC_MESSAGES copying django/contrib/postgres/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hr/LC_MESSAGES copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hr/LC_MESSAGES copying django/contrib/postgres/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hsb/LC_MESSAGES copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hsb/LC_MESSAGES copying django/contrib/postgres/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hu/LC_MESSAGES copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hu/LC_MESSAGES copying django/contrib/postgres/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hy/LC_MESSAGES copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hy/LC_MESSAGES copying django/contrib/postgres/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ia/LC_MESSAGES copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ia/LC_MESSAGES copying django/contrib/postgres/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/id/LC_MESSAGES copying django/contrib/postgres/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/id/LC_MESSAGES copying django/contrib/postgres/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/is/LC_MESSAGES copying django/contrib/postgres/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/is/LC_MESSAGES copying django/contrib/postgres/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/it/LC_MESSAGES copying django/contrib/postgres/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/it/LC_MESSAGES copying django/contrib/postgres/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ja/LC_MESSAGES copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ja/LC_MESSAGES copying django/contrib/postgres/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ka/LC_MESSAGES copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ka/LC_MESSAGES copying django/contrib/postgres/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/kk/LC_MESSAGES copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/kk/LC_MESSAGES copying django/contrib/postgres/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ko/LC_MESSAGES copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ko/LC_MESSAGES copying django/contrib/postgres/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ky/LC_MESSAGES copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ky/LC_MESSAGES copying django/contrib/postgres/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/lt/LC_MESSAGES copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/lt/LC_MESSAGES copying django/contrib/postgres/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/lv/LC_MESSAGES copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/lv/LC_MESSAGES copying django/contrib/postgres/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/mk/LC_MESSAGES copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/mk/LC_MESSAGES copying django/contrib/postgres/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ml/LC_MESSAGES copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ml/LC_MESSAGES copying django/contrib/postgres/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/mn/LC_MESSAGES copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/mn/LC_MESSAGES copying django/contrib/postgres/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/nb/LC_MESSAGES copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/nb/LC_MESSAGES copying django/contrib/postgres/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ne/LC_MESSAGES copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ne/LC_MESSAGES copying django/contrib/postgres/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/nl/LC_MESSAGES copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/nl/LC_MESSAGES copying django/contrib/postgres/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pl/LC_MESSAGES copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pl/LC_MESSAGES copying django/contrib/postgres/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pt/LC_MESSAGES copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pt/LC_MESSAGES copying django/contrib/postgres/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pt_BR/LC_MESSAGES copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pt_BR/LC_MESSAGES copying django/contrib/postgres/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ro/LC_MESSAGES copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ro/LC_MESSAGES copying django/contrib/postgres/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ru/LC_MESSAGES copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ru/LC_MESSAGES copying django/contrib/postgres/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sk/LC_MESSAGES copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sk/LC_MESSAGES copying django/contrib/postgres/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sl/LC_MESSAGES copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sl/LC_MESSAGES copying django/contrib/postgres/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sq/LC_MESSAGES copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sq/LC_MESSAGES copying django/contrib/postgres/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sr/LC_MESSAGES copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sr/LC_MESSAGES copying django/contrib/postgres/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES copying django/contrib/postgres/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sv/LC_MESSAGES copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sv/LC_MESSAGES copying django/contrib/postgres/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tg/LC_MESSAGES copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tg/LC_MESSAGES copying django/contrib/postgres/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tk/LC_MESSAGES copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tk/LC_MESSAGES copying django/contrib/postgres/locale/tk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tr/LC_MESSAGES copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tr/LC_MESSAGES copying django/contrib/postgres/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/uk/LC_MESSAGES copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/uk/LC_MESSAGES copying django/contrib/postgres/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/uz creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/uz/LC_MESSAGES copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/uz/LC_MESSAGES copying django/contrib/postgres/locale/uz/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/uz/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES copying django/contrib/postgres/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES copying django/contrib/postgres/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/templates creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/templates/postgres creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/templates/postgres/widgets copying django/contrib/postgres/templates/postgres/widgets/split_array.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/postgres/templates/postgres/widgets creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/af/LC_MESSAGES copying django/contrib/admin/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/af/LC_MESSAGES copying django/contrib/admin/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/af/LC_MESSAGES copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/af/LC_MESSAGES copying django/contrib/admin/locale/af/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/am creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/am/LC_MESSAGES copying django/contrib/admin/locale/am/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/am/LC_MESSAGES copying django/contrib/admin/locale/am/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/am/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar/LC_MESSAGES copying django/contrib/admin/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar/LC_MESSAGES copying django/contrib/admin/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar/LC_MESSAGES copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar/LC_MESSAGES copying django/contrib/admin/locale/ar/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar_DZ/LC_MESSAGES copying django/contrib/admin/locale/ar_DZ/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ast/LC_MESSAGES copying django/contrib/admin/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ast/LC_MESSAGES copying django/contrib/admin/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ast/LC_MESSAGES copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ast/LC_MESSAGES copying django/contrib/admin/locale/ast/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/az/LC_MESSAGES copying django/contrib/admin/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/az/LC_MESSAGES copying django/contrib/admin/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/az/LC_MESSAGES copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/az/LC_MESSAGES copying django/contrib/admin/locale/az/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/be/LC_MESSAGES copying django/contrib/admin/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/be/LC_MESSAGES copying django/contrib/admin/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/be/LC_MESSAGES copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/be/LC_MESSAGES copying django/contrib/admin/locale/be/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bg/LC_MESSAGES copying django/contrib/admin/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bg/LC_MESSAGES copying django/contrib/admin/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bg/LC_MESSAGES copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bg/LC_MESSAGES copying django/contrib/admin/locale/bg/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bn/LC_MESSAGES copying django/contrib/admin/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bn/LC_MESSAGES copying django/contrib/admin/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bn/LC_MESSAGES copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bn/LC_MESSAGES copying django/contrib/admin/locale/bn/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/br/LC_MESSAGES copying django/contrib/admin/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/br/LC_MESSAGES copying django/contrib/admin/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/br/LC_MESSAGES copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/br/LC_MESSAGES copying django/contrib/admin/locale/br/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bs/LC_MESSAGES copying django/contrib/admin/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bs/LC_MESSAGES copying django/contrib/admin/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bs/LC_MESSAGES copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bs/LC_MESSAGES copying django/contrib/admin/locale/bs/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ca/LC_MESSAGES copying django/contrib/admin/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ca/LC_MESSAGES copying django/contrib/admin/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ca/LC_MESSAGES copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ca/LC_MESSAGES copying django/contrib/admin/locale/ca/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cs/LC_MESSAGES copying django/contrib/admin/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cs/LC_MESSAGES copying django/contrib/admin/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cs/LC_MESSAGES copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cs/LC_MESSAGES copying django/contrib/admin/locale/cs/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cy/LC_MESSAGES copying django/contrib/admin/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cy/LC_MESSAGES copying django/contrib/admin/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cy/LC_MESSAGES copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cy/LC_MESSAGES copying django/contrib/admin/locale/cy/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/da/LC_MESSAGES copying django/contrib/admin/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/da/LC_MESSAGES copying django/contrib/admin/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/da/LC_MESSAGES copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/da/LC_MESSAGES copying django/contrib/admin/locale/da/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/de/LC_MESSAGES copying django/contrib/admin/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/de/LC_MESSAGES copying django/contrib/admin/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/de/LC_MESSAGES copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/de/LC_MESSAGES copying django/contrib/admin/locale/de/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/dsb/LC_MESSAGES copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/dsb/LC_MESSAGES copying django/contrib/admin/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/dsb/LC_MESSAGES copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/dsb/LC_MESSAGES copying django/contrib/admin/locale/dsb/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/el/LC_MESSAGES copying django/contrib/admin/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/el/LC_MESSAGES copying django/contrib/admin/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/el/LC_MESSAGES copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/el/LC_MESSAGES copying django/contrib/admin/locale/el/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en/LC_MESSAGES copying django/contrib/admin/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en/LC_MESSAGES copying django/contrib/admin/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en/LC_MESSAGES copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en/LC_MESSAGES copying django/contrib/admin/locale/en/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_AU/LC_MESSAGES copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_AU/LC_MESSAGES copying django/contrib/admin/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_AU/LC_MESSAGES copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_AU/LC_MESSAGES copying django/contrib/admin/locale/en_AU/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_GB/LC_MESSAGES copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_GB/LC_MESSAGES copying django/contrib/admin/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_GB/LC_MESSAGES copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_GB/LC_MESSAGES copying django/contrib/admin/locale/en_GB/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eo/LC_MESSAGES copying django/contrib/admin/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eo/LC_MESSAGES copying django/contrib/admin/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eo/LC_MESSAGES copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eo/LC_MESSAGES copying django/contrib/admin/locale/eo/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es/LC_MESSAGES copying django/contrib/admin/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es/LC_MESSAGES copying django/contrib/admin/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es/LC_MESSAGES copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es/LC_MESSAGES copying django/contrib/admin/locale/es/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_AR/LC_MESSAGES copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_AR/LC_MESSAGES copying django/contrib/admin/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_AR/LC_MESSAGES copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_AR/LC_MESSAGES copying django/contrib/admin/locale/es_AR/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_CO/LC_MESSAGES copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_CO/LC_MESSAGES copying django/contrib/admin/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_CO/LC_MESSAGES copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_CO/LC_MESSAGES copying django/contrib/admin/locale/es_CO/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_MX/LC_MESSAGES copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_MX/LC_MESSAGES copying django/contrib/admin/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_MX/LC_MESSAGES copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_MX/LC_MESSAGES copying django/contrib/admin/locale/es_MX/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_VE/LC_MESSAGES copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_VE/LC_MESSAGES copying django/contrib/admin/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_VE/LC_MESSAGES copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_VE/LC_MESSAGES copying django/contrib/admin/locale/es_VE/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/et/LC_MESSAGES copying django/contrib/admin/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/et/LC_MESSAGES copying django/contrib/admin/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/et/LC_MESSAGES copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/et/LC_MESSAGES copying django/contrib/admin/locale/et/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eu/LC_MESSAGES copying django/contrib/admin/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eu/LC_MESSAGES copying django/contrib/admin/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eu/LC_MESSAGES copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eu/LC_MESSAGES copying django/contrib/admin/locale/eu/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fa/LC_MESSAGES copying django/contrib/admin/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fa/LC_MESSAGES copying django/contrib/admin/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fa/LC_MESSAGES copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fa/LC_MESSAGES copying django/contrib/admin/locale/fa/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fi/LC_MESSAGES copying django/contrib/admin/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fi/LC_MESSAGES copying django/contrib/admin/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fi/LC_MESSAGES copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fi/LC_MESSAGES copying django/contrib/admin/locale/fi/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fr/LC_MESSAGES copying django/contrib/admin/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fr/LC_MESSAGES copying django/contrib/admin/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fr/LC_MESSAGES copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fr/LC_MESSAGES copying django/contrib/admin/locale/fr/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fy/LC_MESSAGES copying django/contrib/admin/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fy/LC_MESSAGES copying django/contrib/admin/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fy/LC_MESSAGES copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fy/LC_MESSAGES copying django/contrib/admin/locale/fy/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ga/LC_MESSAGES copying django/contrib/admin/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ga/LC_MESSAGES copying django/contrib/admin/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ga/LC_MESSAGES copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ga/LC_MESSAGES copying django/contrib/admin/locale/ga/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gd/LC_MESSAGES copying django/contrib/admin/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gd/LC_MESSAGES copying django/contrib/admin/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gd/LC_MESSAGES copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gd/LC_MESSAGES copying django/contrib/admin/locale/gd/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gl/LC_MESSAGES copying django/contrib/admin/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gl/LC_MESSAGES copying django/contrib/admin/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gl/LC_MESSAGES copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gl/LC_MESSAGES copying django/contrib/admin/locale/gl/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/he/LC_MESSAGES copying django/contrib/admin/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/he/LC_MESSAGES copying django/contrib/admin/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/he/LC_MESSAGES copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/he/LC_MESSAGES copying django/contrib/admin/locale/he/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hi/LC_MESSAGES copying django/contrib/admin/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hi/LC_MESSAGES copying django/contrib/admin/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hi/LC_MESSAGES copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hi/LC_MESSAGES copying django/contrib/admin/locale/hi/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hr/LC_MESSAGES copying django/contrib/admin/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hr/LC_MESSAGES copying django/contrib/admin/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hr/LC_MESSAGES copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hr/LC_MESSAGES copying django/contrib/admin/locale/hr/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hsb/LC_MESSAGES copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hsb/LC_MESSAGES copying django/contrib/admin/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hsb/LC_MESSAGES copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hsb/LC_MESSAGES copying django/contrib/admin/locale/hsb/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hu/LC_MESSAGES copying django/contrib/admin/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hu/LC_MESSAGES copying django/contrib/admin/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hu/LC_MESSAGES copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hu/LC_MESSAGES copying django/contrib/admin/locale/hu/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hy/LC_MESSAGES copying django/contrib/admin/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hy/LC_MESSAGES copying django/contrib/admin/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hy/LC_MESSAGES copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hy/LC_MESSAGES copying django/contrib/admin/locale/hy/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ia/LC_MESSAGES copying django/contrib/admin/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ia/LC_MESSAGES copying django/contrib/admin/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ia/LC_MESSAGES copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ia/LC_MESSAGES copying django/contrib/admin/locale/ia/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/id/LC_MESSAGES copying django/contrib/admin/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/id/LC_MESSAGES copying django/contrib/admin/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/id/LC_MESSAGES copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/id/LC_MESSAGES copying django/contrib/admin/locale/id/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/io/LC_MESSAGES copying django/contrib/admin/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/io/LC_MESSAGES copying django/contrib/admin/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/io/LC_MESSAGES copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/io/LC_MESSAGES copying django/contrib/admin/locale/io/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/is/LC_MESSAGES copying django/contrib/admin/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/is/LC_MESSAGES copying django/contrib/admin/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/is/LC_MESSAGES copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/is/LC_MESSAGES copying django/contrib/admin/locale/is/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/it/LC_MESSAGES copying django/contrib/admin/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/it/LC_MESSAGES copying django/contrib/admin/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/it/LC_MESSAGES copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/it/LC_MESSAGES copying django/contrib/admin/locale/it/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ja/LC_MESSAGES copying django/contrib/admin/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ja/LC_MESSAGES copying django/contrib/admin/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ja/LC_MESSAGES copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ja/LC_MESSAGES copying django/contrib/admin/locale/ja/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ka/LC_MESSAGES copying django/contrib/admin/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ka/LC_MESSAGES copying django/contrib/admin/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ka/LC_MESSAGES copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ka/LC_MESSAGES copying django/contrib/admin/locale/ka/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kab creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kab/LC_MESSAGES copying django/contrib/admin/locale/kab/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kab/LC_MESSAGES copying django/contrib/admin/locale/kab/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kab/LC_MESSAGES copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kab/LC_MESSAGES copying django/contrib/admin/locale/kab/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kab/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kk/LC_MESSAGES copying django/contrib/admin/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kk/LC_MESSAGES copying django/contrib/admin/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kk/LC_MESSAGES copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kk/LC_MESSAGES copying django/contrib/admin/locale/kk/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/km/LC_MESSAGES copying django/contrib/admin/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/km/LC_MESSAGES copying django/contrib/admin/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/km/LC_MESSAGES copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/km/LC_MESSAGES copying django/contrib/admin/locale/km/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kn/LC_MESSAGES copying django/contrib/admin/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kn/LC_MESSAGES copying django/contrib/admin/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kn/LC_MESSAGES copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kn/LC_MESSAGES copying django/contrib/admin/locale/kn/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ko/LC_MESSAGES copying django/contrib/admin/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ko/LC_MESSAGES copying django/contrib/admin/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ko/LC_MESSAGES copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ko/LC_MESSAGES copying django/contrib/admin/locale/ko/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ky/LC_MESSAGES copying django/contrib/admin/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ky/LC_MESSAGES copying django/contrib/admin/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ky/LC_MESSAGES copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ky/LC_MESSAGES copying django/contrib/admin/locale/ky/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lb/LC_MESSAGES copying django/contrib/admin/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lb/LC_MESSAGES copying django/contrib/admin/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lb/LC_MESSAGES copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lb/LC_MESSAGES copying django/contrib/admin/locale/lb/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lt/LC_MESSAGES copying django/contrib/admin/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lt/LC_MESSAGES copying django/contrib/admin/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lt/LC_MESSAGES copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lt/LC_MESSAGES copying django/contrib/admin/locale/lt/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lv/LC_MESSAGES copying django/contrib/admin/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lv/LC_MESSAGES copying django/contrib/admin/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lv/LC_MESSAGES copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lv/LC_MESSAGES copying django/contrib/admin/locale/lv/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mk/LC_MESSAGES copying django/contrib/admin/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mk/LC_MESSAGES copying django/contrib/admin/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mk/LC_MESSAGES copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mk/LC_MESSAGES copying django/contrib/admin/locale/mk/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ml/LC_MESSAGES copying django/contrib/admin/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ml/LC_MESSAGES copying django/contrib/admin/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ml/LC_MESSAGES copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ml/LC_MESSAGES copying django/contrib/admin/locale/ml/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mn/LC_MESSAGES copying django/contrib/admin/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mn/LC_MESSAGES copying django/contrib/admin/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mn/LC_MESSAGES copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mn/LC_MESSAGES copying django/contrib/admin/locale/mn/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mr/LC_MESSAGES copying django/contrib/admin/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mr/LC_MESSAGES copying django/contrib/admin/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mr/LC_MESSAGES copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mr/LC_MESSAGES copying django/contrib/admin/locale/mr/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/my/LC_MESSAGES copying django/contrib/admin/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/my/LC_MESSAGES copying django/contrib/admin/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/my/LC_MESSAGES copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/my/LC_MESSAGES copying django/contrib/admin/locale/my/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nb/LC_MESSAGES copying django/contrib/admin/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nb/LC_MESSAGES copying django/contrib/admin/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nb/LC_MESSAGES copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nb/LC_MESSAGES copying django/contrib/admin/locale/nb/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ne/LC_MESSAGES copying django/contrib/admin/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ne/LC_MESSAGES copying django/contrib/admin/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ne/LC_MESSAGES copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ne/LC_MESSAGES copying django/contrib/admin/locale/ne/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nl/LC_MESSAGES copying django/contrib/admin/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nl/LC_MESSAGES copying django/contrib/admin/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nl/LC_MESSAGES copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nl/LC_MESSAGES copying django/contrib/admin/locale/nl/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nn/LC_MESSAGES copying django/contrib/admin/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nn/LC_MESSAGES copying django/contrib/admin/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nn/LC_MESSAGES copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nn/LC_MESSAGES copying django/contrib/admin/locale/nn/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/os/LC_MESSAGES copying django/contrib/admin/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/os/LC_MESSAGES copying django/contrib/admin/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/os/LC_MESSAGES copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/os/LC_MESSAGES copying django/contrib/admin/locale/os/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pa/LC_MESSAGES copying django/contrib/admin/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pa/LC_MESSAGES copying django/contrib/admin/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pa/LC_MESSAGES copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pa/LC_MESSAGES copying django/contrib/admin/locale/pa/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pl/LC_MESSAGES copying django/contrib/admin/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pl/LC_MESSAGES copying django/contrib/admin/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pl/LC_MESSAGES copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pl/LC_MESSAGES copying django/contrib/admin/locale/pl/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt/LC_MESSAGES copying django/contrib/admin/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt/LC_MESSAGES copying django/contrib/admin/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt/LC_MESSAGES copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt/LC_MESSAGES copying django/contrib/admin/locale/pt/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt_BR/LC_MESSAGES copying django/contrib/admin/locale/pt_BR/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ro/LC_MESSAGES copying django/contrib/admin/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ro/LC_MESSAGES copying django/contrib/admin/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ro/LC_MESSAGES copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ro/LC_MESSAGES copying django/contrib/admin/locale/ro/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ru/LC_MESSAGES copying django/contrib/admin/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ru/LC_MESSAGES copying django/contrib/admin/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ru/LC_MESSAGES copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ru/LC_MESSAGES copying django/contrib/admin/locale/ru/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sk/LC_MESSAGES copying django/contrib/admin/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sk/LC_MESSAGES copying django/contrib/admin/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sk/LC_MESSAGES copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sk/LC_MESSAGES copying django/contrib/admin/locale/sk/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sl/LC_MESSAGES copying django/contrib/admin/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sl/LC_MESSAGES copying django/contrib/admin/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sl/LC_MESSAGES copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sl/LC_MESSAGES copying django/contrib/admin/locale/sl/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sq/LC_MESSAGES copying django/contrib/admin/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sq/LC_MESSAGES copying django/contrib/admin/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sq/LC_MESSAGES copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sq/LC_MESSAGES copying django/contrib/admin/locale/sq/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr/LC_MESSAGES copying django/contrib/admin/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr/LC_MESSAGES copying django/contrib/admin/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr/LC_MESSAGES copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr/LC_MESSAGES copying django/contrib/admin/locale/sr/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr_Latn/LC_MESSAGES copying django/contrib/admin/locale/sr_Latn/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sv/LC_MESSAGES copying django/contrib/admin/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sv/LC_MESSAGES copying django/contrib/admin/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sv/LC_MESSAGES copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sv/LC_MESSAGES copying django/contrib/admin/locale/sv/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sw/LC_MESSAGES copying django/contrib/admin/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sw/LC_MESSAGES copying django/contrib/admin/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sw/LC_MESSAGES copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sw/LC_MESSAGES copying django/contrib/admin/locale/sw/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ta/LC_MESSAGES copying django/contrib/admin/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ta/LC_MESSAGES copying django/contrib/admin/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ta/LC_MESSAGES copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ta/LC_MESSAGES copying django/contrib/admin/locale/ta/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/te/LC_MESSAGES copying django/contrib/admin/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/te/LC_MESSAGES copying django/contrib/admin/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/te/LC_MESSAGES copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/te/LC_MESSAGES copying django/contrib/admin/locale/te/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tg/LC_MESSAGES copying django/contrib/admin/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tg/LC_MESSAGES copying django/contrib/admin/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tg/LC_MESSAGES copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tg/LC_MESSAGES copying django/contrib/admin/locale/tg/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/th/LC_MESSAGES copying django/contrib/admin/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/th/LC_MESSAGES copying django/contrib/admin/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/th/LC_MESSAGES copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/th/LC_MESSAGES copying django/contrib/admin/locale/th/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tr/LC_MESSAGES copying django/contrib/admin/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tr/LC_MESSAGES copying django/contrib/admin/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tr/LC_MESSAGES copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tr/LC_MESSAGES copying django/contrib/admin/locale/tr/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tt/LC_MESSAGES copying django/contrib/admin/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tt/LC_MESSAGES copying django/contrib/admin/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tt/LC_MESSAGES copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tt/LC_MESSAGES copying django/contrib/admin/locale/tt/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/udm/LC_MESSAGES copying django/contrib/admin/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/udm/LC_MESSAGES copying django/contrib/admin/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/udm/LC_MESSAGES copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/udm/LC_MESSAGES copying django/contrib/admin/locale/udm/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uk/LC_MESSAGES copying django/contrib/admin/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uk/LC_MESSAGES copying django/contrib/admin/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uk/LC_MESSAGES copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uk/LC_MESSAGES copying django/contrib/admin/locale/uk/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ur/LC_MESSAGES copying django/contrib/admin/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ur/LC_MESSAGES copying django/contrib/admin/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ur/LC_MESSAGES copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ur/LC_MESSAGES copying django/contrib/admin/locale/ur/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uz creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uz/LC_MESSAGES copying django/contrib/admin/locale/uz/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uz/LC_MESSAGES copying django/contrib/admin/locale/uz/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uz/LC_MESSAGES copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uz/LC_MESSAGES copying django/contrib/admin/locale/uz/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/uz/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/vi/LC_MESSAGES copying django/contrib/admin/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/vi/LC_MESSAGES copying django/contrib/admin/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/vi/LC_MESSAGES copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/vi/LC_MESSAGES copying django/contrib/admin/locale/vi/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hans/LC_MESSAGES copying django/contrib/admin/locale/zh_Hans/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hant/LC_MESSAGES copying django/contrib/admin/locale/zh_Hant/LC_MESSAGES/djangojs.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/autocomplete.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/base.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/changelists.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/dashboard.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/fonts.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/forms.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/login.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/nav_sidebar.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/responsive.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/responsive_rtl.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/rtl.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css copying django/contrib/admin/static/admin/css/widgets.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css/vendor creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css/vendor/select2 copying django/contrib/admin/static/admin/css/vendor/select2/LICENSE-SELECT2.md -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css/vendor/select2 copying django/contrib/admin/static/admin/css/vendor/select2/select2.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css/vendor/select2 copying django/contrib/admin/static/admin/css/vendor/select2/select2.min.css -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/css/vendor/select2 creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/fonts copying django/contrib/admin/static/admin/fonts/LICENSE.txt -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/fonts copying django/contrib/admin/static/admin/fonts/README.txt -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/fonts copying django/contrib/admin/static/admin/fonts/Roboto-Bold-webfont.woff -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/fonts copying django/contrib/admin/static/admin/fonts/Roboto-Light-webfont.woff -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/fonts copying django/contrib/admin/static/admin/fonts/Roboto-Regular-webfont.woff -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/fonts creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/LICENSE -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/README.txt -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/calendar-icons.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-addlink.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-alert.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-calendar.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-changelink.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-clock.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-deletelink.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-no.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-unknown-alt.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-unknown.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-viewlink.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/icon-yes.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/inline-delete.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/search.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/selector-icons.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/sorting-icons.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/tooltag-add.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img copying django/contrib/admin/static/admin/img/tooltag-arrowright.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img/gis copying django/contrib/admin/static/admin/img/gis/move_vertex_off.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img/gis copying django/contrib/admin/static/admin/img/gis/move_vertex_on.svg -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/img/gis creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/SelectBox.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/SelectFilter2.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/actions.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/autocomplete.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/calendar.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/cancel.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/change_form.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/collapse.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/core.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/inlines.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/jquery.init.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/nav_sidebar.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/popup_response.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/prepopulate.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/prepopulate_init.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js copying django/contrib/admin/static/admin/js/urlify.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/admin copying django/contrib/admin/static/admin/js/admin/DateTimeShortcuts.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/admin copying django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/admin creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/jquery copying django/contrib/admin/static/admin/js/vendor/jquery/LICENSE.txt -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/jquery copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/jquery copying django/contrib/admin/static/admin/js/vendor/jquery/jquery.min.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/jquery creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2 copying django/contrib/admin/static/admin/js/vendor/select2/LICENSE.md -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2 copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2 copying django/contrib/admin/static/admin/js/vendor/select2/select2.full.min.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2 creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/af.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ar.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/az.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bg.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bn.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/bs.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ca.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/cs.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/da.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/de.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/dsb.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/el.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/en.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/es.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/et.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/eu.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fa.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fi.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/fr.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/gl.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/he.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hi.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hr.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hsb.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hu.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/hy.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/id.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/is.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/it.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ja.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ka.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/km.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ko.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lt.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/lv.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/mk.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ms.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nb.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ne.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/nl.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pl.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ps.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt-BR.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/pt.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ro.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/ru.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sk.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sl.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sq.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr-Cyrl.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sr.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/sv.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/th.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tk.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/tr.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/uk.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/vi.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-CN.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n copying django/contrib/admin/static/admin/js/vendor/select2/i18n/zh-TW.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/select2/i18n creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/xregexp copying django/contrib/admin/static/admin/js/vendor/xregexp/LICENSE.txt -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/xregexp copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/xregexp copying django/contrib/admin/static/admin/js/vendor/xregexp/xregexp.min.js -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/static/admin/js/vendor/xregexp creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/404.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/500.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/actions.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/app_index.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/app_list.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/base.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/base_site.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_form.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_form_object_tools.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_list.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_list_object_tools.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/change_list_results.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/date_hierarchy.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/delete_confirmation.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/delete_selected_confirmation.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/filter.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/index.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/invalid_setup.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/login.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/nav_sidebar.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/object_history.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/pagination.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/popup_response.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/prepopulated_fields_js.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/search_form.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin copying django/contrib/admin/templates/admin/submit_line.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/auth creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/auth/user copying django/contrib/admin/templates/admin/auth/user/add_form.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/auth/user copying django/contrib/admin/templates/admin/auth/user/change_password.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/auth/user creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/edit_inline copying django/contrib/admin/templates/admin/edit_inline/stacked.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/edit_inline copying django/contrib/admin/templates/admin/edit_inline/tabular.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/edit_inline creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/includes copying django/contrib/admin/templates/admin/includes/fieldset.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/includes copying django/contrib/admin/templates/admin/includes/object_delete_summary.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/includes creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/clearable_file_input.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/foreign_key_raw_id.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/many_to_many_raw_id.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/radio.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/related_widget_wrapper.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/split_datetime.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/widgets copying django/contrib/admin/templates/admin/widgets/url.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/admin/widgets creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/logged_out.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_change_done.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_change_form.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_complete.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_confirm.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_done.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_email.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration copying django/contrib/admin/templates/registration/password_reset_form.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admin/templates/registration creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/af/LC_MESSAGES copying django/contrib/sites/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/af/LC_MESSAGES copying django/contrib/sites/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ar/LC_MESSAGES copying django/contrib/sites/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ar/LC_MESSAGES copying django/contrib/sites/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ar_DZ/LC_MESSAGES copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ar_DZ/LC_MESSAGES copying django/contrib/sites/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ast/LC_MESSAGES copying django/contrib/sites/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ast/LC_MESSAGES copying django/contrib/sites/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/az/LC_MESSAGES copying django/contrib/sites/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/az/LC_MESSAGES copying django/contrib/sites/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/be/LC_MESSAGES copying django/contrib/sites/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/be/LC_MESSAGES copying django/contrib/sites/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bg/LC_MESSAGES copying django/contrib/sites/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bg/LC_MESSAGES copying django/contrib/sites/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bn/LC_MESSAGES copying django/contrib/sites/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bn/LC_MESSAGES copying django/contrib/sites/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/br/LC_MESSAGES copying django/contrib/sites/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/br/LC_MESSAGES copying django/contrib/sites/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bs/LC_MESSAGES copying django/contrib/sites/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bs/LC_MESSAGES copying django/contrib/sites/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ca/LC_MESSAGES copying django/contrib/sites/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ca/LC_MESSAGES copying django/contrib/sites/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/cs/LC_MESSAGES copying django/contrib/sites/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/cs/LC_MESSAGES copying django/contrib/sites/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/cy/LC_MESSAGES copying django/contrib/sites/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/cy/LC_MESSAGES copying django/contrib/sites/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/da/LC_MESSAGES copying django/contrib/sites/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/da/LC_MESSAGES copying django/contrib/sites/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/de/LC_MESSAGES copying django/contrib/sites/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/de/LC_MESSAGES copying django/contrib/sites/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/dsb/LC_MESSAGES copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/dsb/LC_MESSAGES copying django/contrib/sites/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/el/LC_MESSAGES copying django/contrib/sites/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/el/LC_MESSAGES copying django/contrib/sites/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en/LC_MESSAGES copying django/contrib/sites/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en/LC_MESSAGES copying django/contrib/sites/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en_AU/LC_MESSAGES copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en_AU/LC_MESSAGES copying django/contrib/sites/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en_GB/LC_MESSAGES copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en_GB/LC_MESSAGES copying django/contrib/sites/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/eo/LC_MESSAGES copying django/contrib/sites/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/eo/LC_MESSAGES copying django/contrib/sites/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es/LC_MESSAGES copying django/contrib/sites/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es/LC_MESSAGES copying django/contrib/sites/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_AR/LC_MESSAGES copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_AR/LC_MESSAGES copying django/contrib/sites/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_CO/LC_MESSAGES copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_CO/LC_MESSAGES copying django/contrib/sites/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_MX/LC_MESSAGES copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_MX/LC_MESSAGES copying django/contrib/sites/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_VE/LC_MESSAGES copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_VE/LC_MESSAGES copying django/contrib/sites/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/et/LC_MESSAGES copying django/contrib/sites/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/et/LC_MESSAGES copying django/contrib/sites/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/eu/LC_MESSAGES copying django/contrib/sites/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/eu/LC_MESSAGES copying django/contrib/sites/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fa/LC_MESSAGES copying django/contrib/sites/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fa/LC_MESSAGES copying django/contrib/sites/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fi/LC_MESSAGES copying django/contrib/sites/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fi/LC_MESSAGES copying django/contrib/sites/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fr/LC_MESSAGES copying django/contrib/sites/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fr/LC_MESSAGES copying django/contrib/sites/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fy/LC_MESSAGES copying django/contrib/sites/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fy/LC_MESSAGES copying django/contrib/sites/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ga/LC_MESSAGES copying django/contrib/sites/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ga/LC_MESSAGES copying django/contrib/sites/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/gd/LC_MESSAGES copying django/contrib/sites/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/gd/LC_MESSAGES copying django/contrib/sites/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/gl/LC_MESSAGES copying django/contrib/sites/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/gl/LC_MESSAGES copying django/contrib/sites/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/he/LC_MESSAGES copying django/contrib/sites/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/he/LC_MESSAGES copying django/contrib/sites/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hi/LC_MESSAGES copying django/contrib/sites/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hi/LC_MESSAGES copying django/contrib/sites/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hr/LC_MESSAGES copying django/contrib/sites/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hr/LC_MESSAGES copying django/contrib/sites/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hsb/LC_MESSAGES copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hsb/LC_MESSAGES copying django/contrib/sites/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hu/LC_MESSAGES copying django/contrib/sites/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hu/LC_MESSAGES copying django/contrib/sites/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hy/LC_MESSAGES copying django/contrib/sites/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hy/LC_MESSAGES copying django/contrib/sites/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ia/LC_MESSAGES copying django/contrib/sites/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ia/LC_MESSAGES copying django/contrib/sites/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/id/LC_MESSAGES copying django/contrib/sites/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/id/LC_MESSAGES copying django/contrib/sites/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/io/LC_MESSAGES copying django/contrib/sites/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/io/LC_MESSAGES copying django/contrib/sites/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/is/LC_MESSAGES copying django/contrib/sites/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/is/LC_MESSAGES copying django/contrib/sites/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/it/LC_MESSAGES copying django/contrib/sites/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/it/LC_MESSAGES copying django/contrib/sites/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ja/LC_MESSAGES copying django/contrib/sites/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ja/LC_MESSAGES copying django/contrib/sites/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ka/LC_MESSAGES copying django/contrib/sites/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ka/LC_MESSAGES copying django/contrib/sites/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kab creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kab/LC_MESSAGES copying django/contrib/sites/locale/kab/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kab/LC_MESSAGES copying django/contrib/sites/locale/kab/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kab/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kk/LC_MESSAGES copying django/contrib/sites/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kk/LC_MESSAGES copying django/contrib/sites/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/km/LC_MESSAGES copying django/contrib/sites/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/km/LC_MESSAGES copying django/contrib/sites/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kn/LC_MESSAGES copying django/contrib/sites/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kn/LC_MESSAGES copying django/contrib/sites/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ko/LC_MESSAGES copying django/contrib/sites/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ko/LC_MESSAGES copying django/contrib/sites/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ky/LC_MESSAGES copying django/contrib/sites/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ky/LC_MESSAGES copying django/contrib/sites/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lb/LC_MESSAGES copying django/contrib/sites/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lb/LC_MESSAGES copying django/contrib/sites/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lt/LC_MESSAGES copying django/contrib/sites/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lt/LC_MESSAGES copying django/contrib/sites/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lv/LC_MESSAGES copying django/contrib/sites/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lv/LC_MESSAGES copying django/contrib/sites/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mk/LC_MESSAGES copying django/contrib/sites/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mk/LC_MESSAGES copying django/contrib/sites/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ml/LC_MESSAGES copying django/contrib/sites/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ml/LC_MESSAGES copying django/contrib/sites/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mn/LC_MESSAGES copying django/contrib/sites/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mn/LC_MESSAGES copying django/contrib/sites/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mr/LC_MESSAGES copying django/contrib/sites/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mr/LC_MESSAGES copying django/contrib/sites/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/my/LC_MESSAGES copying django/contrib/sites/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/my/LC_MESSAGES copying django/contrib/sites/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nb/LC_MESSAGES copying django/contrib/sites/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nb/LC_MESSAGES copying django/contrib/sites/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ne/LC_MESSAGES copying django/contrib/sites/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ne/LC_MESSAGES copying django/contrib/sites/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nl/LC_MESSAGES copying django/contrib/sites/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nl/LC_MESSAGES copying django/contrib/sites/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nn/LC_MESSAGES copying django/contrib/sites/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nn/LC_MESSAGES copying django/contrib/sites/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/os/LC_MESSAGES copying django/contrib/sites/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/os/LC_MESSAGES copying django/contrib/sites/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pa/LC_MESSAGES copying django/contrib/sites/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pa/LC_MESSAGES copying django/contrib/sites/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pl/LC_MESSAGES copying django/contrib/sites/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pl/LC_MESSAGES copying django/contrib/sites/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pt/LC_MESSAGES copying django/contrib/sites/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pt/LC_MESSAGES copying django/contrib/sites/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pt_BR/LC_MESSAGES copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pt_BR/LC_MESSAGES copying django/contrib/sites/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ro/LC_MESSAGES copying django/contrib/sites/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ro/LC_MESSAGES copying django/contrib/sites/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ru/LC_MESSAGES copying django/contrib/sites/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ru/LC_MESSAGES copying django/contrib/sites/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sk/LC_MESSAGES copying django/contrib/sites/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sk/LC_MESSAGES copying django/contrib/sites/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sl/LC_MESSAGES copying django/contrib/sites/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sl/LC_MESSAGES copying django/contrib/sites/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sq/LC_MESSAGES copying django/contrib/sites/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sq/LC_MESSAGES copying django/contrib/sites/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sr/LC_MESSAGES copying django/contrib/sites/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sr/LC_MESSAGES copying django/contrib/sites/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sr_Latn/LC_MESSAGES copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sr_Latn/LC_MESSAGES copying django/contrib/sites/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sv/LC_MESSAGES copying django/contrib/sites/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sv/LC_MESSAGES copying django/contrib/sites/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sw/LC_MESSAGES copying django/contrib/sites/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sw/LC_MESSAGES copying django/contrib/sites/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ta/LC_MESSAGES copying django/contrib/sites/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ta/LC_MESSAGES copying django/contrib/sites/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/te/LC_MESSAGES copying django/contrib/sites/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/te/LC_MESSAGES copying django/contrib/sites/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tg/LC_MESSAGES copying django/contrib/sites/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tg/LC_MESSAGES copying django/contrib/sites/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/th/LC_MESSAGES copying django/contrib/sites/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/th/LC_MESSAGES copying django/contrib/sites/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tk/LC_MESSAGES copying django/contrib/sites/locale/tk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tk/LC_MESSAGES copying django/contrib/sites/locale/tk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tr/LC_MESSAGES copying django/contrib/sites/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tr/LC_MESSAGES copying django/contrib/sites/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tt/LC_MESSAGES copying django/contrib/sites/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tt/LC_MESSAGES copying django/contrib/sites/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/udm/LC_MESSAGES copying django/contrib/sites/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/udm/LC_MESSAGES copying django/contrib/sites/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/uk/LC_MESSAGES copying django/contrib/sites/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/uk/LC_MESSAGES copying django/contrib/sites/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ur/LC_MESSAGES copying django/contrib/sites/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ur/LC_MESSAGES copying django/contrib/sites/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/uz creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/uz/LC_MESSAGES copying django/contrib/sites/locale/uz/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/uz/LC_MESSAGES copying django/contrib/sites/locale/uz/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/uz/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/vi/LC_MESSAGES copying django/contrib/sites/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/vi/LC_MESSAGES copying django/contrib/sites/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/zh_Hans/LC_MESSAGES copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/zh_Hans/LC_MESSAGES copying django/contrib/sites/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/zh_Hant/LC_MESSAGES copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/zh_Hant/LC_MESSAGES copying django/contrib/sites/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sites/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/af/LC_MESSAGES copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/af/LC_MESSAGES copying django/contrib/admindocs/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ar/LC_MESSAGES copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ar/LC_MESSAGES copying django/contrib/admindocs/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES copying django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ast/LC_MESSAGES copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ast/LC_MESSAGES copying django/contrib/admindocs/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/az/LC_MESSAGES copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/az/LC_MESSAGES copying django/contrib/admindocs/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/be/LC_MESSAGES copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/be/LC_MESSAGES copying django/contrib/admindocs/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bg/LC_MESSAGES copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bg/LC_MESSAGES copying django/contrib/admindocs/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bn/LC_MESSAGES copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bn/LC_MESSAGES copying django/contrib/admindocs/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/br/LC_MESSAGES copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/br/LC_MESSAGES copying django/contrib/admindocs/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bs/LC_MESSAGES copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bs/LC_MESSAGES copying django/contrib/admindocs/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ca/LC_MESSAGES copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ca/LC_MESSAGES copying django/contrib/admindocs/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/cs/LC_MESSAGES copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/cs/LC_MESSAGES copying django/contrib/admindocs/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/cy/LC_MESSAGES copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/cy/LC_MESSAGES copying django/contrib/admindocs/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/da/LC_MESSAGES copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/da/LC_MESSAGES copying django/contrib/admindocs/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/de/LC_MESSAGES copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/de/LC_MESSAGES copying django/contrib/admindocs/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/dsb/LC_MESSAGES copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/dsb/LC_MESSAGES copying django/contrib/admindocs/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/el/LC_MESSAGES copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/el/LC_MESSAGES copying django/contrib/admindocs/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en/LC_MESSAGES copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en/LC_MESSAGES copying django/contrib/admindocs/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en_AU/LC_MESSAGES copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en_AU/LC_MESSAGES copying django/contrib/admindocs/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en_GB/LC_MESSAGES copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en_GB/LC_MESSAGES copying django/contrib/admindocs/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/eo/LC_MESSAGES copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/eo/LC_MESSAGES copying django/contrib/admindocs/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es/LC_MESSAGES copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es/LC_MESSAGES copying django/contrib/admindocs/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_AR/LC_MESSAGES copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_AR/LC_MESSAGES copying django/contrib/admindocs/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_CO/LC_MESSAGES copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_CO/LC_MESSAGES copying django/contrib/admindocs/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_MX/LC_MESSAGES copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_MX/LC_MESSAGES copying django/contrib/admindocs/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_VE/LC_MESSAGES copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_VE/LC_MESSAGES copying django/contrib/admindocs/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/et/LC_MESSAGES copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/et/LC_MESSAGES copying django/contrib/admindocs/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/eu/LC_MESSAGES copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/eu/LC_MESSAGES copying django/contrib/admindocs/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fa/LC_MESSAGES copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fa/LC_MESSAGES copying django/contrib/admindocs/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fi/LC_MESSAGES copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fi/LC_MESSAGES copying django/contrib/admindocs/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fr/LC_MESSAGES copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fr/LC_MESSAGES copying django/contrib/admindocs/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fy/LC_MESSAGES copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fy/LC_MESSAGES copying django/contrib/admindocs/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ga/LC_MESSAGES copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ga/LC_MESSAGES copying django/contrib/admindocs/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/gd/LC_MESSAGES copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/gd/LC_MESSAGES copying django/contrib/admindocs/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/gl/LC_MESSAGES copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/gl/LC_MESSAGES copying django/contrib/admindocs/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/he/LC_MESSAGES copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/he/LC_MESSAGES copying django/contrib/admindocs/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hi/LC_MESSAGES copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hi/LC_MESSAGES copying django/contrib/admindocs/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hr/LC_MESSAGES copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hr/LC_MESSAGES copying django/contrib/admindocs/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hsb/LC_MESSAGES copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hsb/LC_MESSAGES copying django/contrib/admindocs/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hu/LC_MESSAGES copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hu/LC_MESSAGES copying django/contrib/admindocs/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ia/LC_MESSAGES copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ia/LC_MESSAGES copying django/contrib/admindocs/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/id/LC_MESSAGES copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/id/LC_MESSAGES copying django/contrib/admindocs/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/io/LC_MESSAGES copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/io/LC_MESSAGES copying django/contrib/admindocs/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/is/LC_MESSAGES copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/is/LC_MESSAGES copying django/contrib/admindocs/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/it/LC_MESSAGES copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/it/LC_MESSAGES copying django/contrib/admindocs/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ja/LC_MESSAGES copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ja/LC_MESSAGES copying django/contrib/admindocs/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ka/LC_MESSAGES copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ka/LC_MESSAGES copying django/contrib/admindocs/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kab creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kab/LC_MESSAGES copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kab/LC_MESSAGES copying django/contrib/admindocs/locale/kab/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kab/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kk/LC_MESSAGES copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kk/LC_MESSAGES copying django/contrib/admindocs/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/km/LC_MESSAGES copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/km/LC_MESSAGES copying django/contrib/admindocs/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kn/LC_MESSAGES copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kn/LC_MESSAGES copying django/contrib/admindocs/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ko/LC_MESSAGES copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ko/LC_MESSAGES copying django/contrib/admindocs/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ky/LC_MESSAGES copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ky/LC_MESSAGES copying django/contrib/admindocs/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lb/LC_MESSAGES copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lb/LC_MESSAGES copying django/contrib/admindocs/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lt/LC_MESSAGES copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lt/LC_MESSAGES copying django/contrib/admindocs/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lv/LC_MESSAGES copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lv/LC_MESSAGES copying django/contrib/admindocs/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mk/LC_MESSAGES copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mk/LC_MESSAGES copying django/contrib/admindocs/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ml/LC_MESSAGES copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ml/LC_MESSAGES copying django/contrib/admindocs/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mn/LC_MESSAGES copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mn/LC_MESSAGES copying django/contrib/admindocs/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mr/LC_MESSAGES copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mr/LC_MESSAGES copying django/contrib/admindocs/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/my/LC_MESSAGES copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/my/LC_MESSAGES copying django/contrib/admindocs/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nb/LC_MESSAGES copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nb/LC_MESSAGES copying django/contrib/admindocs/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ne/LC_MESSAGES copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ne/LC_MESSAGES copying django/contrib/admindocs/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nl/LC_MESSAGES copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nl/LC_MESSAGES copying django/contrib/admindocs/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nn/LC_MESSAGES copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nn/LC_MESSAGES copying django/contrib/admindocs/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/os/LC_MESSAGES copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/os/LC_MESSAGES copying django/contrib/admindocs/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pa/LC_MESSAGES copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pa/LC_MESSAGES copying django/contrib/admindocs/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pl/LC_MESSAGES copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pl/LC_MESSAGES copying django/contrib/admindocs/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pt/LC_MESSAGES copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pt/LC_MESSAGES copying django/contrib/admindocs/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES copying django/contrib/admindocs/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ro/LC_MESSAGES copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ro/LC_MESSAGES copying django/contrib/admindocs/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ru/LC_MESSAGES copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ru/LC_MESSAGES copying django/contrib/admindocs/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sk/LC_MESSAGES copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sk/LC_MESSAGES copying django/contrib/admindocs/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sl/LC_MESSAGES copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sl/LC_MESSAGES copying django/contrib/admindocs/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sq/LC_MESSAGES copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sq/LC_MESSAGES copying django/contrib/admindocs/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sr/LC_MESSAGES copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sr/LC_MESSAGES copying django/contrib/admindocs/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES copying django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sv/LC_MESSAGES copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sv/LC_MESSAGES copying django/contrib/admindocs/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sw/LC_MESSAGES copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sw/LC_MESSAGES copying django/contrib/admindocs/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ta/LC_MESSAGES copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ta/LC_MESSAGES copying django/contrib/admindocs/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/te/LC_MESSAGES copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/te/LC_MESSAGES copying django/contrib/admindocs/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tg/LC_MESSAGES copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tg/LC_MESSAGES copying django/contrib/admindocs/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/th/LC_MESSAGES copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/th/LC_MESSAGES copying django/contrib/admindocs/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tr/LC_MESSAGES copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tr/LC_MESSAGES copying django/contrib/admindocs/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tt/LC_MESSAGES copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tt/LC_MESSAGES copying django/contrib/admindocs/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/udm/LC_MESSAGES copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/udm/LC_MESSAGES copying django/contrib/admindocs/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/uk/LC_MESSAGES copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/uk/LC_MESSAGES copying django/contrib/admindocs/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ur/LC_MESSAGES copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ur/LC_MESSAGES copying django/contrib/admindocs/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/vi/LC_MESSAGES copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/vi/LC_MESSAGES copying django/contrib/admindocs/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES copying django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES copying django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/bookmarklets.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/index.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/missing_docutils.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/model_detail.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/model_index.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/template_detail.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/template_filter_index.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/template_tag_index.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/view_detail.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc copying django/contrib/admindocs/templates/admin_doc/view_index.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/admindocs/templates/admin_doc creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/af/LC_MESSAGES copying django/contrib/sessions/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/af/LC_MESSAGES copying django/contrib/sessions/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ar/LC_MESSAGES copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ar/LC_MESSAGES copying django/contrib/sessions/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES copying django/contrib/sessions/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ast/LC_MESSAGES copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ast/LC_MESSAGES copying django/contrib/sessions/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/az/LC_MESSAGES copying django/contrib/sessions/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/az/LC_MESSAGES copying django/contrib/sessions/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/be/LC_MESSAGES copying django/contrib/sessions/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/be/LC_MESSAGES copying django/contrib/sessions/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bg/LC_MESSAGES copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bg/LC_MESSAGES copying django/contrib/sessions/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bn/LC_MESSAGES copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bn/LC_MESSAGES copying django/contrib/sessions/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/br/LC_MESSAGES copying django/contrib/sessions/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/br/LC_MESSAGES copying django/contrib/sessions/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bs/LC_MESSAGES copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bs/LC_MESSAGES copying django/contrib/sessions/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ca/LC_MESSAGES copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ca/LC_MESSAGES copying django/contrib/sessions/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/cs/LC_MESSAGES copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/cs/LC_MESSAGES copying django/contrib/sessions/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/cy/LC_MESSAGES copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/cy/LC_MESSAGES copying django/contrib/sessions/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/da/LC_MESSAGES copying django/contrib/sessions/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/da/LC_MESSAGES copying django/contrib/sessions/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/de/LC_MESSAGES copying django/contrib/sessions/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/de/LC_MESSAGES copying django/contrib/sessions/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/dsb/LC_MESSAGES copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/dsb/LC_MESSAGES copying django/contrib/sessions/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/el/LC_MESSAGES copying django/contrib/sessions/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/el/LC_MESSAGES copying django/contrib/sessions/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en/LC_MESSAGES copying django/contrib/sessions/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en/LC_MESSAGES copying django/contrib/sessions/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en_AU/LC_MESSAGES copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en_AU/LC_MESSAGES copying django/contrib/sessions/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en_GB/LC_MESSAGES copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en_GB/LC_MESSAGES copying django/contrib/sessions/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/eo/LC_MESSAGES copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/eo/LC_MESSAGES copying django/contrib/sessions/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es/LC_MESSAGES copying django/contrib/sessions/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es/LC_MESSAGES copying django/contrib/sessions/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_AR/LC_MESSAGES copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_AR/LC_MESSAGES copying django/contrib/sessions/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_CO/LC_MESSAGES copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_CO/LC_MESSAGES copying django/contrib/sessions/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_MX/LC_MESSAGES copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_MX/LC_MESSAGES copying django/contrib/sessions/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_VE/LC_MESSAGES copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_VE/LC_MESSAGES copying django/contrib/sessions/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/et/LC_MESSAGES copying django/contrib/sessions/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/et/LC_MESSAGES copying django/contrib/sessions/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/eu/LC_MESSAGES copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/eu/LC_MESSAGES copying django/contrib/sessions/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fa/LC_MESSAGES copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fa/LC_MESSAGES copying django/contrib/sessions/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fi/LC_MESSAGES copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fi/LC_MESSAGES copying django/contrib/sessions/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fr/LC_MESSAGES copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fr/LC_MESSAGES copying django/contrib/sessions/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fy/LC_MESSAGES copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fy/LC_MESSAGES copying django/contrib/sessions/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ga/LC_MESSAGES copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ga/LC_MESSAGES copying django/contrib/sessions/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/gd/LC_MESSAGES copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/gd/LC_MESSAGES copying django/contrib/sessions/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/gl/LC_MESSAGES copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/gl/LC_MESSAGES copying django/contrib/sessions/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/he/LC_MESSAGES copying django/contrib/sessions/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/he/LC_MESSAGES copying django/contrib/sessions/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hi/LC_MESSAGES copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hi/LC_MESSAGES copying django/contrib/sessions/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hr/LC_MESSAGES copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hr/LC_MESSAGES copying django/contrib/sessions/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hsb/LC_MESSAGES copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hsb/LC_MESSAGES copying django/contrib/sessions/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hu/LC_MESSAGES copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hu/LC_MESSAGES copying django/contrib/sessions/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hy/LC_MESSAGES copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hy/LC_MESSAGES copying django/contrib/sessions/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ia/LC_MESSAGES copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ia/LC_MESSAGES copying django/contrib/sessions/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/id/LC_MESSAGES copying django/contrib/sessions/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/id/LC_MESSAGES copying django/contrib/sessions/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/io/LC_MESSAGES copying django/contrib/sessions/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/io/LC_MESSAGES copying django/contrib/sessions/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/is/LC_MESSAGES copying django/contrib/sessions/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/is/LC_MESSAGES copying django/contrib/sessions/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/it/LC_MESSAGES copying django/contrib/sessions/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/it/LC_MESSAGES copying django/contrib/sessions/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ja/LC_MESSAGES copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ja/LC_MESSAGES copying django/contrib/sessions/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ka/LC_MESSAGES copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ka/LC_MESSAGES copying django/contrib/sessions/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kab creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kab/LC_MESSAGES copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kab/LC_MESSAGES copying django/contrib/sessions/locale/kab/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kab/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kk/LC_MESSAGES copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kk/LC_MESSAGES copying django/contrib/sessions/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/km/LC_MESSAGES copying django/contrib/sessions/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/km/LC_MESSAGES copying django/contrib/sessions/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kn/LC_MESSAGES copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kn/LC_MESSAGES copying django/contrib/sessions/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ko/LC_MESSAGES copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ko/LC_MESSAGES copying django/contrib/sessions/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ky/LC_MESSAGES copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ky/LC_MESSAGES copying django/contrib/sessions/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lb/LC_MESSAGES copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lb/LC_MESSAGES copying django/contrib/sessions/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lt/LC_MESSAGES copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lt/LC_MESSAGES copying django/contrib/sessions/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lv/LC_MESSAGES copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lv/LC_MESSAGES copying django/contrib/sessions/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mk/LC_MESSAGES copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mk/LC_MESSAGES copying django/contrib/sessions/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ml/LC_MESSAGES copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ml/LC_MESSAGES copying django/contrib/sessions/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mn/LC_MESSAGES copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mn/LC_MESSAGES copying django/contrib/sessions/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mr/LC_MESSAGES copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mr/LC_MESSAGES copying django/contrib/sessions/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/my/LC_MESSAGES copying django/contrib/sessions/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/my/LC_MESSAGES copying django/contrib/sessions/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nb/LC_MESSAGES copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nb/LC_MESSAGES copying django/contrib/sessions/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ne/LC_MESSAGES copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ne/LC_MESSAGES copying django/contrib/sessions/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nl/LC_MESSAGES copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nl/LC_MESSAGES copying django/contrib/sessions/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nn/LC_MESSAGES copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nn/LC_MESSAGES copying django/contrib/sessions/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/os/LC_MESSAGES copying django/contrib/sessions/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/os/LC_MESSAGES copying django/contrib/sessions/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pa/LC_MESSAGES copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pa/LC_MESSAGES copying django/contrib/sessions/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pl/LC_MESSAGES copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pl/LC_MESSAGES copying django/contrib/sessions/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pt/LC_MESSAGES copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pt/LC_MESSAGES copying django/contrib/sessions/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pt_BR/LC_MESSAGES copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pt_BR/LC_MESSAGES copying django/contrib/sessions/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ro/LC_MESSAGES copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ro/LC_MESSAGES copying django/contrib/sessions/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ru/LC_MESSAGES copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ru/LC_MESSAGES copying django/contrib/sessions/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sk/LC_MESSAGES copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sk/LC_MESSAGES copying django/contrib/sessions/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sl/LC_MESSAGES copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sl/LC_MESSAGES copying django/contrib/sessions/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sq/LC_MESSAGES copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sq/LC_MESSAGES copying django/contrib/sessions/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sr/LC_MESSAGES copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sr/LC_MESSAGES copying django/contrib/sessions/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES copying django/contrib/sessions/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sv/LC_MESSAGES copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sv/LC_MESSAGES copying django/contrib/sessions/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sw/LC_MESSAGES copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sw/LC_MESSAGES copying django/contrib/sessions/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ta/LC_MESSAGES copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ta/LC_MESSAGES copying django/contrib/sessions/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/te/LC_MESSAGES copying django/contrib/sessions/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/te/LC_MESSAGES copying django/contrib/sessions/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tg/LC_MESSAGES copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tg/LC_MESSAGES copying django/contrib/sessions/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/th/LC_MESSAGES copying django/contrib/sessions/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/th/LC_MESSAGES copying django/contrib/sessions/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tk/LC_MESSAGES copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tk/LC_MESSAGES copying django/contrib/sessions/locale/tk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tr/LC_MESSAGES copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tr/LC_MESSAGES copying django/contrib/sessions/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tt/LC_MESSAGES copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tt/LC_MESSAGES copying django/contrib/sessions/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/udm/LC_MESSAGES copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/udm/LC_MESSAGES copying django/contrib/sessions/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/uk/LC_MESSAGES copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/uk/LC_MESSAGES copying django/contrib/sessions/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ur/LC_MESSAGES copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ur/LC_MESSAGES copying django/contrib/sessions/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/uz creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/uz/LC_MESSAGES copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/uz/LC_MESSAGES copying django/contrib/sessions/locale/uz/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/uz/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/vi/LC_MESSAGES copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/vi/LC_MESSAGES copying django/contrib/sessions/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES copying django/contrib/sessions/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying django/contrib/sessions/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/sessions/locale/zh_Hant/LC_MESSAGES copying django/contrib/auth/common-passwords.txt.gz -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/af/LC_MESSAGES copying django/contrib/auth/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/af/LC_MESSAGES copying django/contrib/auth/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ar/LC_MESSAGES copying django/contrib/auth/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ar/LC_MESSAGES copying django/contrib/auth/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ar_DZ/LC_MESSAGES copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ar_DZ/LC_MESSAGES copying django/contrib/auth/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ast/LC_MESSAGES copying django/contrib/auth/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ast/LC_MESSAGES copying django/contrib/auth/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/az/LC_MESSAGES copying django/contrib/auth/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/az/LC_MESSAGES copying django/contrib/auth/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/be/LC_MESSAGES copying django/contrib/auth/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/be/LC_MESSAGES copying django/contrib/auth/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bg/LC_MESSAGES copying django/contrib/auth/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bg/LC_MESSAGES copying django/contrib/auth/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bn/LC_MESSAGES copying django/contrib/auth/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bn/LC_MESSAGES copying django/contrib/auth/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/br/LC_MESSAGES copying django/contrib/auth/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/br/LC_MESSAGES copying django/contrib/auth/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bs/LC_MESSAGES copying django/contrib/auth/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bs/LC_MESSAGES copying django/contrib/auth/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ca/LC_MESSAGES copying django/contrib/auth/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ca/LC_MESSAGES copying django/contrib/auth/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/cs/LC_MESSAGES copying django/contrib/auth/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/cs/LC_MESSAGES copying django/contrib/auth/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/cy/LC_MESSAGES copying django/contrib/auth/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/cy/LC_MESSAGES copying django/contrib/auth/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/da/LC_MESSAGES copying django/contrib/auth/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/da/LC_MESSAGES copying django/contrib/auth/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/de/LC_MESSAGES copying django/contrib/auth/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/de/LC_MESSAGES copying django/contrib/auth/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/dsb/LC_MESSAGES copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/dsb/LC_MESSAGES copying django/contrib/auth/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/el/LC_MESSAGES copying django/contrib/auth/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/el/LC_MESSAGES copying django/contrib/auth/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en/LC_MESSAGES copying django/contrib/auth/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en/LC_MESSAGES copying django/contrib/auth/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en_AU/LC_MESSAGES copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en_AU/LC_MESSAGES copying django/contrib/auth/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en_GB/LC_MESSAGES copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en_GB/LC_MESSAGES copying django/contrib/auth/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/eo/LC_MESSAGES copying django/contrib/auth/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/eo/LC_MESSAGES copying django/contrib/auth/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es/LC_MESSAGES copying django/contrib/auth/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es/LC_MESSAGES copying django/contrib/auth/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_AR/LC_MESSAGES copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_AR/LC_MESSAGES copying django/contrib/auth/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_CO/LC_MESSAGES copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_CO/LC_MESSAGES copying django/contrib/auth/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_MX/LC_MESSAGES copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_MX/LC_MESSAGES copying django/contrib/auth/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_VE/LC_MESSAGES copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_VE/LC_MESSAGES copying django/contrib/auth/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/et/LC_MESSAGES copying django/contrib/auth/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/et/LC_MESSAGES copying django/contrib/auth/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/eu/LC_MESSAGES copying django/contrib/auth/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/eu/LC_MESSAGES copying django/contrib/auth/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fa/LC_MESSAGES copying django/contrib/auth/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fa/LC_MESSAGES copying django/contrib/auth/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fi/LC_MESSAGES copying django/contrib/auth/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fi/LC_MESSAGES copying django/contrib/auth/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fr/LC_MESSAGES copying django/contrib/auth/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fr/LC_MESSAGES copying django/contrib/auth/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fy/LC_MESSAGES copying django/contrib/auth/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fy/LC_MESSAGES copying django/contrib/auth/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ga/LC_MESSAGES copying django/contrib/auth/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ga/LC_MESSAGES copying django/contrib/auth/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/gd/LC_MESSAGES copying django/contrib/auth/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/gd/LC_MESSAGES copying django/contrib/auth/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/gl/LC_MESSAGES copying django/contrib/auth/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/gl/LC_MESSAGES copying django/contrib/auth/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/he/LC_MESSAGES copying django/contrib/auth/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/he/LC_MESSAGES copying django/contrib/auth/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hi/LC_MESSAGES copying django/contrib/auth/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hi/LC_MESSAGES copying django/contrib/auth/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hr/LC_MESSAGES copying django/contrib/auth/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hr/LC_MESSAGES copying django/contrib/auth/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hsb/LC_MESSAGES copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hsb/LC_MESSAGES copying django/contrib/auth/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hu/LC_MESSAGES copying django/contrib/auth/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hu/LC_MESSAGES copying django/contrib/auth/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hy/LC_MESSAGES copying django/contrib/auth/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hy/LC_MESSAGES copying django/contrib/auth/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ia/LC_MESSAGES copying django/contrib/auth/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ia/LC_MESSAGES copying django/contrib/auth/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/id/LC_MESSAGES copying django/contrib/auth/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/id/LC_MESSAGES copying django/contrib/auth/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/io/LC_MESSAGES copying django/contrib/auth/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/io/LC_MESSAGES copying django/contrib/auth/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/is/LC_MESSAGES copying django/contrib/auth/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/is/LC_MESSAGES copying django/contrib/auth/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/it/LC_MESSAGES copying django/contrib/auth/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/it/LC_MESSAGES copying django/contrib/auth/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ja/LC_MESSAGES copying django/contrib/auth/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ja/LC_MESSAGES copying django/contrib/auth/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ka/LC_MESSAGES copying django/contrib/auth/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ka/LC_MESSAGES copying django/contrib/auth/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kab creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kab/LC_MESSAGES copying django/contrib/auth/locale/kab/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kab/LC_MESSAGES copying django/contrib/auth/locale/kab/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kab/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kk/LC_MESSAGES copying django/contrib/auth/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kk/LC_MESSAGES copying django/contrib/auth/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/km/LC_MESSAGES copying django/contrib/auth/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/km/LC_MESSAGES copying django/contrib/auth/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kn/LC_MESSAGES copying django/contrib/auth/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kn/LC_MESSAGES copying django/contrib/auth/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ko/LC_MESSAGES copying django/contrib/auth/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ko/LC_MESSAGES copying django/contrib/auth/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ky/LC_MESSAGES copying django/contrib/auth/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ky/LC_MESSAGES copying django/contrib/auth/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lb/LC_MESSAGES copying django/contrib/auth/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lb/LC_MESSAGES copying django/contrib/auth/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lt/LC_MESSAGES copying django/contrib/auth/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lt/LC_MESSAGES copying django/contrib/auth/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lv/LC_MESSAGES copying django/contrib/auth/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lv/LC_MESSAGES copying django/contrib/auth/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mk/LC_MESSAGES copying django/contrib/auth/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mk/LC_MESSAGES copying django/contrib/auth/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ml/LC_MESSAGES copying django/contrib/auth/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ml/LC_MESSAGES copying django/contrib/auth/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mn/LC_MESSAGES copying django/contrib/auth/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mn/LC_MESSAGES copying django/contrib/auth/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mr/LC_MESSAGES copying django/contrib/auth/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mr/LC_MESSAGES copying django/contrib/auth/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/my/LC_MESSAGES copying django/contrib/auth/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/my/LC_MESSAGES copying django/contrib/auth/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nb/LC_MESSAGES copying django/contrib/auth/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nb/LC_MESSAGES copying django/contrib/auth/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ne/LC_MESSAGES copying django/contrib/auth/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ne/LC_MESSAGES copying django/contrib/auth/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nl/LC_MESSAGES copying django/contrib/auth/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nl/LC_MESSAGES copying django/contrib/auth/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nn/LC_MESSAGES copying django/contrib/auth/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nn/LC_MESSAGES copying django/contrib/auth/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/os/LC_MESSAGES copying django/contrib/auth/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/os/LC_MESSAGES copying django/contrib/auth/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pa/LC_MESSAGES copying django/contrib/auth/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pa/LC_MESSAGES copying django/contrib/auth/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pl/LC_MESSAGES copying django/contrib/auth/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pl/LC_MESSAGES copying django/contrib/auth/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pt/LC_MESSAGES copying django/contrib/auth/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pt/LC_MESSAGES copying django/contrib/auth/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pt_BR/LC_MESSAGES copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pt_BR/LC_MESSAGES copying django/contrib/auth/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ro/LC_MESSAGES copying django/contrib/auth/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ro/LC_MESSAGES copying django/contrib/auth/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ru/LC_MESSAGES copying django/contrib/auth/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ru/LC_MESSAGES copying django/contrib/auth/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sk/LC_MESSAGES copying django/contrib/auth/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sk/LC_MESSAGES copying django/contrib/auth/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sl/LC_MESSAGES copying django/contrib/auth/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sl/LC_MESSAGES copying django/contrib/auth/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sq/LC_MESSAGES copying django/contrib/auth/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sq/LC_MESSAGES copying django/contrib/auth/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sr/LC_MESSAGES copying django/contrib/auth/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sr/LC_MESSAGES copying django/contrib/auth/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sr_Latn/LC_MESSAGES copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sr_Latn/LC_MESSAGES copying django/contrib/auth/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sv/LC_MESSAGES copying django/contrib/auth/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sv/LC_MESSAGES copying django/contrib/auth/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sw/LC_MESSAGES copying django/contrib/auth/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sw/LC_MESSAGES copying django/contrib/auth/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ta/LC_MESSAGES copying django/contrib/auth/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ta/LC_MESSAGES copying django/contrib/auth/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/te/LC_MESSAGES copying django/contrib/auth/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/te/LC_MESSAGES copying django/contrib/auth/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tg/LC_MESSAGES copying django/contrib/auth/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tg/LC_MESSAGES copying django/contrib/auth/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/th/LC_MESSAGES copying django/contrib/auth/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/th/LC_MESSAGES copying django/contrib/auth/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tk/LC_MESSAGES copying django/contrib/auth/locale/tk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tk/LC_MESSAGES copying django/contrib/auth/locale/tk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tr/LC_MESSAGES copying django/contrib/auth/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tr/LC_MESSAGES copying django/contrib/auth/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tt/LC_MESSAGES copying django/contrib/auth/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tt/LC_MESSAGES copying django/contrib/auth/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/udm/LC_MESSAGES copying django/contrib/auth/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/udm/LC_MESSAGES copying django/contrib/auth/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/uk/LC_MESSAGES copying django/contrib/auth/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/uk/LC_MESSAGES copying django/contrib/auth/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ur/LC_MESSAGES copying django/contrib/auth/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ur/LC_MESSAGES copying django/contrib/auth/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/uz creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/uz/LC_MESSAGES copying django/contrib/auth/locale/uz/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/uz/LC_MESSAGES copying django/contrib/auth/locale/uz/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/uz/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/vi/LC_MESSAGES copying django/contrib/auth/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/vi/LC_MESSAGES copying django/contrib/auth/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/zh_Hans/LC_MESSAGES copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/zh_Hans/LC_MESSAGES copying django/contrib/auth/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/zh_Hant/LC_MESSAGES copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/zh_Hant/LC_MESSAGES copying django/contrib/auth/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/templates creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/templates/auth creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/templates/auth/widgets copying django/contrib/auth/templates/auth/widgets/read_only_password_hash.html -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/templates/auth/widgets creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/templates/registration copying django/contrib/auth/templates/registration/password_reset_subject.txt -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/auth/templates/registration creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/af/LC_MESSAGES copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/af/LC_MESSAGES copying django/contrib/contenttypes/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ar/LC_MESSAGES copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ar/LC_MESSAGES copying django/contrib/contenttypes/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES copying django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ast/LC_MESSAGES copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ast/LC_MESSAGES copying django/contrib/contenttypes/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/az/LC_MESSAGES copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/az/LC_MESSAGES copying django/contrib/contenttypes/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/be/LC_MESSAGES copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/be/LC_MESSAGES copying django/contrib/contenttypes/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bg/LC_MESSAGES copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bg/LC_MESSAGES copying django/contrib/contenttypes/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bn/LC_MESSAGES copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bn/LC_MESSAGES copying django/contrib/contenttypes/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/br/LC_MESSAGES copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/br/LC_MESSAGES copying django/contrib/contenttypes/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bs/LC_MESSAGES copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bs/LC_MESSAGES copying django/contrib/contenttypes/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ca/LC_MESSAGES copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ca/LC_MESSAGES copying django/contrib/contenttypes/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/cs/LC_MESSAGES copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/cs/LC_MESSAGES copying django/contrib/contenttypes/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/cy/LC_MESSAGES copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/cy/LC_MESSAGES copying django/contrib/contenttypes/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/da/LC_MESSAGES copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/da/LC_MESSAGES copying django/contrib/contenttypes/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/de/LC_MESSAGES copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/de/LC_MESSAGES copying django/contrib/contenttypes/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/dsb/LC_MESSAGES copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/dsb/LC_MESSAGES copying django/contrib/contenttypes/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/el/LC_MESSAGES copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/el/LC_MESSAGES copying django/contrib/contenttypes/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en/LC_MESSAGES copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en/LC_MESSAGES copying django/contrib/contenttypes/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES copying django/contrib/contenttypes/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES copying django/contrib/contenttypes/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/eo/LC_MESSAGES copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/eo/LC_MESSAGES copying django/contrib/contenttypes/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es/LC_MESSAGES copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es/LC_MESSAGES copying django/contrib/contenttypes/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES copying django/contrib/contenttypes/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES copying django/contrib/contenttypes/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES copying django/contrib/contenttypes/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES copying django/contrib/contenttypes/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/et/LC_MESSAGES copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/et/LC_MESSAGES copying django/contrib/contenttypes/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/eu/LC_MESSAGES copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/eu/LC_MESSAGES copying django/contrib/contenttypes/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fa/LC_MESSAGES copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fa/LC_MESSAGES copying django/contrib/contenttypes/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fi/LC_MESSAGES copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fi/LC_MESSAGES copying django/contrib/contenttypes/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fr/LC_MESSAGES copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fr/LC_MESSAGES copying django/contrib/contenttypes/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fy/LC_MESSAGES copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fy/LC_MESSAGES copying django/contrib/contenttypes/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ga/LC_MESSAGES copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ga/LC_MESSAGES copying django/contrib/contenttypes/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/gd/LC_MESSAGES copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/gd/LC_MESSAGES copying django/contrib/contenttypes/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/gl/LC_MESSAGES copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/gl/LC_MESSAGES copying django/contrib/contenttypes/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/he/LC_MESSAGES copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/he/LC_MESSAGES copying django/contrib/contenttypes/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hi/LC_MESSAGES copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hi/LC_MESSAGES copying django/contrib/contenttypes/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hr/LC_MESSAGES copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hr/LC_MESSAGES copying django/contrib/contenttypes/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hsb/LC_MESSAGES copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hsb/LC_MESSAGES copying django/contrib/contenttypes/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hu/LC_MESSAGES copying django/contrib/contenttypes/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hy/LC_MESSAGES copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hy/LC_MESSAGES copying django/contrib/contenttypes/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ia/LC_MESSAGES copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ia/LC_MESSAGES copying django/contrib/contenttypes/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/id/LC_MESSAGES copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/id/LC_MESSAGES copying django/contrib/contenttypes/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/io/LC_MESSAGES copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/io/LC_MESSAGES copying django/contrib/contenttypes/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/is/LC_MESSAGES copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/is/LC_MESSAGES copying django/contrib/contenttypes/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/it/LC_MESSAGES copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/it/LC_MESSAGES copying django/contrib/contenttypes/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ja/LC_MESSAGES copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ja/LC_MESSAGES copying django/contrib/contenttypes/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ka/LC_MESSAGES copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ka/LC_MESSAGES copying django/contrib/contenttypes/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/kk/LC_MESSAGES copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/kk/LC_MESSAGES copying django/contrib/contenttypes/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/km/LC_MESSAGES copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/km/LC_MESSAGES copying django/contrib/contenttypes/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/kn/LC_MESSAGES copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/kn/LC_MESSAGES copying django/contrib/contenttypes/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ko/LC_MESSAGES copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ko/LC_MESSAGES copying django/contrib/contenttypes/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ky/LC_MESSAGES copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ky/LC_MESSAGES copying django/contrib/contenttypes/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lb/LC_MESSAGES copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lb/LC_MESSAGES copying django/contrib/contenttypes/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lt/LC_MESSAGES copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lt/LC_MESSAGES copying django/contrib/contenttypes/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lv/LC_MESSAGES copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lv/LC_MESSAGES copying django/contrib/contenttypes/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mk/LC_MESSAGES copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mk/LC_MESSAGES copying django/contrib/contenttypes/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ml/LC_MESSAGES copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ml/LC_MESSAGES copying django/contrib/contenttypes/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mn/LC_MESSAGES copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mn/LC_MESSAGES copying django/contrib/contenttypes/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mr/LC_MESSAGES copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mr/LC_MESSAGES copying django/contrib/contenttypes/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/my/LC_MESSAGES copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/my/LC_MESSAGES copying django/contrib/contenttypes/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nb/LC_MESSAGES copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nb/LC_MESSAGES copying django/contrib/contenttypes/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ne/LC_MESSAGES copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ne/LC_MESSAGES copying django/contrib/contenttypes/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nl/LC_MESSAGES copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nl/LC_MESSAGES copying django/contrib/contenttypes/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nn/LC_MESSAGES copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nn/LC_MESSAGES copying django/contrib/contenttypes/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/os/LC_MESSAGES copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/os/LC_MESSAGES copying django/contrib/contenttypes/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pa/LC_MESSAGES copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pa/LC_MESSAGES copying django/contrib/contenttypes/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pl/LC_MESSAGES copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pl/LC_MESSAGES copying django/contrib/contenttypes/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pt/LC_MESSAGES copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pt/LC_MESSAGES copying django/contrib/contenttypes/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES copying django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ro/LC_MESSAGES copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ro/LC_MESSAGES copying django/contrib/contenttypes/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ru/LC_MESSAGES copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ru/LC_MESSAGES copying django/contrib/contenttypes/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sk/LC_MESSAGES copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sk/LC_MESSAGES copying django/contrib/contenttypes/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sl/LC_MESSAGES copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sl/LC_MESSAGES copying django/contrib/contenttypes/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sq/LC_MESSAGES copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sq/LC_MESSAGES copying django/contrib/contenttypes/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sr/LC_MESSAGES copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sr/LC_MESSAGES copying django/contrib/contenttypes/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES copying django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sv/LC_MESSAGES copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sv/LC_MESSAGES copying django/contrib/contenttypes/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sw/LC_MESSAGES copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sw/LC_MESSAGES copying django/contrib/contenttypes/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ta/LC_MESSAGES copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ta/LC_MESSAGES copying django/contrib/contenttypes/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/te/LC_MESSAGES copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/te/LC_MESSAGES copying django/contrib/contenttypes/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tg/LC_MESSAGES copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tg/LC_MESSAGES copying django/contrib/contenttypes/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/th/LC_MESSAGES copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/th/LC_MESSAGES copying django/contrib/contenttypes/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tk/LC_MESSAGES copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tk/LC_MESSAGES copying django/contrib/contenttypes/locale/tk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tr/LC_MESSAGES copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tr/LC_MESSAGES copying django/contrib/contenttypes/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tt/LC_MESSAGES copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tt/LC_MESSAGES copying django/contrib/contenttypes/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/udm/LC_MESSAGES copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/udm/LC_MESSAGES copying django/contrib/contenttypes/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/uk/LC_MESSAGES copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/uk/LC_MESSAGES copying django/contrib/contenttypes/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ur/LC_MESSAGES copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ur/LC_MESSAGES copying django/contrib/contenttypes/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/vi/LC_MESSAGES copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/vi/LC_MESSAGES copying django/contrib/contenttypes/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES copying django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES copying django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/contenttypes/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/af/LC_MESSAGES copying django/contrib/humanize/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/af/LC_MESSAGES copying django/contrib/humanize/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ar/LC_MESSAGES copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ar/LC_MESSAGES copying django/contrib/humanize/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES copying django/contrib/humanize/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ast/LC_MESSAGES copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ast/LC_MESSAGES copying django/contrib/humanize/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/az/LC_MESSAGES copying django/contrib/humanize/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/az/LC_MESSAGES copying django/contrib/humanize/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/be/LC_MESSAGES copying django/contrib/humanize/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/be/LC_MESSAGES copying django/contrib/humanize/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bg/LC_MESSAGES copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bg/LC_MESSAGES copying django/contrib/humanize/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bn/LC_MESSAGES copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bn/LC_MESSAGES copying django/contrib/humanize/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/br/LC_MESSAGES copying django/contrib/humanize/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/br/LC_MESSAGES copying django/contrib/humanize/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bs/LC_MESSAGES copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bs/LC_MESSAGES copying django/contrib/humanize/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ca/LC_MESSAGES copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ca/LC_MESSAGES copying django/contrib/humanize/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/cs/LC_MESSAGES copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/cs/LC_MESSAGES copying django/contrib/humanize/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/cy/LC_MESSAGES copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/cy/LC_MESSAGES copying django/contrib/humanize/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/da/LC_MESSAGES copying django/contrib/humanize/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/da/LC_MESSAGES copying django/contrib/humanize/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/de/LC_MESSAGES copying django/contrib/humanize/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/de/LC_MESSAGES copying django/contrib/humanize/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/dsb/LC_MESSAGES copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/dsb/LC_MESSAGES copying django/contrib/humanize/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/el/LC_MESSAGES copying django/contrib/humanize/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/el/LC_MESSAGES copying django/contrib/humanize/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en/LC_MESSAGES copying django/contrib/humanize/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en/LC_MESSAGES copying django/contrib/humanize/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en_AU/LC_MESSAGES copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en_AU/LC_MESSAGES copying django/contrib/humanize/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en_GB/LC_MESSAGES copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en_GB/LC_MESSAGES copying django/contrib/humanize/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/eo/LC_MESSAGES copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/eo/LC_MESSAGES copying django/contrib/humanize/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es/LC_MESSAGES copying django/contrib/humanize/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es/LC_MESSAGES copying django/contrib/humanize/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_AR/LC_MESSAGES copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_AR/LC_MESSAGES copying django/contrib/humanize/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_CO/LC_MESSAGES copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_CO/LC_MESSAGES copying django/contrib/humanize/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_MX/LC_MESSAGES copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_MX/LC_MESSAGES copying django/contrib/humanize/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_VE/LC_MESSAGES copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_VE/LC_MESSAGES copying django/contrib/humanize/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/et/LC_MESSAGES copying django/contrib/humanize/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/et/LC_MESSAGES copying django/contrib/humanize/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/eu/LC_MESSAGES copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/eu/LC_MESSAGES copying django/contrib/humanize/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fa/LC_MESSAGES copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fa/LC_MESSAGES copying django/contrib/humanize/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fi/LC_MESSAGES copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fi/LC_MESSAGES copying django/contrib/humanize/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fr/LC_MESSAGES copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fr/LC_MESSAGES copying django/contrib/humanize/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fy/LC_MESSAGES copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fy/LC_MESSAGES copying django/contrib/humanize/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ga/LC_MESSAGES copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ga/LC_MESSAGES copying django/contrib/humanize/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/gd/LC_MESSAGES copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/gd/LC_MESSAGES copying django/contrib/humanize/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/gl/LC_MESSAGES copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/gl/LC_MESSAGES copying django/contrib/humanize/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/he/LC_MESSAGES copying django/contrib/humanize/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/he/LC_MESSAGES copying django/contrib/humanize/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hi/LC_MESSAGES copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hi/LC_MESSAGES copying django/contrib/humanize/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hr/LC_MESSAGES copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hr/LC_MESSAGES copying django/contrib/humanize/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hsb/LC_MESSAGES copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hsb/LC_MESSAGES copying django/contrib/humanize/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hu/LC_MESSAGES copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hu/LC_MESSAGES copying django/contrib/humanize/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hy/LC_MESSAGES copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hy/LC_MESSAGES copying django/contrib/humanize/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ia/LC_MESSAGES copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ia/LC_MESSAGES copying django/contrib/humanize/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/id/LC_MESSAGES copying django/contrib/humanize/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/id/LC_MESSAGES copying django/contrib/humanize/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/io/LC_MESSAGES copying django/contrib/humanize/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/io/LC_MESSAGES copying django/contrib/humanize/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/is/LC_MESSAGES copying django/contrib/humanize/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/is/LC_MESSAGES copying django/contrib/humanize/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/it/LC_MESSAGES copying django/contrib/humanize/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/it/LC_MESSAGES copying django/contrib/humanize/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ja/LC_MESSAGES copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ja/LC_MESSAGES copying django/contrib/humanize/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ka/LC_MESSAGES copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ka/LC_MESSAGES copying django/contrib/humanize/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/kk/LC_MESSAGES copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/kk/LC_MESSAGES copying django/contrib/humanize/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/km/LC_MESSAGES copying django/contrib/humanize/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/km/LC_MESSAGES copying django/contrib/humanize/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/kn/LC_MESSAGES copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/kn/LC_MESSAGES copying django/contrib/humanize/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ko/LC_MESSAGES copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ko/LC_MESSAGES copying django/contrib/humanize/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ky/LC_MESSAGES copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ky/LC_MESSAGES copying django/contrib/humanize/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lb/LC_MESSAGES copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lb/LC_MESSAGES copying django/contrib/humanize/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lt/LC_MESSAGES copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lt/LC_MESSAGES copying django/contrib/humanize/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lv/LC_MESSAGES copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lv/LC_MESSAGES copying django/contrib/humanize/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mk/LC_MESSAGES copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mk/LC_MESSAGES copying django/contrib/humanize/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ml/LC_MESSAGES copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ml/LC_MESSAGES copying django/contrib/humanize/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mn/LC_MESSAGES copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mn/LC_MESSAGES copying django/contrib/humanize/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mr/LC_MESSAGES copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mr/LC_MESSAGES copying django/contrib/humanize/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ms creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ms/LC_MESSAGES copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ms/LC_MESSAGES copying django/contrib/humanize/locale/ms/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ms/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/my/LC_MESSAGES copying django/contrib/humanize/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/my/LC_MESSAGES copying django/contrib/humanize/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nb/LC_MESSAGES copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nb/LC_MESSAGES copying django/contrib/humanize/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ne/LC_MESSAGES copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ne/LC_MESSAGES copying django/contrib/humanize/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nl/LC_MESSAGES copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nl/LC_MESSAGES copying django/contrib/humanize/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nn/LC_MESSAGES copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nn/LC_MESSAGES copying django/contrib/humanize/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/os/LC_MESSAGES copying django/contrib/humanize/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/os/LC_MESSAGES copying django/contrib/humanize/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pa/LC_MESSAGES copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pa/LC_MESSAGES copying django/contrib/humanize/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pl/LC_MESSAGES copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pl/LC_MESSAGES copying django/contrib/humanize/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pt/LC_MESSAGES copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pt/LC_MESSAGES copying django/contrib/humanize/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pt_BR/LC_MESSAGES copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pt_BR/LC_MESSAGES copying django/contrib/humanize/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ro/LC_MESSAGES copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ro/LC_MESSAGES copying django/contrib/humanize/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ru/LC_MESSAGES copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ru/LC_MESSAGES copying django/contrib/humanize/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sk/LC_MESSAGES copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sk/LC_MESSAGES copying django/contrib/humanize/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sl/LC_MESSAGES copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sl/LC_MESSAGES copying django/contrib/humanize/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sq/LC_MESSAGES copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sq/LC_MESSAGES copying django/contrib/humanize/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sr/LC_MESSAGES copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sr/LC_MESSAGES copying django/contrib/humanize/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES copying django/contrib/humanize/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sv/LC_MESSAGES copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sv/LC_MESSAGES copying django/contrib/humanize/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sw/LC_MESSAGES copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sw/LC_MESSAGES copying django/contrib/humanize/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ta/LC_MESSAGES copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ta/LC_MESSAGES copying django/contrib/humanize/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/te/LC_MESSAGES copying django/contrib/humanize/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/te/LC_MESSAGES copying django/contrib/humanize/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tg/LC_MESSAGES copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tg/LC_MESSAGES copying django/contrib/humanize/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/th/LC_MESSAGES copying django/contrib/humanize/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/th/LC_MESSAGES copying django/contrib/humanize/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tr/LC_MESSAGES copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tr/LC_MESSAGES copying django/contrib/humanize/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tt/LC_MESSAGES copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tt/LC_MESSAGES copying django/contrib/humanize/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/udm/LC_MESSAGES copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/udm/LC_MESSAGES copying django/contrib/humanize/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/uk/LC_MESSAGES copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/uk/LC_MESSAGES copying django/contrib/humanize/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ur/LC_MESSAGES copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ur/LC_MESSAGES copying django/contrib/humanize/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/uz creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/uz/LC_MESSAGES copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/uz/LC_MESSAGES copying django/contrib/humanize/locale/uz/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/uz/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/vi/LC_MESSAGES copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/vi/LC_MESSAGES copying django/contrib/humanize/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES copying django/contrib/humanize/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES copying django/contrib/humanize/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/humanize/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/af/LC_MESSAGES copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/af/LC_MESSAGES copying django/contrib/flatpages/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ar/LC_MESSAGES copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ar/LC_MESSAGES copying django/contrib/flatpages/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES copying django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ast/LC_MESSAGES copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ast/LC_MESSAGES copying django/contrib/flatpages/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/az/LC_MESSAGES copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/az/LC_MESSAGES copying django/contrib/flatpages/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/be/LC_MESSAGES copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/be/LC_MESSAGES copying django/contrib/flatpages/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bg/LC_MESSAGES copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bg/LC_MESSAGES copying django/contrib/flatpages/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bn/LC_MESSAGES copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bn/LC_MESSAGES copying django/contrib/flatpages/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/br/LC_MESSAGES copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/br/LC_MESSAGES copying django/contrib/flatpages/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bs/LC_MESSAGES copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bs/LC_MESSAGES copying django/contrib/flatpages/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ca/LC_MESSAGES copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ca/LC_MESSAGES copying django/contrib/flatpages/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/cs/LC_MESSAGES copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/cs/LC_MESSAGES copying django/contrib/flatpages/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/cy/LC_MESSAGES copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/cy/LC_MESSAGES copying django/contrib/flatpages/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/da/LC_MESSAGES copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/da/LC_MESSAGES copying django/contrib/flatpages/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/de/LC_MESSAGES copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/de/LC_MESSAGES copying django/contrib/flatpages/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/dsb/LC_MESSAGES copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/dsb/LC_MESSAGES copying django/contrib/flatpages/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/el/LC_MESSAGES copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/el/LC_MESSAGES copying django/contrib/flatpages/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en/LC_MESSAGES copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en/LC_MESSAGES copying django/contrib/flatpages/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en_AU/LC_MESSAGES copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en_AU/LC_MESSAGES copying django/contrib/flatpages/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en_GB/LC_MESSAGES copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en_GB/LC_MESSAGES copying django/contrib/flatpages/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/eo/LC_MESSAGES copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/eo/LC_MESSAGES copying django/contrib/flatpages/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es/LC_MESSAGES copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es/LC_MESSAGES copying django/contrib/flatpages/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_AR/LC_MESSAGES copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_AR/LC_MESSAGES copying django/contrib/flatpages/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_CO/LC_MESSAGES copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_CO/LC_MESSAGES copying django/contrib/flatpages/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_MX/LC_MESSAGES copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_MX/LC_MESSAGES copying django/contrib/flatpages/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_VE/LC_MESSAGES copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_VE/LC_MESSAGES copying django/contrib/flatpages/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/et/LC_MESSAGES copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/et/LC_MESSAGES copying django/contrib/flatpages/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/eu/LC_MESSAGES copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/eu/LC_MESSAGES copying django/contrib/flatpages/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fa/LC_MESSAGES copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fa/LC_MESSAGES copying django/contrib/flatpages/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fi/LC_MESSAGES copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fi/LC_MESSAGES copying django/contrib/flatpages/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fr/LC_MESSAGES copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fr/LC_MESSAGES copying django/contrib/flatpages/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fy/LC_MESSAGES copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fy/LC_MESSAGES copying django/contrib/flatpages/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ga/LC_MESSAGES copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ga/LC_MESSAGES copying django/contrib/flatpages/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/gd/LC_MESSAGES copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/gd/LC_MESSAGES copying django/contrib/flatpages/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/gl/LC_MESSAGES copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/gl/LC_MESSAGES copying django/contrib/flatpages/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/he/LC_MESSAGES copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/he/LC_MESSAGES copying django/contrib/flatpages/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hi/LC_MESSAGES copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hi/LC_MESSAGES copying django/contrib/flatpages/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hr/LC_MESSAGES copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hr/LC_MESSAGES copying django/contrib/flatpages/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hsb/LC_MESSAGES copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hsb/LC_MESSAGES copying django/contrib/flatpages/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hu/LC_MESSAGES copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hu/LC_MESSAGES copying django/contrib/flatpages/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hy/LC_MESSAGES copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hy/LC_MESSAGES copying django/contrib/flatpages/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ia/LC_MESSAGES copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ia/LC_MESSAGES copying django/contrib/flatpages/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/id/LC_MESSAGES copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/id/LC_MESSAGES copying django/contrib/flatpages/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/io/LC_MESSAGES copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/io/LC_MESSAGES copying django/contrib/flatpages/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/is/LC_MESSAGES copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/is/LC_MESSAGES copying django/contrib/flatpages/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/it/LC_MESSAGES copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/it/LC_MESSAGES copying django/contrib/flatpages/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ja/LC_MESSAGES copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ja/LC_MESSAGES copying django/contrib/flatpages/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ka/LC_MESSAGES copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ka/LC_MESSAGES copying django/contrib/flatpages/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/kk/LC_MESSAGES copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/kk/LC_MESSAGES copying django/contrib/flatpages/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/km/LC_MESSAGES copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/km/LC_MESSAGES copying django/contrib/flatpages/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/kn/LC_MESSAGES copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/kn/LC_MESSAGES copying django/contrib/flatpages/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ko/LC_MESSAGES copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ko/LC_MESSAGES copying django/contrib/flatpages/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ky/LC_MESSAGES copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ky/LC_MESSAGES copying django/contrib/flatpages/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lb/LC_MESSAGES copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lb/LC_MESSAGES copying django/contrib/flatpages/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lt/LC_MESSAGES copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lt/LC_MESSAGES copying django/contrib/flatpages/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lv/LC_MESSAGES copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lv/LC_MESSAGES copying django/contrib/flatpages/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mk/LC_MESSAGES copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mk/LC_MESSAGES copying django/contrib/flatpages/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ml/LC_MESSAGES copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ml/LC_MESSAGES copying django/contrib/flatpages/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mn/LC_MESSAGES copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mn/LC_MESSAGES copying django/contrib/flatpages/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mr/LC_MESSAGES copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mr/LC_MESSAGES copying django/contrib/flatpages/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/my/LC_MESSAGES copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/my/LC_MESSAGES copying django/contrib/flatpages/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nb/LC_MESSAGES copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nb/LC_MESSAGES copying django/contrib/flatpages/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ne/LC_MESSAGES copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ne/LC_MESSAGES copying django/contrib/flatpages/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nl/LC_MESSAGES copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nl/LC_MESSAGES copying django/contrib/flatpages/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nn/LC_MESSAGES copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nn/LC_MESSAGES copying django/contrib/flatpages/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/os/LC_MESSAGES copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/os/LC_MESSAGES copying django/contrib/flatpages/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pa/LC_MESSAGES copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pa/LC_MESSAGES copying django/contrib/flatpages/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pl/LC_MESSAGES copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pl/LC_MESSAGES copying django/contrib/flatpages/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pt/LC_MESSAGES copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pt/LC_MESSAGES copying django/contrib/flatpages/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES copying django/contrib/flatpages/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ro/LC_MESSAGES copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ro/LC_MESSAGES copying django/contrib/flatpages/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ru/LC_MESSAGES copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ru/LC_MESSAGES copying django/contrib/flatpages/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sk/LC_MESSAGES copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sk/LC_MESSAGES copying django/contrib/flatpages/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sl/LC_MESSAGES copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sl/LC_MESSAGES copying django/contrib/flatpages/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sq/LC_MESSAGES copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sq/LC_MESSAGES copying django/contrib/flatpages/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sr/LC_MESSAGES copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sr/LC_MESSAGES copying django/contrib/flatpages/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES copying django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sv/LC_MESSAGES copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sv/LC_MESSAGES copying django/contrib/flatpages/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sw/LC_MESSAGES copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sw/LC_MESSAGES copying django/contrib/flatpages/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ta/LC_MESSAGES copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ta/LC_MESSAGES copying django/contrib/flatpages/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/te/LC_MESSAGES copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/te/LC_MESSAGES copying django/contrib/flatpages/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tg/LC_MESSAGES copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tg/LC_MESSAGES copying django/contrib/flatpages/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/th/LC_MESSAGES copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/th/LC_MESSAGES copying django/contrib/flatpages/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tk/LC_MESSAGES copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tk/LC_MESSAGES copying django/contrib/flatpages/locale/tk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tr/LC_MESSAGES copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tr/LC_MESSAGES copying django/contrib/flatpages/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tt/LC_MESSAGES copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tt/LC_MESSAGES copying django/contrib/flatpages/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/udm/LC_MESSAGES copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/udm/LC_MESSAGES copying django/contrib/flatpages/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/uk/LC_MESSAGES copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/uk/LC_MESSAGES copying django/contrib/flatpages/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ur/LC_MESSAGES copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ur/LC_MESSAGES copying django/contrib/flatpages/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/vi/LC_MESSAGES copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/vi/LC_MESSAGES copying django/contrib/flatpages/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES copying django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES copying django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/flatpages/locale/zh_Hant/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/af creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/af/LC_MESSAGES copying django/contrib/redirects/locale/af/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/af/LC_MESSAGES copying django/contrib/redirects/locale/af/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/af/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ar creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ar/LC_MESSAGES copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ar/LC_MESSAGES copying django/contrib/redirects/locale/ar/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ar/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ar_DZ creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES copying django/contrib/redirects/locale/ar_DZ/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ar_DZ/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ast creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ast/LC_MESSAGES copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ast/LC_MESSAGES copying django/contrib/redirects/locale/ast/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ast/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/az creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/az/LC_MESSAGES copying django/contrib/redirects/locale/az/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/az/LC_MESSAGES copying django/contrib/redirects/locale/az/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/az/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/be creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/be/LC_MESSAGES copying django/contrib/redirects/locale/be/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/be/LC_MESSAGES copying django/contrib/redirects/locale/be/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/be/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bg/LC_MESSAGES copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bg/LC_MESSAGES copying django/contrib/redirects/locale/bg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bn/LC_MESSAGES copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bn/LC_MESSAGES copying django/contrib/redirects/locale/bn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/br creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/br/LC_MESSAGES copying django/contrib/redirects/locale/br/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/br/LC_MESSAGES copying django/contrib/redirects/locale/br/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/br/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bs/LC_MESSAGES copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bs/LC_MESSAGES copying django/contrib/redirects/locale/bs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/bs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ca creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ca/LC_MESSAGES copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ca/LC_MESSAGES copying django/contrib/redirects/locale/ca/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ca/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/cs creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/cs/LC_MESSAGES copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/cs/LC_MESSAGES copying django/contrib/redirects/locale/cs/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/cs/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/cy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/cy/LC_MESSAGES copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/cy/LC_MESSAGES copying django/contrib/redirects/locale/cy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/cy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/da creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/da/LC_MESSAGES copying django/contrib/redirects/locale/da/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/da/LC_MESSAGES copying django/contrib/redirects/locale/da/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/da/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/de creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/de/LC_MESSAGES copying django/contrib/redirects/locale/de/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/de/LC_MESSAGES copying django/contrib/redirects/locale/de/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/de/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/dsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/dsb/LC_MESSAGES copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/dsb/LC_MESSAGES copying django/contrib/redirects/locale/dsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/dsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/el creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/el/LC_MESSAGES copying django/contrib/redirects/locale/el/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/el/LC_MESSAGES copying django/contrib/redirects/locale/el/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/el/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en/LC_MESSAGES copying django/contrib/redirects/locale/en/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en/LC_MESSAGES copying django/contrib/redirects/locale/en/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en_AU creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en_AU/LC_MESSAGES copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en_AU/LC_MESSAGES copying django/contrib/redirects/locale/en_AU/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en_AU/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en_GB creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en_GB/LC_MESSAGES copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en_GB/LC_MESSAGES copying django/contrib/redirects/locale/en_GB/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/en_GB/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/eo creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/eo/LC_MESSAGES copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/eo/LC_MESSAGES copying django/contrib/redirects/locale/eo/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/eo/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es/LC_MESSAGES copying django/contrib/redirects/locale/es/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es/LC_MESSAGES copying django/contrib/redirects/locale/es/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_AR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_AR/LC_MESSAGES copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_AR/LC_MESSAGES copying django/contrib/redirects/locale/es_AR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_AR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_CO creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_CO/LC_MESSAGES copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_CO/LC_MESSAGES copying django/contrib/redirects/locale/es_CO/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_CO/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_MX creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_MX/LC_MESSAGES copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_MX/LC_MESSAGES copying django/contrib/redirects/locale/es_MX/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_MX/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_VE creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_VE/LC_MESSAGES copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_VE/LC_MESSAGES copying django/contrib/redirects/locale/es_VE/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/es_VE/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/et creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/et/LC_MESSAGES copying django/contrib/redirects/locale/et/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/et/LC_MESSAGES copying django/contrib/redirects/locale/et/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/et/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/eu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/eu/LC_MESSAGES copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/eu/LC_MESSAGES copying django/contrib/redirects/locale/eu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/eu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fa/LC_MESSAGES copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fa/LC_MESSAGES copying django/contrib/redirects/locale/fa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fi/LC_MESSAGES copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fi/LC_MESSAGES copying django/contrib/redirects/locale/fi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fr/LC_MESSAGES copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fr/LC_MESSAGES copying django/contrib/redirects/locale/fr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fy/LC_MESSAGES copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fy/LC_MESSAGES copying django/contrib/redirects/locale/fy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/fy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ga creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ga/LC_MESSAGES copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ga/LC_MESSAGES copying django/contrib/redirects/locale/ga/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ga/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/gd creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/gd/LC_MESSAGES copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/gd/LC_MESSAGES copying django/contrib/redirects/locale/gd/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/gd/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/gl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/gl/LC_MESSAGES copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/gl/LC_MESSAGES copying django/contrib/redirects/locale/gl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/gl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/he creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/he/LC_MESSAGES copying django/contrib/redirects/locale/he/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/he/LC_MESSAGES copying django/contrib/redirects/locale/he/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/he/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hi/LC_MESSAGES copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hi/LC_MESSAGES copying django/contrib/redirects/locale/hi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hr/LC_MESSAGES copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hr/LC_MESSAGES copying django/contrib/redirects/locale/hr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hsb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hsb/LC_MESSAGES copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hsb/LC_MESSAGES copying django/contrib/redirects/locale/hsb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hsb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hu creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hu/LC_MESSAGES copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hu/LC_MESSAGES copying django/contrib/redirects/locale/hu/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hu/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hy creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hy/LC_MESSAGES copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hy/LC_MESSAGES copying django/contrib/redirects/locale/hy/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/hy/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ia creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ia/LC_MESSAGES copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ia/LC_MESSAGES copying django/contrib/redirects/locale/ia/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ia/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/id creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/id/LC_MESSAGES copying django/contrib/redirects/locale/id/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/id/LC_MESSAGES copying django/contrib/redirects/locale/id/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/id/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/io creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/io/LC_MESSAGES copying django/contrib/redirects/locale/io/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/io/LC_MESSAGES copying django/contrib/redirects/locale/io/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/io/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/is creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/is/LC_MESSAGES copying django/contrib/redirects/locale/is/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/is/LC_MESSAGES copying django/contrib/redirects/locale/is/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/is/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/it creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/it/LC_MESSAGES copying django/contrib/redirects/locale/it/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/it/LC_MESSAGES copying django/contrib/redirects/locale/it/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/it/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ja creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ja/LC_MESSAGES copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ja/LC_MESSAGES copying django/contrib/redirects/locale/ja/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ja/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ka creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ka/LC_MESSAGES copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ka/LC_MESSAGES copying django/contrib/redirects/locale/ka/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ka/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kab creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kab/LC_MESSAGES copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kab/LC_MESSAGES copying django/contrib/redirects/locale/kab/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kab/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kk/LC_MESSAGES copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kk/LC_MESSAGES copying django/contrib/redirects/locale/kk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/km creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/km/LC_MESSAGES copying django/contrib/redirects/locale/km/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/km/LC_MESSAGES copying django/contrib/redirects/locale/km/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/km/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kn/LC_MESSAGES copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kn/LC_MESSAGES copying django/contrib/redirects/locale/kn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/kn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ko creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ko/LC_MESSAGES copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ko/LC_MESSAGES copying django/contrib/redirects/locale/ko/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ko/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ky creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ky/LC_MESSAGES copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ky/LC_MESSAGES copying django/contrib/redirects/locale/ky/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ky/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lb/LC_MESSAGES copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lb/LC_MESSAGES copying django/contrib/redirects/locale/lb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lt/LC_MESSAGES copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lt/LC_MESSAGES copying django/contrib/redirects/locale/lt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lv/LC_MESSAGES copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lv/LC_MESSAGES copying django/contrib/redirects/locale/lv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/lv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mk/LC_MESSAGES copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mk/LC_MESSAGES copying django/contrib/redirects/locale/mk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ml creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ml/LC_MESSAGES copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ml/LC_MESSAGES copying django/contrib/redirects/locale/ml/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ml/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mn/LC_MESSAGES copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mn/LC_MESSAGES copying django/contrib/redirects/locale/mn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mr/LC_MESSAGES copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mr/LC_MESSAGES copying django/contrib/redirects/locale/mr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/mr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/my creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/my/LC_MESSAGES copying django/contrib/redirects/locale/my/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/my/LC_MESSAGES copying django/contrib/redirects/locale/my/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/my/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nb creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nb/LC_MESSAGES copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nb/LC_MESSAGES copying django/contrib/redirects/locale/nb/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nb/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ne creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ne/LC_MESSAGES copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ne/LC_MESSAGES copying django/contrib/redirects/locale/ne/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ne/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nl/LC_MESSAGES copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nl/LC_MESSAGES copying django/contrib/redirects/locale/nl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nn/LC_MESSAGES copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nn/LC_MESSAGES copying django/contrib/redirects/locale/nn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/nn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/os creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/os/LC_MESSAGES copying django/contrib/redirects/locale/os/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/os/LC_MESSAGES copying django/contrib/redirects/locale/os/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/os/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pa creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pa/LC_MESSAGES copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pa/LC_MESSAGES copying django/contrib/redirects/locale/pa/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pa/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pl/LC_MESSAGES copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pl/LC_MESSAGES copying django/contrib/redirects/locale/pl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pt/LC_MESSAGES copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pt/LC_MESSAGES copying django/contrib/redirects/locale/pt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pt_BR creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pt_BR/LC_MESSAGES copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pt_BR/LC_MESSAGES copying django/contrib/redirects/locale/pt_BR/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/pt_BR/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ro creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ro/LC_MESSAGES copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ro/LC_MESSAGES copying django/contrib/redirects/locale/ro/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ro/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ru creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ru/LC_MESSAGES copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ru/LC_MESSAGES copying django/contrib/redirects/locale/ru/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ru/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sk/LC_MESSAGES copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sk/LC_MESSAGES copying django/contrib/redirects/locale/sk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sl creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sl/LC_MESSAGES copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sl/LC_MESSAGES copying django/contrib/redirects/locale/sl/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sl/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sq creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sq/LC_MESSAGES copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sq/LC_MESSAGES copying django/contrib/redirects/locale/sq/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sq/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sr/LC_MESSAGES copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sr/LC_MESSAGES copying django/contrib/redirects/locale/sr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sr_Latn creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES copying django/contrib/redirects/locale/sr_Latn/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sr_Latn/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sv creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sv/LC_MESSAGES copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sv/LC_MESSAGES copying django/contrib/redirects/locale/sv/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sv/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sw creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sw/LC_MESSAGES copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sw/LC_MESSAGES copying django/contrib/redirects/locale/sw/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/sw/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ta creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ta/LC_MESSAGES copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ta/LC_MESSAGES copying django/contrib/redirects/locale/ta/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ta/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/te creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/te/LC_MESSAGES copying django/contrib/redirects/locale/te/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/te/LC_MESSAGES copying django/contrib/redirects/locale/te/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/te/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tg creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tg/LC_MESSAGES copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tg/LC_MESSAGES copying django/contrib/redirects/locale/tg/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tg/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/th creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/th/LC_MESSAGES copying django/contrib/redirects/locale/th/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/th/LC_MESSAGES copying django/contrib/redirects/locale/th/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/th/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tk/LC_MESSAGES copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tk/LC_MESSAGES copying django/contrib/redirects/locale/tk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tr creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tr/LC_MESSAGES copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tr/LC_MESSAGES copying django/contrib/redirects/locale/tr/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tr/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tt creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tt/LC_MESSAGES copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tt/LC_MESSAGES copying django/contrib/redirects/locale/tt/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/tt/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/udm creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/udm/LC_MESSAGES copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/udm/LC_MESSAGES copying django/contrib/redirects/locale/udm/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/udm/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/uk creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/uk/LC_MESSAGES copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/uk/LC_MESSAGES copying django/contrib/redirects/locale/uk/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/uk/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ur creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ur/LC_MESSAGES copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ur/LC_MESSAGES copying django/contrib/redirects/locale/ur/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/ur/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/uz creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/uz/LC_MESSAGES copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/uz/LC_MESSAGES copying django/contrib/redirects/locale/uz/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/uz/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/vi creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/vi/LC_MESSAGES copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/vi/LC_MESSAGES copying django/contrib/redirects/locale/vi/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/vi/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/zh_Hans creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES copying django/contrib/redirects/locale/zh_Hans/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/zh_Hans/LC_MESSAGES creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/zh_Hant creating /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.mo -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying django/contrib/redirects/locale/zh_Hant/LC_MESSAGES/django.po -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/redirects/locale/zh_Hant/LC_MESSAGES copying django/contrib/gis/gdal/LICENSE -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/gdal copying django/contrib/gis/geos/LICENSE -> /<>/.pybuild/cpython3_3.11_django/build/django/contrib/gis/geos running build_scripts creating build creating build/scripts-3.11 copying and adjusting django/bin/django-admin.py -> build/scripts-3.11 changing mode of build/scripts-3.11/django-admin.py from 644 to 755 make -C docs html LANGUAGE=en make[2]: Entering directory '/<>/docs' sphinx-build -b djangohtml -n -d _build/doctrees -D language=en . _build/html Running Sphinx v5.3.0 making output directory... done loading intersphinx inventory from /usr/share/doc/python3-doc/html/objects.inv... loading intersphinx inventory from /usr/share/doc/sphinx-doc/html/objects.inv... loading intersphinx inventory from /usr/share/doc/python-psycopg2-doc/html/objects.inv... building [mo]: targets for 0 po files that are out of date building [djangohtml]: targets for 530 source files that are out of date updating environment: [new config] 530 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... [ 2%] glossary reading sources... [ 2%] howto/auth-remote-user 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... [ 5%] 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... [ 6%] howto/initial-data reading sources... [ 6%] howto/legacy-databases 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... [ 8%] 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... [ 9%] 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... [ 10%] internals/contributing/writing-code/unit-tests reading sources... [ 10%] 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... [ 11%] internals/index reading sources... [ 11%] internals/mailing-lists reading sources... [ 11%] internals/organization reading sources... [ 11%] internals/release-process reading sources... [ 11%] internals/security reading sources... [ 12%] intro/contributing reading sources... [ 12%] intro/index reading sources... [ 12%] intro/install reading sources... [ 12%] intro/overview reading sources... [ 12%] intro/reusable-apps reading sources... [ 13%] intro/tutorial01 reading sources... [ 13%] intro/tutorial02 reading sources... [ 13%] intro/tutorial03 reading sources... [ 13%] intro/tutorial04 reading sources... [ 13%] intro/tutorial05 reading sources... [ 13%] intro/tutorial06 reading sources... [ 14%] intro/tutorial07 reading sources... [ 14%] intro/whatsnext reading sources... [ 14%] misc/api-stability reading sources... [ 14%] misc/design-philosophies reading sources... [ 14%] misc/distributions reading sources... [ 15%] misc/index reading sources... [ 15%] 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... [ 16%] ref/class-based-views/generic-date-based reading sources... [ 16%] ref/class-based-views/generic-display reading sources... [ 16%] 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... [ 17%] ref/class-based-views/mixins-editing reading sources... [ 17%] 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... [ 18%] ref/contrib/admin/actions reading sources... [ 18%] ref/contrib/admin/admindocs reading sources... [ 18%] ref/contrib/admin/index reading sources... [ 18%] ref/contrib/admin/javascript reading sources... [ 18%] ref/contrib/auth reading sources... [ 19%] ref/contrib/contenttypes reading sources... [ 19%] ref/contrib/flatpages reading sources... [ 19%] ref/contrib/gis/admin reading sources... [ 19%] ref/contrib/gis/commands reading sources... [ 19%] ref/contrib/gis/db-api reading sources... [ 20%] ref/contrib/gis/deployment reading sources... [ 20%] ref/contrib/gis/feeds reading sources... [ 20%] 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... [ 21%] ref/contrib/gis/geoquerysets reading sources... [ 21%] ref/contrib/gis/geos reading sources... [ 21%] ref/contrib/gis/index reading sources... [ 21%] ref/contrib/gis/install/geolibs reading sources... [ 21%] ref/contrib/gis/install/index reading sources... [ 22%] ref/contrib/gis/install/postgis reading sources... [ 22%] ref/contrib/gis/install/spatialite reading sources... [ 22%] ref/contrib/gis/layermapping reading sources... [ 22%] ref/contrib/gis/measure reading sources... [ 22%] ref/contrib/gis/model-api reading sources... [ 23%] ref/contrib/gis/ogrinspect reading sources... [ 23%] ref/contrib/gis/serializers reading sources... [ 23%] ref/contrib/gis/sitemaps reading sources... [ 23%] ref/contrib/gis/testing reading sources... [ 23%] ref/contrib/gis/tutorial reading sources... [ 23%] ref/contrib/gis/utils reading sources... [ 24%] ref/contrib/humanize reading sources... [ 24%] ref/contrib/index reading sources... [ 24%] ref/contrib/messages reading sources... [ 24%] ref/contrib/postgres/aggregates reading sources... [ 24%] ref/contrib/postgres/constraints reading sources... [ 25%] ref/contrib/postgres/fields reading sources... [ 25%] ref/contrib/postgres/forms reading sources... [ 25%] ref/contrib/postgres/functions reading sources... [ 25%] ref/contrib/postgres/index reading sources... [ 25%] ref/contrib/postgres/indexes reading sources... [ 26%] ref/contrib/postgres/lookups reading sources... [ 26%] ref/contrib/postgres/operations reading sources... [ 26%] ref/contrib/postgres/search reading sources... [ 26%] ref/contrib/postgres/validators reading sources... [ 26%] ref/contrib/redirects reading sources... [ 26%] ref/contrib/sitemaps reading sources... [ 27%] ref/contrib/sites reading sources... [ 27%] ref/contrib/staticfiles reading sources... [ 27%] ref/contrib/syndication reading sources... [ 27%] ref/csrf reading sources... [ 27%] ref/databases reading sources... [ 28%] ref/django-admin reading sources... [ 28%] ref/exceptions reading sources... [ 28%] ref/files/file reading sources... [ 28%] ref/files/index reading sources... [ 28%] ref/files/storage reading sources... [ 29%] ref/files/uploads reading sources... [ 29%] ref/forms/api reading sources... [ 29%] ref/forms/fields reading sources... [ 29%] ref/forms/formsets reading sources... [ 29%] ref/forms/index reading sources... [ 30%] ref/forms/models reading sources... [ 30%] ref/forms/renderers reading sources... [ 30%] ref/forms/validation reading sources... [ 30%] ref/forms/widgets reading sources... [ 30%] ref/index reading sources... [ 30%] ref/middleware reading sources... [ 31%] ref/migration-operations reading sources... [ 31%] ref/models/class reading sources... [ 31%] ref/models/conditional-expressions reading sources... [ 31%] ref/models/constraints reading sources... [ 31%] ref/models/database-functions reading sources... [ 32%] ref/models/expressions reading sources... [ 32%] ref/models/fields reading sources... [ 32%] ref/models/index reading sources... [ 32%] ref/models/indexes reading sources... [ 32%] ref/models/instances reading sources... [ 33%] ref/models/lookups reading sources... [ 33%] ref/models/meta reading sources... [ 33%] ref/models/options reading sources... [ 33%] ref/models/querysets reading sources... [ 33%] ref/models/relations reading sources... [ 33%] ref/paginator reading sources... [ 34%] ref/request-response reading sources... [ 34%] ref/schema-editor reading sources... [ 34%] ref/settings reading sources... [ 34%] ref/signals reading sources... [ 34%] ref/template-response reading sources... [ 35%] ref/templates/api reading sources... [ 35%] ref/templates/builtins reading sources... [ 35%] ref/templates/index reading sources... [ 35%] ref/templates/language reading sources... [ 35%] ref/unicode reading sources... [ 36%] ref/urlresolvers reading sources... [ 36%] ref/urls reading sources... [ 36%] ref/utils reading sources... [ 36%] ref/validators reading sources... [ 36%] ref/views reading sources... [ 36%] releases/0.95 reading sources... [ 37%] releases/0.96 reading sources... [ 37%] releases/1.0 reading sources... [ 37%] releases/1.0-porting-guide reading sources... [ 37%] releases/1.0.1 reading sources... [ 37%] releases/1.0.2 reading sources... [ 38%] releases/1.1 reading sources... [ 38%] releases/1.1.2 reading sources... [ 38%] releases/1.1.3 reading sources... [ 38%] releases/1.1.4 reading sources... [ 38%] releases/1.10 reading sources... [ 39%] releases/1.10.1 reading sources... [ 39%] releases/1.10.2 reading sources... [ 39%] releases/1.10.3 reading sources... [ 39%] releases/1.10.4 reading sources... [ 39%] releases/1.10.5 reading sources... [ 40%] releases/1.10.6 reading sources... [ 40%] releases/1.10.7 reading sources... [ 40%] releases/1.10.8 reading sources... [ 40%] releases/1.11 reading sources... [ 40%] releases/1.11.1 reading sources... [ 40%] releases/1.11.10 reading sources... [ 41%] releases/1.11.11 reading sources... [ 41%] releases/1.11.12 reading sources... [ 41%] releases/1.11.13 reading sources... [ 41%] releases/1.11.14 reading sources... [ 41%] releases/1.11.15 reading sources... [ 42%] releases/1.11.16 reading sources... [ 42%] releases/1.11.17 reading sources... [ 42%] releases/1.11.18 reading sources... [ 42%] releases/1.11.19 reading sources... [ 42%] releases/1.11.2 reading sources... [ 43%] releases/1.11.20 reading sources... [ 43%] releases/1.11.21 reading sources... [ 43%] releases/1.11.22 reading sources... [ 43%] releases/1.11.23 reading sources... [ 43%] releases/1.11.24 reading sources... [ 43%] releases/1.11.25 reading sources... [ 44%] releases/1.11.26 reading sources... [ 44%] releases/1.11.27 reading sources... [ 44%] releases/1.11.28 reading sources... [ 44%] releases/1.11.29 reading sources... [ 44%] releases/1.11.3 reading sources... [ 45%] releases/1.11.4 reading sources... [ 45%] releases/1.11.5 reading sources... [ 45%] releases/1.11.6 reading sources... [ 45%] releases/1.11.7 reading sources... [ 45%] releases/1.11.8 reading sources... [ 46%] releases/1.11.9 reading sources... [ 46%] releases/1.2 reading sources... [ 46%] releases/1.2.1 reading sources... [ 46%] releases/1.2.2 reading sources... [ 46%] releases/1.2.3 reading sources... [ 46%] releases/1.2.4 reading sources... [ 47%] releases/1.2.5 reading sources... [ 47%] releases/1.2.6 reading sources... [ 47%] releases/1.2.7 reading sources... [ 47%] releases/1.3 reading sources... [ 47%] releases/1.3.1 reading sources... [ 48%] releases/1.3.2 reading sources... [ 48%] releases/1.3.3 reading sources... [ 48%] releases/1.3.4 reading sources... [ 48%] releases/1.3.5 reading sources... [ 48%] releases/1.3.6 reading sources... [ 49%] releases/1.3.7 reading sources... [ 49%] releases/1.4 reading sources... [ 49%] releases/1.4.1 reading sources... [ 49%] releases/1.4.10 reading sources... [ 49%] releases/1.4.11 reading sources... [ 50%] releases/1.4.12 reading sources... [ 50%] releases/1.4.13 reading sources... [ 50%] releases/1.4.14 reading sources... [ 50%] releases/1.4.15 reading sources... [ 50%] releases/1.4.16 reading sources... [ 50%] releases/1.4.17 reading sources... [ 51%] releases/1.4.18 reading sources... [ 51%] releases/1.4.19 reading sources... [ 51%] releases/1.4.2 reading sources... [ 51%] releases/1.4.20 reading sources... [ 51%] releases/1.4.21 reading sources... [ 52%] releases/1.4.22 reading sources... [ 52%] releases/1.4.3 reading sources... [ 52%] releases/1.4.4 reading sources... [ 52%] releases/1.4.5 reading sources... [ 52%] releases/1.4.6 reading sources... [ 53%] releases/1.4.7 reading sources... [ 53%] releases/1.4.8 reading sources... [ 53%] releases/1.4.9 reading sources... [ 53%] releases/1.5 reading sources... [ 53%] releases/1.5.1 reading sources... [ 53%] releases/1.5.10 reading sources... [ 54%] releases/1.5.11 reading sources... [ 54%] releases/1.5.12 reading sources... [ 54%] releases/1.5.2 reading sources... [ 54%] releases/1.5.3 reading sources... [ 54%] releases/1.5.4 reading sources... [ 55%] releases/1.5.5 reading sources... [ 55%] releases/1.5.6 reading sources... [ 55%] releases/1.5.7 reading sources... [ 55%] releases/1.5.8 reading sources... [ 55%] releases/1.5.9 reading sources... [ 56%] releases/1.6 reading sources... [ 56%] releases/1.6.1 reading sources... [ 56%] releases/1.6.10 reading sources... [ 56%] releases/1.6.11 reading sources... [ 56%] releases/1.6.2 reading sources... [ 56%] releases/1.6.3 reading sources... [ 57%] releases/1.6.4 reading sources... [ 57%] releases/1.6.5 reading sources... [ 57%] releases/1.6.6 reading sources... [ 57%] releases/1.6.7 reading sources... [ 57%] releases/1.6.8 reading sources... [ 58%] releases/1.6.9 reading sources... [ 58%] releases/1.7 reading sources... [ 58%] releases/1.7.1 reading sources... [ 58%] releases/1.7.10 reading sources... [ 58%] releases/1.7.11 reading sources... [ 59%] releases/1.7.2 reading sources... [ 59%] releases/1.7.3 reading sources... [ 59%] releases/1.7.4 reading sources... [ 59%] releases/1.7.5 reading sources... [ 59%] releases/1.7.6 reading sources... [ 60%] releases/1.7.7 reading sources... [ 60%] releases/1.7.8 reading sources... [ 60%] releases/1.7.9 reading sources... [ 60%] releases/1.8 reading sources... [ 60%] releases/1.8.1 reading sources... [ 60%] releases/1.8.10 reading sources... [ 61%] releases/1.8.11 reading sources... [ 61%] releases/1.8.12 reading sources... [ 61%] releases/1.8.13 reading sources... [ 61%] releases/1.8.14 reading sources... [ 61%] releases/1.8.15 reading sources... [ 62%] releases/1.8.16 reading sources... [ 62%] releases/1.8.17 reading sources... [ 62%] releases/1.8.18 reading sources... [ 62%] releases/1.8.19 reading sources... [ 62%] releases/1.8.2 reading sources... [ 63%] releases/1.8.3 reading sources... [ 63%] releases/1.8.4 reading sources... [ 63%] releases/1.8.5 reading sources... [ 63%] releases/1.8.6 reading sources... [ 63%] releases/1.8.7 reading sources... [ 63%] releases/1.8.8 reading sources... [ 64%] releases/1.8.9 reading sources... [ 64%] releases/1.9 reading sources... [ 64%] releases/1.9.1 reading sources... [ 64%] releases/1.9.10 reading sources... [ 64%] releases/1.9.11 reading sources... [ 65%] releases/1.9.12 reading sources... [ 65%] releases/1.9.13 reading sources... [ 65%] releases/1.9.2 reading sources... [ 65%] releases/1.9.3 reading sources... [ 65%] releases/1.9.4 reading sources... [ 66%] releases/1.9.5 reading sources... [ 66%] releases/1.9.6 reading sources... [ 66%] releases/1.9.7 reading sources... [ 66%] releases/1.9.8 reading sources... [ 66%] releases/1.9.9 reading sources... [ 66%] releases/2.0 reading sources... [ 67%] releases/2.0.1 reading sources... [ 67%] releases/2.0.10 reading sources... [ 67%] releases/2.0.11 reading sources... [ 67%] releases/2.0.12 reading sources... [ 67%] releases/2.0.13 reading sources... [ 68%] releases/2.0.2 reading sources... [ 68%] releases/2.0.3 reading sources... [ 68%] releases/2.0.4 reading sources... [ 68%] releases/2.0.5 reading sources... [ 68%] releases/2.0.6 reading sources... [ 69%] releases/2.0.7 reading sources... [ 69%] releases/2.0.8 reading sources... [ 69%] releases/2.0.9 reading sources... [ 69%] releases/2.1 reading sources... [ 69%] releases/2.1.1 reading sources... [ 70%] releases/2.1.10 reading sources... [ 70%] releases/2.1.11 reading sources... [ 70%] releases/2.1.12 reading sources... [ 70%] releases/2.1.13 reading sources... [ 70%] releases/2.1.14 reading sources... [ 70%] releases/2.1.15 reading sources... [ 71%] releases/2.1.2 reading sources... [ 71%] releases/2.1.3 reading sources... [ 71%] releases/2.1.4 reading sources... [ 71%] releases/2.1.5 reading sources... [ 71%] releases/2.1.6 reading sources... [ 72%] releases/2.1.7 reading sources... [ 72%] releases/2.1.8 reading sources... [ 72%] releases/2.1.9 reading sources... [ 72%] releases/2.2 reading sources... [ 72%] releases/2.2.1 reading sources... [ 73%] releases/2.2.10 reading sources... [ 73%] releases/2.2.11 reading sources... [ 73%] releases/2.2.12 reading sources... [ 73%] releases/2.2.13 reading sources... [ 73%] releases/2.2.14 reading sources... [ 73%] releases/2.2.15 reading sources... [ 74%] releases/2.2.16 reading sources... [ 74%] releases/2.2.17 reading sources... [ 74%] releases/2.2.18 reading sources... [ 74%] releases/2.2.19 reading sources... [ 74%] releases/2.2.2 reading sources... [ 75%] releases/2.2.20 reading sources... [ 75%] releases/2.2.21 reading sources... [ 75%] releases/2.2.22 reading sources... [ 75%] releases/2.2.23 reading sources... [ 75%] releases/2.2.24 reading sources... [ 76%] releases/2.2.25 reading sources... [ 76%] releases/2.2.26 reading sources... [ 76%] releases/2.2.27 reading sources... [ 76%] releases/2.2.28 reading sources... [ 76%] releases/2.2.3 reading sources... [ 76%] releases/2.2.4 reading sources... [ 77%] releases/2.2.5 reading sources... [ 77%] releases/2.2.6 reading sources... [ 77%] releases/2.2.7 reading sources... [ 77%] releases/2.2.8 reading sources... [ 77%] releases/2.2.9 reading sources... [ 78%] releases/3.0 reading sources... [ 78%] releases/3.0.1 reading sources... [ 78%] releases/3.0.10 reading sources... [ 78%] releases/3.0.11 reading sources... [ 78%] releases/3.0.12 reading sources... [ 79%] releases/3.0.13 reading sources... [ 79%] releases/3.0.14 reading sources... [ 79%] releases/3.0.2 reading sources... [ 79%] releases/3.0.3 reading sources... [ 79%] releases/3.0.4 reading sources... [ 80%] releases/3.0.5 reading sources... [ 80%] releases/3.0.6 reading sources... [ 80%] releases/3.0.7 reading sources... [ 80%] releases/3.0.8 reading sources... [ 80%] releases/3.0.9 reading sources... [ 80%] releases/3.1 reading sources... [ 81%] releases/3.1.1 reading sources... [ 81%] releases/3.1.10 reading sources... [ 81%] releases/3.1.11 reading sources... [ 81%] releases/3.1.12 reading sources... [ 81%] releases/3.1.13 reading sources... [ 82%] releases/3.1.14 reading sources... [ 82%] releases/3.1.2 reading sources... [ 82%] releases/3.1.3 reading sources... [ 82%] releases/3.1.4 reading sources... [ 82%] releases/3.1.5 reading sources... [ 83%] releases/3.1.6 reading sources... [ 83%] releases/3.1.7 reading sources... [ 83%] releases/3.1.8 reading sources... [ 83%] releases/3.1.9 reading sources... [ 83%] releases/3.2 reading sources... [ 83%] releases/3.2.1 reading sources... [ 84%] releases/3.2.10 reading sources... [ 84%] releases/3.2.11 reading sources... [ 84%] releases/3.2.12 reading sources... [ 84%] releases/3.2.13 reading sources... [ 84%] releases/3.2.14 reading sources... [ 85%] releases/3.2.15 reading sources... [ 85%] releases/3.2.16 reading sources... [ 85%] releases/3.2.17 reading sources... [ 85%] releases/3.2.18 reading sources... [ 85%] releases/3.2.19 reading sources... [ 86%] releases/3.2.2 reading sources... [ 86%] releases/3.2.3 reading sources... [ 86%] releases/3.2.4 reading sources... [ 86%] releases/3.2.5 reading sources... [ 86%] releases/3.2.6 reading sources... [ 86%] releases/3.2.7 reading sources... [ 87%] releases/3.2.8 reading sources... [ 87%] releases/3.2.9 reading sources... [ 87%] releases/index reading sources... [ 87%] releases/security reading sources... [ 87%] topics/async reading sources... [ 88%] topics/auth/customizing reading sources... [ 88%] topics/auth/default reading sources... [ 88%] topics/auth/index reading sources... [ 88%] topics/auth/passwords reading sources... [ 88%] 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... [ 89%] topics/class-based-views/index reading sources... [ 89%] 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... [ 90%] topics/db/examples/many_to_many reading sources... [ 90%] topics/db/examples/many_to_one reading sources... [ 91%] topics/db/examples/one_to_one reading sources... [ 91%] topics/db/index reading sources... [ 91%] topics/db/instrumentation reading sources... [ 91%] topics/db/managers reading sources... [ 91%] topics/db/models reading sources... [ 92%] topics/db/multi-db reading sources... [ 92%] topics/db/optimization reading sources... [ 92%] topics/db/queries reading sources... [ 92%] topics/db/search reading sources... [ 92%] 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... [ 93%] topics/files reading sources... [ 93%] topics/forms/formsets reading sources... [ 94%] topics/forms/index reading sources... [ 94%] topics/forms/media reading sources... [ 94%] topics/forms/modelforms reading sources... [ 94%] topics/http/decorators reading sources... [ 94%] 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... [ 95%] 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... [ 96%] 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... [ 97%] 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... [ 2%] glossary writing output... [ 2%] howto/auth-remote-user 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... [ 5%] 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... [ 6%] howto/initial-data writing output... [ 6%] howto/legacy-databases 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... [ 8%] 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... [ 9%] 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... [ 10%] internals/contributing/writing-code/unit-tests writing output... [ 10%] 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... [ 11%] internals/index writing output... [ 11%] internals/mailing-lists writing output... [ 11%] internals/organization writing output... [ 11%] internals/release-process writing output... [ 11%] internals/security writing output... [ 12%] intro/contributing writing output... [ 12%] intro/index writing output... [ 12%] intro/install writing output... [ 12%] intro/overview writing output... [ 12%] intro/reusable-apps writing output... [ 13%] intro/tutorial01 writing output... [ 13%] intro/tutorial02 writing output... [ 13%] intro/tutorial03 writing output... [ 13%] intro/tutorial04 writing output... [ 13%] intro/tutorial05 writing output... [ 13%] intro/tutorial06 writing output... [ 14%] intro/tutorial07 writing output... [ 14%] intro/whatsnext writing output... [ 14%] misc/api-stability writing output... [ 14%] misc/design-philosophies writing output... [ 14%] misc/distributions writing output... [ 15%] misc/index writing output... [ 15%] 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... [ 16%] ref/class-based-views/generic-date-based writing output... [ 16%] ref/class-based-views/generic-display writing output... [ 16%] 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... [ 17%] ref/class-based-views/mixins-editing writing output... [ 17%] 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... [ 18%] ref/contrib/admin/actions writing output... [ 18%] ref/contrib/admin/admindocs writing output... [ 18%] ref/contrib/admin/index writing output... [ 18%] ref/contrib/admin/javascript writing output... [ 18%] ref/contrib/auth writing output... [ 19%] ref/contrib/contenttypes writing output... [ 19%] ref/contrib/flatpages writing output... [ 19%] ref/contrib/gis/admin writing output... [ 19%] ref/contrib/gis/commands writing output... [ 19%] ref/contrib/gis/db-api writing output... [ 20%] ref/contrib/gis/deployment writing output... [ 20%] ref/contrib/gis/feeds writing output... [ 20%] 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... [ 21%] ref/contrib/gis/geoquerysets writing output... [ 21%] ref/contrib/gis/geos writing output... [ 21%] ref/contrib/gis/index writing output... [ 21%] ref/contrib/gis/install/geolibs writing output... [ 21%] ref/contrib/gis/install/index writing output... [ 22%] ref/contrib/gis/install/postgis writing output... [ 22%] ref/contrib/gis/install/spatialite writing output... [ 22%] ref/contrib/gis/layermapping writing output... [ 22%] ref/contrib/gis/measure writing output... [ 22%] ref/contrib/gis/model-api writing output... [ 23%] ref/contrib/gis/ogrinspect writing output... [ 23%] ref/contrib/gis/serializers writing output... [ 23%] ref/contrib/gis/sitemaps writing output... [ 23%] ref/contrib/gis/testing writing output... [ 23%] ref/contrib/gis/tutorial writing output... [ 23%] ref/contrib/gis/utils writing output... [ 24%] ref/contrib/humanize writing output... [ 24%] ref/contrib/index writing output... [ 24%] ref/contrib/messages writing output... [ 24%] ref/contrib/postgres/aggregates writing output... [ 24%] ref/contrib/postgres/constraints writing output... [ 25%] ref/contrib/postgres/fields writing output... [ 25%] ref/contrib/postgres/forms writing output... [ 25%] ref/contrib/postgres/functions writing output... [ 25%] ref/contrib/postgres/index writing output... [ 25%] ref/contrib/postgres/indexes writing output... [ 26%] ref/contrib/postgres/lookups writing output... [ 26%] ref/contrib/postgres/operations writing output... [ 26%] ref/contrib/postgres/search writing output... [ 26%] ref/contrib/postgres/validators writing output... [ 26%] ref/contrib/redirects writing output... [ 26%] ref/contrib/sitemaps writing output... [ 27%] ref/contrib/sites writing output... [ 27%] ref/contrib/staticfiles writing output... [ 27%] ref/contrib/syndication writing output... [ 27%] ref/csrf writing output... [ 27%] ref/databases writing output... [ 28%] ref/django-admin writing output... [ 28%] ref/exceptions writing output... [ 28%] ref/files/file writing output... [ 28%] ref/files/index writing output... [ 28%] ref/files/storage writing output... [ 29%] ref/files/uploads writing output... [ 29%] ref/forms/api writing output... [ 29%] ref/forms/fields writing output... [ 29%] ref/forms/formsets writing output... [ 29%] ref/forms/index writing output... [ 30%] ref/forms/models writing output... [ 30%] ref/forms/renderers writing output... [ 30%] ref/forms/validation writing output... [ 30%] ref/forms/widgets writing output... [ 30%] ref/index writing output... [ 30%] ref/middleware writing output... [ 31%] ref/migration-operations writing output... [ 31%] ref/models/class writing output... [ 31%] ref/models/conditional-expressions writing output... [ 31%] ref/models/constraints writing output... [ 31%] ref/models/database-functions writing output... [ 32%] ref/models/expressions writing output... [ 32%] ref/models/fields writing output... [ 32%] ref/models/index writing output... [ 32%] ref/models/indexes writing output... [ 32%] ref/models/instances writing output... [ 33%] ref/models/lookups writing output... [ 33%] ref/models/meta writing output... [ 33%] ref/models/options writing output... [ 33%] ref/models/querysets writing output... [ 33%] ref/models/relations writing output... [ 33%] ref/paginator writing output... [ 34%] ref/request-response writing output... [ 34%] ref/schema-editor writing output... [ 34%] ref/settings writing output... [ 34%] ref/signals writing output... [ 34%] ref/template-response writing output... [ 35%] ref/templates/api writing output... [ 35%] ref/templates/builtins writing output... [ 35%] ref/templates/index writing output... [ 35%] ref/templates/language writing output... [ 35%] ref/unicode writing output... [ 36%] ref/urlresolvers writing output... [ 36%] ref/urls writing output... [ 36%] ref/utils writing output... [ 36%] ref/validators writing output... [ 36%] ref/views writing output... [ 36%] releases/0.95 writing output... [ 37%] releases/0.96 writing output... [ 37%] releases/1.0 writing output... [ 37%] releases/1.0-porting-guide writing output... [ 37%] releases/1.0.1 writing output... [ 37%] releases/1.0.2 writing output... [ 38%] releases/1.1 writing output... [ 38%] releases/1.1.2 writing output... [ 38%] releases/1.1.3 writing output... [ 38%] releases/1.1.4 writing output... [ 38%] releases/1.10 writing output... [ 39%] releases/1.10.1 writing output... [ 39%] releases/1.10.2 writing output... [ 39%] releases/1.10.3 writing output... [ 39%] releases/1.10.4 writing output... [ 39%] releases/1.10.5 writing output... [ 40%] releases/1.10.6 writing output... [ 40%] releases/1.10.7 writing output... [ 40%] releases/1.10.8 writing output... [ 40%] releases/1.11 writing output... [ 40%] releases/1.11.1 writing output... [ 40%] releases/1.11.10 writing output... [ 41%] releases/1.11.11 writing output... [ 41%] releases/1.11.12 writing output... [ 41%] releases/1.11.13 writing output... [ 41%] releases/1.11.14 writing output... [ 41%] releases/1.11.15 writing output... [ 42%] releases/1.11.16 writing output... [ 42%] releases/1.11.17 writing output... [ 42%] releases/1.11.18 writing output... [ 42%] releases/1.11.19 writing output... [ 42%] releases/1.11.2 writing output... [ 43%] releases/1.11.20 writing output... [ 43%] releases/1.11.21 writing output... [ 43%] releases/1.11.22 writing output... [ 43%] releases/1.11.23 writing output... [ 43%] releases/1.11.24 writing output... [ 43%] releases/1.11.25 writing output... [ 44%] releases/1.11.26 writing output... [ 44%] releases/1.11.27 writing output... [ 44%] releases/1.11.28 writing output... [ 44%] releases/1.11.29 writing output... [ 44%] releases/1.11.3 writing output... [ 45%] releases/1.11.4 writing output... [ 45%] releases/1.11.5 writing output... [ 45%] releases/1.11.6 writing output... [ 45%] releases/1.11.7 writing output... [ 45%] releases/1.11.8 writing output... [ 46%] releases/1.11.9 writing output... [ 46%] releases/1.2 writing output... [ 46%] releases/1.2.1 writing output... [ 46%] releases/1.2.2 writing output... [ 46%] releases/1.2.3 writing output... [ 46%] releases/1.2.4 writing output... [ 47%] releases/1.2.5 writing output... [ 47%] releases/1.2.6 writing output... [ 47%] releases/1.2.7 writing output... [ 47%] releases/1.3 writing output... [ 47%] releases/1.3.1 writing output... [ 48%] releases/1.3.2 writing output... [ 48%] releases/1.3.3 writing output... [ 48%] releases/1.3.4 writing output... [ 48%] releases/1.3.5 writing output... [ 48%] releases/1.3.6 writing output... [ 49%] releases/1.3.7 writing output... [ 49%] releases/1.4 writing output... [ 49%] releases/1.4.1 writing output... [ 49%] releases/1.4.10 writing output... [ 49%] releases/1.4.11 writing output... [ 50%] releases/1.4.12 writing output... [ 50%] releases/1.4.13 writing output... [ 50%] releases/1.4.14 writing output... [ 50%] releases/1.4.15 writing output... [ 50%] releases/1.4.16 writing output... [ 50%] releases/1.4.17 writing output... [ 51%] releases/1.4.18 writing output... [ 51%] releases/1.4.19 writing output... [ 51%] releases/1.4.2 writing output... [ 51%] releases/1.4.20 writing output... [ 51%] releases/1.4.21 writing output... [ 52%] releases/1.4.22 writing output... [ 52%] releases/1.4.3 writing output... [ 52%] releases/1.4.4 writing output... [ 52%] releases/1.4.5 writing output... [ 52%] releases/1.4.6 writing output... [ 53%] releases/1.4.7 writing output... [ 53%] releases/1.4.8 writing output... [ 53%] releases/1.4.9 writing output... [ 53%] releases/1.5 writing output... [ 53%] releases/1.5.1 writing output... [ 53%] releases/1.5.10 writing output... [ 54%] releases/1.5.11 writing output... [ 54%] releases/1.5.12 writing output... [ 54%] releases/1.5.2 writing output... [ 54%] releases/1.5.3 writing output... [ 54%] releases/1.5.4 writing output... [ 55%] releases/1.5.5 writing output... [ 55%] releases/1.5.6 writing output... [ 55%] releases/1.5.7 writing output... [ 55%] releases/1.5.8 writing output... [ 55%] releases/1.5.9 writing output... [ 56%] releases/1.6 writing output... [ 56%] releases/1.6.1 writing output... [ 56%] releases/1.6.10 writing output... [ 56%] releases/1.6.11 writing output... [ 56%] releases/1.6.2 writing output... [ 56%] releases/1.6.3 writing output... [ 57%] releases/1.6.4 writing output... [ 57%] releases/1.6.5 writing output... [ 57%] releases/1.6.6 writing output... [ 57%] releases/1.6.7 writing output... [ 57%] releases/1.6.8 writing output... [ 58%] releases/1.6.9 writing output... [ 58%] releases/1.7 writing output... [ 58%] releases/1.7.1 writing output... [ 58%] releases/1.7.10 writing output... [ 58%] releases/1.7.11 writing output... [ 59%] releases/1.7.2 writing output... [ 59%] releases/1.7.3 writing output... [ 59%] releases/1.7.4 writing output... [ 59%] releases/1.7.5 writing output... [ 59%] releases/1.7.6 writing output... [ 60%] releases/1.7.7 writing output... [ 60%] releases/1.7.8 writing output... [ 60%] releases/1.7.9 writing output... [ 60%] releases/1.8 writing output... [ 60%] releases/1.8.1 writing output... [ 60%] releases/1.8.10 writing output... [ 61%] releases/1.8.11 writing output... [ 61%] releases/1.8.12 writing output... [ 61%] releases/1.8.13 writing output... [ 61%] releases/1.8.14 writing output... [ 61%] releases/1.8.15 writing output... [ 62%] releases/1.8.16 writing output... [ 62%] releases/1.8.17 writing output... [ 62%] releases/1.8.18 writing output... [ 62%] releases/1.8.19 writing output... [ 62%] releases/1.8.2 writing output... [ 63%] releases/1.8.3 writing output... [ 63%] releases/1.8.4 writing output... [ 63%] releases/1.8.5 writing output... [ 63%] releases/1.8.6 writing output... [ 63%] releases/1.8.7 writing output... [ 63%] releases/1.8.8 writing output... [ 64%] releases/1.8.9 writing output... [ 64%] releases/1.9 writing output... [ 64%] releases/1.9.1 writing output... [ 64%] releases/1.9.10 writing output... [ 64%] releases/1.9.11 writing output... [ 65%] releases/1.9.12 writing output... [ 65%] releases/1.9.13 writing output... [ 65%] releases/1.9.2 writing output... [ 65%] releases/1.9.3 writing output... [ 65%] releases/1.9.4 writing output... [ 66%] releases/1.9.5 writing output... [ 66%] releases/1.9.6 writing output... [ 66%] releases/1.9.7 writing output... [ 66%] releases/1.9.8 writing output... [ 66%] releases/1.9.9 writing output... [ 66%] releases/2.0 writing output... [ 67%] releases/2.0.1 writing output... [ 67%] releases/2.0.10 writing output... [ 67%] releases/2.0.11 writing output... [ 67%] releases/2.0.12 writing output... [ 67%] releases/2.0.13 writing output... [ 68%] releases/2.0.2 writing output... [ 68%] releases/2.0.3 writing output... [ 68%] releases/2.0.4 writing output... [ 68%] releases/2.0.5 writing output... [ 68%] releases/2.0.6 writing output... [ 69%] releases/2.0.7 writing output... [ 69%] releases/2.0.8 writing output... [ 69%] releases/2.0.9 writing output... [ 69%] releases/2.1 writing output... [ 69%] releases/2.1.1 writing output... [ 70%] releases/2.1.10 writing output... [ 70%] releases/2.1.11 writing output... [ 70%] releases/2.1.12 writing output... [ 70%] releases/2.1.13 writing output... [ 70%] releases/2.1.14 writing output... [ 70%] releases/2.1.15 writing output... [ 71%] releases/2.1.2 writing output... [ 71%] releases/2.1.3 writing output... [ 71%] releases/2.1.4 writing output... [ 71%] releases/2.1.5 writing output... [ 71%] releases/2.1.6 writing output... [ 72%] releases/2.1.7 writing output... [ 72%] releases/2.1.8 writing output... [ 72%] releases/2.1.9 writing output... [ 72%] releases/2.2 writing output... [ 72%] releases/2.2.1 writing output... [ 73%] releases/2.2.10 writing output... [ 73%] releases/2.2.11 writing output... [ 73%] releases/2.2.12 writing output... [ 73%] releases/2.2.13 writing output... [ 73%] releases/2.2.14 writing output... [ 73%] releases/2.2.15 writing output... [ 74%] releases/2.2.16 writing output... [ 74%] releases/2.2.17 writing output... [ 74%] releases/2.2.18 writing output... [ 74%] releases/2.2.19 writing output... [ 74%] releases/2.2.2 writing output... [ 75%] releases/2.2.20 writing output... [ 75%] releases/2.2.21 writing output... [ 75%] releases/2.2.22 writing output... [ 75%] releases/2.2.23 writing output... [ 75%] releases/2.2.24 writing output... [ 76%] releases/2.2.25 writing output... [ 76%] releases/2.2.26 writing output... [ 76%] releases/2.2.27 writing output... [ 76%] releases/2.2.28 writing output... [ 76%] releases/2.2.3 writing output... [ 76%] releases/2.2.4 writing output... [ 77%] releases/2.2.5 writing output... [ 77%] releases/2.2.6 writing output... [ 77%] releases/2.2.7 writing output... [ 77%] releases/2.2.8 writing output... [ 77%] releases/2.2.9 writing output... [ 78%] releases/3.0 writing output... [ 78%] releases/3.0.1 writing output... [ 78%] releases/3.0.10 writing output... [ 78%] releases/3.0.11 writing output... [ 78%] releases/3.0.12 writing output... [ 79%] releases/3.0.13 writing output... [ 79%] releases/3.0.14 writing output... [ 79%] releases/3.0.2 writing output... [ 79%] releases/3.0.3 writing output... [ 79%] releases/3.0.4 writing output... [ 80%] releases/3.0.5 writing output... [ 80%] releases/3.0.6 writing output... [ 80%] releases/3.0.7 writing output... [ 80%] releases/3.0.8 writing output... [ 80%] releases/3.0.9 writing output... [ 80%] releases/3.1 writing output... [ 81%] releases/3.1.1 writing output... [ 81%] releases/3.1.10 writing output... [ 81%] releases/3.1.11 writing output... [ 81%] releases/3.1.12 writing output... [ 81%] releases/3.1.13 writing output... [ 82%] releases/3.1.14 writing output... [ 82%] releases/3.1.2 writing output... [ 82%] releases/3.1.3 writing output... [ 82%] releases/3.1.4 writing output... [ 82%] releases/3.1.5 writing output... [ 83%] releases/3.1.6 writing output... [ 83%] releases/3.1.7 writing output... [ 83%] releases/3.1.8 writing output... [ 83%] releases/3.1.9 writing output... [ 83%] releases/3.2 writing output... [ 83%] releases/3.2.1 writing output... [ 84%] releases/3.2.10 writing output... [ 84%] releases/3.2.11 writing output... [ 84%] releases/3.2.12 writing output... [ 84%] releases/3.2.13 writing output... [ 84%] releases/3.2.14 writing output... [ 85%] releases/3.2.15 writing output... [ 85%] releases/3.2.16 writing output... [ 85%] releases/3.2.17 writing output... [ 85%] releases/3.2.18 writing output... [ 85%] releases/3.2.19 writing output... [ 86%] releases/3.2.2 writing output... [ 86%] releases/3.2.3 writing output... [ 86%] releases/3.2.4 writing output... [ 86%] releases/3.2.5 writing output... [ 86%] releases/3.2.6 writing output... [ 86%] releases/3.2.7 writing output... [ 87%] releases/3.2.8 writing output... [ 87%] releases/3.2.9 writing output... [ 87%] releases/index writing output... [ 87%] releases/security writing output... [ 87%] topics/async writing output... [ 88%] topics/auth/customizing writing output... [ 88%] topics/auth/default writing output... [ 88%] topics/auth/index writing output... [ 88%] topics/auth/passwords writing output... [ 88%] 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... [ 89%] topics/class-based-views/index writing output... [ 89%] 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... [ 90%] topics/db/examples/many_to_many writing output... [ 90%] topics/db/examples/many_to_one writing output... [ 91%] topics/db/examples/one_to_one writing output... [ 91%] topics/db/index writing output... [ 91%] topics/db/instrumentation writing output... [ 91%] topics/db/managers writing output... [ 91%] topics/db/models writing output... [ 92%] topics/db/multi-db writing output... [ 92%] topics/db/optimization writing output... [ 92%] topics/db/queries writing output... [ 92%] topics/db/search writing output... [ 92%] 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... [ 93%] topics/files writing output... [ 93%] topics/forms/formsets writing output... [ 94%] topics/forms/index writing output... [ 94%] topics/forms/media writing output... [ 94%] topics/forms/modelforms writing output... [ 94%] topics/http/decorators writing output... [ 94%] 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... [ 95%] 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... [ 96%] 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... [ 97%] 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 generating indices... genindex py-modindex done highlighting module code... [ 0%] asgiref.sync highlighting module code... [ 1%] django highlighting module code... [ 1%] django.apps.config highlighting module code... [ 2%] django.conf.urls highlighting module code... [ 3%] django.conf.urls.i18n highlighting module code... [ 3%] django.contrib.admin highlighting module code... [ 4%] django.contrib.admin.decorators highlighting module code... [ 5%] 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.db.models.aggregates highlighting module code... [ 11%] django.contrib.gis.db.models.fields highlighting module code... [ 12%] django.contrib.gis.db.models.functions highlighting module code... [ 13%] django.contrib.gis.feeds highlighting module code... [ 13%] django.contrib.gis.forms.fields highlighting module code... [ 14%] django.contrib.gis.forms.widgets highlighting module code... [ 15%] django.contrib.gis.gdal.datasource highlighting module code... [ 15%] django.contrib.gis.gdal.driver highlighting module code... [ 16%] django.contrib.gis.gdal.envelope highlighting module code... [ 17%] django.contrib.gis.gdal.error highlighting module code... [ 17%] django.contrib.gis.gdal.geometries highlighting module code... [ 18%] django.contrib.gis.gdal.geomtype highlighting module code... [ 19%] django.contrib.gis.gdal.raster.source highlighting module code... [ 19%] django.contrib.gis.gdal.srs highlighting module code... [ 20%] django.contrib.gis.geos.collections highlighting module code... [ 21%] django.contrib.gis.geos.error highlighting module code... [ 21%] django.contrib.gis.geos.factory highlighting module code... [ 22%] django.contrib.gis.geos.geometry highlighting module code... [ 23%] django.contrib.gis.geos.io highlighting module code... [ 23%] django.contrib.gis.geos.linestring highlighting module code... [ 24%] django.contrib.gis.geos.point highlighting module code... [ 25%] django.contrib.gis.geos.polygon highlighting module code... [ 25%] django.contrib.gis.geos.prototypes.io highlighting module code... [ 26%] django.contrib.gis.measure highlighting module code... [ 26%] django.contrib.gis.utils.layermapping highlighting module code... [ 27%] django.contrib.gis.utils.ogrinspect highlighting module code... [ 28%] django.contrib.messages.api highlighting module code... [ 28%] django.contrib.messages.middleware highlighting module code... [ 29%] django.contrib.postgres.constraints highlighting module code... [ 30%] django.contrib.postgres.functions highlighting module code... [ 30%] django.contrib.postgres.indexes highlighting module code... [ 31%] django.contrib.postgres.validators highlighting module code... [ 32%] django.contrib.sessions.exceptions highlighting module code... [ 32%] django.contrib.sessions.middleware highlighting module code... [ 33%] django.contrib.sitemaps highlighting module code... [ 34%] django.contrib.sites.middleware highlighting module code... [ 34%] django.core.checks.messages highlighting module code... [ 35%] django.core.exceptions highlighting module code... [ 36%] django.core.files.base highlighting module code... [ 36%] django.core.files.images highlighting module code... [ 37%] django.core.files.storage highlighting module code... [ 38%] django.core.files.uploadedfile highlighting module code... [ 38%] django.core.files.uploadhandler highlighting module code... [ 39%] django.core.mail highlighting module code... [ 40%] django.core.mail.message highlighting module code... [ 40%] django.core.management.base highlighting module code... [ 41%] django.core.paginator highlighting module code... [ 42%] django.core.signing highlighting module code... [ 42%] django.core.validators highlighting module code... [ 43%] django.db.backends.base.schema highlighting module code... [ 44%] django.db.migrations.operations.fields highlighting module code... [ 44%] django.db.migrations.operations.models highlighting module code... [ 45%] django.db.migrations.operations.special highlighting module code... [ 46%] django.db.models.aggregates highlighting module code... [ 46%] django.db.models.base highlighting module code... [ 47%] django.db.models.constraints highlighting module code... [ 48%] django.db.models.deletion highlighting module code... [ 48%] django.db.models.expressions highlighting module code... [ 49%] django.db.models.fields highlighting module code... [ 50%] django.db.models.fields.files highlighting module code... [ 50%] django.db.models.fields.json highlighting module code... [ 51%] django.db.models.fields.related highlighting module code... [ 51%] django.db.models.functions.comparison highlighting module code... [ 52%] django.db.models.functions.datetime highlighting module code... [ 53%] django.db.models.functions.math highlighting module code... [ 53%] django.db.models.functions.text highlighting module code... [ 54%] django.db.models.functions.window highlighting module code... [ 55%] django.db.models.indexes highlighting module code... [ 55%] django.db.models.lookups highlighting module code... [ 56%] django.db.models.manager highlighting module code... [ 57%] django.db.models.options highlighting module code... [ 57%] django.db.models.query highlighting module code... [ 58%] django.db.models.query_utils highlighting module code... [ 59%] django.db.transaction highlighting module code... [ 59%] django.db.utils highlighting module code... [ 60%] django.dispatch.dispatcher highlighting module code... [ 61%] django.forms.boundfield highlighting module code... [ 61%] django.forms.fields highlighting module code... [ 62%] django.forms.forms highlighting module code... [ 63%] django.forms.formsets highlighting module code... [ 63%] django.forms.models highlighting module code... [ 64%] django.forms.renderers highlighting module code... [ 65%] django.forms.widgets highlighting module code... [ 65%] django.http.request highlighting module code... [ 66%] django.http.response highlighting module code... [ 67%] django.middleware.cache highlighting module code... [ 67%] django.middleware.clickjacking highlighting module code... [ 68%] django.middleware.common highlighting module code... [ 69%] django.middleware.csrf highlighting module code... [ 69%] django.middleware.gzip highlighting module code... [ 70%] django.middleware.http highlighting module code... [ 71%] django.middleware.locale highlighting module code... [ 71%] django.middleware.security highlighting module code... [ 72%] django.shortcuts highlighting module code... [ 73%] django.template.backends.django highlighting module code... [ 73%] django.template.backends.jinja2 highlighting module code... [ 74%] django.template.base highlighting module code... [ 75%] django.template.context highlighting module code... [ 75%] django.template.context_processors highlighting module code... [ 76%] django.template.engine highlighting module code... [ 76%] django.template.exceptions highlighting module code... [ 77%] django.template.loader highlighting module code... [ 78%] django.template.loaders.base highlighting module code... [ 78%] django.template.response highlighting module code... [ 79%] django.test.client highlighting module code... [ 80%] django.test.runner highlighting module code... [ 80%] django.test.testcases highlighting module code... [ 81%] django.test.utils highlighting module code... [ 82%] django.urls.base highlighting module code... [ 82%] django.urls.conf highlighting module code... [ 83%] django.urls.converters highlighting module code... [ 84%] django.urls.exceptions highlighting module code... [ 84%] django.urls.resolvers highlighting module code... [ 85%] django.utils.cache highlighting module code... [ 86%] django.utils.dateparse highlighting module code... [ 86%] django.utils.decorators highlighting module code... [ 87%] django.utils.encoding highlighting module code... [ 88%] django.utils.feedgenerator highlighting module code... [ 88%] django.utils.functional highlighting module code... [ 89%] django.utils.html highlighting module code... [ 90%] django.utils.http highlighting module code... [ 90%] django.utils.log highlighting module code... [ 91%] django.utils.module_loading highlighting module code... [ 92%] django.utils.safestring highlighting module code... [ 92%] django.utils.text highlighting module code... [ 93%] django.utils.timezone highlighting module code... [ 94%] django.utils.translation highlighting module code... [ 94%] django.views.debug highlighting module code... [ 95%] django.views.decorators.cache highlighting module code... [ 96%] django.views.decorators.common highlighting module code... [ 96%] django.views.decorators.csrf highlighting module code... [ 97%] django.views.decorators.debug highlighting module code... [ 98%] 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/fieldsets.png copying images... [ 91%] ref/contrib/admin/_images/list_filter.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. The HTML pages are in _build/html. Build finished. The HTML pages are in _build/html. make[2]: Leaving directory '/<>/docs' make[1]: Leaving directory '/<>' debian/rules override_dh_auto_test make[1]: Entering directory '/<>' set -e; cd tests && for python in $(py3versions -s); do \ echo "——— Running tests with $python ———"; \ LC_ALL=C.UTF-8 PYTHONPATH=.. $python ./runtests.py --verbosity=2; \ done ——— Running tests with python3.11 ——— Testing against Django installed in '/<>/django' with up to 4 processes Importing application from_db_value Importing application shortcuts Importing application migrations Importing application utils_tests Importing application m2m_through_regress Importing application middleware Importing application db_functions Importing application select_related Importing application m2m_through Importing application aggregation_regress Importing application model_forms Importing application serializers Importing application bash_completion Importing application wsgi Importing application str Importing application or_lookups Importing application fixtures Importing application no_models Importing application properties Importing application m2m_signals Importing application extra_regress Importing application test_runner Importing application model_options Importing application shell Importing application admin_registration Importing application m2o_recursive Importing application dispatch Importing application get_or_create Importing application annotations Importing application backends Importing application sites_tests Importing application null_queries Importing application builtin_server Importing application reverse_lookup Importing application update_only_fields Importing application inspectdb Importing application defer_regress Importing application custom_columns Importing application admin_changelist Importing application model_package Importing application redirects_tests Importing application admin_utils Importing application admin_docs Importing application dbshell Importing application empty Importing application logging_tests Importing application datetimes Importing application requests Importing application bulk_create Importing application model_meta Importing application db_typecasts Importing application dates Importing application aggregation Importing application admin_ordering Importing application field_defaults Importing application model_fields Importing application expressions Importing application indexes Importing application migration_test_data_persistence Importing application model_indexes Importing application raw_query Importing application prefetch_related Importing application admin_filters Importing application swappable_models Importing application null_fk Importing application migrations2 Importing application introspection Importing application generic_relations Importing application generic_inline_admin Importing application distinct_on_fields Importing application servers Importing application null_fk_ordering Importing application model_formsets_regress Importing application defer Importing application validators Importing application conditional_processing Importing application order_with_respect_to Importing application sitemaps_tests Importing application admin_views Importing application middleware_exceptions Importing application responses Importing application validation Importing application custom_lookups Importing application urlpatterns Importing application select_for_update Importing application context_processors Importing application one_to_one Importing application known_related_objects Importing application app_loading Importing application resolve_url Importing application filtered_relation Importing application db_utils Importing application test_client_regress Importing application many_to_one Importing application foreign_object Importing application template_tests Importing application forms_tests Importing application view_tests Importing application field_subclassing Importing application csrf_tests Importing application transaction_hooks Importing application admin_widgets Importing application sites_framework Importing application model_regress Importing application queryset_pickle Importing application httpwrappers Importing application delete Importing application admin_custom_urls Importing application test_utils Importing application m2m_intermediary Importing application i18n Importing application custom_managers Importing application cache Importing application constraints Importing application expressions_case Importing application m2m_and_m2o Importing application template_backends Importing application fixtures_model_package Importing application inline_formsets Importing application many_to_many Importing application basic Importing application auth_tests Importing application signing Importing application save_delete_hooks Importing application deprecation Importing application base Importing application model_formsets Importing application multiple_database Importing application managers_regress Importing application max_lengths Importing application m2m_recursive Importing application user_commands Importing application empty_models Importing application model_inheritance Importing application template_loader Importing application custom_pk Importing application admin_scripts Importing application messages_tests Importing application version Importing application humanize_tests Importing application urlpatterns_reverse Importing application ordering Importing application schema Importing application select_related_onetoone Importing application unmanaged_models Importing application settings_tests Importing application admin_inlines Importing application get_earliest_or_latest Importing application timezones Importing application proxy_model_inheritance Importing application check_framework Importing application generic_relations_regress Importing application decorators Importing application test_client Importing application files Importing application file_uploads Importing application invalid_models_tests Importing application modeladmin Importing application absolute_url_overrides Importing application expressions_window Importing application custom_migration_operations Importing application proxy_models Importing application model_inheritance_regress Importing application get_object_or_404 Importing application generic_views Importing application postgres_tests Importing application handlers Importing application contenttypes_tests Importing application file_storage Importing application model_enums Importing application async Importing application model_utils Importing application field_deconstruction Importing application admin_autodiscover Importing application mail Importing application select_related_regress Importing application signals Importing application flatpages_tests Importing application fixtures_regress Importing application migrate_signals Importing application string_lookup Importing application staticfiles_tests Importing application delete_regress Importing application sessions_tests Importing application pagination Importing application signed_cookies_tests Importing application reserved_names Importing application custom_methods Importing application nested_foreign_keys Importing application many_to_one_null Importing application test_exceptions Importing application update Importing application admin_default_site Importing application admin_checks Importing application force_insert_update Importing application transactions Importing application m2m_regress Importing application m2m_multiple Importing application project_template Importing application mutually_referential Importing application asgi Importing application lookup Importing application datatypes Importing application queries Importing application apps Importing application syndication_tests Creating test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Operations to perform: Synchronize unmigrated apps: absolute_url_overrides, admin_autodiscover, admin_changelist, admin_checks, admin_custom_urls, admin_default_site, admin_docs, admin_filters, admin_inlines, admin_ordering, admin_registration, admin_scripts, admin_utils, admin_views, admin_widgets, aggregation, aggregation_regress, annotations, app_loading, apps, asgi, async, auth, auth_tests, backends, base, bash_completion, basic, builtin_server, bulk_create, cache, check_framework, conditional_processing, constraints, contenttypes, contenttypes_tests, context_processors, csrf_tests, custom_columns, custom_lookups, custom_managers, custom_methods, custom_migration_operations, custom_pk, datatypes, dates, datetimes, db_typecasts, db_utils, dbshell, decorators, defer, defer_regress, delete, delete_regress, deprecation, dispatch, distinct_on_fields, empty, empty_models, expressions, expressions_case, expressions_window, extra_regress, field_deconstruction, field_defaults, field_subclassing, file_storage, file_uploads, files, filtered_relation, fixtures, fixtures_model_package, fixtures_regress, flatpages_tests, force_insert_update, foreign_object, forms_tests, from_db_value, generic_inline_admin, generic_relations, generic_relations_regress, generic_views, get_earliest_or_latest, get_object_or_404, get_or_create, handlers, httpwrappers, humanize_tests, i18n, indexes, inline_formsets, inspectdb, introspection, invalid_models_tests, known_related_objects, logging_tests, lookup, m2m_and_m2o, m2m_intermediary, m2m_multiple, m2m_recursive, m2m_regress, m2m_signals, m2m_through, m2m_through_regress, m2o_recursive, mail, managers_regress, many_to_many, many_to_one, many_to_one_null, max_lengths, messages, messages_tests, middleware, middleware_exceptions, migrate_signals, migrations, migrations2, model_enums, model_fields, model_forms, model_formsets, model_formsets_regress, model_indexes, model_inheritance, model_inheritance_regress, model_meta, model_options, model_package, model_regress, model_utils, modeladmin, multiple_database, mutually_referential, nested_foreign_keys, no_models, null_fk, null_fk_ordering, null_queries, one_to_one, or_lookups, order_with_respect_to, ordering, pagination, prefetch_related, project_template, properties, proxy_model_inheritance, proxy_models, queries, queryset_pickle, raw_query, redirects_tests, requests, reserved_names, resolve_url, responses, reverse_lookup, save_delete_hooks, schema, select_for_update, select_related, select_related_onetoone, select_related_regress, serializers, servers, sessions, sessions_tests, settings_tests, shell, shortcuts, signals, signed_cookies_tests, signing, sitemaps_tests, sites_tests, staticfiles, staticfiles_tests, str, string_lookup, swappable_models, syndication_tests, template_backends, template_loader, template_tests, test_client, test_client_regress, test_exceptions, test_runner, test_utils, timezones, transaction_hooks, transactions, unmanaged_models, update, update_only_fields, urlpatterns, urlpatterns_reverse, user_commands, utils_tests, validation, validators, version, view_tests, wsgi Apply all migrations: admin, db_functions, flatpages, migration_test_data_persistence, postgres_tests, redirects, sites, sites_framework Synchronizing apps without migrations: Creating tables... Creating table django_content_type Creating table auth_permission Creating table auth_group Creating table auth_user Creating table django_session Creating table from_db_value_cashmodel Creating table migrations_modelwithcustombase Creating table migrations_unmigratedmodel Creating table utils_tests_category Creating table utils_tests_categoryinfo Creating table m2m_through_regress_membership Creating table m2m_through_regress_usermembership Creating table m2m_through_regress_person Creating table m2m_through_regress_group Creating table m2m_through_regress_car Creating table m2m_through_regress_driver Creating table m2m_through_regress_cardriver Creating table m2m_through_regress_event Creating table m2m_through_regress_competitor Creating table m2m_through_regress_individualcompetitor Creating table m2m_through_regress_competingteam Creating table select_related_domain Creating table select_related_kingdom Creating table select_related_phylum Creating table select_related_klass Creating table select_related_order Creating table select_related_family Creating table select_related_genus Creating table select_related_species Creating table select_related_hybridspecies Creating table select_related_topping Creating table select_related_pizza Creating table select_related_taggeditem Creating table select_related_bookmark Creating table m2m_through_person Creating table m2m_through_personchild Creating table m2m_through_group Creating table m2m_through_membership Creating table test_table Creating table m2m_through_testnodefaultsornulls Creating table m2m_through_personselfrefm2m Creating table m2m_through_friendship Creating table m2m_through_symmetricalfriendship Creating table m2m_through_event Creating table m2m_through_invitation Creating table m2m_through_employee Creating table m2m_through_relationship Creating table m2m_through_ingredient Creating table m2m_through_recipe Creating table m2m_through_recipeingredient Creating table aggregation_regress_author Creating table aggregation_regress_publisher Creating table aggregation_regress_itemtag Creating table aggregation_regress_book Creating table aggregation_regress_store Creating table aggregation_regress_entries Creating table aggregation_regress_clues Creating table aggregation_regress_withmanualpk Creating table aggregation_regress_hardbackbook Creating table aggregation_regress_alfa Creating table aggregation_regress_bravo Creating table aggregation_regress_charlie Creating table aggregation_regress_selfreffk Creating table model_forms_person Creating table model_forms_category Creating table model_forms_writer Creating table model_forms_article Creating table model_forms_improvedarticle Creating table model_forms_improvedarticlewithparentlink Creating table model_forms_betterwriter Creating table model_forms_publication Creating table model_forms_publicationdefaults Creating table model_forms_author Creating table model_forms_author1 Creating table model_forms_writerprofile Creating table model_forms_document Creating table model_forms_textfile Creating table model_forms_customff Creating table model_forms_filepathmodel Creating table model_forms_imagefile Creating table model_forms_optionalimagefile Creating table model_forms_noextensionimagefile Creating table model_forms_homepage Creating table model_forms_product Creating table model_forms_price Creating table model_forms_triple Creating table model_forms_articlestatus Creating table model_forms_inventory Creating table model_forms_book Creating table model_forms_derivedbook Creating table model_forms_explicitpk Creating table model_forms_post Creating table model_forms_datetimepost Creating table model_forms_derivedpost Creating table model_forms_bigint Creating table model_forms_customfieldforexclusionmodel Creating table model_forms_flexibledatepost Creating table model_forms_colour Creating table model_forms_colourfulitem Creating table model_forms_customerrormessage Creating table model_forms_character Creating table model_forms_stumpjoke Creating table model_forms_student Creating table model_forms_photo Creating table model_forms_uuidpk Creating table model_forms_strictassignmentfieldspecific Creating table model_forms_strictassignmentall Creating table model_forms_award Creating table model_forms_nullableuniquecharfieldmodel Creating table serializers_categorymetadata Creating table serializers_category Creating table serializers_author Creating table serializers_article Creating table serializers_authorprofile Creating table serializers_actor Creating table serializers_movie Creating table serializers_score Creating table serializers_player Creating table serializers_basemodel Creating table serializers_complexmodel Creating table serializers_binarydata Creating table serializers_booleandata Creating table serializers_chardata Creating table serializers_datedata Creating table serializers_datetimedata Creating table serializers_decimaldata Creating table serializers_emaildata Creating table serializers_filedata Creating table serializers_filepathdata Creating table serializers_floatdata Creating table serializers_integerdata Creating table serializers_bigintegerdata Creating table serializers_genericipaddressdata Creating table serializers_nullbooleandata Creating table serializers_positivebigintegerdata Creating table serializers_positiveintegerdata Creating table serializers_positivesmallintegerdata Creating table serializers_slugdata Creating table serializers_smalldata Creating table serializers_textdata Creating table serializers_timedata Creating table serializers_tag Creating table serializers_genericdata Creating table serializers_anchor Creating table serializers_uniqueanchor Creating table serializers_fkdata Creating table serializers_m2mdata Creating table serializers_o2odata Creating table serializers_fkselfdata Creating table serializers_m2mselfdata Creating table serializers_fkdatatofield Creating table serializers_fkdatatoo2o Creating table serializers_m2mintermediatedata Creating table serializers_intermediate Creating table serializers_booleanpkdata Creating table serializers_charpkdata Creating table serializers_datepkdata Creating table serializers_datetimepkdata Creating table serializers_decimalpkdata Creating table serializers_emailpkdata Creating table serializers_filepathpkdata Creating table serializers_floatpkdata Creating table serializers_integerpkdata Creating table serializers_genericipaddresspkdata Creating table serializers_positiveintegerpkdata Creating table serializers_positivesmallintegerpkdata Creating table serializers_slugpkdata Creating table serializers_smallpkdata Creating table serializers_uuiddata Creating table serializers_uuiddefaultdata Creating table serializers_fktouuid Creating table serializers_autonowdatetimedata Creating table serializers_modifyingsavedata Creating table serializers_inheritabstractmodel Creating table serializers_inheritbasemodel Creating table serializers_explicitinheritbasemodel Creating table serializers_lengthmodel Creating table serializers_parent Creating table serializers_child Creating table serializers_naturalkeyanchor Creating table serializers_fkdatanaturalkey Creating table serializers_naturalkeything Creating table serializers_naturalpkwithdefault Creating table serializers_fkaspknonaturalkey Creating table str_internationalarticle Creating table or_lookups_article Creating table fixtures_category Creating table fixtures_article Creating table fixtures_blog Creating table fixtures_tag Creating table fixtures_person Creating table fixtures_spy Creating table fixtures_visa Creating table fixtures_book Creating table fixtures_primarykeyuuidmodel Creating table fixtures_naturalkeything Creating table fixtures_circulara Creating table fixtures_circularb Creating table properties_person Creating table m2m_signals_part Creating table m2m_signals_car Creating table m2m_signals_sportscar Creating table m2m_signals_person Creating table extra_regress_revisionablemodel Creating table extra_regress_order Creating table extra_regress_testobject Creating table test_runner_person Creating table test_runner_throughbase Creating table test_runner_through Creating table test_runner_b Creating table model_options_author Creating table model_options_editor Creating table model_options_book Creating table model_options_bookstore Creating table model_options_editorstore Creating table model_options_scientistref Creating table model_options_articleref Creating table admin_registration_person Creating table admin_registration_traveler Creating table admin_registration_place Creating table m2o_recursive_category Creating table m2o_recursive_person Creating table get_or_create_person Creating table get_or_create_defaultperson Creating table get_or_create_manualprimarykeytest Creating table get_or_create_profile Creating table get_or_create_tag Creating table get_or_create_thing Creating table get_or_create_publisher Creating table get_or_create_author Creating table get_or_create_book Creating table annotations_author Creating table annotations_publisher Creating table annotations_book Creating table annotations_store Creating table annotations_departmentstore Creating table annotations_employee Creating table annotations_company Creating table annotations_ticket Creating table backends_square Creating table backends_person Creating table backends_schoolclass Creating table backends_verylongmodelnamezzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz Creating table backends_tag Creating table CaseSensitive_Post Creating table backends_reporter Creating table backends_article Creating table backends_item Creating table backends_object Creating table backends_objectreference Creating table backends_objectselfreference Creating table backends_circulara Creating table backends_circularb Creating table backends_rawdata Creating table backends_author Creating table backends_book Creating table order Creating table null_queries_poll Creating table null_queries_choice Creating table null_queries_outera Creating table null_queries_outerb Creating table null_queries_inner Creating table reverse_lookup_user Creating table reverse_lookup_poll Creating table reverse_lookup_choice Creating table update_only_fields_account Creating table update_only_fields_person Creating table update_only_fields_employee Creating table update_only_fields_profile Creating table inspectdb_people Creating table inspectdb_message Creating table inspectdb_peopledata Creating table inspectdb_peoplemoredata Creating table inspectdb_digitsincolumnname Creating table inspectdb_special.table name Creating table inspectdb_columntypes Creating table inspectdb_jsonfieldcolumntype Creating table inspectdb_charfielddbcollation Creating table inspectdb_textfielddbcollation Creating table inspectdb_uniquetogether Creating table defer_regress_item Creating table defer_regress_relateditem Creating table defer_regress_child Creating table defer_regress_leaf Creating table defer_regress_resolvethis Creating table defer_regress_simpleitem Creating table defer_regress_feature Creating table defer_regress_specialfeature Creating table defer_regress_onetooneitem Creating table defer_regress_itemandsimpleitem Creating table defer_regress_profile Creating table defer_regress_location Creating table defer_regress_request Creating table defer_regress_base Creating table defer_regress_derived Creating table my_author_table Creating table custom_columns_article Creating table admin_changelist_event Creating table admin_changelist_parent Creating table admin_changelist_child Creating table admin_changelist_genre Creating table admin_changelist_band Creating table admin_changelist_musician Creating table admin_changelist_group Creating table admin_changelist_concert Creating table admin_changelist_membership Creating table admin_changelist_quartet Creating table admin_changelist_chordsmusician Creating table admin_changelist_chordsband Creating table admin_changelist_invitation Creating table admin_changelist_swallow Creating table admin_changelist_swallowonetoone Creating table admin_changelist_unorderedobject Creating table admin_changelist_orderedobject Creating table admin_changelist_customiduser Creating table admin_changelist_charpk Creating table model_package_site Creating table model_package_article Creating table model_package_publication Creating table model_package_advertisement Creating table admin_utils_site Creating table admin_utils_article Creating table admin_utils_count Creating table admin_utils_event Creating table admin_utils_location Creating table admin_utils_guest Creating table admin_utils_eventguide Creating table admin_utils_vehicle Creating table admin_utils_car Creating table admin_docs_company Creating table admin_docs_group Creating table admin_docs_family Creating table admin_docs_person Creating table empty_empty Creating table datetimes_article Creating table datetimes_comment Creating table datetimes_category Creating table bulk_create_country Creating table bulk_create_proxymulticountry Creating table bulk_create_restaurant Creating table bulk_create_pizzeria Creating table bulk_create_state Creating table bulk_create_twofields Creating table bulk_create_nofields Creating table bulk_create_smallautofieldmodel Creating table bulk_create_bigautofieldmodel Creating table bulk_create_nullablefields Creating table model_meta_relation Creating table model_meta_baseperson Creating table model_meta_person Creating table model_meta_personthroughproxysubclass Creating table model_meta_relating Creating table model_meta_commonancestor Creating table model_meta_firstparent Creating table model_meta_secondparent Creating table model_meta_child Creating table dates_article Creating table dates_comment Creating table dates_category Creating table aggregation_author Creating table aggregation_publisher Creating table aggregation_book Creating table aggregation_store Creating table admin_ordering_band Creating table admin_ordering_song Creating table field_defaults_article Creating table model_fields_foo Creating table model_fields_bar Creating table model_fields_whiz Creating table model_fields_whizdelayed Creating table model_fields_whiziter Creating table model_fields_whiziterempty Creating table model_fields_choiceful Creating table model_fields_bigd Creating table model_fields_floatmodel Creating table model_fields_bigs Creating table model_fields_unicodeslugfield Creating table model_fields_automodel Creating table model_fields_bigautomodel Creating table model_fields_smallautomodel Creating table model_fields_smallintegermodel Creating table model_fields_integermodel Creating table model_fields_bigintegermodel Creating table model_fields_positivebigintegermodel Creating table model_fields_positivesmallintegermodel Creating table model_fields_positiveintegermodel Creating table model_fields_post Creating table model_fields_nullbooleanmodel Creating table model_fields_booleanmodel Creating table model_fields_datetimemodel Creating table model_fields_durationmodel Creating table model_fields_nulldurationmodel Creating table model_fields_primarykeycharmodel Creating table model_fields_fkstobooleans Creating table model_fields_fktochar Creating table model_fields_renamedfield Creating table model_fields_verbosenamefield Creating table model_fields_genericipaddress Creating table model_fields_decimallessthanone Creating table model_fields_fieldclassattributemodel Creating table model_fields_datamodel Creating table model_fields_document Creating table model_fields_person Creating table model_fields_personwithheight Creating table model_fields_personwithheightandwidth Creating table model_fields_persondimensionsfirst Creating table model_fields_persontwoimages Creating table model_fields_jsonmodel Creating table model_fields_nullablejsonmodel Creating table model_fields_relatedjsonmodel Creating table model_fields_allfieldsmodel Creating table model_fields_manytomany Creating table model_fields_uuidmodel Creating table model_fields_nullableuuidmodel Creating table model_fields_primarykeyuuidmodel Creating table model_fields_relatedtouuidmodel Creating table model_fields_uuidchild Creating table model_fields_uuidgrandchild Creating table expressions_manager Creating table expressions_employee Creating table expressions_remoteemployee Creating table expressions_company Creating table expressions_number Creating table expressions_ExPeRiMeNt Creating table expressions_result Creating table expressions_time Creating table expressions_simulationrun Creating table expressions_uuidpk Creating table expressions_uuid Creating table indexes_articletranslation Creating table indexes_article Creating table indexes_indextogethersinglelist Creating table indexes_indexedarticle Creating table indexes_indexedarticle2 Creating table model_indexes_book Creating table model_indexes_childmodel1 Creating table model_indexes_childmodel2 Creating table raw_query_author Creating table raw_query_book Creating table raw_query_bookfkaspk Creating table raw_query_coffee Creating table raw_query_mixedcaseidcolumn Creating table raw_query_reviewer Creating table raw_query_friendlyauthor Creating table prefetch_related_author Creating table prefetch_related_authorwithage Creating table prefetch_related_favoriteauthors Creating table prefetch_related_authoraddress Creating table prefetch_related_book Creating table prefetch_related_bookwithyear Creating table prefetch_related_bio Creating table prefetch_related_reader Creating table prefetch_related_bookreview Creating table prefetch_related_qualification Creating table prefetch_related_teacher Creating table prefetch_related_department Creating table prefetch_related_taggeditem Creating table prefetch_related_article Creating table prefetch_related_bookmark Creating table prefetch_related_comment Creating table prefetch_related_house Creating table prefetch_related_room Creating table prefetch_related_person Creating table prefetch_related_employee Creating table prefetch_related_lessonentry Creating table prefetch_related_wordentry Creating table prefetch_related_author2 Creating table prefetch_related_pet Creating table prefetch_related_flea Creating table admin_filters_book Creating table admin_filters_improvedbook Creating table admin_filters_department Creating table admin_filters_employee Creating table admin_filters_taggeditem Creating table admin_filters_bookmark Creating table swappable_models_article Creating table swappable_models_alternatearticle Creating table null_fk_systemdetails Creating table null_fk_systeminfo Creating table null_fk_forum Creating table null_fk_post Creating table null_fk_comment Creating table null_fk_item Creating table null_fk_propertyvalue Creating table null_fk_property Creating table introspection_city Creating table introspection_country Creating table introspection_district Creating table introspection_reporter Creating table introspection_article Creating table introspection_comment Creating table introspection_checkconstraintmodel Creating table introspection_uniqueconstraintconditionmodel Creating table generic_relations_taggeditem Creating table generic_relations_valuabletaggeditem Creating table generic_relations_abstractcomparison Creating table generic_relations_comparison Creating table generic_relations_animal Creating table generic_relations_vegetable Creating table generic_relations_carrot Creating table generic_relations_mineral Creating table generic_relations_gecko Creating table generic_relations_rock Creating table generic_relations_valuablerock Creating table generic_relations_manualpk Creating table generic_relations_forproxymodelmodel Creating table generic_relations_forconcretemodelmodel Creating table generic_relations_concreterelatedmodel Creating table generic_relations_allowsnullgfk Creating table generic_inline_admin_episode Creating table generic_inline_admin_media Creating table generic_inline_admin_category Creating table generic_inline_admin_phonenumber Creating table generic_inline_admin_contact Creating table generic_inline_admin_episodepermanent Creating table distinct_on_fields_tag Creating table distinct_on_fields_celebrity Creating table distinct_on_fields_fan Creating table distinct_on_fields_staff Creating table distinct_on_fields_stafftag Creating table servers_person Creating table null_fk_ordering_author Creating table null_fk_ordering_article Creating table null_fk_ordering_systeminfo Creating table null_fk_ordering_forum Creating table null_fk_ordering_post Creating table null_fk_ordering_comment Creating table model_formsets_regress_user Creating table model_formsets_regress_usersite Creating table model_formsets_regress_userprofile Creating table model_formsets_regress_userpreferences Creating table model_formsets_regress_profilenetwork Creating table model_formsets_regress_place Creating table model_formsets_regress_restaurant Creating table model_formsets_regress_manager Creating table model_formsets_regress_network Creating table model_formsets_regress_host Creating table defer_secondary Creating table defer_primary Creating table defer_child Creating table defer_bigchild Creating table order_with_respect_to_question Creating table order_with_respect_to_answer Creating table order_with_respect_to_post Creating table order_with_respect_to_entity Creating table order_with_respect_to_dimension Creating table order_with_respect_to_component Creating table sitemaps_tests_testmodel Creating table sitemaps_tests_i18ntestmodel Creating table admin_views_section Creating table admin_views_article Creating table admin_views_book Creating table admin_views_promo Creating table admin_views_chapter Creating table admin_views_chapterxtra1 Creating table admin_views_chapterxtra2 Creating table admin_views_rowlevelchangepermissionmodel Creating table admin_views_customarticle Creating table admin_views_modelwithstringprimarykey Creating table admin_views_color Creating table admin_views_thing Creating table admin_views_actor Creating table admin_views_inquisition Creating table admin_views_sketch Creating table admin_views_character Creating table admin_views_stumpjoke Creating table admin_views_fabric Creating table admin_views_person Creating table admin_views_persona Creating table admin_views_account Creating table admin_views_fooaccount Creating table admin_views_baraccount Creating table admin_views_subscriber Creating table admin_views_externalsubscriber Creating table admin_views_oldsubscriber Creating table admin_views_media Creating table admin_views_podcast Creating table admin_views_vodcast Creating table admin_views_parent Creating table admin_views_child Creating table admin_views_pkchild Creating table admin_views_toy Creating table admin_views_emptymodel Creating table admin_views_gallery Creating table admin_views_picture Creating table admin_views_language Creating table admin_views_title Creating table admin_views_titletranslation Creating table admin_views_recommender Creating table admin_views_recommendation Creating table admin_views_collector Creating table admin_views_widget Creating table admin_views_doohickey Creating table admin_views_grommet Creating table admin_views_whatsit Creating table admin_views_doodad Creating table admin_views_fancydoodad Creating table admin_views_category Creating table admin_views_link Creating table admin_views_prepopulatedpost Creating table admin_views_prepopulatedsubpost Creating table admin_views_post Creating table admin_views_gadget Creating table admin_views_villain Creating table admin_views_supervillain Creating table admin_views_funkytag Creating table admin_views_plot Creating table admin_views_plotdetails Creating table admin_views_secrethideout Creating table admin_views_supersecrethideout Creating table admin_views_bookmark Creating table admin_views_cyclicone Creating table admin_views_cyclictwo Creating table admin_views_topping Creating table admin_views_pizza Creating table admin_views_album Creating table admin_views_song Creating table admin_views_employee Creating table admin_views_workhour Creating table admin_views_manager Creating table admin_views_bonus Creating table admin_views_question Creating table admin_views_answer Creating table admin_views_reservation Creating table admin_views_fooddelivery Creating table admin_views_coverletter Creating table admin_views_paper Creating table admin_views_shortmessage Creating table admin_views_telegram Creating table admin_views_story Creating table admin_views_otherstory Creating table admin_views_complexsortedperson Creating table admin_views_pluggablesearchperson Creating table admin_views_prepopulatedpostlargeslug Creating table admin_views_adminorderedfield Creating table admin_views_adminorderedmodelmethod Creating table admin_views_adminorderedadminmethod Creating table admin_views_adminorderedcallable Creating table admin_views_report Creating table admin_views_mainprepopulated Creating table admin_views_relatedprepopulated Creating table admin_views_unorderedobject Creating table admin_views_undeletableobject Creating table admin_views_unchangeableobject Creating table admin_views_usermessenger Creating table admin_views_simple Creating table admin_views_choice Creating table admin_views_parentwithdependentchildren Creating table admin_views_dependentchild Creating table admin_views_filteredmanager Creating table admin_views_emptymodelvisible Creating table admin_views_emptymodelhidden Creating table admin_views_emptymodelmixin Creating table admin_views_state Creating table admin_views_city Creating table admin_views_restaurant Creating table admin_views_worker Creating table admin_views_referencedbyparent Creating table admin_views_parentwithfk Creating table admin_views_childofreferer Creating table admin_views_inlinereferer Creating table admin_views_referencedbyinline Creating table admin_views_inlinereference Creating table admin_views_recipe Creating table admin_views_ingredient Creating table admin_views_recipeingredient Creating table admin_views_notreferenced Creating table admin_views_explicitlyprovidedpk Creating table admin_views_implicitlygeneratedpk Creating table admin_views_referencedbygenrel Creating table admin_views_genrelreference Creating table admin_views_parentwithuuidpk Creating table admin_views_relatedwithuuidpkmodel Creating table admin_views_author Creating table admin_views_authorship Creating table admin_views_readonlyrelatedfield Creating table validation_modeltovalidate Creating table validation_uniquefieldsmodel Creating table validation_custompkmodel Creating table validation_uniquetogethermodel Creating table validation_uniquefordatemodel Creating table validation_custommessagesmodel Creating table validation_author Creating table validation_article Creating table validation_post Creating table validation_flexibledatepost Creating table validation_uniqueerrorsmodel Creating table validation_genericipaddresstestmodel Creating table validation_genericipaddrunpackuniquetest Creating table custom_lookups_author Creating table custom_lookups_article Creating table custom_lookups_mysqlunixtimestamp Creating table custom_lookups_custommodel Creating table select_for_update_entity Creating table select_for_update_country Creating table select_for_update_eucountry Creating table select_for_update_city Creating table select_for_update_eucity Creating table select_for_update_citycountryproxy Creating table select_for_update_person Creating table select_for_update_personprofile Creating table context_processors_debugobject Creating table one_to_one_place Creating table one_to_one_restaurant Creating table one_to_one_bar Creating table one_to_one_undergroundbar Creating table one_to_one_waiter Creating table one_to_one_favorites Creating table one_to_one_manualprimarykey Creating table one_to_one_relatedmodel Creating table one_to_one_multimodel Creating table one_to_one_target Creating table one_to_one_pointer Creating table one_to_one_pointer2 Creating table one_to_one_hiddenpointer Creating table one_to_one_tofieldpointer Creating table one_to_one_school Creating table one_to_one_director Creating table known_related_objects_tournament Creating table known_related_objects_organiser Creating table known_related_objects_pool Creating table known_related_objects_poolstyle Creating table resolve_url_unimportantthing Creating table filtered_relation_author Creating table filtered_relation_editor Creating table filtered_relation_book Creating table filtered_relation_borrower Creating table filtered_relation_reservation Creating table filtered_relation_rentalsession Creating table filtered_relation_seller Creating table filtered_relation_currency Creating table filtered_relation_exchangerate Creating table filtered_relation_bookdailysales Creating table test_client_regress_customuser Creating table many_to_one_reporter Creating table many_to_one_article Creating table many_to_one_country Creating table many_to_one_city Creating table many_to_one_district Creating table many_to_one_first Creating table many_to_one_second Creating table many_to_one_third Creating table many_to_one_parent Creating table many_to_one_parentstringprimarykey Creating table many_to_one_child Creating table many_to_one_childnullableparent Creating table many_to_one_childstringprimarykeyparent Creating table many_to_one_tofieldchild Creating table many_to_one_category Creating table many_to_one_record Creating table many_to_one_relation Creating table many_to_one_school Creating table many_to_one_student Creating table foreign_object_article Creating table foreign_object_newsarticle Creating table foreign_object_articletranslation Creating table foreign_object_articletag Creating table foreign_object_articleidea Creating table foreign_object_address Creating table foreign_object_customer Creating table foreign_object_contact Creating table foreign_object_slugpage Creating table foreign_object_country Creating table foreign_object_person Creating table foreign_object_group Creating table foreign_object_membership Creating table foreign_object_friendship Creating table forms_tests_boundarymodel Creating table forms_tests_defaults Creating table forms_tests_choicemodel Creating table forms_tests_choiceoptionmodel Creating table forms_tests_choicefieldmodel Creating table forms_tests_optionalmultichoicemodel Creating table forms_tests_filemodel Creating table forms_tests_article Creating table view_tests_author Creating table view_tests_article Creating table view_tests_urlarticle Creating table view_tests_datearticle Creating table transaction_hooks_thing Creating table admin_widgets_member Creating table admin_widgets_artist Creating table admin_widgets_band Creating table admin_widgets_unsafelimitchoicesto Creating table admin_widgets_album Creating table admin_widgets_releaseevent Creating table admin_widgets_videostream Creating table admin_widgets_inventory Creating table admin_widgets_event Creating table admin_widgets_car Creating table admin_widgets_cartire Creating table admin_widgets_honeycomb Creating table admin_widgets_bee Creating table admin_widgets_individual Creating table admin_widgets_company Creating table admin_widgets_advisor Creating table admin_widgets_student Creating table admin_widgets_school Creating table admin_widgets_profile Creating table model_regress_article Creating table model_regress_movie Creating table model_regress_party Creating table model_regress_event Creating table model_regress_department Creating table model_regress_worker Creating table model_regress_nonautopk Creating table model_regress_model1 Creating table model_regress_model2 Creating table model_regress_model3 Creating table queryset_pickle_group Creating table queryset_pickle_event Creating table queryset_pickle_happening Creating table queryset_pickle_binaryfieldmodel Creating table queryset_pickle_somemodel Creating table queryset_pickle_m2mmodel Creating table queryset_pickle_myevent Creating table queryset_pickle_edition Creating table delete_p Creating table delete_r Creating table delete_s Creating table delete_t Creating table delete_u Creating table delete_rchild Creating table delete_rchildchild Creating table delete_a Creating table delete_b Creating table delete_m Creating table delete_mr Creating table delete_mrnull Creating table delete_avatar Creating table delete_user Creating table delete_hiddenuser Creating table delete_hiddenuserprofile Creating table delete_m2mto Creating table delete_m2mfrom Creating table delete_parent Creating table delete_child Creating table delete_base Creating table delete_reltobase Creating table delete_origin Creating table delete_referrer Creating table delete_secondreferrer Creating table delete_deletetop Creating table delete_b1 Creating table delete_b2 Creating table delete_b3 Creating table delete_deletebottom Creating table delete_genericb1 Creating table delete_genericb2 Creating table delete_genericdeletebottom Creating table delete_genericdeletebottomparent Creating table admin_custom_urls_action Creating table admin_custom_urls_person Creating table admin_custom_urls_car Creating table test_utils_car Creating table test_utils_person Creating table test_utils_possessedcar Creating table m2m_intermediary_reporter Creating table m2m_intermediary_article Creating table m2m_intermediary_writer Creating table i18n_testmodel Creating table i18n_company Creating table custom_managers_person Creating table custom_managers_funperson Creating table custom_managers_book Creating table custom_managers_car Creating table custom_managers_relatedmodel Creating table custom_managers_restrictedmodel Creating table custom_managers_onetoonerestrictedmodel Creating table custom_managers_personfromabstract Creating table cache_poll Creating table constraints_product Creating table constraints_uniqueconstraintproduct Creating table constraints_uniqueconstraintconditionproduct Creating table constraints_childmodel Creating table expressions_case_casetestmodel Creating table expressions_case_o2ocasetestmodel Creating table expressions_case_fkcasetestmodel Creating table expressions_case_client Creating table m2m_and_m2o_user Creating table m2m_and_m2o_issue Creating table m2m_and_m2o_stringreferencemodel Creating table fixtures_model_package_article Creating table inline_formsets_school Creating table inline_formsets_parent Creating table inline_formsets_child Creating table inline_formsets_poet Creating table inline_formsets_poem Creating table many_to_many_publication Creating table many_to_many_tag Creating table many_to_many_article Creating table many_to_many_user Creating table many_to_many_userarticle Creating table many_to_many_inheritedarticlea Creating table many_to_many_inheritedarticleb Creating table basic_article Creating table basic_featuredarticle Creating table basic_selfref Creating table basic_primarykeywithdefault Creating table basic_childprimarykeywithdefault Creating table auth_tests_customuser Creating table auth_tests_customuserwithoutisactivefield Creating table auth_tests_extensionuser Creating table auth_tests_custompermissionsuser Creating table auth_tests_customusernonuniqueusername Creating table auth_tests_isactivetestuser1 Creating table auth_tests_minimaluser Creating table auth_tests_nopassworduser Creating table auth_tests_concrete Creating table auth_tests_uuiduser Creating table auth_tests_customemailfield Creating table auth_tests_email Creating table auth_tests_customuserwithfk Creating table auth_tests_integerusernameuser Creating table auth_tests_userwithdisabledlastloginfield Creating table auth_tests_organization Creating table auth_tests_customuserwithm2m Creating table auth_tests_customuserwithm2mthrough Creating table auth_tests_membership Creating table save_delete_hooks_person Creating table base_mymodel Creating table model_formsets_author Creating table model_formsets_betterauthor Creating table model_formsets_book Creating table model_formsets_bookwithcustompk Creating table model_formsets_editor Creating table model_formsets_bookwithoptionalalteditor Creating table model_formsets_alternatebook Creating table model_formsets_authormeeting Creating table model_formsets_customprimarykey Creating table model_formsets_place Creating table model_formsets_owner Creating table model_formsets_location Creating table model_formsets_ownerprofile Creating table model_formsets_restaurant Creating table model_formsets_product Creating table model_formsets_price Creating table model_formsets_mexicanrestaurant Creating table model_formsets_classymexicanrestaurant Creating table model_formsets_repository Creating table model_formsets_revision Creating table model_formsets_person Creating table model_formsets_membership Creating table model_formsets_team Creating table model_formsets_player Creating table model_formsets_poet Creating table model_formsets_poem Creating table model_formsets_post Creating table model_formsets_uuidpkparent Creating table model_formsets_uuidpkchild Creating table model_formsets_childwitheditablepk Creating table model_formsets_autopkchildofuuidpkparent Creating table model_formsets_autopkparent Creating table model_formsets_uuidpkchildofautopkparent Creating table model_formsets_parentwithuuidalternatekey Creating table model_formsets_childrelatedviaak Creating table multiple_database_review Creating table multiple_database_person Creating table multiple_database_book Creating table multiple_database_pet Creating table multiple_database_userprofile Creating table managers_regress_parent Creating table managers_regress_child1 Creating table managers_regress_child2 Creating table managers_regress_child3 Creating table managers_regress_child4 Creating table managers_regress_child5 Creating table managers_regress_child6 Creating table managers_regress_child7 Creating table managers_regress_relatedmodel Creating table managers_regress_relationmodel Creating table max_lengths_personwithdefaultmaxlengths Creating table max_lengths_personwithcustommaxlengths Creating table m2m_recursive_person Creating table m2m_recursive_colleague Creating table model_inheritance_worker Creating table model_inheritance_student Creating table model_inheritance_post Creating table model_inheritance_comment Creating table model_inheritance_link Creating table model_inheritance_chef Creating table model_inheritance_place Creating table my_restaurant Creating table model_inheritance_italianrestaurant Creating table model_inheritance_supplier Creating table model_inheritance_parkinglot Creating table model_inheritance_title Creating table model_inheritance_mixinmodel Creating table model_inheritance_base Creating table model_inheritance_subbase Creating table model_inheritance_grandparent Creating table model_inheritance_parent Creating table model_inheritance_child Creating table model_inheritance_grandchild Creating table custom_pk_employee Creating table custom_pk_business Creating table custom_pk_bar Creating table custom_pk_foo Creating table ordering_author Creating table ordering_article Creating table ordering_childarticle Creating table ordering_reference Creating table select_related_onetoone_user Creating table select_related_onetoone_userprofile Creating table select_related_onetoone_userstatresult Creating table select_related_onetoone_userstat Creating table select_related_onetoone_statdetails Creating table select_related_onetoone_advanceduserstat Creating table select_related_onetoone_image Creating table select_related_onetoone_product Creating table select_related_onetoone_parent1 Creating table select_related_onetoone_parent2 Creating table select_related_onetoone_child1 Creating table select_related_onetoone_child2 Creating table select_related_onetoone_child3 Creating table select_related_onetoone_child4 Creating table select_related_onetoone_linkedlist Creating table a01 Creating table b01 Creating table c01 Creating table unmanaged_models_proxy1 Creating table unmanaged_models_proxy2 Creating table unmanaged_models_managed1 Creating table admin_inlines_parent Creating table admin_inlines_teacher Creating table admin_inlines_child Creating table admin_inlines_book Creating table admin_inlines_author Creating table admin_inlines_nonautopkbook Creating table admin_inlines_nonautopkbookchild Creating table admin_inlines_editablepkbook Creating table admin_inlines_holder Creating table admin_inlines_inner Creating table admin_inlines_holder2 Creating table admin_inlines_inner2 Creating table admin_inlines_holder3 Creating table admin_inlines_inner3 Creating table admin_inlines_holder4 Creating table admin_inlines_inner4stacked Creating table admin_inlines_inner4tabular Creating table admin_inlines_holder5 Creating table admin_inlines_inner5stacked Creating table admin_inlines_inner5tabular Creating table admin_inlines_person Creating table admin_inlines_outfititem Creating table admin_inlines_fashionista Creating table admin_inlines_shoppingweakness Creating table admin_inlines_titlecollection Creating table admin_inlines_title Creating table admin_inlines_poll Creating table admin_inlines_question Creating table admin_inlines_novel Creating table admin_inlines_chapter Creating table admin_inlines_footnote Creating table admin_inlines_capofamiglia Creating table admin_inlines_consigliere Creating table admin_inlines_sottocapo Creating table admin_inlines_readonlyinline Creating table admin_inlines_parentmodelwithcustompk Creating table admin_inlines_childmodel1 Creating table admin_inlines_childmodel2 Creating table admin_inlines_binarytree Creating table admin_inlines_lifeform Creating table admin_inlines_extraterrestrial Creating table admin_inlines_sighting Creating table admin_inlines_someparentmodel Creating table admin_inlines_somechildmodel Creating table admin_inlines_profilecollection Creating table admin_inlines_profile Creating table get_earliest_or_latest_article Creating table get_earliest_or_latest_person Creating table get_earliest_or_latest_indexerrorarticle Creating table timezones_event Creating table timezones_maybeevent Creating table timezones_session Creating table timezones_sessionevent Creating table timezones_timestamp Creating table timezones_alldayevent Creating table proxy_model_inheritance_concretemodel Creating table proxy_model_inheritance_concretemodelsubclass Creating table check_framework_simplemodel Creating table generic_relations_regress_link Creating table generic_relations_regress_place Creating table generic_relations_regress_restaurant Creating table generic_relations_regress_cafe Creating table generic_relations_regress_address Creating table generic_relations_regress_person Creating table generic_relations_regress_charlink Creating table generic_relations_regress_textlink Creating table generic_relations_regress_oddrelation1 Creating table generic_relations_regress_oddrelation2 Creating table generic_relations_regress_note Creating table generic_relations_regress_contact Creating table generic_relations_regress_organization Creating table generic_relations_regress_company Creating table generic_relations_regress_developer Creating table generic_relations_regress_team Creating table generic_relations_regress_guild Creating table generic_relations_regress_tag Creating table generic_relations_regress_board Creating table generic_relations_regress_haslinkthing Creating table generic_relations_regress_a Creating table generic_relations_regress_b Creating table generic_relations_regress_c Creating table generic_relations_regress_d Creating table generic_relations_regress_node Creating table generic_relations_regress_content Creating table generic_relations_regress_related Creating table file_uploads_filemodel Creating table modeladmin_band Creating table modeladmin_song Creating table modeladmin_concert Creating table modeladmin_validationtestmodel Creating table modeladmin_validationtestinlinemodel Creating table expressions_window_classification Creating table expressions_window_employee Creating table expressions_window_detail Creating table proxy_models_person Creating table proxy_models_statusperson Creating table proxy_models_lowerstatusperson Creating table proxy_models_user Creating table proxy_models_country Creating table proxy_models_state Creating table proxy_models_baseuser Creating table proxy_models_trackeruser Creating table proxy_models_issue Creating table proxy_models_bug Creating table proxy_models_improvement Creating table model_inheritance_regress_place Creating table model_inheritance_regress_restaurant Creating table model_inheritance_regress_italianrestaurant Creating table model_inheritance_regress_parkinglot Creating table model_inheritance_regress_parkinglot3 Creating table model_inheritance_regress_parkinglot4a Creating table model_inheritance_regress_parkinglot4b Creating table model_inheritance_regress_supplier Creating table model_inheritance_regress_wholesaler Creating table model_inheritance_regress_parent Creating table model_inheritance_regress_child Creating table model_inheritance_regress_selfrefparent Creating table model_inheritance_regress_selfrefchild Creating table model_inheritance_regress_article Creating table model_inheritance_regress_articlewithauthor Creating table model_inheritance_regress_m2mbase Creating table model_inheritance_regress_m2mchild Creating table model_inheritance_regress_qualitycontrol Creating table model_inheritance_regress_basem Creating table model_inheritance_regress_derivedm Creating table model_inheritance_regress_internalcertificationaudit Creating table model_inheritance_regress_person Creating table model_inheritance_regress_birthdayparty Creating table model_inheritance_regress_bachelorparty Creating table model_inheritance_regress_messybachelorparty Creating table model_inheritance_regress_searchablelocation Creating table model_inheritance_regress_busstation Creating table model_inheritance_regress_trainstation Creating table model_inheritance_regress_user Creating table model_inheritance_regress_profile Creating table model_inheritance_regress_politician Creating table model_inheritance_regress_congressman Creating table model_inheritance_regress_senator Creating table get_object_or_404_author Creating table get_object_or_404_article Creating table generic_views_artist Creating table generic_views_author Creating table generic_views_book Creating table generic_views_page Creating table generic_views_booksigning Creating table contenttypes_tests_site Creating table contenttypes_tests_author Creating table contenttypes_tests_article Creating table contenttypes_tests_schemeincludedurl Creating table contenttypes_tests_concretemodel Creating table contenttypes_tests_foowithouturl Creating table contenttypes_tests_foowithurl Creating table contenttypes_tests_foowithbrokenabsoluteurl Creating table contenttypes_tests_question Creating table contenttypes_tests_answer Creating table contenttypes_tests_post Creating table contenttypes_tests_modelwithnullfktosite Creating table contenttypes_tests_modelwithm2mtosite Creating table file_storage_storage Creating table async_simplemodel Creating table admin_autodiscover_story Creating table select_related_regress_building Creating table select_related_regress_device Creating table select_related_regress_port Creating table select_related_regress_connection Creating table select_related_regress_tuser Creating table select_related_regress_person Creating table select_related_regress_organizer Creating table select_related_regress_student Creating table select_related_regress_class Creating table select_related_regress_enrollment Creating table select_related_regress_country Creating table select_related_regress_state Creating table select_related_regress_clientstatus Creating table select_related_regress_client Creating table select_related_regress_specialclient Creating table select_related_regress_parent Creating table select_related_regress_child Creating table select_related_regress_item Creating table select_related_regress_fowl Creating table select_related_regress_hen Creating table select_related_regress_chick Creating table select_related_regress_a Creating table select_related_regress_b Creating table select_related_regress_c Creating table signals_person Creating table signals_car Creating table signals_author Creating table signals_book Creating table fixtures_regress_animal Creating table Fixtures_regress_plant Creating table fixtures_regress_stuff Creating table fixtures_regress_absolute Creating table fixtures_regress_parent Creating table fixtures_regress_child Creating table fixtures_regress_channel Creating table fixtures_regress_article Creating table fixtures_regress_specialarticle Creating table fixtures_regress_feature Creating table fixtures_regress_widget Creating table fixtures_regress_store Creating table fixtures_regress_person Creating table fixtures_regress_book Creating table fixtures_regress_nkchild Creating table fixtures_regress_reftonkchild Creating table fixtures_regress_circle1 Creating table fixtures_regress_circle2 Creating table fixtures_regress_circle3 Creating table fixtures_regress_circle4 Creating table fixtures_regress_circle5 Creating table fixtures_regress_circle6 Creating table fixtures_regress_externaldependency Creating table fixtures_regress_thingy Creating table fixtures_regress_m2mtoself Creating table fixtures_regress_m2msimplea Creating table fixtures_regress_m2msimpleb Creating table fixtures_regress_m2msimplecirculara Creating table fixtures_regress_m2msimplecircularb Creating table fixtures_regress_m2mcomplexa Creating table fixtures_regress_m2mcomplexb Creating table fixtures_regress_m2mthroughab Creating table fixtures_regress_m2mcomplexcircular1a Creating table fixtures_regress_m2mcomplexcircular1b Creating table fixtures_regress_m2mcomplexcircular1c Creating table fixtures_regress_m2mcircular1throughab Creating table fixtures_regress_m2mcircular1throughbc Creating table fixtures_regress_m2mcircular1throughca Creating table fixtures_regress_m2mcomplexcircular2a Creating table fixtures_regress_m2mcomplexcircular2b Creating table fixtures_regress_m2mcircular2throughab Creating table string_lookup_foo Creating table string_lookup_bar Creating table string_lookup_whiz Creating table string_lookup_child Creating table string_lookup_base Creating table string_lookup_article Creating table delete_regress_award Creating table delete_regress_awardnote Creating table delete_regress_person Creating table delete_regress_book Creating table delete_regress_toy Creating table delete_regress_child Creating table delete_regress_playedwith Creating table delete_regress_playedwithnote Creating table delete_regress_contact Creating table delete_regress_email Creating table delete_regress_researcher Creating table delete_regress_food Creating table delete_regress_eaten Creating table delete_regress_policy Creating table delete_regress_version Creating table delete_regress_location Creating table delete_regress_item Creating table delete_regress_file Creating table delete_regress_fooimage Creating table delete_regress_foofile Creating table delete_regress_foophoto Creating table delete_regress_orgunit Creating table delete_regress_login Creating table delete_regress_house Creating table delete_regress_orderedperson Creating table sessions_tests_customsession Creating table pagination_article Creating table select Creating table custom_methods_article Creating table nested_foreign_keys_person Creating table nested_foreign_keys_movie Creating table nested_foreign_keys_event Creating table nested_foreign_keys_screening Creating table nested_foreign_keys_screeningnullfk Creating table nested_foreign_keys_package Creating table nested_foreign_keys_packagenullfk Creating table many_to_one_null_reporter Creating table many_to_one_null_article Creating table many_to_one_null_car Creating table many_to_one_null_driver Creating table update_datapoint Creating table update_relatedpoint Creating table update_a Creating table update_b Creating table update_c Creating table update_d Creating table update_foo Creating table update_bar Creating table update_uniquenumber Creating table update_uniquenumberchild Creating table admin_checks_album Creating table admin_checks_song Creating table admin_checks_twoalbumfkandane Creating table admin_checks_author Creating table admin_checks_book Creating table admin_checks_authorsbooks Creating table admin_checks_state Creating table admin_checks_city Creating table admin_checks_influence Creating table force_insert_update_counter Creating table force_insert_update_inheritedcounter Creating table force_insert_update_subcounter Creating table force_insert_update_withcustompk Creating table transactions_reporter Creating table m2m_regress_selfrefer Creating table m2m_regress_tag Creating table m2m_regress_tagcollection Creating table m2m_regress_entry Creating table m2m_regress_selfreferchild Creating table m2m_regress_selfreferchildsibling Creating table m2m_regress_line Creating table m2m_regress_worksheet Creating table m2m_regress_user Creating table m2m_regress_regressionmodelsplit Creating table m2m_regress_post Creating table m2m_multiple_category Creating table m2m_multiple_article Creating table mutually_referential_parent Creating table mutually_referential_child Creating table lookup_alarm Creating table lookup_author Creating table lookup_article Creating table lookup_tag Creating table lookup_season Creating table lookup_game Creating table lookup_player Creating table lookup_product Creating table lookup_stock Creating table lookup_freebie Creating table datatypes_donut Creating table datatypes_rumbaba Creating table queries_dumbcategory Creating table queries_namedcategory Creating table queries_tag Creating table queries_note Creating table queries_annotation Creating table queries_datetimepk Creating table queries_extrainfo Creating table queries_author Creating table queries_item Creating table queries_report Creating table queries_reportcomment Creating table queries_ranking Creating table queries_cover Creating table queries_number Creating table queries_valid Creating table queries_x Creating table queries_y Creating table queries_loopx Creating table queries_loopy Creating table queries_loopz Creating table queries_managedmodel Creating table queries_detail Creating table queries_member Creating table queries_child Creating table queries_custompk Creating table queries_related Creating table queries_custompktag Creating table queries_celebrity Creating table queries_tvchef Creating table queries_fan Creating table queries_leafa Creating table queries_leafb Creating table queries_join Creating table queries_reservedname Creating table queries_sharedconnection Creating table queries_pointera Creating table queries_pointerb Creating table queries_singleobject Creating table queries_relatedobject Creating table queries_plaything Creating table queries_article Creating table queries_food Creating table queries_eaten Creating table queries_node Creating table queries_objecta Creating table queries_childobjecta Creating table queries_objectb Creating table queries_objectc Creating table queries_simplecategory Creating table queries_specialcategory Creating table queries_categoryitem Creating table queries_mixedcasefieldcategoryitem Creating table queries_mixedcasedbcolumncategoryitem Creating table queries_onetoonecategory Creating table queries_categoryrelationship Creating table queries_commonmixedcaseforeignkeys Creating table queries_nullablename Creating table queries_modeld Creating table queries_modelc Creating table queries_modelb Creating table queries_modela Creating table queries_job Creating table queries_jobresponsibilities Creating table queries_responsibility Creating table queries_fk1 Creating table queries_fk2 Creating table queries_fk3 Creating table queries_basea Creating table queries_identifier Creating table queries_program Creating table queries_channel Creating table queries_book Creating table queries_chapter Creating table queries_paragraph Creating table queries_page Creating table queries_myobject Creating table queries_order Creating table queries_orderitem Creating table queries_baseuser Creating table queries_task Creating table queries_staff Creating table queries_staffuser Creating table queries_ticket21203parent Creating table queries_ticket21203child Creating table queries_person Creating table queries_company Creating table queries_employment Creating table queries_school Creating table queries_student Creating table queries_classroom Creating table queries_teacher Creating table queries_ticket23605aparent Creating table queries_ticket23605a Creating table queries_ticket23605b Creating table queries_ticket23605c Creating table Individual Creating table RelatedIndividual Creating table queries_customdbcolumn Creating table queries_returningmodel Creating table queries_nonintegerpkreturningmodel Creating table queries_jsonfieldnullable Creating table apps_totallynormal Creating table syndication_tests_entry Creating table syndication_tests_article Running deferred SQL... Running migrations: Applying admin.0001_initial... OK Applying admin.0002_logentry_remove_auto_add... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying db_functions.0001_setup_extensions... OK Applying db_functions.0002_create_test_models... OK Applying sites.0001_initial... OK Applying flatpages.0001_initial... OK Applying migration_test_data_persistence.0001_initial... OK Applying migration_test_data_persistence.0002_add_book... OK Applying postgres_tests.0001_setup_extensions... OK Applying postgres_tests.0002_create_test_models... OK Applying redirects.0001_initial... OK Applying redirects.0002_alter_redirect_new_path_help_text... OK Applying sites.0002_alter_domain_unique... OK Applying sites_framework.0001_initial... OK Cloning test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Cloning test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Cloning test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Cloning test database for alias 'default' ('file:memorydb_default?mode=memory&cache=shared')... Creating test database for alias 'other' ('file:memorydb_other?mode=memory&cache=shared')... Operations to perform: Synchronize unmigrated apps: absolute_url_overrides, admin_autodiscover, admin_changelist, admin_checks, admin_custom_urls, admin_default_site, admin_docs, admin_filters, admin_inlines, admin_ordering, admin_registration, admin_scripts, admin_utils, admin_views, admin_widgets, aggregation, aggregation_regress, annotations, app_loading, apps, asgi, async, auth, auth_tests, backends, base, bash_completion, basic, builtin_server, bulk_create, cache, check_framework, conditional_processing, constraints, contenttypes, contenttypes_tests, context_processors, csrf_tests, custom_columns, custom_lookups, custom_managers, custom_methods, custom_migration_operations, custom_pk, datatypes, dates, datetimes, db_typecasts, db_utils, dbshell, decorators, defer, defer_regress, delete, delete_regress, deprecation, dispatch, distinct_on_fields, empty, empty_models, expressions, expressions_case, expressions_window, extra_regress, field_deconstruction, field_defaults, field_subclassing, file_storage, file_uploads, files, filtered_relation, fixtures, fixtures_model_package, fixtures_regress, flatpages_tests, force_insert_update, foreign_object, forms_tests, from_db_value, generic_inline_admin, generic_relations, generic_relations_regress, generic_views, get_earliest_or_latest, get_object_or_404, get_or_create, handlers, httpwrappers, humanize_tests, i18n, indexes, inline_formsets, inspectdb, introspection, invalid_models_tests, known_related_objects, logging_tests, lookup, m2m_and_m2o, m2m_intermediary, m2m_multiple, m2m_recursive, m2m_regress, m2m_signals, m2m_through, m2m_through_regress, m2o_recursive, mail, managers_regress, many_to_many, many_to_one, many_to_one_null, max_lengths, messages, messages_tests, middleware, middleware_exceptions, migrate_signals, migrations, migrations2, model_enums, model_fields, model_forms, model_formsets, model_formsets_regress, model_indexes, model_inheritance, model_inheritance_regress, model_meta, model_options, model_package, model_regress, model_utils, modeladmin, multiple_database, mutually_referential, nested_foreign_keys, no_models, null_fk, null_fk_ordering, null_queries, one_to_one, or_lookups, order_with_respect_to, ordering, pagination, prefetch_related, project_template, properties, proxy_model_inheritance, proxy_models, queries, queryset_pickle, raw_query, redirects_tests, requests, reserved_names, resolve_url, responses, reverse_lookup, save_delete_hooks, schema, select_for_update, select_related, select_related_onetoone, select_related_regress, serializers, servers, sessions, sessions_tests, settings_tests, shell, shortcuts, signals, signed_cookies_tests, signing, sitemaps_tests, sites_tests, staticfiles, staticfiles_tests, str, string_lookup, swappable_models, syndication_tests, template_backends, template_loader, template_tests, test_client, test_client_regress, test_exceptions, test_runner, test_utils, timezones, transaction_hooks, transactions, unmanaged_models, update, update_only_fields, urlpatterns, urlpatterns_reverse, user_commands, utils_tests, validation, validators, version, view_tests, wsgi Apply all migrations: admin, db_functions, flatpages, migration_test_data_persistence, postgres_tests, redirects, sites, sites_framework Synchronizing apps without migrations: Creating tables... Creating table django_content_type Creating table auth_permission Creating table auth_group Creating table auth_user Creating table django_session Creating table from_db_value_cashmodel Creating table migrations_modelwithcustombase Creating table migrations_unmigratedmodel Creating table utils_tests_category Creating table utils_tests_categoryinfo Creating table m2m_through_regress_membership Creating table m2m_through_regress_usermembership Creating table m2m_through_regress_person Creating table m2m_through_regress_group Creating table m2m_through_regress_car Creating table m2m_through_regress_driver Creating table m2m_through_regress_cardriver Creating table m2m_through_regress_event Creating table m2m_through_regress_competitor Creating table m2m_through_regress_individualcompetitor Creating table m2m_through_regress_competingteam Creating table select_related_domain Creating table select_related_kingdom Creating table select_related_phylum Creating table select_related_klass Creating table select_related_order Creating table select_related_family Creating table select_related_genus Creating table select_related_species Creating table select_related_hybridspecies Creating table select_related_topping Creating table select_related_pizza Creating table select_related_taggeditem Creating table select_related_bookmark Creating table m2m_through_person Creating table m2m_through_personchild Creating table m2m_through_group Creating table m2m_through_membership Creating table test_table Creating table m2m_through_testnodefaultsornulls Creating table m2m_through_personselfrefm2m Creating table m2m_through_friendship Creating table m2m_through_symmetricalfriendship Creating table m2m_through_event Creating table m2m_through_invitation Creating table m2m_through_employee Creating table m2m_through_relationship Creating table m2m_through_ingredient Creating table m2m_through_recipe Creating table m2m_through_recipeingredient Creating table aggregation_regress_author Creating table aggregation_regress_publisher Creating table aggregation_regress_itemtag Creating table aggregation_regress_book Creating table aggregation_regress_store Creating table aggregation_regress_entries Creating table aggregation_regress_clues Creating table aggregation_regress_withmanualpk Creating table aggregation_regress_hardbackbook Creating table aggregation_regress_alfa Creating table aggregation_regress_bravo Creating table aggregation_regress_charlie Creating table aggregation_regress_selfreffk Creating table model_forms_person Creating table model_forms_category Creating table model_forms_writer Creating table model_forms_article Creating table model_forms_improvedarticle Creating table model_forms_improvedarticlewithparentlink Creating table model_forms_betterwriter Creating table model_forms_publication Creating table model_forms_publicationdefaults Creating table model_forms_author Creating table model_forms_author1 Creating table model_forms_writerprofile Creating table model_forms_document Creating table model_forms_textfile Creating table model_forms_customff Creating table model_forms_filepathmodel Creating table model_forms_imagefile Creating table model_forms_optionalimagefile Creating table model_forms_noextensionimagefile Creating table model_forms_homepage Creating table model_forms_product Creating table model_forms_price Creating table model_forms_triple Creating table model_forms_articlestatus Creating table model_forms_inventory Creating table model_forms_book Creating table model_forms_derivedbook Creating table model_forms_explicitpk Creating table model_forms_post Creating table model_forms_datetimepost Creating table model_forms_derivedpost Creating table model_forms_bigint Creating table model_forms_customfieldforexclusionmodel Creating table model_forms_flexibledatepost Creating table model_forms_colour Creating table model_forms_colourfulitem Creating table model_forms_customerrormessage Creating table model_forms_character Creating table model_forms_stumpjoke Creating table model_forms_student Creating table model_forms_photo Creating table model_forms_uuidpk Creating table model_forms_strictassignmentfieldspecific Creating table model_forms_strictassignmentall Creating table model_forms_award Creating table model_forms_nullableuniquecharfieldmodel Creating table serializers_categorymetadata Creating table serializers_category Creating table serializers_author Creating table serializers_article Creating table serializers_authorprofile Creating table serializers_actor Creating table serializers_movie Creating table serializers_score Creating table serializers_player Creating table serializers_basemodel Creating table serializers_complexmodel Creating table serializers_binarydata Creating table serializers_booleandata Creating table serializers_chardata Creating table serializers_datedata Creating table serializers_datetimedata Creating table serializers_decimaldata Creating table serializers_emaildata Creating table serializers_filedata Creating table serializers_filepathdata Creating table serializers_floatdata Creating table serializers_integerdata Creating table serializers_bigintegerdata Creating table serializers_genericipaddressdata Creating table serializers_nullbooleandata Creating table serializers_positivebigintegerdata Creating table serializers_positiveintegerdata Creating table serializers_positivesmallintegerdata Creating table serializers_slugdata Creating table serializers_smalldata Creating table serializers_textdata Creating table serializers_timedata Creating table serializers_tag Creating table serializers_genericdata Creating table serializers_anchor Creating table serializers_uniqueanchor Creating table serializers_fkdata Creating table serializers_m2mdata Creating table serializers_o2odata Creating table serializers_fkselfdata Creating table serializers_m2mselfdata Creating table serializers_fkdatatofield Creating table serializers_fkdatatoo2o Creating table serializers_m2mintermediatedata Creating table serializers_intermediate Creating table serializers_booleanpkdata Creating table serializers_charpkdata Creating table serializers_datepkdata Creating table serializers_datetimepkdata Creating table serializers_decimalpkdata Creating table serializers_emailpkdata Creating table serializers_filepathpkdata Creating table serializers_floatpkdata Creating table serializers_integerpkdata Creating table serializers_genericipaddresspkdata Creating table serializers_positiveintegerpkdata Creating table serializers_positivesmallintegerpkdata Creating table serializers_slugpkdata Creating table serializers_smallpkdata Creating table serializers_uuiddata Creating table serializers_uuiddefaultdata Creating table serializers_fktouuid Creating table serializers_autonowdatetimedata Creating table serializers_modifyingsavedata Creating table serializers_inheritabstractmodel Creating table serializers_inheritbasemodel Creating table serializers_explicitinheritbasemodel Creating table serializers_lengthmodel Creating table serializers_parent Creating table serializers_child Creating table serializers_naturalkeyanchor Creating table serializers_fkdatanaturalkey Creating table serializers_naturalkeything Creating table serializers_naturalpkwithdefault Creating table serializers_fkaspknonaturalkey Creating table str_internationalarticle Creating table or_lookups_article Creating table fixtures_category Creating table fixtures_article Creating table fixtures_blog Creating table fixtures_tag Creating table fixtures_person Creating table fixtures_spy Creating table fixtures_visa Creating table fixtures_book Creating table fixtures_primarykeyuuidmodel Creating table fixtures_naturalkeything Creating table fixtures_circulara Creating table fixtures_circularb Creating table properties_person Creating table m2m_signals_part Creating table m2m_signals_car Creating table m2m_signals_sportscar Creating table m2m_signals_person Creating table extra_regress_revisionablemodel Creating table extra_regress_order Creating table extra_regress_testobject Creating table test_runner_person Creating table test_runner_throughbase Creating table test_runner_through Creating table test_runner_b Creating table model_options_author Creating table model_options_editor Creating table model_options_book Creating table model_options_bookstore Creating table model_options_editorstore Creating table model_options_scientistref Creating table model_options_articleref Creating table admin_registration_person Creating table admin_registration_traveler Creating table admin_registration_place Creating table m2o_recursive_category Creating table m2o_recursive_person Creating table get_or_create_person Creating table get_or_create_defaultperson Creating table get_or_create_manualprimarykeytest Creating table get_or_create_profile Creating table get_or_create_tag Creating table get_or_create_thing Creating table get_or_create_publisher Creating table get_or_create_author Creating table get_or_create_book Creating table annotations_author Creating table annotations_publisher Creating table annotations_book Creating table annotations_store Creating table annotations_departmentstore Creating table annotations_employee Creating table annotations_company Creating table annotations_ticket Creating table backends_square Creating table backends_person Creating table backends_schoolclass Creating table backends_verylongmodelnamezzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz Creating table backends_tag Creating table CaseSensitive_Post Creating table backends_reporter Creating table backends_article Creating table backends_item Creating table backends_object Creating table backends_objectreference Creating table backends_objectselfreference Creating table backends_circulara Creating table backends_circularb Creating table backends_rawdata Creating table backends_author Creating table backends_book Creating table order Creating table null_queries_poll Creating table null_queries_choice Creating table null_queries_outera Creating table null_queries_outerb Creating table null_queries_inner Creating table reverse_lookup_user Creating table reverse_lookup_poll Creating table reverse_lookup_choice Creating table update_only_fields_account Creating table update_only_fields_person Creating table update_only_fields_employee Creating table update_only_fields_profile Creating table inspectdb_people Creating table inspectdb_message Creating table inspectdb_peopledata Creating table inspectdb_peoplemoredata Creating table inspectdb_digitsincolumnname Creating table inspectdb_special.table name Creating table inspectdb_columntypes Creating table inspectdb_jsonfieldcolumntype Creating table inspectdb_charfielddbcollation Creating table inspectdb_textfielddbcollation Creating table inspectdb_uniquetogether Creating table defer_regress_item Creating table defer_regress_relateditem Creating table defer_regress_child Creating table defer_regress_leaf Creating table defer_regress_resolvethis Creating table defer_regress_simpleitem Creating table defer_regress_feature Creating table defer_regress_specialfeature Creating table defer_regress_onetooneitem Creating table defer_regress_itemandsimpleitem Creating table defer_regress_profile Creating table defer_regress_location Creating table defer_regress_request Creating table defer_regress_base Creating table defer_regress_derived Creating table my_author_table Creating table custom_columns_article Creating table admin_changelist_event Creating table admin_changelist_parent Creating table admin_changelist_child Creating table admin_changelist_genre Creating table admin_changelist_band Creating table admin_changelist_musician Creating table admin_changelist_group Creating table admin_changelist_concert Creating table admin_changelist_membership Creating table admin_changelist_quartet Creating table admin_changelist_chordsmusician Creating table admin_changelist_chordsband Creating table admin_changelist_invitation Creating table admin_changelist_swallow Creating table admin_changelist_swallowonetoone Creating table admin_changelist_unorderedobject Creating table admin_changelist_orderedobject Creating table admin_changelist_customiduser Creating table admin_changelist_charpk Creating table model_package_site Creating table model_package_article Creating table model_package_publication Creating table model_package_advertisement Creating table admin_utils_site Creating table admin_utils_article Creating table admin_utils_count Creating table admin_utils_event Creating table admin_utils_location Creating table admin_utils_guest Creating table admin_utils_eventguide Creating table admin_utils_vehicle Creating table admin_utils_car Creating table admin_docs_company Creating table admin_docs_group Creating table admin_docs_family Creating table admin_docs_person Creating table empty_empty Creating table datetimes_article Creating table datetimes_comment Creating table datetimes_category Creating table bulk_create_country Creating table bulk_create_proxymulticountry Creating table bulk_create_restaurant Creating table bulk_create_pizzeria Creating table bulk_create_state Creating table bulk_create_twofields Creating table bulk_create_nofields Creating table bulk_create_smallautofieldmodel Creating table bulk_create_bigautofieldmodel Creating table bulk_create_nullablefields Creating table model_meta_relation Creating table model_meta_baseperson Creating table model_meta_person Creating table model_meta_personthroughproxysubclass Creating table model_meta_relating Creating table model_meta_commonancestor Creating table model_meta_firstparent Creating table model_meta_secondparent Creating table model_meta_child Creating table dates_article Creating table dates_comment Creating table dates_category Creating table aggregation_author Creating table aggregation_publisher Creating table aggregation_book Creating table aggregation_store Creating table admin_ordering_band Creating table admin_ordering_song Creating table field_defaults_article Creating table model_fields_foo Creating table model_fields_bar Creating table model_fields_whiz Creating table model_fields_whizdelayed Creating table model_fields_whiziter Creating table model_fields_whiziterempty Creating table model_fields_choiceful Creating table model_fields_bigd Creating table model_fields_floatmodel Creating table model_fields_bigs Creating table model_fields_unicodeslugfield Creating table model_fields_automodel Creating table model_fields_bigautomodel Creating table model_fields_smallautomodel Creating table model_fields_smallintegermodel Creating table model_fields_integermodel Creating table model_fields_bigintegermodel Creating table model_fields_positivebigintegermodel Creating table model_fields_positivesmallintegermodel Creating table model_fields_positiveintegermodel Creating table model_fields_post Creating table model_fields_nullbooleanmodel Creating table model_fields_booleanmodel Creating table model_fields_datetimemodel Creating table model_fields_durationmodel Creating table model_fields_nulldurationmodel Creating table model_fields_primarykeycharmodel Creating table model_fields_fkstobooleans Creating table model_fields_fktochar Creating table model_fields_renamedfield Creating table model_fields_verbosenamefield Creating table model_fields_genericipaddress Creating table model_fields_decimallessthanone Creating table model_fields_fieldclassattributemodel Creating table model_fields_datamodel Creating table model_fields_document Creating table model_fields_person Creating table model_fields_personwithheight Creating table model_fields_personwithheightandwidth Creating table model_fields_persondimensionsfirst Creating table model_fields_persontwoimages Creating table model_fields_jsonmodel Creating table model_fields_nullablejsonmodel Creating table model_fields_relatedjsonmodel Creating table model_fields_allfieldsmodel Creating table model_fields_manytomany Creating table model_fields_uuidmodel Creating table model_fields_nullableuuidmodel Creating table model_fields_primarykeyuuidmodel Creating table model_fields_relatedtouuidmodel Creating table model_fields_uuidchild Creating table model_fields_uuidgrandchild Creating table expressions_manager Creating table expressions_employee Creating table expressions_remoteemployee Creating table expressions_company Creating table expressions_number Creating table expressions_ExPeRiMeNt Creating table expressions_result Creating table expressions_time Creating table expressions_simulationrun Creating table expressions_uuidpk Creating table expressions_uuid Creating table indexes_articletranslation Creating table indexes_article Creating table indexes_indextogethersinglelist Creating table indexes_indexedarticle Creating table indexes_indexedarticle2 Creating table model_indexes_book Creating table model_indexes_childmodel1 Creating table model_indexes_childmodel2 Creating table raw_query_author Creating table raw_query_book Creating table raw_query_bookfkaspk Creating table raw_query_coffee Creating table raw_query_mixedcaseidcolumn Creating table raw_query_reviewer Creating table raw_query_friendlyauthor Creating table prefetch_related_author Creating table prefetch_related_authorwithage Creating table prefetch_related_favoriteauthors Creating table prefetch_related_authoraddress Creating table prefetch_related_book Creating table prefetch_related_bookwithyear Creating table prefetch_related_bio Creating table prefetch_related_reader Creating table prefetch_related_bookreview Creating table prefetch_related_qualification Creating table prefetch_related_teacher Creating table prefetch_related_department Creating table prefetch_related_taggeditem Creating table prefetch_related_article Creating table prefetch_related_bookmark Creating table prefetch_related_comment Creating table prefetch_related_house Creating table prefetch_related_room Creating table prefetch_related_person Creating table prefetch_related_employee Creating table prefetch_related_lessonentry Creating table prefetch_related_wordentry Creating table prefetch_related_author2 Creating table prefetch_related_pet Creating table prefetch_related_flea Creating table admin_filters_book Creating table admin_filters_improvedbook Creating table admin_filters_department Creating table admin_filters_employee Creating table admin_filters_taggeditem Creating table admin_filters_bookmark Creating table swappable_models_article Creating table swappable_models_alternatearticle Creating table null_fk_systemdetails Creating table null_fk_systeminfo Creating table null_fk_forum Creating table null_fk_post Creating table null_fk_comment Creating table null_fk_item Creating table null_fk_propertyvalue Creating table null_fk_property Creating table introspection_city Creating table introspection_country Creating table introspection_district Creating table introspection_reporter Creating table introspection_article Creating table introspection_comment Creating table introspection_checkconstraintmodel Creating table introspection_uniqueconstraintconditionmodel Creating table generic_relations_taggeditem Creating table generic_relations_valuabletaggeditem Creating table generic_relations_abstractcomparison Creating table generic_relations_comparison Creating table generic_relations_animal Creating table generic_relations_vegetable Creating table generic_relations_carrot Creating table generic_relations_mineral Creating table generic_relations_gecko Creating table generic_relations_rock Creating table generic_relations_valuablerock Creating table generic_relations_manualpk Creating table generic_relations_forproxymodelmodel Creating table generic_relations_forconcretemodelmodel Creating table generic_relations_concreterelatedmodel Creating table generic_relations_allowsnullgfk Creating table generic_inline_admin_episode Creating table generic_inline_admin_media Creating table generic_inline_admin_category Creating table generic_inline_admin_phonenumber Creating table generic_inline_admin_contact Creating table generic_inline_admin_episodepermanent Creating table distinct_on_fields_tag Creating table distinct_on_fields_celebrity Creating table distinct_on_fields_fan Creating table distinct_on_fields_staff Creating table distinct_on_fields_stafftag Creating table servers_person Creating table null_fk_ordering_author Creating table null_fk_ordering_article Creating table null_fk_ordering_systeminfo Creating table null_fk_ordering_forum Creating table null_fk_ordering_post Creating table null_fk_ordering_comment Creating table model_formsets_regress_user Creating table model_formsets_regress_usersite Creating table model_formsets_regress_userprofile Creating table model_formsets_regress_userpreferences Creating table model_formsets_regress_profilenetwork Creating table model_formsets_regress_place Creating table model_formsets_regress_restaurant Creating table model_formsets_regress_manager Creating table model_formsets_regress_network Creating table model_formsets_regress_host Creating table defer_secondary Creating table defer_primary Creating table defer_child Creating table defer_bigchild Creating table order_with_respect_to_question Creating table order_with_respect_to_answer Creating table order_with_respect_to_post Creating table order_with_respect_to_entity Creating table order_with_respect_to_dimension Creating table order_with_respect_to_component Creating table sitemaps_tests_testmodel Creating table sitemaps_tests_i18ntestmodel Creating table admin_views_section Creating table admin_views_article Creating table admin_views_book Creating table admin_views_promo Creating table admin_views_chapter Creating table admin_views_chapterxtra1 Creating table admin_views_chapterxtra2 Creating table admin_views_rowlevelchangepermissionmodel Creating table admin_views_customarticle Creating table admin_views_modelwithstringprimarykey Creating table admin_views_color Creating table admin_views_thing Creating table admin_views_actor Creating table admin_views_inquisition Creating table admin_views_sketch Creating table admin_views_character Creating table admin_views_stumpjoke Creating table admin_views_fabric Creating table admin_views_person Creating table admin_views_persona Creating table admin_views_account Creating table admin_views_fooaccount Creating table admin_views_baraccount Creating table admin_views_subscriber Creating table admin_views_externalsubscriber Creating table admin_views_oldsubscriber Creating table admin_views_media Creating table admin_views_podcast Creating table admin_views_vodcast Creating table admin_views_parent Creating table admin_views_child Creating table admin_views_pkchild Creating table admin_views_toy Creating table admin_views_emptymodel Creating table admin_views_gallery Creating table admin_views_picture Creating table admin_views_language Creating table admin_views_title Creating table admin_views_titletranslation Creating table admin_views_recommender Creating table admin_views_recommendation Creating table admin_views_collector Creating table admin_views_widget Creating table admin_views_doohickey Creating table admin_views_grommet Creating table admin_views_whatsit Creating table admin_views_doodad Creating table admin_views_fancydoodad Creating table admin_views_category Creating table admin_views_link Creating table admin_views_prepopulatedpost Creating table admin_views_prepopulatedsubpost Creating table admin_views_post Creating table admin_views_gadget Creating table admin_views_villain Creating table admin_views_supervillain Creating table admin_views_funkytag Creating table admin_views_plot Creating table admin_views_plotdetails Creating table admin_views_secrethideout Creating table admin_views_supersecrethideout Creating table admin_views_bookmark Creating table admin_views_cyclicone Creating table admin_views_cyclictwo Creating table admin_views_topping Creating table admin_views_pizza Creating table admin_views_album Creating table admin_views_song Creating table admin_views_employee Creating table admin_views_workhour Creating table admin_views_manager Creating table admin_views_bonus Creating table admin_views_question Creating table admin_views_answer Creating table admin_views_reservation Creating table admin_views_fooddelivery Creating table admin_views_coverletter Creating table admin_views_paper Creating table admin_views_shortmessage Creating table admin_views_telegram Creating table admin_views_story Creating table admin_views_otherstory Creating table admin_views_complexsortedperson Creating table admin_views_pluggablesearchperson Creating table admin_views_prepopulatedpostlargeslug Creating table admin_views_adminorderedfield Creating table admin_views_adminorderedmodelmethod Creating table admin_views_adminorderedadminmethod Creating table admin_views_adminorderedcallable Creating table admin_views_report Creating table admin_views_mainprepopulated Creating table admin_views_relatedprepopulated Creating table admin_views_unorderedobject Creating table admin_views_undeletableobject Creating table admin_views_unchangeableobject Creating table admin_views_usermessenger Creating table admin_views_simple Creating table admin_views_choice Creating table admin_views_parentwithdependentchildren Creating table admin_views_dependentchild Creating table admin_views_filteredmanager Creating table admin_views_emptymodelvisible Creating table admin_views_emptymodelhidden Creating table admin_views_emptymodelmixin Creating table admin_views_state Creating table admin_views_city Creating table admin_views_restaurant Creating table admin_views_worker Creating table admin_views_referencedbyparent Creating table admin_views_parentwithfk Creating table admin_views_childofreferer Creating table admin_views_inlinereferer Creating table admin_views_referencedbyinline Creating table admin_views_inlinereference Creating table admin_views_recipe Creating table admin_views_ingredient Creating table admin_views_recipeingredient Creating table admin_views_notreferenced Creating table admin_views_explicitlyprovidedpk Creating table admin_views_implicitlygeneratedpk Creating table admin_views_referencedbygenrel Creating table admin_views_genrelreference Creating table admin_views_parentwithuuidpk Creating table admin_views_relatedwithuuidpkmodel Creating table admin_views_author Creating table admin_views_authorship Creating table admin_views_readonlyrelatedfield Creating table validation_modeltovalidate Creating table validation_uniquefieldsmodel Creating table validation_custompkmodel Creating table validation_uniquetogethermodel Creating table validation_uniquefordatemodel Creating table validation_custommessagesmodel Creating table validation_author Creating table validation_article Creating table validation_post Creating table validation_flexibledatepost Creating table validation_uniqueerrorsmodel Creating table validation_genericipaddresstestmodel Creating table validation_genericipaddrunpackuniquetest Creating table custom_lookups_author Creating table custom_lookups_article Creating table custom_lookups_mysqlunixtimestamp Creating table custom_lookups_custommodel Creating table select_for_update_entity Creating table select_for_update_country Creating table select_for_update_eucountry Creating table select_for_update_city Creating table select_for_update_eucity Creating table select_for_update_citycountryproxy Creating table select_for_update_person Creating table select_for_update_personprofile Creating table context_processors_debugobject Creating table one_to_one_place Creating table one_to_one_restaurant Creating table one_to_one_bar Creating table one_to_one_undergroundbar Creating table one_to_one_waiter Creating table one_to_one_favorites Creating table one_to_one_manualprimarykey Creating table one_to_one_relatedmodel Creating table one_to_one_multimodel Creating table one_to_one_target Creating table one_to_one_pointer Creating table one_to_one_pointer2 Creating table one_to_one_hiddenpointer Creating table one_to_one_tofieldpointer Creating table one_to_one_school Creating table one_to_one_director Creating table known_related_objects_tournament Creating table known_related_objects_organiser Creating table known_related_objects_pool Creating table known_related_objects_poolstyle Creating table resolve_url_unimportantthing Creating table filtered_relation_author Creating table filtered_relation_editor Creating table filtered_relation_book Creating table filtered_relation_borrower Creating table filtered_relation_reservation Creating table filtered_relation_rentalsession Creating table filtered_relation_seller Creating table filtered_relation_currency Creating table filtered_relation_exchangerate Creating table filtered_relation_bookdailysales Creating table test_client_regress_customuser Creating table many_to_one_reporter Creating table many_to_one_article Creating table many_to_one_country Creating table many_to_one_city Creating table many_to_one_district Creating table many_to_one_first Creating table many_to_one_second Creating table many_to_one_third Creating table many_to_one_parent Creating table many_to_one_parentstringprimarykey Creating table many_to_one_child Creating table many_to_one_childnullableparent Creating table many_to_one_childstringprimarykeyparent Creating table many_to_one_tofieldchild Creating table many_to_one_category Creating table many_to_one_record Creating table many_to_one_relation Creating table many_to_one_school Creating table many_to_one_student Creating table foreign_object_article Creating table foreign_object_newsarticle Creating table foreign_object_articletranslation Creating table foreign_object_articletag Creating table foreign_object_articleidea Creating table foreign_object_address Creating table foreign_object_customer Creating table foreign_object_contact Creating table foreign_object_slugpage Creating table foreign_object_country Creating table foreign_object_person Creating table foreign_object_group Creating table foreign_object_membership Creating table foreign_object_friendship Creating table forms_tests_boundarymodel Creating table forms_tests_defaults Creating table forms_tests_choicemodel Creating table forms_tests_choiceoptionmodel Creating table forms_tests_choicefieldmodel Creating table forms_tests_optionalmultichoicemodel Creating table forms_tests_filemodel Creating table forms_tests_article Creating table view_tests_author Creating table view_tests_article Creating table view_tests_urlarticle Creating table view_tests_datearticle Creating table transaction_hooks_thing Creating table admin_widgets_member Creating table admin_widgets_artist Creating table admin_widgets_band Creating table admin_widgets_unsafelimitchoicesto Creating table admin_widgets_album Creating table admin_widgets_releaseevent Creating table admin_widgets_videostream Creating table admin_widgets_inventory Creating table admin_widgets_event Creating table admin_widgets_car Creating table admin_widgets_cartire Creating table admin_widgets_honeycomb Creating table admin_widgets_bee Creating table admin_widgets_individual Creating table admin_widgets_company Creating table admin_widgets_advisor Creating table admin_widgets_student Creating table admin_widgets_school Creating table admin_widgets_profile Creating table model_regress_article Creating table model_regress_movie Creating table model_regress_party Creating table model_regress_event Creating table model_regress_department Creating table model_regress_worker Creating table model_regress_nonautopk Creating table model_regress_model1 Creating table model_regress_model2 Creating table model_regress_model3 Creating table queryset_pickle_group Creating table queryset_pickle_event Creating table queryset_pickle_happening Creating table queryset_pickle_binaryfieldmodel Creating table queryset_pickle_somemodel Creating table queryset_pickle_m2mmodel Creating table queryset_pickle_myevent Creating table queryset_pickle_edition Creating table delete_p Creating table delete_r Creating table delete_s Creating table delete_t Creating table delete_u Creating table delete_rchild Creating table delete_rchildchild Creating table delete_a Creating table delete_b Creating table delete_m Creating table delete_mr Creating table delete_mrnull Creating table delete_avatar Creating table delete_user Creating table delete_hiddenuser Creating table delete_hiddenuserprofile Creating table delete_m2mto Creating table delete_m2mfrom Creating table delete_parent Creating table delete_child Creating table delete_base Creating table delete_reltobase Creating table delete_origin Creating table delete_referrer Creating table delete_secondreferrer Creating table delete_deletetop Creating table delete_b1 Creating table delete_b2 Creating table delete_b3 Creating table delete_deletebottom Creating table delete_genericb1 Creating table delete_genericb2 Creating table delete_genericdeletebottom Creating table delete_genericdeletebottomparent Creating table admin_custom_urls_action Creating table admin_custom_urls_person Creating table admin_custom_urls_car Creating table test_utils_car Creating table test_utils_person Creating table test_utils_possessedcar Creating table m2m_intermediary_reporter Creating table m2m_intermediary_article Creating table m2m_intermediary_writer Creating table i18n_testmodel Creating table i18n_company Creating table custom_managers_person Creating table custom_managers_funperson Creating table custom_managers_book Creating table custom_managers_car Creating table custom_managers_relatedmodel Creating table custom_managers_restrictedmodel Creating table custom_managers_onetoonerestrictedmodel Creating table custom_managers_personfromabstract Creating table cache_poll Creating table constraints_product Creating table constraints_uniqueconstraintproduct Creating table constraints_uniqueconstraintconditionproduct Creating table constraints_childmodel Creating table expressions_case_casetestmodel Creating table expressions_case_o2ocasetestmodel Creating table expressions_case_fkcasetestmodel Creating table expressions_case_client Creating table m2m_and_m2o_user Creating table m2m_and_m2o_issue Creating table m2m_and_m2o_stringreferencemodel Creating table fixtures_model_package_article Creating table inline_formsets_school Creating table inline_formsets_parent Creating table inline_formsets_child Creating table inline_formsets_poet Creating table inline_formsets_poem Creating table many_to_many_publication Creating table many_to_many_tag Creating table many_to_many_article Creating table many_to_many_user Creating table many_to_many_userarticle Creating table many_to_many_inheritedarticlea Creating table many_to_many_inheritedarticleb Creating table basic_article Creating table basic_featuredarticle Creating table basic_selfref Creating table basic_primarykeywithdefault Creating table basic_childprimarykeywithdefault Creating table auth_tests_customuser Creating table auth_tests_customuserwithoutisactivefield Creating table auth_tests_extensionuser Creating table auth_tests_custompermissionsuser Creating table auth_tests_customusernonuniqueusername Creating table auth_tests_isactivetestuser1 Creating table auth_tests_minimaluser Creating table auth_tests_nopassworduser Creating table auth_tests_concrete Creating table auth_tests_uuiduser Creating table auth_tests_customemailfield Creating table auth_tests_email Creating table auth_tests_customuserwithfk Creating table auth_tests_integerusernameuser Creating table auth_tests_userwithdisabledlastloginfield Creating table auth_tests_organization Creating table auth_tests_customuserwithm2m Creating table auth_tests_customuserwithm2mthrough Creating table auth_tests_membership Creating table save_delete_hooks_person Creating table base_mymodel Creating table model_formsets_author Creating table model_formsets_betterauthor Creating table model_formsets_book Creating table model_formsets_bookwithcustompk Creating table model_formsets_editor Creating table model_formsets_bookwithoptionalalteditor Creating table model_formsets_alternatebook Creating table model_formsets_authormeeting Creating table model_formsets_customprimarykey Creating table model_formsets_place Creating table model_formsets_owner Creating table model_formsets_location Creating table model_formsets_ownerprofile Creating table model_formsets_restaurant Creating table model_formsets_product Creating table model_formsets_price Creating table model_formsets_mexicanrestaurant Creating table model_formsets_classymexicanrestaurant Creating table model_formsets_repository Creating table model_formsets_revision Creating table model_formsets_person Creating table model_formsets_membership Creating table model_formsets_team Creating table model_formsets_player Creating table model_formsets_poet Creating table model_formsets_poem Creating table model_formsets_post Creating table model_formsets_uuidpkparent Creating table model_formsets_uuidpkchild Creating table model_formsets_childwitheditablepk Creating table model_formsets_autopkchildofuuidpkparent Creating table model_formsets_autopkparent Creating table model_formsets_uuidpkchildofautopkparent Creating table model_formsets_parentwithuuidalternatekey Creating table model_formsets_childrelatedviaak Creating table multiple_database_review Creating table multiple_database_person Creating table multiple_database_book Creating table multiple_database_pet Creating table multiple_database_userprofile Creating table managers_regress_parent Creating table managers_regress_child1 Creating table managers_regress_child2 Creating table managers_regress_child3 Creating table managers_regress_child4 Creating table managers_regress_child5 Creating table managers_regress_child6 Creating table managers_regress_child7 Creating table managers_regress_relatedmodel Creating table managers_regress_relationmodel Creating table max_lengths_personwithdefaultmaxlengths Creating table max_lengths_personwithcustommaxlengths Creating table m2m_recursive_person Creating table m2m_recursive_colleague Creating table model_inheritance_worker Creating table model_inheritance_student Creating table model_inheritance_post Creating table model_inheritance_comment Creating table model_inheritance_link Creating table model_inheritance_chef Creating table model_inheritance_place Creating table my_restaurant Creating table model_inheritance_italianrestaurant Creating table model_inheritance_supplier Creating table model_inheritance_parkinglot Creating table model_inheritance_title Creating table model_inheritance_mixinmodel Creating table model_inheritance_base Creating table model_inheritance_subbase Creating table model_inheritance_grandparent Creating table model_inheritance_parent Creating table model_inheritance_child Creating table model_inheritance_grandchild Creating table custom_pk_employee Creating table custom_pk_business Creating table custom_pk_bar Creating table custom_pk_foo Creating table ordering_author Creating table ordering_article Creating table ordering_childarticle Creating table ordering_reference Creating table select_related_onetoone_user Creating table select_related_onetoone_userprofile Creating table select_related_onetoone_userstatresult Creating table select_related_onetoone_userstat Creating table select_related_onetoone_statdetails Creating table select_related_onetoone_advanceduserstat Creating table select_related_onetoone_image Creating table select_related_onetoone_product Creating table select_related_onetoone_parent1 Creating table select_related_onetoone_parent2 Creating table select_related_onetoone_child1 Creating table select_related_onetoone_child2 Creating table select_related_onetoone_child3 Creating table select_related_onetoone_child4 Creating table select_related_onetoone_linkedlist Creating table a01 Creating table b01 Creating table c01 Creating table unmanaged_models_proxy1 Creating table unmanaged_models_proxy2 Creating table unmanaged_models_managed1 Creating table admin_inlines_parent Creating table admin_inlines_teacher Creating table admin_inlines_child Creating table admin_inlines_book Creating table admin_inlines_author Creating table admin_inlines_nonautopkbook Creating table admin_inlines_nonautopkbookchild Creating table admin_inlines_editablepkbook Creating table admin_inlines_holder Creating table admin_inlines_inner Creating table admin_inlines_holder2 Creating table admin_inlines_inner2 Creating table admin_inlines_holder3 Creating table admin_inlines_inner3 Creating table admin_inlines_holder4 Creating table admin_inlines_inner4stacked Creating table admin_inlines_inner4tabular Creating table admin_inlines_holder5 Creating table admin_inlines_inner5stacked Creating table admin_inlines_inner5tabular Creating table admin_inlines_person Creating table admin_inlines_outfititem Creating table admin_inlines_fashionista Creating table admin_inlines_shoppingweakness Creating table admin_inlines_titlecollection Creating table admin_inlines_title Creating table admin_inlines_poll Creating table admin_inlines_question Creating table admin_inlines_novel Creating table admin_inlines_chapter Creating table admin_inlines_footnote Creating table admin_inlines_capofamiglia Creating table admin_inlines_consigliere Creating table admin_inlines_sottocapo Creating table admin_inlines_readonlyinline Creating table admin_inlines_parentmodelwithcustompk Creating table admin_inlines_childmodel1 Creating table admin_inlines_childmodel2 Creating table admin_inlines_binarytree Creating table admin_inlines_lifeform Creating table admin_inlines_extraterrestrial Creating table admin_inlines_sighting Creating table admin_inlines_someparentmodel Creating table admin_inlines_somechildmodel Creating table admin_inlines_profilecollection Creating table admin_inlines_profile Creating table get_earliest_or_latest_article Creating table get_earliest_or_latest_person Creating table get_earliest_or_latest_indexerrorarticle Creating table timezones_event Creating table timezones_maybeevent Creating table timezones_session Creating table timezones_sessionevent Creating table timezones_timestamp Creating table timezones_alldayevent Creating table proxy_model_inheritance_concretemodel Creating table proxy_model_inheritance_concretemodelsubclass Creating table check_framework_simplemodel Creating table generic_relations_regress_link Creating table generic_relations_regress_place Creating table generic_relations_regress_restaurant Creating table generic_relations_regress_cafe Creating table generic_relations_regress_address Creating table generic_relations_regress_person Creating table generic_relations_regress_charlink Creating table generic_relations_regress_textlink Creating table generic_relations_regress_oddrelation1 Creating table generic_relations_regress_oddrelation2 Creating table generic_relations_regress_note Creating table generic_relations_regress_contact Creating table generic_relations_regress_organization Creating table generic_relations_regress_company Creating table generic_relations_regress_developer Creating table generic_relations_regress_team Creating table generic_relations_regress_guild Creating table generic_relations_regress_tag Creating table generic_relations_regress_board Creating table generic_relations_regress_haslinkthing Creating table generic_relations_regress_a Creating table generic_relations_regress_b Creating table generic_relations_regress_c Creating table generic_relations_regress_d Creating table generic_relations_regress_node Creating table generic_relations_regress_content Creating table generic_relations_regress_related Creating table file_uploads_filemodel Creating table modeladmin_band Creating table modeladmin_song Creating table modeladmin_concert Creating table modeladmin_validationtestmodel Creating table modeladmin_validationtestinlinemodel Creating table expressions_window_classification Creating table expressions_window_employee Creating table expressions_window_detail Creating table proxy_models_person Creating table proxy_models_statusperson Creating table proxy_models_lowerstatusperson Creating table proxy_models_user Creating table proxy_models_country Creating table proxy_models_state Creating table proxy_models_baseuser Creating table proxy_models_trackeruser Creating table proxy_models_issue Creating table proxy_models_bug Creating table proxy_models_improvement Creating table model_inheritance_regress_place Creating table model_inheritance_regress_restaurant Creating table model_inheritance_regress_italianrestaurant Creating table model_inheritance_regress_parkinglot Creating table model_inheritance_regress_parkinglot3 Creating table model_inheritance_regress_parkinglot4a Creating table model_inheritance_regress_parkinglot4b Creating table model_inheritance_regress_supplier Creating table model_inheritance_regress_wholesaler Creating table model_inheritance_regress_parent Creating table model_inheritance_regress_child Creating table model_inheritance_regress_selfrefparent Creating table model_inheritance_regress_selfrefchild Creating table model_inheritance_regress_article Creating table model_inheritance_regress_articlewithauthor Creating table model_inheritance_regress_m2mbase Creating table model_inheritance_regress_m2mchild Creating table model_inheritance_regress_qualitycontrol Creating table model_inheritance_regress_basem Creating table model_inheritance_regress_derivedm Creating table model_inheritance_regress_internalcertificationaudit Creating table model_inheritance_regress_person Creating table model_inheritance_regress_birthdayparty Creating table model_inheritance_regress_bachelorparty Creating table model_inheritance_regress_messybachelorparty Creating table model_inheritance_regress_searchablelocation Creating table model_inheritance_regress_busstation Creating table model_inheritance_regress_trainstation Creating table model_inheritance_regress_user Creating table model_inheritance_regress_profile Creating table model_inheritance_regress_politician Creating table model_inheritance_regress_congressman Creating table model_inheritance_regress_senator Creating table get_object_or_404_author Creating table get_object_or_404_article Creating table generic_views_artist Creating table generic_views_author Creating table generic_views_book Creating table generic_views_page Creating table generic_views_booksigning Creating table contenttypes_tests_site Creating table contenttypes_tests_author Creating table contenttypes_tests_article Creating table contenttypes_tests_schemeincludedurl Creating table contenttypes_tests_concretemodel Creating table contenttypes_tests_foowithouturl Creating table contenttypes_tests_foowithurl Creating table contenttypes_tests_foowithbrokenabsoluteurl Creating table contenttypes_tests_question Creating table contenttypes_tests_answer Creating table contenttypes_tests_post Creating table contenttypes_tests_modelwithnullfktosite Creating table contenttypes_tests_modelwithm2mtosite Creating table file_storage_storage Creating table async_simplemodel Creating table admin_autodiscover_story Creating table select_related_regress_building Creating table select_related_regress_device Creating table select_related_regress_port Creating table select_related_regress_connection Creating table select_related_regress_tuser Creating table select_related_regress_person Creating table select_related_regress_organizer Creating table select_related_regress_student Creating table select_related_regress_class Creating table select_related_regress_enrollment Creating table select_related_regress_country Creating table select_related_regress_state Creating table select_related_regress_clientstatus Creating table select_related_regress_client Creating table select_related_regress_specialclient Creating table select_related_regress_parent Creating table select_related_regress_child Creating table select_related_regress_item Creating table select_related_regress_fowl Creating table select_related_regress_hen Creating table select_related_regress_chick Creating table select_related_regress_a Creating table select_related_regress_b Creating table select_related_regress_c Creating table signals_person Creating table signals_car Creating table signals_author Creating table signals_book Creating table fixtures_regress_animal Creating table Fixtures_regress_plant Creating table fixtures_regress_stuff Creating table fixtures_regress_absolute Creating table fixtures_regress_parent Creating table fixtures_regress_child Creating table fixtures_regress_channel Creating table fixtures_regress_article Creating table fixtures_regress_specialarticle Creating table fixtures_regress_feature Creating table fixtures_regress_widget Creating table fixtures_regress_store Creating table fixtures_regress_person Creating table fixtures_regress_book Creating table fixtures_regress_nkchild Creating table fixtures_regress_reftonkchild Creating table fixtures_regress_circle1 Creating table fixtures_regress_circle2 Creating table fixtures_regress_circle3 Creating table fixtures_regress_circle4 Creating table fixtures_regress_circle5 Creating table fixtures_regress_circle6 Creating table fixtures_regress_externaldependency Creating table fixtures_regress_thingy Creating table fixtures_regress_m2mtoself Creating table fixtures_regress_m2msimplea Creating table fixtures_regress_m2msimpleb Creating table fixtures_regress_m2msimplecirculara Creating table fixtures_regress_m2msimplecircularb Creating table fixtures_regress_m2mcomplexa Creating table fixtures_regress_m2mcomplexb Creating table fixtures_regress_m2mthroughab Creating table fixtures_regress_m2mcomplexcircular1a Creating table fixtures_regress_m2mcomplexcircular1b Creating table fixtures_regress_m2mcomplexcircular1c Creating table fixtures_regress_m2mcircular1throughab Creating table fixtures_regress_m2mcircular1throughbc Creating table fixtures_regress_m2mcircular1throughca Creating table fixtures_regress_m2mcomplexcircular2a Creating table fixtures_regress_m2mcomplexcircular2b Creating table fixtures_regress_m2mcircular2throughab Creating table string_lookup_foo Creating table string_lookup_bar Creating table string_lookup_whiz Creating table string_lookup_child Creating table string_lookup_base Creating table string_lookup_article Creating table delete_regress_award Creating table delete_regress_awardnote Creating table delete_regress_person Creating table delete_regress_book Creating table delete_regress_toy Creating table delete_regress_child Creating table delete_regress_playedwith Creating table delete_regress_playedwithnote Creating table delete_regress_contact Creating table delete_regress_email Creating table delete_regress_researcher Creating table delete_regress_food Creating table delete_regress_eaten Creating table delete_regress_policy Creating table delete_regress_version Creating table delete_regress_location Creating table delete_regress_item Creating table delete_regress_file Creating table delete_regress_fooimage Creating table delete_regress_foofile Creating table delete_regress_foophoto Creating table delete_regress_orgunit Creating table delete_regress_login Creating table delete_regress_house Creating table delete_regress_orderedperson Creating table sessions_tests_customsession Creating table pagination_article Creating table select Creating table custom_methods_article Creating table nested_foreign_keys_person Creating table nested_foreign_keys_movie Creating table nested_foreign_keys_event Creating table nested_foreign_keys_screening Creating table nested_foreign_keys_screeningnullfk Creating table nested_foreign_keys_package Creating table nested_foreign_keys_packagenullfk Creating table many_to_one_null_reporter Creating table many_to_one_null_article Creating table many_to_one_null_car Creating table many_to_one_null_driver Creating table update_datapoint Creating table update_relatedpoint Creating table update_a Creating table update_b Creating table update_c Creating table update_d Creating table update_foo Creating table update_bar Creating table update_uniquenumber Creating table update_uniquenumberchild Creating table admin_checks_album Creating table admin_checks_song Creating table admin_checks_twoalbumfkandane Creating table admin_checks_author Creating table admin_checks_book Creating table admin_checks_authorsbooks Creating table admin_checks_state Creating table admin_checks_city Creating table admin_checks_influence Creating table force_insert_update_counter Creating table force_insert_update_inheritedcounter Creating table force_insert_update_subcounter Creating table force_insert_update_withcustompk Creating table transactions_reporter Creating table m2m_regress_selfrefer Creating table m2m_regress_tag Creating table m2m_regress_tagcollection Creating table m2m_regress_entry Creating table m2m_regress_selfreferchild Creating table m2m_regress_selfreferchildsibling Creating table m2m_regress_line Creating table m2m_regress_worksheet Creating table m2m_regress_user Creating table m2m_regress_regressionmodelsplit Creating table m2m_regress_post Creating table m2m_multiple_category Creating table m2m_multiple_article Creating table mutually_referential_parent Creating table mutually_referential_child Creating table lookup_alarm Creating table lookup_author Creating table lookup_article Creating table lookup_tag Creating table lookup_season Creating table lookup_game Creating table lookup_player Creating table lookup_product Creating table lookup_stock Creating table lookup_freebie Creating table datatypes_donut Creating table datatypes_rumbaba Creating table queries_dumbcategory Creating table queries_namedcategory Creating table queries_tag Creating table queries_note Creating table queries_annotation Creating table queries_datetimepk Creating table queries_extrainfo Creating table queries_author Creating table queries_item Creating table queries_report Creating table queries_reportcomment Creating table queries_ranking Creating table queries_cover Creating table queries_number Creating table queries_valid Creating table queries_x Creating table queries_y Creating table queries_loopx Creating table queries_loopy Creating table queries_loopz Creating table queries_managedmodel Creating table queries_detail Creating table queries_member Creating table queries_child Creating table queries_custompk Creating table queries_related Creating table queries_custompktag Creating table queries_celebrity Creating table queries_tvchef Creating table queries_fan Creating table queries_leafa Creating table queries_leafb Creating table queries_join Creating table queries_reservedname Creating table queries_sharedconnection Creating table queries_pointera Creating table queries_pointerb Creating table queries_singleobject Creating table queries_relatedobject Creating table queries_plaything Creating table queries_article Creating table queries_food Creating table queries_eaten Creating table queries_node Creating table queries_objecta Creating table queries_childobjecta Creating table queries_objectb Creating table queries_objectc Creating table queries_simplecategory Creating table queries_specialcategory Creating table queries_categoryitem Creating table queries_mixedcasefieldcategoryitem Creating table queries_mixedcasedbcolumncategoryitem Creating table queries_onetoonecategory Creating table queries_categoryrelationship Creating table queries_commonmixedcaseforeignkeys Creating table queries_nullablename Creating table queries_modeld Creating table queries_modelc Creating table queries_modelb Creating table queries_modela Creating table queries_job Creating table queries_jobresponsibilities Creating table queries_responsibility Creating table queries_fk1 Creating table queries_fk2 Creating table queries_fk3 Creating table queries_basea Creating table queries_identifier Creating table queries_program Creating table queries_channel Creating table queries_book Creating table queries_chapter Creating table queries_paragraph Creating table queries_page Creating table queries_myobject Creating table queries_order Creating table queries_orderitem Creating table queries_baseuser Creating table queries_task Creating table queries_staff Creating table queries_staffuser Creating table queries_ticket21203parent Creating table queries_ticket21203child Creating table queries_person Creating table queries_company Creating table queries_employment Creating table queries_school Creating table queries_student Creating table queries_classroom Creating table queries_teacher Creating table queries_ticket23605aparent Creating table queries_ticket23605a Creating table queries_ticket23605b Creating table queries_ticket23605c Creating table Individual Creating table RelatedIndividual Creating table queries_customdbcolumn Creating table queries_returningmodel Creating table queries_nonintegerpkreturningmodel Creating table queries_jsonfieldnullable Creating table apps_totallynormal Creating table syndication_tests_entry Creating table syndication_tests_article Running deferred SQL... Running migrations: Applying admin.0001_initial... OK Applying admin.0002_logentry_remove_auto_add... OK Applying admin.0003_logentry_add_action_flag_choices... OK Applying db_functions.0001_setup_extensions... OK Applying db_functions.0002_create_test_models... OK Applying sites.0001_initial... OK Applying flatpages.0001_initial... OK Applying migration_test_data_persistence.0001_initial... OK Applying migration_test_data_persistence.0002_add_book... OK Applying postgres_tests.0001_setup_extensions... OK Applying postgres_tests.0002_create_test_models... OK Applying redirects.0001_initial... OK Applying redirects.0002_alter_redirect_new_path_help_text... OK Applying sites.0002_alter_domain_unique... OK Applying sites_framework.0001_initial... OK Cloning test database for alias 'other' ('file:memorydb_other?mode=memory&cache=shared')... Cloning test database for alias 'other' ('file:memorydb_other?mode=memory&cache=shared')... Cloning test database for alias 'other' ('file:memorydb_other?mode=memory&cache=shared')... Cloning test database for alias 'other' ('file:memorydb_other?mode=memory&cache=shared')... System check identified no issues (25 silenced). test_aggregation (from_db_value.tests.FromDBValueTest.test_aggregation) ... ok test_connection (from_db_value.tests.FromDBValueTest.test_connection) ... ok test_defer (from_db_value.tests.FromDBValueTest.test_defer) ... ok test_simple_load (from_db_value.tests.FromDBValueTest.test_simple_load) ... ok test_values (from_db_value.tests.FromDBValueTest.test_values) ... ok test_values_list (from_db_value.tests.FromDBValueTest.test_values_list) ... ok test_apply (migrations.test_loader.RecorderTests.test_apply) Tests marking migrations as applied/unapplied. ... ok test_pickle (utils_tests.test_simplelazyobject.TestUtilsSimpleLazyObjectDjangoTestCase.test_pickle) ... ok test_makemigrations_app_name_specified_as_label (migrations.test_commands.AppLabelErrorTests.test_makemigrations_app_name_specified_as_label) ... ok test_makemigrations_nonexistent_app_label (migrations.test_commands.AppLabelErrorTests.test_makemigrations_nonexistent_app_label) ... ok test_migrate_app_name_specified_as_label (migrations.test_commands.AppLabelErrorTests.test_migrate_app_name_specified_as_label) ... ok test_migrate_nonexistent_app_label (migrations.test_commands.AppLabelErrorTests.test_migrate_nonexistent_app_label) ... ok test_showmigrations_app_name_specified_as_label (migrations.test_commands.AppLabelErrorTests.test_showmigrations_app_name_specified_as_label) ... ok test_showmigrations_nonexistent_app_label (migrations.test_commands.AppLabelErrorTests.test_showmigrations_nonexistent_app_label) ... ok test_sqlmigrate_app_name_specified_as_label (migrations.test_commands.AppLabelErrorTests.test_sqlmigrate_app_name_specified_as_label) ... ok test_sqlmigrate_nonexistent_app_label (migrations.test_commands.AppLabelErrorTests.test_sqlmigrate_nonexistent_app_label) ... ok test_squashmigrations_app_name_specified_as_label (migrations.test_commands.AppLabelErrorTests.test_squashmigrations_app_name_specified_as_label) ... ok test_squashmigrations_nonexistent_app_label (migrations.test_commands.AppLabelErrorTests.test_squashmigrations_nonexistent_app_label) ... ok test_m2m_prefetch_proxied (m2m_through_regress.test_multitable.MultiTableTests.test_m2m_prefetch_proxied) ... ok test_m2m_prefetch_reverse_proxied (m2m_through_regress.test_multitable.MultiTableTests.test_m2m_prefetch_reverse_proxied) ... ok test_m2m_query (m2m_through_regress.test_multitable.MultiTableTests.test_m2m_query) ... ok test_m2m_query_proxied (m2m_through_regress.test_multitable.MultiTableTests.test_m2m_query_proxied) ... ok test_m2m_reverse_query (m2m_through_regress.test_multitable.MultiTableTests.test_m2m_reverse_query) ... ok test_m2m_reverse_query_proxied (m2m_through_regress.test_multitable.MultiTableTests.test_m2m_reverse_query_proxied) ... ok test_serialization (m2m_through_regress.tests.M2MThroughSerializationTestCase.test_serialization) m2m-through models aren't serialized as m2m fields. Refs #8134 ... ok test_both_date_objects (utils_tests.test_timesince.TimesinceTests.test_both_date_objects) Timesince should work with both date objects (#9672) ... ok test_date_objects (utils_tests.test_timesince.TimesinceTests.test_date_objects) Both timesince and timeuntil should work on date objects (#17937). ... ok test_depth (utils_tests.test_timesince.TimesinceTests.test_depth) ... ok test_depth_invalid (utils_tests.test_timesince.TimesinceTests.test_depth_invalid) ... ok test_different_timezones (utils_tests.test_timesince.TimesinceTests.test_different_timezones) When using two different timezones. ... ok test_display_first_unit (utils_tests.test_timesince.TimesinceTests.test_display_first_unit) If the two differing units aren't adjacent, only the first unit is ... ok test_display_second_before_first (utils_tests.test_timesince.TimesinceTests.test_display_second_before_first) When the second date occurs before the first, we should always ... ok test_equal_datetimes (utils_tests.test_timesince.TimesinceTests.test_equal_datetimes) equal datetimes. ... ok test_ignore_microseconds_and_seconds (utils_tests.test_timesince.TimesinceTests.test_ignore_microseconds_and_seconds) Microseconds and seconds are ignored. ... ok test_leap_year (utils_tests.test_timesince.TimesinceTests.test_leap_year) ... ok test_leap_year_new_years_eve (utils_tests.test_timesince.TimesinceTests.test_leap_year_new_years_eve) ... ok test_multiple_units (utils_tests.test_timesince.TimesinceTests.test_multiple_units) Test multiple units. ... ok test_naive_datetime_with_tzinfo_attribute (utils_tests.test_timesince.TimesinceTests.test_naive_datetime_with_tzinfo_attribute) ... ok test_other_units (utils_tests.test_timesince.TimesinceTests.test_other_units) Test other units. ... ok test_second_before_equal_first_humanize_time_strings (utils_tests.test_timesince.TimesinceTests.test_second_before_equal_first_humanize_time_strings) ... ok test_thousand_years_ago (utils_tests.test_timesince.TimesinceTests.test_thousand_years_ago) ... ok test_join_trimming_forwards (m2m_through_regress.tests.M2MThroughTestCase.test_join_trimming_forwards) Too many copies of the intermediate table aren't involved when doing a ... ok test_join_trimming_reverse (m2m_through_regress.tests.M2MThroughTestCase.test_join_trimming_reverse) ... ok test_retrieve_forward_m2m_items (m2m_through_regress.tests.M2MThroughTestCase.test_retrieve_forward_m2m_items) ... ok test_retrieve_forward_m2m_items_via_custom_id_intermediary (m2m_through_regress.tests.M2MThroughTestCase.test_retrieve_forward_m2m_items_via_custom_id_intermediary) ... ok test_retrieve_reverse_m2m_items (m2m_through_regress.tests.M2MThroughTestCase.test_retrieve_reverse_m2m_items) ... ok test_retrieve_reverse_m2m_items_via_custom_id_intermediary (m2m_through_regress.tests.M2MThroughTestCase.test_retrieve_reverse_m2m_items_via_custom_id_intermediary) ... ok test_sequence_creation (m2m_through_regress.tests.ThroughLoadDataTestCase.test_sequence_creation) Sequences on an m2m_through are created for the through model, not a ... ok test_add (m2m_through_regress.tests.ToFieldThroughTests.test_add) ... ok test_add_null_reverse (m2m_through_regress.tests.ToFieldThroughTests.test_add_null_reverse) ... ok test_add_null_reverse_related (m2m_through_regress.tests.ToFieldThroughTests.test_add_null_reverse_related) ... ok test_add_related_null (m2m_through_regress.tests.ToFieldThroughTests.test_add_related_null) ... ok test_add_reverse (m2m_through_regress.tests.ToFieldThroughTests.test_add_reverse) ... ok test_m2m_relations_unusable_on_null_pk_obj (m2m_through_regress.tests.ToFieldThroughTests.test_m2m_relations_unusable_on_null_pk_obj) ... ok test_m2m_relations_unusable_on_null_to_field (m2m_through_regress.tests.ToFieldThroughTests.test_m2m_relations_unusable_on_null_to_field) ... ok test_remove (m2m_through_regress.tests.ToFieldThroughTests.test_remove) ... ok test_remove_reverse (m2m_through_regress.tests.ToFieldThroughTests.test_remove_reverse) ... ok test_to_field (m2m_through_regress.tests.ToFieldThroughTests.test_to_field) ... ok test_to_field_clear (m2m_through_regress.tests.ToFieldThroughTests.test_to_field_clear) ... ok test_to_field_clear_reverse (m2m_through_regress.tests.ToFieldThroughTests.test_to_field_clear_reverse) ... ok test_to_field_reverse (m2m_through_regress.tests.ToFieldThroughTests.test_to_field_reverse) ... ok test_cast_from_db_date_to_datetime (db_functions.comparison.test_cast.CastTests.test_cast_from_db_date_to_datetime) ... ok test_cast_from_db_datetime_to_date (db_functions.comparison.test_cast.CastTests.test_cast_from_db_datetime_to_date) ... ok test_cast_from_db_datetime_to_date_group_by (db_functions.comparison.test_cast.CastTests.test_cast_from_db_datetime_to_date_group_by) ... ok test_cast_from_db_datetime_to_time (db_functions.comparison.test_cast.CastTests.test_cast_from_db_datetime_to_time) ... ok test_cast_from_field (db_functions.comparison.test_cast.CastTests.test_cast_from_field) ... ok test_cast_from_python (db_functions.comparison.test_cast.CastTests.test_cast_from_python) ... ok test_cast_from_python_to_date (db_functions.comparison.test_cast.CastTests.test_cast_from_python_to_date) ... ok test_cast_from_python_to_datetime (db_functions.comparison.test_cast.CastTests.test_cast_from_python_to_datetime) ... ok test_cast_from_value (db_functions.comparison.test_cast.CastTests.test_cast_from_value) ... ok test_cast_to_char_field_with_max_length (db_functions.comparison.test_cast.CastTests.test_cast_to_char_field_with_max_length) ... skipped "Database doesn't support feature(s): supports_cast_with_precision" test_cast_to_char_field_without_max_length (db_functions.comparison.test_cast.CastTests.test_cast_to_char_field_without_max_length) ... ok test_cast_to_decimal_field (db_functions.comparison.test_cast.CastTests.test_cast_to_decimal_field) ... skipped "Database doesn't support feature(s): supports_cast_with_precision" test_cast_to_duration (db_functions.comparison.test_cast.CastTests.test_cast_to_duration) ... ok test_cast_to_integer (db_functions.comparison.test_cast.CastTests.test_cast_to_integer) ... ok test_cast_to_text_field (db_functions.comparison.test_cast.CastTests.test_cast_to_text_field) ... ok test_basic (db_functions.comparison.test_coalesce.CoalesceTests.test_basic) ... ok test_gt_two_expressions (db_functions.comparison.test_coalesce.CoalesceTests.test_gt_two_expressions) ... ok test_mixed_values (db_functions.comparison.test_coalesce.CoalesceTests.test_mixed_values) ... ok test_ordering (db_functions.comparison.test_coalesce.CoalesceTests.test_ordering) ... ok test_collate_filter_ci (db_functions.comparison.test_collate.CollateTests.test_collate_filter_ci) ... ok test_collate_order_by_cs (db_functions.comparison.test_collate.CollateTests.test_collate_order_by_cs) ... ok test_invalid_collation (db_functions.comparison.test_collate.CollateTests.test_invalid_collation) ... ok test_language_collation_order_by (db_functions.comparison.test_collate.CollateTests.test_language_collation_order_by) ... skipped 'This backend does not support language collations.' test_not_supported (db_functions.comparison.test_json_object.JSONObjectNotSupportedTests.test_not_supported) ... skipped 'Database has feature(s) has_json_object_function' test_check_consistent_history (migrations.test_loader.LoaderTests.test_check_consistent_history) ... ok test_check_consistent_history_squashed (migrations.test_loader.LoaderTests.test_check_consistent_history_squashed) MigrationLoader.check_consistent_history() should ignore unapplied ... ok test_explicit_missing_module (migrations.test_loader.LoaderTests.test_explicit_missing_module) If a MIGRATION_MODULES override points to a missing module, the error ... ok test_first (migrations.test_loader.LoaderTests.test_first) Makes sure the '__first__' migrations build correctly. ... ok test_ignore_files (migrations.test_loader.LoaderTests.test_ignore_files) Files prefixed with underscore, tilde, or dot aren't loaded. ... ok test_load (migrations.test_loader.LoaderTests.test_load) Makes sure the loader can load the migrations for the test apps, ... ok test_load_empty_dir (migrations.test_loader.LoaderTests.test_load_empty_dir) ... ok test_load_import_error (migrations.test_loader.LoaderTests.test_load_import_error) ... ok test_load_module_file (migrations.test_loader.LoaderTests.test_load_module_file) ... ok test_load_unmigrated_dependency (migrations.test_loader.LoaderTests.test_load_unmigrated_dependency) Makes sure the loader can load migrations with a dependency on an unmigrated app. ... ok test_loading_namespace_package (migrations.test_loader.LoaderTests.test_loading_namespace_package) Migration directories without an __init__.py file are ignored. ... ok test_loading_package_without__file__ (migrations.test_loader.LoaderTests.test_loading_package_without__file__) To support frozen environments, MigrationLoader loads migrations from ... ok test_loading_squashed (migrations.test_loader.LoaderTests.test_loading_squashed) Tests loading a squashed migration ... ok test_loading_squashed_complex (migrations.test_loader.LoaderTests.test_loading_squashed_complex) Tests loading a complex set of squashed migrations ... ok test_loading_squashed_complex_multi_apps (migrations.test_loader.LoaderTests.test_loading_squashed_complex_multi_apps) ... ok test_loading_squashed_complex_multi_apps_partially_applied (migrations.test_loader.LoaderTests.test_loading_squashed_complex_multi_apps_partially_applied) ... ok test_loading_squashed_erroneous (migrations.test_loader.LoaderTests.test_loading_squashed_erroneous) Tests loading a complex but erroneous set of squashed migrations ... ok test_loading_squashed_ref_squashed (migrations.test_loader.LoaderTests.test_loading_squashed_ref_squashed) Tests loading a squashed migration with a new migration referencing it ... ok test_marked_as_migrated (migrations.test_loader.LoaderTests.test_marked_as_migrated) Undefined MIGRATION_MODULES implies default migration module. ... ok test_marked_as_unmigrated (migrations.test_loader.LoaderTests.test_marked_as_unmigrated) MIGRATION_MODULES allows disabling of migrations for a particular app. ... ok test_name_match (migrations.test_loader.LoaderTests.test_name_match) Tests prefix name matching ... ok test_plan_handles_repeated_migrations (migrations.test_loader.LoaderTests.test_plan_handles_repeated_migrations) _generate_plan() doesn't readd migrations already in the plan (#29180). ... ok test_run_before (migrations.test_loader.LoaderTests.test_run_before) Makes sure the loader uses Migration.run_before. ... ok test_all_null (db_functions.comparison.test_greatest.GreatestTests.test_all_null) ... ok test_basic (db_functions.comparison.test_greatest.GreatestTests.test_basic) ... ok test_coalesce_workaround (db_functions.comparison.test_greatest.GreatestTests.test_coalesce_workaround) ... ok test_coalesce_workaround_mysql (db_functions.comparison.test_greatest.GreatestTests.test_coalesce_workaround_mysql) ... skipped 'MySQL-specific workaround' test_decimal_filter (db_functions.comparison.test_greatest.GreatestTests.test_decimal_filter) ... ok test_ignores_null (db_functions.comparison.test_greatest.GreatestTests.test_ignores_null) ... skipped "Database doesn't support feature(s): greatest_least_ignores_nulls" test_one_expressions (db_functions.comparison.test_greatest.GreatestTests.test_one_expressions) ... ok test_propagates_null (db_functions.comparison.test_greatest.GreatestTests.test_propagates_null) ... ok test_related_field (db_functions.comparison.test_greatest.GreatestTests.test_related_field) ... ok test_update (db_functions.comparison.test_greatest.GreatestTests.test_update) ... ok test_basic (db_functions.comparison.test_json_object.JSONObjectTests.test_basic) ... ok test_empty (db_functions.comparison.test_json_object.JSONObjectTests.test_empty) ... ok test_expressions (db_functions.comparison.test_json_object.JSONObjectTests.test_expressions) ... ok test_nested_empty_json_object (db_functions.comparison.test_json_object.JSONObjectTests.test_nested_empty_json_object) ... ok test_nested_json_object (db_functions.comparison.test_json_object.JSONObjectTests.test_nested_json_object) ... ok test_textfield (db_functions.comparison.test_json_object.JSONObjectTests.test_textfield) ... ok test_basic (db_functions.comparison.test_nullif.NullIfTests.test_basic) ... ok test_null_argument (db_functions.comparison.test_nullif.NullIfTests.test_null_argument) ... ok test_null_literal (db_functions.comparison.test_nullif.NullIfTests.test_null_literal) ... skipped 'Oracle specific test for NULL-literal' test_too_few_args (db_functions.comparison.test_nullif.NullIfTests.test_too_few_args) ... ok test_all_null (db_functions.comparison.test_least.LeastTests.test_all_null) ... ok test_basic (db_functions.comparison.test_least.LeastTests.test_basic) ... ok test_coalesce_workaround (db_functions.comparison.test_least.LeastTests.test_coalesce_workaround) ... ok test_coalesce_workaround_mysql (db_functions.comparison.test_least.LeastTests.test_coalesce_workaround_mysql) ... skipped 'MySQL-specific workaround' test_decimal_filter (db_functions.comparison.test_least.LeastTests.test_decimal_filter) ... ok test_ignores_null (db_functions.comparison.test_least.LeastTests.test_ignores_null) ... skipped "Database doesn't support feature(s): greatest_least_ignores_nulls" test_one_expressions (db_functions.comparison.test_least.LeastTests.test_one_expressions) ... ok test_propagates_null (db_functions.comparison.test_least.LeastTests.test_propagates_null) ... ok test_related_field (db_functions.comparison.test_least.LeastTests.test_related_field) ... ok test_update (db_functions.comparison.test_least.LeastTests.test_update) ... ok test_basic (db_functions.datetime.test_now.NowTests.test_basic) ... ok test_decimal (db_functions.math.test_abs.AbsTests.test_decimal) ... ok test_float (db_functions.math.test_abs.AbsTests.test_float) ... ok test_integer (db_functions.math.test_abs.AbsTests.test_integer) ... ok test_null (db_functions.math.test_abs.AbsTests.test_null) ... ok test_transform (db_functions.math.test_abs.AbsTests.test_transform) ... ok test_add_alter_order_with_respect_to (migrations.test_autodetector.AutodetectorTests.test_add_alter_order_with_respect_to) Setting order_with_respect_to when adding the FK too does ... ok test_add_blank_textfield_and_charfield (migrations.test_autodetector.AutodetectorTests.test_add_blank_textfield_and_charfield) #23405 - Adding a NOT NULL and blank `CharField` or `TextField` ... ok test_add_constraints (migrations.test_autodetector.AutodetectorTests.test_add_constraints) Test change detection of new constraints. ... ok test_add_date_fields_with_auto_now_add_asking_for_default (migrations.test_autodetector.AutodetectorTests.test_add_date_fields_with_auto_now_add_asking_for_default) ... ok test_add_date_fields_with_auto_now_add_not_asking_for_null_addition (migrations.test_autodetector.AutodetectorTests.test_add_date_fields_with_auto_now_add_not_asking_for_null_addition) ... ok test_add_date_fields_with_auto_now_not_asking_for_default (migrations.test_autodetector.AutodetectorTests.test_add_date_fields_with_auto_now_not_asking_for_default) ... ok test_add_field (migrations.test_autodetector.AutodetectorTests.test_add_field) Tests autodetection of new fields. ... ok test_add_field_and_foo_together (migrations.test_autodetector.AutodetectorTests.test_add_field_and_foo_together) Added fields will be created before using them in index/unique_together. ... ok test_add_field_with_default (migrations.test_autodetector.AutodetectorTests.test_add_field_with_default) #22030 - Adding a field with a default should work. ... ok test_add_foo_together (migrations.test_autodetector.AutodetectorTests.test_add_foo_together) Tests index/unique_together detection. ... ok test_add_indexes (migrations.test_autodetector.AutodetectorTests.test_add_indexes) Test change detection of new indexes. ... ok test_add_many_to_many (migrations.test_autodetector.AutodetectorTests.test_add_many_to_many) #22435 - Adding a ManyToManyField should not prompt for a default. ... ok test_add_model_order_with_respect_to (migrations.test_autodetector.AutodetectorTests.test_add_model_order_with_respect_to) Setting order_with_respect_to when adding the whole model ... ok test_add_model_order_with_respect_to_index_constraint (migrations.test_autodetector.AutodetectorTests.test_add_model_order_with_respect_to_index_constraint) ... ok test_add_model_order_with_respect_to_index_foo_together (migrations.test_autodetector.AutodetectorTests.test_add_model_order_with_respect_to_index_foo_together) ... ok test_add_model_with_field_removed_from_base_model (migrations.test_autodetector.AutodetectorTests.test_add_model_with_field_removed_from_base_model) Removing a base field takes place before adding a new inherited model ... ok test_add_non_blank_textfield_and_charfield (migrations.test_autodetector.AutodetectorTests.test_add_non_blank_textfield_and_charfield) #23405 - Adding a NOT NULL and non-blank `CharField` or `TextField` ... ok test_alter_db_table_add (migrations.test_autodetector.AutodetectorTests.test_alter_db_table_add) Tests detection for adding db_table in model's options. ... ok test_alter_db_table_change (migrations.test_autodetector.AutodetectorTests.test_alter_db_table_change) Tests detection for changing db_table in model's options'. ... ok test_alter_db_table_no_changes (migrations.test_autodetector.AutodetectorTests.test_alter_db_table_no_changes) Alter_db_table doesn't generate a migration if no changes have been made. ... ok test_alter_db_table_remove (migrations.test_autodetector.AutodetectorTests.test_alter_db_table_remove) Tests detection for removing db_table in model's options. ... ok test_alter_db_table_with_model_change (migrations.test_autodetector.AutodetectorTests.test_alter_db_table_with_model_change) Tests when model and db_table changes, autodetector must create two ... ok test_alter_field (migrations.test_autodetector.AutodetectorTests.test_alter_field) Tests autodetection of new fields. ... ok test_alter_field_to_fk_dependency_other_app (migrations.test_autodetector.AutodetectorTests.test_alter_field_to_fk_dependency_other_app) ... ok test_alter_field_to_not_null_oneoff_default (migrations.test_autodetector.AutodetectorTests.test_alter_field_to_not_null_oneoff_default) #23609 - Tests autodetection of nullable to non-nullable alterations. ... ok test_alter_field_to_not_null_with_default (migrations.test_autodetector.AutodetectorTests.test_alter_field_to_not_null_with_default) #23609 - Tests autodetection of nullable to non-nullable alterations. ... ok test_alter_field_to_not_null_without_default (migrations.test_autodetector.AutodetectorTests.test_alter_field_to_not_null_without_default) #23609 - Tests autodetection of nullable to non-nullable alterations. ... ok test_alter_fk_before_model_deletion (migrations.test_autodetector.AutodetectorTests.test_alter_fk_before_model_deletion) ForeignKeys are altered _before_ the model they used to ... ok test_alter_many_to_many (migrations.test_autodetector.AutodetectorTests.test_alter_many_to_many) ... ok test_alter_model_managers (migrations.test_autodetector.AutodetectorTests.test_alter_model_managers) Changing the model managers adds a new operation. ... ok test_alter_model_options (migrations.test_autodetector.AutodetectorTests.test_alter_model_options) Changing a model's options should make a change. ... ok test_alter_model_options_proxy (migrations.test_autodetector.AutodetectorTests.test_alter_model_options_proxy) Changing a proxy model's options should also make a change. ... ok test_arrange_for_graph (migrations.test_autodetector.AutodetectorTests.test_arrange_for_graph) Tests auto-naming of migrations for graph matching. ... ok test_arrange_for_graph_with_multiple_initial (migrations.test_autodetector.AutodetectorTests.test_arrange_for_graph_with_multiple_initial) ... ok test_bases_first (migrations.test_autodetector.AutodetectorTests.test_bases_first) Bases of other models come first. ... ok test_bases_first_mixed_case_app_label (migrations.test_autodetector.AutodetectorTests.test_bases_first_mixed_case_app_label) ... ok test_circular_dependency_mixed_addcreate (migrations.test_autodetector.AutodetectorTests.test_circular_dependency_mixed_addcreate) #23315 - The dependency resolver knows to put all CreateModel ... ok test_circular_dependency_swappable (migrations.test_autodetector.AutodetectorTests.test_circular_dependency_swappable) #23322 - The dependency resolver knows to explicitly resolve ... ok test_circular_dependency_swappable2 (migrations.test_autodetector.AutodetectorTests.test_circular_dependency_swappable2) #23322 - The dependency resolver knows to explicitly resolve ... ok test_circular_dependency_swappable_self (migrations.test_autodetector.AutodetectorTests.test_circular_dependency_swappable_self) #23322 - The dependency resolver knows to explicitly resolve ... ok test_circular_fk_dependency (migrations.test_autodetector.AutodetectorTests.test_circular_fk_dependency) Having a circular ForeignKey dependency automatically ... ok test_concrete_field_changed_to_many_to_many (migrations.test_autodetector.AutodetectorTests.test_concrete_field_changed_to_many_to_many) #23938 - Changing a concrete field into a ManyToManyField ... ok test_create_model_and_unique_together (migrations.test_autodetector.AutodetectorTests.test_create_model_and_unique_together) ... ok test_create_model_with_check_constraint (migrations.test_autodetector.AutodetectorTests.test_create_model_with_check_constraint) Test creation of new model with constraints already defined. ... ok test_create_model_with_indexes (migrations.test_autodetector.AutodetectorTests.test_create_model_with_indexes) Test creation of new model with indexes already defined. ... ok test_create_with_through_model (migrations.test_autodetector.AutodetectorTests.test_create_with_through_model) Adding a m2m with a through model and the models that use it should be ... ok test_custom_deconstructible (migrations.test_autodetector.AutodetectorTests.test_custom_deconstructible) Two instances which deconstruct to the same value aren't considered a ... ok test_custom_migration_name (migrations.test_autodetector.AutodetectorTests.test_custom_migration_name) Tests custom naming of migrations for graph matching. ... ok test_deconstruct_field_kwarg (migrations.test_autodetector.AutodetectorTests.test_deconstruct_field_kwarg) Field instances are handled correctly by nested deconstruction. ... ok test_deconstruct_type (migrations.test_autodetector.AutodetectorTests.test_deconstruct_type) #22951 -- Uninstantiated classes with deconstruct are correctly returned ... ok test_deconstructible_dict (migrations.test_autodetector.AutodetectorTests.test_deconstructible_dict) Nested deconstruction descends into dict values. ... ok test_deconstructible_list (migrations.test_autodetector.AutodetectorTests.test_deconstructible_list) Nested deconstruction descends into lists. ... ok test_deconstructible_tuple (migrations.test_autodetector.AutodetectorTests.test_deconstructible_tuple) Nested deconstruction descends into tuples. ... ok test_default_related_name_option (migrations.test_autodetector.AutodetectorTests.test_default_related_name_option) ... ok test_different_regex_does_alter (migrations.test_autodetector.AutodetectorTests.test_different_regex_does_alter) ... ok test_empty_foo_together (migrations.test_autodetector.AutodetectorTests.test_empty_foo_together) #23452 - Empty unique/index_together shouldn't generate a migration. ... ok test_first_dependency (migrations.test_autodetector.AutodetectorTests.test_first_dependency) A dependency to an app with no migrations uses __first__. ... ok test_fk_dependency (migrations.test_autodetector.AutodetectorTests.test_fk_dependency) Having a ForeignKey automatically adds a dependency. ... ok test_fk_dependency_other_app (migrations.test_autodetector.AutodetectorTests.test_fk_dependency_other_app) #23100 - ForeignKeys correctly depend on other apps' models. ... ok test_foo_together_no_changes (migrations.test_autodetector.AutodetectorTests.test_foo_together_no_changes) index/unique_together doesn't generate a migration if no ... ok test_foo_together_ordering (migrations.test_autodetector.AutodetectorTests.test_foo_together_ordering) index/unique_together also triggers on ordering changes. ... ok test_foo_together_remove_fk (migrations.test_autodetector.AutodetectorTests.test_foo_together_remove_fk) Tests unique_together and field removal detection & ordering ... ok test_foreign_key_removed_before_target_model (migrations.test_autodetector.AutodetectorTests.test_foreign_key_removed_before_target_model) Removing an FK and the model it targets in the same change must remove ... ok test_identical_regex_doesnt_alter (migrations.test_autodetector.AutodetectorTests.test_identical_regex_doesnt_alter) ... ok test_keep_db_table_with_model_change (migrations.test_autodetector.AutodetectorTests.test_keep_db_table_with_model_change) Tests when model changes but db_table stays as-is, autodetector must not ... ok test_last_dependency (migrations.test_autodetector.AutodetectorTests.test_last_dependency) A dependency to an app with existing migrations uses the ... ok test_m2m_w_through_multistep_remove (migrations.test_autodetector.AutodetectorTests.test_m2m_w_through_multistep_remove) A model with a m2m field that specifies a "through" model cannot be ... ok test_managed_to_unmanaged (migrations.test_autodetector.AutodetectorTests.test_managed_to_unmanaged) ... ok test_many_to_many_changed_to_concrete_field (migrations.test_autodetector.AutodetectorTests.test_many_to_many_changed_to_concrete_field) #23938 - Changing a ManyToManyField into a concrete field ... ok test_many_to_many_removed_before_through_model (migrations.test_autodetector.AutodetectorTests.test_many_to_many_removed_before_through_model) Removing a ManyToManyField and the "through" model in the same change ... ok test_many_to_many_removed_before_through_model_2 (migrations.test_autodetector.AutodetectorTests.test_many_to_many_removed_before_through_model_2) Removing a model that contains a ManyToManyField and the "through" model ... ok test_mti_inheritance_model_removal (migrations.test_autodetector.AutodetectorTests.test_mti_inheritance_model_removal) ... ok test_multiple_bases (migrations.test_autodetector.AutodetectorTests.test_multiple_bases) #23956 - Inheriting models doesn't move *_ptr fields into AddField operations. ... ok test_nested_deconstructible_objects (migrations.test_autodetector.AutodetectorTests.test_nested_deconstructible_objects) Nested deconstruction is applied recursively to the args/kwargs of ... ok test_new_model (migrations.test_autodetector.AutodetectorTests.test_new_model) Tests autodetection of new models. ... ok test_non_circular_foreignkey_dependency_removal (migrations.test_autodetector.AutodetectorTests.test_non_circular_foreignkey_dependency_removal) If two models with a ForeignKey from one to the other are removed at the ... ok test_old_model (migrations.test_autodetector.AutodetectorTests.test_old_model) Tests deletion of old models. ... ok test_order_fields_indexes (migrations.test_autodetector.AutodetectorTests.test_order_fields_indexes) Test change detection of reordering of fields in indexes. ... ok test_pk_fk_included (migrations.test_autodetector.AutodetectorTests.test_pk_fk_included) A relation used as the primary key is kept as part of CreateModel. ... ok test_proxy (migrations.test_autodetector.AutodetectorTests.test_proxy) The autodetector correctly deals with proxy models. ... ok test_proxy_bases_first (migrations.test_autodetector.AutodetectorTests.test_proxy_bases_first) Bases of proxies come first. ... ok test_proxy_custom_pk (migrations.test_autodetector.AutodetectorTests.test_proxy_custom_pk) #23415 - The autodetector must correctly deal with custom FK on proxy ... ok test_proxy_fk_dependency (migrations.test_autodetector.AutodetectorTests.test_proxy_fk_dependency) FK dependencies still work on proxy models. ... ok test_proxy_to_mti_with_fk_to_proxy (migrations.test_autodetector.AutodetectorTests.test_proxy_to_mti_with_fk_to_proxy) ... ok test_proxy_to_mti_with_fk_to_proxy_proxy (migrations.test_autodetector.AutodetectorTests.test_proxy_to_mti_with_fk_to_proxy_proxy) ... ok test_remove_alter_order_with_respect_to (migrations.test_autodetector.AutodetectorTests.test_remove_alter_order_with_respect_to) Removing order_with_respect_to when removing the FK too does ... ok test_remove_constraints (migrations.test_autodetector.AutodetectorTests.test_remove_constraints) Test change detection of removed constraints. ... ok test_remove_field (migrations.test_autodetector.AutodetectorTests.test_remove_field) Tests autodetection of removed fields. ... ok test_remove_field_and_foo_together (migrations.test_autodetector.AutodetectorTests.test_remove_field_and_foo_together) Removed fields will be removed after updating index/unique_together. ... ok test_remove_foo_together (migrations.test_autodetector.AutodetectorTests.test_remove_foo_together) Tests index/unique_together detection. ... ok test_remove_indexes (migrations.test_autodetector.AutodetectorTests.test_remove_indexes) Test change detection of removed indexes. ... ok test_rename_field (migrations.test_autodetector.AutodetectorTests.test_rename_field) Tests autodetection of renamed fields. ... ok test_rename_field_and_foo_together (migrations.test_autodetector.AutodetectorTests.test_rename_field_and_foo_together) Removed fields will be removed after updating index/unique_together. ... ok test_rename_field_foreign_key_to_field (migrations.test_autodetector.AutodetectorTests.test_rename_field_foreign_key_to_field) ... ok test_rename_field_preserved_db_column (migrations.test_autodetector.AutodetectorTests.test_rename_field_preserved_db_column) RenameField is used if a field is renamed and db_column equal to the ... ok test_rename_foreign_object_fields (migrations.test_autodetector.AutodetectorTests.test_rename_foreign_object_fields) ... ok test_rename_m2m_through_model (migrations.test_autodetector.AutodetectorTests.test_rename_m2m_through_model) Tests autodetection of renamed models that are used in M2M relations as ... ok test_rename_model (migrations.test_autodetector.AutodetectorTests.test_rename_model) Tests autodetection of renamed models. ... ok test_rename_model_case (migrations.test_autodetector.AutodetectorTests.test_rename_model_case) Model name is case-insensitive. Changing case doesn't lead to any ... ok test_rename_model_reverse_relation_dependencies (migrations.test_autodetector.AutodetectorTests.test_rename_model_reverse_relation_dependencies) The migration to rename a model pointed to by a foreign key in another ... ok test_rename_model_with_fks_in_different_position (migrations.test_autodetector.AutodetectorTests.test_rename_model_with_fks_in_different_position) #24537 - The order of fields in a model does not influence ... ok test_rename_model_with_renamed_rel_field (migrations.test_autodetector.AutodetectorTests.test_rename_model_with_renamed_rel_field) Tests autodetection of renamed models while simultaneously renaming one ... ok test_rename_referenced_primary_key (migrations.test_autodetector.AutodetectorTests.test_rename_referenced_primary_key) ... ok test_rename_related_field_preserved_db_column (migrations.test_autodetector.AutodetectorTests.test_rename_related_field_preserved_db_column) ... ok test_replace_string_with_foreignkey (migrations.test_autodetector.AutodetectorTests.test_replace_string_with_foreignkey) #22300 - Adding an FK in the same "spot" as a deleted CharField should ... ok test_same_app_circular_fk_dependency (migrations.test_autodetector.AutodetectorTests.test_same_app_circular_fk_dependency) A migration with a FK between two models of the same app does ... ok test_same_app_circular_fk_dependency_with_unique_together_and_indexes (migrations.test_autodetector.AutodetectorTests.test_same_app_circular_fk_dependency_with_unique_together_and_indexes) #22275 - A migration with circular FK dependency does not try ... ok test_same_app_no_fk_dependency (migrations.test_autodetector.AutodetectorTests.test_same_app_no_fk_dependency) A migration with a FK between two models of the same app ... ok test_set_alter_order_with_respect_to (migrations.test_autodetector.AutodetectorTests.test_set_alter_order_with_respect_to) Setting order_with_respect_to adds a field. ... ok test_set_alter_order_with_respect_to_index_constraint_foo_together (migrations.test_autodetector.AutodetectorTests.test_set_alter_order_with_respect_to_index_constraint_foo_together) ... ok test_supports_functools_partial (migrations.test_autodetector.AutodetectorTests.test_supports_functools_partial) ... ok test_swappable (migrations.test_autodetector.AutodetectorTests.test_swappable) ... ok test_swappable_changed (migrations.test_autodetector.AutodetectorTests.test_swappable_changed) ... ok test_swappable_circular_multi_mti (migrations.test_autodetector.AutodetectorTests.test_swappable_circular_multi_mti) ... ok test_swappable_first_inheritance (migrations.test_autodetector.AutodetectorTests.test_swappable_first_inheritance) Swappable models get their CreateModel first. ... ok test_swappable_first_setting (migrations.test_autodetector.AutodetectorTests.test_swappable_first_setting) Swappable models get their CreateModel first. ... ok test_trim_apps (migrations.test_autodetector.AutodetectorTests.test_trim_apps) Trim does not remove dependencies but does remove unwanted apps. ... ok test_unmanaged_create (migrations.test_autodetector.AutodetectorTests.test_unmanaged_create) The autodetector correctly deals with managed models. ... ok test_unmanaged_custom_pk (migrations.test_autodetector.AutodetectorTests.test_unmanaged_custom_pk) #23415 - The autodetector must correctly deal with custom FK on ... ok test_unmanaged_delete (migrations.test_autodetector.AutodetectorTests.test_unmanaged_delete) ... ok test_unmanaged_to_managed (migrations.test_autodetector.AutodetectorTests.test_unmanaged_to_managed) ... ok test_decimal (db_functions.math.test_acos.ACosTests.test_decimal) ... ok test_float (db_functions.math.test_acos.ACosTests.test_float) ... ok test_integer (db_functions.math.test_acos.ACosTests.test_integer) ... ok test_null (db_functions.math.test_acos.ACosTests.test_null) ... ok test_transform (db_functions.math.test_acos.ACosTests.test_transform) ... ok test_decimal (db_functions.math.test_atan.ATanTests.test_decimal) ... ok test_float (db_functions.math.test_atan.ATanTests.test_float) ... ok test_integer (db_functions.math.test_atan.ATanTests.test_integer) ... ok test_null (db_functions.math.test_atan.ATanTests.test_null) ... ok test_transform (db_functions.math.test_atan.ATanTests.test_transform) ... ok test_decimal (db_functions.math.test_asin.ASinTests.test_decimal) ... ok test_float (db_functions.math.test_asin.ASinTests.test_float) ... ok test_integer (db_functions.math.test_asin.ASinTests.test_integer) ... ok test_null (db_functions.math.test_asin.ASinTests.test_null) ... ok test_transform (db_functions.math.test_asin.ASinTests.test_transform) ... ok test_decimal (db_functions.math.test_atan2.ATan2Tests.test_decimal) ... ok test_float (db_functions.math.test_atan2.ATan2Tests.test_float) ... ok test_integer (db_functions.math.test_atan2.ATan2Tests.test_integer) ... ok test_null (db_functions.math.test_atan2.ATan2Tests.test_null) ... ok test_extract_day_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_day_func) ... ok test_extract_duration (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_duration) ... skipped "Database doesn't support feature(s): has_native_duration_field" test_extract_duration_unsupported_lookups (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_duration_unsupported_lookups) ... ok test_extract_duration_without_native_duration_field (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_duration_without_native_duration_field) ... ok test_extract_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_func) ... ok test_extract_hour_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_hour_func) ... ok test_extract_iso_weekday_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_iso_weekday_func) ... ok test_extract_iso_year_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_iso_year_func) ... ok test_extract_iso_year_func_boundaries (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_iso_year_func_boundaries) ... ok test_extract_lookup_name_sql_injection (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_lookup_name_sql_injection) ... ok test_extract_minute_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_minute_func) ... ok test_extract_month_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_month_func) ... ok test_extract_none (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_none) ... ok test_extract_quarter_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_quarter_func) ... ok test_extract_quarter_func_boundaries (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_quarter_func_boundaries) ... ok test_extract_second_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_second_func) ... ok test_extract_week_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_week_func) ... ok test_extract_week_func_boundaries (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_week_func_boundaries) ... ok test_extract_weekday_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_weekday_func) ... ok test_extract_year_exact_lookup (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_year_exact_lookup) Extract year uses a BETWEEN filter to compare the year to allow indexes ... ok test_extract_year_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_year_func) ... ok test_extract_year_greaterthan_lookup (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_year_greaterthan_lookup) ... ok test_extract_year_lessthan_lookup (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_extract_year_lessthan_lookup) ... ok test_trunc_date_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_date_func) ... ok test_trunc_date_none (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_date_none) ... ok test_trunc_day_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_day_func) ... ok test_trunc_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_func) ... ok test_trunc_hour_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_hour_func) ... ok test_trunc_lookup_name_sql_injection (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_lookup_name_sql_injection) ... ok test_trunc_minute_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_minute_func) ... ok test_trunc_month_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_month_func) ... ok test_trunc_none (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_none) ... ok test_trunc_quarter_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_quarter_func) ... ok test_trunc_second_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_second_func) ... ok test_trunc_subquery_with_parameters (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_subquery_with_parameters) ... ok test_trunc_time_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_time_func) ... ok test_trunc_time_none (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_time_none) ... ok test_trunc_week_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_week_func) ... ok test_trunc_year_func (db_functions.datetime.test_extract_trunc.DateFunctionTests.test_trunc_year_func) ... ok test_decimal (db_functions.math.test_ceil.CeilTests.test_decimal) ... ok test_float (db_functions.math.test_ceil.CeilTests.test_float) ... ok test_integer (db_functions.math.test_ceil.CeilTests.test_integer) ... ok test_null (db_functions.math.test_ceil.CeilTests.test_null) ... ok test_transform (db_functions.math.test_ceil.CeilTests.test_transform) ... ok test_decimal (db_functions.math.test_cos.CosTests.test_decimal) ... ok test_float (db_functions.math.test_cos.CosTests.test_float) ... ok test_integer (db_functions.math.test_cos.CosTests.test_integer) ... ok test_null (db_functions.math.test_cos.CosTests.test_null) ... ok test_transform (db_functions.math.test_cos.CosTests.test_transform) ... ok test_decimal (db_functions.math.test_cot.CotTests.test_decimal) ... ok test_float (db_functions.math.test_cot.CotTests.test_float) ... ok test_integer (db_functions.math.test_cot.CotTests.test_integer) ... ok test_null (db_functions.math.test_cot.CotTests.test_null) ... ok test_transform (db_functions.math.test_cot.CotTests.test_transform) ... ok test_decimal (db_functions.math.test_degrees.DegreesTests.test_decimal) ... ok test_float (db_functions.math.test_degrees.DegreesTests.test_float) ... ok test_integer (db_functions.math.test_degrees.DegreesTests.test_integer) ... ok test_null (db_functions.math.test_degrees.DegreesTests.test_null) ... ok test_transform (db_functions.math.test_degrees.DegreesTests.test_transform) ... ok test_decimal (db_functions.math.test_floor.FloorTests.test_decimal) ... ok test_float (db_functions.math.test_floor.FloorTests.test_float) ... ok test_integer (db_functions.math.test_floor.FloorTests.test_integer) ... ok test_null (db_functions.math.test_floor.FloorTests.test_null) ... ok test_transform (db_functions.math.test_floor.FloorTests.test_transform) ... ok test_decimal (db_functions.math.test_exp.ExpTests.test_decimal) ... ok test_float (db_functions.math.test_exp.ExpTests.test_float) ... ok test_integer (db_functions.math.test_exp.ExpTests.test_integer) ... ok test_null (db_functions.math.test_exp.ExpTests.test_null) ... ok test_transform (db_functions.math.test_exp.ExpTests.test_transform) ... ok test_decimal (db_functions.math.test_mod.ModTests.test_decimal) ... ok test_float (db_functions.math.test_mod.ModTests.test_float) ... ok test_integer (db_functions.math.test_mod.ModTests.test_integer) ... ok test_null (db_functions.math.test_mod.ModTests.test_null) ... ok test_decimal (db_functions.math.test_log.LogTests.test_decimal) ... ok test_float (db_functions.math.test_log.LogTests.test_float) ... ok test_integer (db_functions.math.test_log.LogTests.test_integer) ... ok test_null (db_functions.math.test_log.LogTests.test_null) ... ok test_decimal (db_functions.math.test_ln.LnTests.test_decimal) ... ok test_float (db_functions.math.test_ln.LnTests.test_float) ... ok test_integer (db_functions.math.test_ln.LnTests.test_integer) ... ok test_null (db_functions.math.test_ln.LnTests.test_null) ... ok test_transform (db_functions.math.test_ln.LnTests.test_transform) ... ok test (db_functions.math.test_pi.PiTests.test) ... ok test_extract_day_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_day_func) ... ok test_extract_duration (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_duration) ... skipped "Database doesn't support feature(s): has_native_duration_field" test_extract_duration_unsupported_lookups (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_duration_unsupported_lookups) ... ok test_extract_duration_without_native_duration_field (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_duration_without_native_duration_field) ... ok test_extract_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_func) ... ok test_extract_func_explicit_timezone_priority (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_func_explicit_timezone_priority) ... ok test_extract_func_with_timezone (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_func_with_timezone) ... ok test_extract_hour_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_hour_func) ... ok test_extract_invalid_field_with_timezone (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_invalid_field_with_timezone) ... ok test_extract_iso_weekday_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_iso_weekday_func) ... ok test_extract_iso_year_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_iso_year_func) ... ok test_extract_iso_year_func_boundaries (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_iso_year_func_boundaries) ... ok test_extract_lookup_name_sql_injection (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_lookup_name_sql_injection) ... ok test_extract_minute_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_minute_func) ... ok test_extract_month_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_month_func) ... ok test_extract_none (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_none) ... ok test_extract_quarter_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_quarter_func) ... ok test_extract_quarter_func_boundaries (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_quarter_func_boundaries) ... ok test_extract_second_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_second_func) ... ok test_extract_week_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_week_func) ... ok test_extract_week_func_boundaries (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_week_func_boundaries) ... ok test_extract_weekday_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_weekday_func) ... ok test_extract_year_exact_lookup (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_year_exact_lookup) Extract year uses a BETWEEN filter to compare the year to allow indexes ... ok test_extract_year_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_year_func) ... ok test_extract_year_greaterthan_lookup (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_year_greaterthan_lookup) ... ok test_extract_year_lessthan_lookup (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_extract_year_lessthan_lookup) ... ok test_trunc_ambiguous_and_invalid_times (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_ambiguous_and_invalid_times) ... ok test_trunc_date_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_date_func) ... ok test_trunc_date_none (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_date_none) ... ok test_trunc_day_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_day_func) ... ok test_trunc_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_func) ... ok test_trunc_func_with_timezone (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_func_with_timezone) If the truncated datetime transitions to a different offset (daylight ... ok test_trunc_hour_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_hour_func) ... ok test_trunc_invalid_field_with_timezone (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_invalid_field_with_timezone) ... ok test_trunc_lookup_name_sql_injection (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_lookup_name_sql_injection) ... ok test_trunc_minute_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_minute_func) ... ok test_trunc_month_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_month_func) ... ok test_trunc_none (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_none) ... ok test_trunc_quarter_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_quarter_func) ... ok test_trunc_second_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_second_func) ... ok test_trunc_subquery_with_parameters (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_subquery_with_parameters) ... ok test_trunc_time_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_time_func) ... ok test_trunc_time_none (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_time_none) ... ok test_trunc_timezone_applied_before_truncation (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_timezone_applied_before_truncation) ... ok test_trunc_week_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_week_func) ... ok test_trunc_year_func (db_functions.datetime.test_extract_trunc.DateFunctionWithTimeZoneTests.test_trunc_year_func) ... ok test (db_functions.math.test_random.RandomTests.test) ... ok test_decimal (db_functions.math.test_power.PowerTests.test_decimal) ... ok test_float (db_functions.math.test_power.PowerTests.test_float) ... ok test_integer (db_functions.math.test_power.PowerTests.test_integer) ... ok test_null (db_functions.math.test_power.PowerTests.test_null) ... ok test_decimal (db_functions.math.test_round.RoundTests.test_decimal) ... ok test_float (db_functions.math.test_round.RoundTests.test_float) ... ok test_integer (db_functions.math.test_round.RoundTests.test_integer) ... ok test_null (db_functions.math.test_round.RoundTests.test_null) ... ok test_transform (db_functions.math.test_round.RoundTests.test_transform) ... ok test_decimal (db_functions.math.test_radians.RadiansTests.test_decimal) ... ok test_float (db_functions.math.test_radians.RadiansTests.test_float) ... ok test_integer (db_functions.math.test_radians.RadiansTests.test_integer) ... ok test_null (db_functions.math.test_radians.RadiansTests.test_null) ... ok test_transform (db_functions.math.test_radians.RadiansTests.test_transform) ... ok test_decimal (db_functions.math.test_sign.SignTests.test_decimal) ... ok test_float (db_functions.math.test_sign.SignTests.test_float) ... ok test_integer (db_functions.math.test_sign.SignTests.test_integer) ... ok test_null (db_functions.math.test_sign.SignTests.test_null) ... ok test_transform (db_functions.math.test_sign.SignTests.test_transform) ... ok test_decimal (db_functions.math.test_sin.SinTests.test_decimal) ... ok test_float (db_functions.math.test_sin.SinTests.test_float) ... ok test_integer (db_functions.math.test_sin.SinTests.test_integer) ... ok test_null (db_functions.math.test_sin.SinTests.test_null) ... ok test_transform (db_functions.math.test_sin.SinTests.test_transform) ... ok test_decimal (db_functions.math.test_sqrt.SqrtTests.test_decimal) ... ok test_float (db_functions.math.test_sqrt.SqrtTests.test_float) ... ok test_integer (db_functions.math.test_sqrt.SqrtTests.test_integer) ... ok test_null (db_functions.math.test_sqrt.SqrtTests.test_null) ... ok test_transform (db_functions.math.test_sqrt.SqrtTests.test_transform) ... ok test_basic (db_functions.text.test_chr.ChrTests.test_basic) ... ok test_non_ascii (db_functions.text.test_chr.ChrTests.test_non_ascii) ... ok test_transform (db_functions.text.test_chr.ChrTests.test_transform) ... ok test_func_transform_bilateral (db_functions.tests.FunctionTests.test_func_transform_bilateral) ... ok test_func_transform_bilateral_multivalue (db_functions.tests.FunctionTests.test_func_transform_bilateral_multivalue) ... ok test_function_as_filter (db_functions.tests.FunctionTests.test_function_as_filter) ... ok test_nested_function_ordering (db_functions.tests.FunctionTests.test_nested_function_ordering) ... ok test_decimal (db_functions.math.test_tan.TanTests.test_decimal) ... ok test_float (db_functions.math.test_tan.TanTests.test_float) ... ok test_integer (db_functions.math.test_tan.TanTests.test_integer) ... ok test_null (db_functions.math.test_tan.TanTests.test_null) ... ok test_transform (db_functions.math.test_tan.TanTests.test_transform) ... ok test_basic (db_functions.text.test_left.LeftTests.test_basic) ... ok test_expressions (db_functions.text.test_left.LeftTests.test_expressions) ... ok test_invalid_length (db_functions.text.test_left.LeftTests.test_invalid_length) ... ok test_basic (db_functions.text.test_length.LengthTests.test_basic) ... ok test_ordering (db_functions.text.test_length.LengthTests.test_ordering) ... ok test_transform (db_functions.text.test_length.LengthTests.test_transform) ... ok test_basic (db_functions.text.test_lower.LowerTests.test_basic) ... ok test_num_args (db_functions.text.test_lower.LowerTests.test_num_args) ... ok test_transform (db_functions.text.test_lower.LowerTests.test_transform) ... ok test_basic (db_functions.text.test_md5.MD5Tests.test_basic) ... ok test_transform (db_functions.text.test_md5.MD5Tests.test_transform) ... ok test_basic (db_functions.text.test_concat.ConcatTests.test_basic) ... ok test_coalesce_idempotent (db_functions.text.test_concat.ConcatTests.test_coalesce_idempotent) ... ok test_gt_two_expressions (db_functions.text.test_concat.ConcatTests.test_gt_two_expressions) ... ok test_many (db_functions.text.test_concat.ConcatTests.test_many) ... ok test_mixed_char_text (db_functions.text.test_concat.ConcatTests.test_mixed_char_text) ... ok test_sql_generation_idempotency (db_functions.text.test_concat.ConcatTests.test_sql_generation_idempotency) ... ok test_basic (db_functions.text.test_ord.OrdTests.test_basic) ... ok test_transform (db_functions.text.test_ord.OrdTests.test_transform) ... ok test_basic (db_functions.text.test_repeat.RepeatTests.test_basic) ... ok test_negative_number (db_functions.text.test_repeat.RepeatTests.test_negative_number) ... ok test_combined_with_length (db_functions.text.test_pad.PadTests.test_combined_with_length) ... ok test_pad (db_functions.text.test_pad.PadTests.test_pad) ... ok test_pad_negative_length (db_functions.text.test_pad.PadTests.test_pad_negative_length) ... ok test_basic (db_functions.text.test_reverse.ReverseTests.test_basic) ... ok test_expressions (db_functions.text.test_reverse.ReverseTests.test_expressions) ... ok test_null (db_functions.text.test_reverse.ReverseTests.test_null) ... ok test_transform (db_functions.text.test_reverse.ReverseTests.test_transform) ... ok test_case_sensitive (db_functions.text.test_replace.ReplaceTests.test_case_sensitive) ... ok test_replace_expression (db_functions.text.test_replace.ReplaceTests.test_replace_expression) ... ok test_replace_with_default_arg (db_functions.text.test_replace.ReplaceTests.test_replace_with_default_arg) ... ok test_replace_with_empty_string (db_functions.text.test_replace.ReplaceTests.test_replace_with_empty_string) ... ok test_update (db_functions.text.test_replace.ReplaceTests.test_update) ... ok test_basic (db_functions.text.test_right.RightTests.test_basic) ... ok test_expressions (db_functions.text.test_right.RightTests.test_expressions) ... ok test_invalid_length (db_functions.text.test_right.RightTests.test_invalid_length) ... ok test_basic (db_functions.text.test_sha224.SHA224Tests.test_basic) ... ok test_transform (db_functions.text.test_sha224.SHA224Tests.test_transform) ... ok test_unsupported (db_functions.text.test_sha224.SHA224Tests.test_unsupported) ... skipped "Oracle doesn't support SHA224." test_basic (db_functions.text.test_sha1.SHA1Tests.test_basic) ... ok test_transform (db_functions.text.test_sha1.SHA1Tests.test_transform) ... ok test_basic (db_functions.text.test_sha256.SHA256Tests.test_basic) ... ok test_transform (db_functions.text.test_sha256.SHA256Tests.test_transform) ... ok test_basic (db_functions.text.test_sha384.SHA384Tests.test_basic) ... ok test_transform (db_functions.text.test_sha384.SHA384Tests.test_transform) ... ok test_basic (db_functions.text.test_sha512.SHA512Tests.test_basic) ... ok test_transform (db_functions.text.test_sha512.SHA512Tests.test_transform) ... ok test_trim (db_functions.text.test_trim.TrimTests.test_trim) ... ok test_trim_transform (db_functions.text.test_trim.TrimTests.test_trim_transform) ... ok test_basic (db_functions.text.test_upper.UpperTests.test_basic) ... ok test_transform (db_functions.text.test_upper.UpperTests.test_transform) ... ok test_basic (db_functions.text.test_substr.SubstrTests.test_basic) ... ok test_expressions (db_functions.text.test_substr.SubstrTests.test_expressions) ... ok test_pos_gt_zero (db_functions.text.test_substr.SubstrTests.test_pos_gt_zero) ... ok test_start (db_functions.text.test_substr.SubstrTests.test_start) ... ok test_annotate_charfield (db_functions.text.test_strindex.StrIndexTests.test_annotate_charfield) ... ok test_annotate_textfield (db_functions.text.test_strindex.StrIndexTests.test_annotate_textfield) ... ok test_filtering (db_functions.text.test_strindex.StrIndexTests.test_filtering) ... ok test_order_by (db_functions.text.test_strindex.StrIndexTests.test_order_by) ... ok test_unicode_values (db_functions.text.test_strindex.StrIndexTests.test_unicode_values) ... ok test_choices (m2m_through.tests.M2mThroughToFieldsTests.test_choices) ... ok test_retrieval (m2m_through.tests.M2mThroughToFieldsTests.test_retrieval) ... ok test_add_on_symmetrical_m2m_with_intermediate_model (m2m_through.tests.M2mThroughReferentialTests.test_add_on_symmetrical_m2m_with_intermediate_model) ... ok test_self_referential_empty_qs (m2m_through.tests.M2mThroughReferentialTests.test_self_referential_empty_qs) ... ok test_self_referential_non_symmetrical_both (m2m_through.tests.M2mThroughReferentialTests.test_self_referential_non_symmetrical_both) ... ok test_self_referential_non_symmetrical_clear_first_side (m2m_through.tests.M2mThroughReferentialTests.test_self_referential_non_symmetrical_clear_first_side) ... ok test_self_referential_non_symmetrical_first_side (m2m_through.tests.M2mThroughReferentialTests.test_self_referential_non_symmetrical_first_side) ... ok test_self_referential_non_symmetrical_second_side (m2m_through.tests.M2mThroughReferentialTests.test_self_referential_non_symmetrical_second_side) ... ok test_self_referential_symmetrical (m2m_through.tests.M2mThroughReferentialTests.test_self_referential_symmetrical) ... ok test_set_on_symmetrical_m2m_with_intermediate_model (m2m_through.tests.M2mThroughReferentialTests.test_set_on_symmetrical_m2m_with_intermediate_model) ... ok test_through_fields_self_referential (m2m_through.tests.M2mThroughReferentialTests.test_through_fields_self_referential) ... ok test_access_fks_with_select_related (select_related.tests.SelectRelatedTests.test_access_fks_with_select_related) A select_related() call will fill in those related objects without any ... ok test_access_fks_without_select_related (select_related.tests.SelectRelatedTests.test_access_fks_without_select_related) Normally, accessing FKs doesn't fill in related objects ... ok test_certain_fields (select_related.tests.SelectRelatedTests.test_certain_fields) The optional fields passed to select_related() control which related ... ok test_chaining (select_related.tests.SelectRelatedTests.test_chaining) ... ok test_field_traversal (select_related.tests.SelectRelatedTests.test_field_traversal) ... ok test_list_with_depth (select_related.tests.SelectRelatedTests.test_list_with_depth) Passing a relationship field lookup specifier to select_related() will ... ok test_list_with_select_related (select_related.tests.SelectRelatedTests.test_list_with_select_related) select_related() applies to entire lists, not just items. ... ok test_list_without_select_related (select_related.tests.SelectRelatedTests.test_list_without_select_related) ... ok test_more_certain_fields (select_related.tests.SelectRelatedTests.test_more_certain_fields) In this case, we explicitly say to select the 'genus' and ... ok test_none_clears_list (select_related.tests.SelectRelatedTests.test_none_clears_list) ... ok test_reverse_relation_caching (select_related.tests.SelectRelatedTests.test_reverse_relation_caching) ... ok test_select_related_after_values (select_related.tests.SelectRelatedTests.test_select_related_after_values) Running select_related() after calling values() raises a TypeError ... ok test_select_related_after_values_list (select_related.tests.SelectRelatedTests.test_select_related_after_values_list) Running select_related() after calling values_list() raises a TypeError ... ok test_select_related_with_extra (select_related.tests.SelectRelatedTests.test_select_related_with_extra) ... ok test_existing_join_not_promoted (aggregation_regress.tests.JoinPromotionTests.test_existing_join_not_promoted) ... ok test_non_nullable_fk_not_promoted (aggregation_regress.tests.JoinPromotionTests.test_non_nullable_fk_not_promoted) ... ok test_ticket_21150 (aggregation_regress.tests.JoinPromotionTests.test_ticket_21150) ... ok test_ticket_24748 (aggregation_regress.tests.SelfReferentialFKTests.test_ticket_24748) ... ok test_create_save_error (model_forms.test_uuid.ModelFormBaseTest.test_create_save_error) ... ok test_model_multiple_choice_field_uuid_pk (model_forms.test_uuid.ModelFormBaseTest.test_model_multiple_choice_field_uuid_pk) ... ok test_update_save_error (model_forms.test_uuid.ModelFormBaseTest.test_update_save_error) ... ok test_model_form_clean_applies_to_model (model_forms.tests.CustomCleanTests.test_model_form_clean_applies_to_model) Regression test for #12960. Make sure the cleaned_data returned from ... ok test_override_clean (model_forms.tests.CustomCleanTests.test_override_clean) Regression for #12596: Calling super from ModelForm.clean() should be ... ok test_clean_false (model_forms.tests.FileAndImageFieldTests.test_clean_false) If the ``clean`` method on a non-required FileField receives False as ... ok test_clean_false_required (model_forms.tests.FileAndImageFieldTests.test_clean_false_required) If the ``clean`` method on a required FileField receives False as the ... ok test_clear_and_file_contradiction (model_forms.tests.FileAndImageFieldTests.test_clear_and_file_contradiction) If the user submits a new file upload AND checks the clear checkbox, ... ok test_custom_file_field_save (model_forms.tests.FileAndImageFieldTests.test_custom_file_field_save) Regression for #11149: save_form_data should be called only once ... ok test_file_field_data (model_forms.tests.FileAndImageFieldTests.test_file_field_data) ... ok test_file_field_multiple_save (model_forms.tests.FileAndImageFieldTests.test_file_field_multiple_save) Simulate a file upload and check how many times Model.save() gets ... ok test_file_path_field_blank (model_forms.tests.FileAndImageFieldTests.test_file_path_field_blank) FilePathField(blank=True) includes the empty option. ... ok test_filefield_required_false (model_forms.tests.FileAndImageFieldTests.test_filefield_required_false) ... ok test_full_clear (model_forms.tests.FileAndImageFieldTests.test_full_clear) Integration happy-path test that a model FileField can actually be set ... ok test_image_field (model_forms.tests.FileAndImageFieldTests.test_image_field) ... ok test_render_empty_file_field (model_forms.tests.FileAndImageFieldTests.test_render_empty_file_field) ... ok test_add_on_m2m_with_intermediate_model (m2m_through.tests.M2mThroughTests.test_add_on_m2m_with_intermediate_model) ... ok test_add_on_m2m_with_intermediate_model_callable_through_default (m2m_through.tests.M2mThroughTests.test_add_on_m2m_with_intermediate_model_callable_through_default) ... ok test_add_on_m2m_with_intermediate_model_value_required (m2m_through.tests.M2mThroughTests.test_add_on_m2m_with_intermediate_model_value_required) ... ok test_add_on_m2m_with_intermediate_model_value_required_fails (m2m_through.tests.M2mThroughTests.test_add_on_m2m_with_intermediate_model_value_required_fails) ... ok test_add_on_reverse_m2m_with_intermediate_model (m2m_through.tests.M2mThroughTests.test_add_on_reverse_m2m_with_intermediate_model) ... ok test_clear_on_reverse_removes_all_the_m2m_relationships (m2m_through.tests.M2mThroughTests.test_clear_on_reverse_removes_all_the_m2m_relationships) ... ok test_clear_removes_all_the_m2m_relationships (m2m_through.tests.M2mThroughTests.test_clear_removes_all_the_m2m_relationships) ... ok test_create_on_m2m_with_intermediate_model (m2m_through.tests.M2mThroughTests.test_create_on_m2m_with_intermediate_model) ... ok test_create_on_m2m_with_intermediate_model_callable_through_default (m2m_through.tests.M2mThroughTests.test_create_on_m2m_with_intermediate_model_callable_through_default) ... ok test_create_on_m2m_with_intermediate_model_value_required (m2m_through.tests.M2mThroughTests.test_create_on_m2m_with_intermediate_model_value_required) ... ok test_create_on_m2m_with_intermediate_model_value_required_fails (m2m_through.tests.M2mThroughTests.test_create_on_m2m_with_intermediate_model_value_required_fails) ... ok test_create_on_reverse_m2m_with_intermediate_model (m2m_through.tests.M2mThroughTests.test_create_on_reverse_m2m_with_intermediate_model) ... ok test_custom_related_name_doesnt_conflict_with_fky_related_name (m2m_through.tests.M2mThroughTests.test_custom_related_name_doesnt_conflict_with_fky_related_name) ... ok test_custom_related_name_forward_empty_qs (m2m_through.tests.M2mThroughTests.test_custom_related_name_forward_empty_qs) ... ok test_custom_related_name_forward_non_empty_qs (m2m_through.tests.M2mThroughTests.test_custom_related_name_forward_non_empty_qs) ... ok test_custom_related_name_reverse_empty_qs (m2m_through.tests.M2mThroughTests.test_custom_related_name_reverse_empty_qs) ... ok test_custom_related_name_reverse_non_empty_qs (m2m_through.tests.M2mThroughTests.test_custom_related_name_reverse_non_empty_qs) ... ok test_filter_on_intermediate_model (m2m_through.tests.M2mThroughTests.test_filter_on_intermediate_model) ... ok test_get_on_intermediate_model (m2m_through.tests.M2mThroughTests.test_get_on_intermediate_model) ... ok test_get_or_create_on_m2m_with_intermediate_model_value_required (m2m_through.tests.M2mThroughTests.test_get_or_create_on_m2m_with_intermediate_model_value_required) ... ok test_get_or_create_on_m2m_with_intermediate_model_value_required_fails (m2m_through.tests.M2mThroughTests.test_get_or_create_on_m2m_with_intermediate_model_value_required_fails) ... ok test_order_by_relational_field_through_model (m2m_through.tests.M2mThroughTests.test_order_by_relational_field_through_model) ... ok test_query_first_model_by_intermediate_model_attribute (m2m_through.tests.M2mThroughTests.test_query_first_model_by_intermediate_model_attribute) ... ok test_query_model_by_attribute_name_of_related_model (m2m_through.tests.M2mThroughTests.test_query_model_by_attribute_name_of_related_model) ... ok test_query_model_by_custom_related_name (m2m_through.tests.M2mThroughTests.test_query_model_by_custom_related_name) ... ok test_query_model_by_intermediate_can_return_non_unique_queryset (m2m_through.tests.M2mThroughTests.test_query_model_by_intermediate_can_return_non_unique_queryset) ... ok test_query_model_by_related_model_name (m2m_through.tests.M2mThroughTests.test_query_model_by_related_model_name) ... ok test_query_second_model_by_intermediate_model_attribute (m2m_through.tests.M2mThroughTests.test_query_second_model_by_intermediate_model_attribute) ... ok test_remove_on_m2m_with_intermediate_model (m2m_through.tests.M2mThroughTests.test_remove_on_m2m_with_intermediate_model) ... ok test_remove_on_m2m_with_intermediate_model_multiple (m2m_through.tests.M2mThroughTests.test_remove_on_m2m_with_intermediate_model_multiple) ... ok test_remove_on_reverse_m2m_with_intermediate_model (m2m_through.tests.M2mThroughTests.test_remove_on_reverse_m2m_with_intermediate_model) ... ok test_retrieve_intermediate_items (m2m_through.tests.M2mThroughTests.test_retrieve_intermediate_items) ... ok test_retrieve_reverse_intermediate_items (m2m_through.tests.M2mThroughTests.test_retrieve_reverse_intermediate_items) ... ok test_reverse_inherited_m2m_with_through_fields_list_hashable (m2m_through.tests.M2mThroughTests.test_reverse_inherited_m2m_with_through_fields_list_hashable) ... ok test_set_on_m2m_with_intermediate_model (m2m_through.tests.M2mThroughTests.test_set_on_m2m_with_intermediate_model) ... ok test_set_on_m2m_with_intermediate_model_callable_through_default (m2m_through.tests.M2mThroughTests.test_set_on_m2m_with_intermediate_model_callable_through_default) ... ok test_set_on_m2m_with_intermediate_model_value_required (m2m_through.tests.M2mThroughTests.test_set_on_m2m_with_intermediate_model_value_required) ... ok test_set_on_m2m_with_intermediate_model_value_required_fails (m2m_through.tests.M2mThroughTests.test_set_on_m2m_with_intermediate_model_value_required_fails) ... ok test_set_on_reverse_m2m_with_intermediate_model (m2m_through.tests.M2mThroughTests.test_set_on_reverse_m2m_with_intermediate_model) ... ok test_through_fields (m2m_through.tests.M2mThroughTests.test_through_fields) Relations with intermediary tables with multiple FKs ... ok test_update_or_create_on_m2m_with_intermediate_model_value_required (m2m_through.tests.M2mThroughTests.test_update_or_create_on_m2m_with_intermediate_model_value_required) ... ok test_update_or_create_on_m2m_with_intermediate_model_value_required_fails (m2m_through.tests.M2mThroughTests.test_update_or_create_on_m2m_with_intermediate_model_value_required_fails) ... ok test_basics (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_basics) ... ok test_choice_iterator_passes_model_to_widget (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_choice_iterator_passes_model_to_widget) ... ok test_choices (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_choices) ... ok test_choices_bool (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_choices_bool) ... ok test_choices_bool_empty_label (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_choices_bool_empty_label) ... ok test_choices_freshness (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_choices_freshness) ... ok test_choices_not_fetched_when_not_rendering (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_choices_not_fetched_when_not_rendering) ... ok test_choices_radio_blank (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_choices_radio_blank) ... ok test_clean_model_instance (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_clean_model_instance) ... ok test_clean_to_field_name (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_clean_to_field_name) ... ok test_custom_choice_iterator_passes_model_to_widget (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_custom_choice_iterator_passes_model_to_widget) ... ok test_deepcopies_widget (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_deepcopies_widget) ... ok test_disabled_modelchoicefield (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_disabled_modelchoicefield) ... ok test_disabled_modelchoicefield_has_changed (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_disabled_modelchoicefield_has_changed) ... ok test_disabled_modelchoicefield_initial_model_instance (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_disabled_modelchoicefield_initial_model_instance) ... ok test_disabled_modelmultiplechoicefield_has_changed (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_disabled_modelmultiplechoicefield_has_changed) ... ok test_disabled_multiplemodelchoicefield (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_disabled_multiplemodelchoicefield) ... ok test_no_extra_query_when_accessing_attrs (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_no_extra_query_when_accessing_attrs) ModelChoiceField with RadioSelect widget doesn't produce unnecessary ... ok test_num_queries (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_num_queries) Widgets that render multiple subwidgets shouldn't make more than one ... ok test_overridable_choice_iterator (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_overridable_choice_iterator) Iterator defaults to ModelChoiceIterator and can be overridden with ... ok test_queryset_manager (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_queryset_manager) ... ok test_queryset_none (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_queryset_none) ... ok test_result_cache_not_shared (model_forms.test_modelchoicefield.ModelChoiceFieldTests.test_result_cache_not_shared) ... ok test_model_form_applies_localize_to_all_fields (model_forms.tests.LocalizedModelFormTest.test_model_form_applies_localize_to_all_fields) ... ok test_model_form_applies_localize_to_some_fields (model_forms.tests.LocalizedModelFormTest.test_model_form_applies_localize_to_some_fields) ... ok test_model_form_refuses_arbitrary_string (model_forms.tests.LocalizedModelFormTest.test_model_form_refuses_arbitrary_string) ... ok test_callable_called_each_time_form_is_instantiated (model_forms.tests.LimitChoicesToTests.test_callable_called_each_time_form_is_instantiated) ... ok test_custom_field_with_queryset_but_no_limit_choices_to (model_forms.tests.LimitChoicesToTests.test_custom_field_with_queryset_but_no_limit_choices_to) A custom field with a `queryset` attribute but no `limit_choices_to` ... ok test_fields_for_model_applies_limit_choices_to (model_forms.tests.LimitChoicesToTests.test_fields_for_model_applies_limit_choices_to) ... ok test_limit_choices_to_callable_for_fk_rel (model_forms.tests.LimitChoicesToTests.test_limit_choices_to_callable_for_fk_rel) A ForeignKey can use limit_choices_to as a callable (#2554). ... ok test_limit_choices_to_callable_for_m2m_rel (model_forms.tests.LimitChoicesToTests.test_limit_choices_to_callable_for_m2m_rel) A ManyToManyField can use limit_choices_to as a callable (#2554). ... ok test_limit_choices_to_no_duplicates (model_forms.tests.LimitChoicesToTests.test_limit_choices_to_no_duplicates) ... ok test_clean_does_deduplicate_values (model_forms.tests.ModelMultipleChoiceFieldTests.test_clean_does_deduplicate_values) ... ok test_model_multiple_choice_field (model_forms.tests.ModelMultipleChoiceFieldTests.test_model_multiple_choice_field) ... ok test_model_multiple_choice_field_22745 (model_forms.tests.ModelMultipleChoiceFieldTests.test_model_multiple_choice_field_22745) #22745 -- Make sure that ModelMultipleChoiceField with ... ok test_model_multiple_choice_number_of_queries (model_forms.tests.ModelMultipleChoiceFieldTests.test_model_multiple_choice_number_of_queries) ModelMultipleChoiceField does O(1) queries instead of O(n) (#10156). ... ok test_model_multiple_choice_required_false (model_forms.tests.ModelMultipleChoiceFieldTests.test_model_multiple_choice_required_false) ... ok test_model_multiple_choice_run_validators (model_forms.tests.ModelMultipleChoiceFieldTests.test_model_multiple_choice_run_validators) ModelMultipleChoiceField run given validators (#14144). ... ok test_model_multiple_choice_show_hidden_initial (model_forms.tests.ModelMultipleChoiceFieldTests.test_model_multiple_choice_show_hidden_initial) Test support of show_hidden_initial by ModelMultipleChoiceField. ... ok test_show_hidden_initial_changed_queries_efficiently (model_forms.tests.ModelMultipleChoiceFieldTests.test_show_hidden_initial_changed_queries_efficiently) ... ok test_to_field_name_with_initial_data (model_forms.tests.ModelMultipleChoiceFieldTests.test_to_field_name_with_initial_data) ... ok test_assignment_of_none (model_forms.tests.ModelOneToOneFieldTests.test_assignment_of_none) ... ok test_assignment_of_none_null_false (model_forms.tests.ModelOneToOneFieldTests.test_assignment_of_none_null_false) ... ok test_modelform_onetoonefield (model_forms.tests.ModelOneToOneFieldTests.test_modelform_onetoonefield) ... ok test_modelform_subclassed_model (model_forms.tests.ModelOneToOneFieldTests.test_modelform_subclassed_model) ... ok test_onetoonefield (model_forms.tests.ModelOneToOneFieldTests.test_onetoonefield) ... ok test_auto_id (model_forms.tests.ModelFormBasicTests.test_auto_id) ... ok test_base_form (model_forms.tests.ModelFormBasicTests.test_base_form) ... ok test_basic_creation (model_forms.tests.ModelFormBasicTests.test_basic_creation) ... ok test_custom_form_fields (model_forms.tests.ModelFormBasicTests.test_custom_form_fields) ... ok test_initial_values (model_forms.tests.ModelFormBasicTests.test_initial_values) ... ok test_m2m_editing (model_forms.tests.ModelFormBasicTests.test_m2m_editing) ... ok test_m2m_initial_callable (model_forms.tests.ModelFormBasicTests.test_m2m_initial_callable) Regression for #10349: A callable can be provided as the initial value for an m2m field ... ok test_multi_fields (model_forms.tests.ModelFormBasicTests.test_multi_fields) ... ok test_recleaning_model_form_instance (model_forms.tests.ModelFormBasicTests.test_recleaning_model_form_instance) Re-cleaning an instance that was added via a ModelForm shouldn't raise ... ok test_runtime_choicefield_populated (model_forms.tests.ModelFormBasicTests.test_runtime_choicefield_populated) ... ok test_save_commit_false (model_forms.tests.ModelFormBasicTests.test_save_commit_false) ... ok test_save_with_data_errors (model_forms.tests.ModelFormBasicTests.test_save_with_data_errors) ... ok test_subset_fields (model_forms.tests.ModelFormBasicTests.test_subset_fields) ... ok test_validate_foreign_key_to_model_with_overridden_manager (model_forms.tests.ModelFormBasicTests.test_validate_foreign_key_to_model_with_overridden_manager) ... ok test_validate_foreign_key_uses_default_manager (model_forms.tests.ModelFormBasicTests.test_validate_foreign_key_uses_default_manager) ... ok test_aggregate (aggregation_regress.tests.AggregationTests.test_aggregate) ... ok test_aggregate_annotation (aggregation_regress.tests.AggregationTests.test_aggregate_annotation) ... ok test_aggregate_duplicate_columns (aggregation_regress.tests.AggregationTests.test_aggregate_duplicate_columns) ... skipped "Database doesn't support any of the feature(s): allows_group_by_pk, allows_group_by_selected_pks" test_aggregate_duplicate_columns_only (aggregation_regress.tests.AggregationTests.test_aggregate_duplicate_columns_only) ... skipped "Database doesn't support any of the feature(s): allows_group_by_pk, allows_group_by_selected_pks" test_aggregate_duplicate_columns_select_related (aggregation_regress.tests.AggregationTests.test_aggregate_duplicate_columns_select_related) ... skipped "Database doesn't support any of the feature(s): allows_group_by_pk, allows_group_by_selected_pks" test_aggregate_fexpr (aggregation_regress.tests.AggregationTests.test_aggregate_fexpr) ... ok test_aggregate_on_relation (aggregation_regress.tests.AggregationTests.test_aggregate_on_relation) ... ok test_aggregate_unmanaged_model_as_tables (aggregation_regress.tests.AggregationTests.test_aggregate_unmanaged_model_as_tables) ... skipped "Database doesn't support feature(s): allows_group_by_selected_pks" test_aggregate_unmanaged_model_columns (aggregation_regress.tests.AggregationTests.test_aggregate_unmanaged_model_columns) Unmanaged models are sometimes used to represent database views which ... skipped "Database doesn't support feature(s): allows_group_by_selected_pks" test_aggregates_in_where_clause (aggregation_regress.tests.AggregationTests.test_aggregates_in_where_clause) Regression test for #12822: DatabaseError: aggregates not allowed in ... ok test_aggregates_in_where_clause_pre_eval (aggregation_regress.tests.AggregationTests.test_aggregates_in_where_clause_pre_eval) Regression test for #12822: DatabaseError: aggregates not allowed in ... ok test_aggregation_with_generic_reverse_relation (aggregation_regress.tests.AggregationTests.test_aggregation_with_generic_reverse_relation) Regression test for #10870: Aggregates with joins ignore extra ... ok test_allow_distinct (aggregation_regress.tests.AggregationTests.test_allow_distinct) ... ok test_annotate_and_join (aggregation_regress.tests.AggregationTests.test_annotate_and_join) ... ok test_annotate_distinct_aggregate (aggregation_regress.tests.AggregationTests.test_annotate_distinct_aggregate) ... ok test_annotate_joins (aggregation_regress.tests.AggregationTests.test_annotate_joins) The base table's join isn't promoted to LOUTER. This could ... ok test_annotate_on_relation (aggregation_regress.tests.AggregationTests.test_annotate_on_relation) ... ok test_annotate_reserved_word (aggregation_regress.tests.AggregationTests.test_annotate_reserved_word) Regression #18333 - Ensure annotated column name is properly quoted. ... ok test_annotate_values_list_flat (aggregation_regress.tests.AggregationTests.test_annotate_values_list_flat) Find ages that are shared by at least two authors. ... ok test_annotate_with_extra (aggregation_regress.tests.AggregationTests.test_annotate_with_extra) Regression test for #11916: Extra params + aggregation creates ... ok test_annotated_conditional_aggregate (aggregation_regress.tests.AggregationTests.test_annotated_conditional_aggregate) ... ok test_annotation (aggregation_regress.tests.AggregationTests.test_annotation) ... ok test_annotation_disjunction (aggregation_regress.tests.AggregationTests.test_annotation_disjunction) ... ok test_annotation_with_value (aggregation_regress.tests.AggregationTests.test_annotation_with_value) ... ok test_boolean_conversion (aggregation_regress.tests.AggregationTests.test_boolean_conversion) ... ok test_conditional_aggregate (aggregation_regress.tests.AggregationTests.test_conditional_aggregate) ... ok test_conditional_aggregate_on_complex_condition (aggregation_regress.tests.AggregationTests.test_conditional_aggregate_on_complex_condition) ... ok test_db_col_table (aggregation_regress.tests.AggregationTests.test_db_col_table) ... ok test_decimal_aggregate_annotation_filter (aggregation_regress.tests.AggregationTests.test_decimal_aggregate_annotation_filter) Filtering on an aggregate annotation with Decimal values should work. ... ok test_distinct_conditional_aggregate (aggregation_regress.tests.AggregationTests.test_distinct_conditional_aggregate) ... ok test_duplicate_alias (aggregation_regress.tests.AggregationTests.test_duplicate_alias) ... ok test_empty (aggregation_regress.tests.AggregationTests.test_empty) ... ok test_empty_filter_aggregate (aggregation_regress.tests.AggregationTests.test_empty_filter_aggregate) ... ok test_empty_filter_count (aggregation_regress.tests.AggregationTests.test_empty_filter_count) ... ok test_f_expression_annotation (aggregation_regress.tests.AggregationTests.test_f_expression_annotation) ... ok test_field_error (aggregation_regress.tests.AggregationTests.test_field_error) ... ok test_field_name_conflict (aggregation_regress.tests.AggregationTests.test_field_name_conflict) ... ok test_filtering_by_annotation_name (aggregation_regress.tests.AggregationTests.test_filtering_by_annotation_name) ... ok test_fk_attname_conflict (aggregation_regress.tests.AggregationTests.test_fk_attname_conflict) ... ok test_fobj_group_by (aggregation_regress.tests.AggregationTests.test_fobj_group_by) An F() object referring to related column works correctly in group by. ... ok test_having_group_by (aggregation_regress.tests.AggregationTests.test_having_group_by) ... ok test_having_subquery_select (aggregation_regress.tests.AggregationTests.test_having_subquery_select) ... ok test_m2m_name_conflict (aggregation_regress.tests.AggregationTests.test_m2m_name_conflict) ... ok test_more (aggregation_regress.tests.AggregationTests.test_more) ... ok test_more_more (aggregation_regress.tests.AggregationTests.test_more_more) ... ok test_more_more_more (aggregation_regress.tests.AggregationTests.test_more_more_more) ... ok test_name_expressions (aggregation_regress.tests.AggregationTests.test_name_expressions) ... ok test_name_filters (aggregation_regress.tests.AggregationTests.test_name_filters) ... ok test_negated_aggregation (aggregation_regress.tests.AggregationTests.test_negated_aggregation) ... ok test_none_call_before_aggregate (aggregation_regress.tests.AggregationTests.test_none_call_before_aggregate) ... ok test_pickle (aggregation_regress.tests.AggregationTests.test_pickle) ... ok test_quoting_aggregate_order_by (aggregation_regress.tests.AggregationTests.test_quoting_aggregate_order_by) ... ok test_reverse_join_trimming (aggregation_regress.tests.AggregationTests.test_reverse_join_trimming) ... ok test_reverse_relation_name_conflict (aggregation_regress.tests.AggregationTests.test_reverse_relation_name_conflict) ... ok test_sliced_conditional_aggregate (aggregation_regress.tests.AggregationTests.test_sliced_conditional_aggregate) ... ok test_stddev (aggregation_regress.tests.AggregationTests.test_stddev) ... ok test_ticket_11293 (aggregation_regress.tests.AggregationTests.test_ticket_11293) ... ok test_ticket_11293_q_immutable (aggregation_regress.tests.AggregationTests.test_ticket_11293_q_immutable) Splitting a q object to parts for where/having doesn't alter ... ok test_values_annotate_values (aggregation_regress.tests.AggregationTests.test_values_annotate_values) ... ok test_values_list_annotation_args_ordering (aggregation_regress.tests.AggregationTests.test_values_list_annotation_args_ordering) Annotate *args ordering should be preserved in values_list results. ... ok test_values_queryset_non_conflict (aggregation_regress.tests.AggregationTests.test_values_queryset_non_conflict) ... ok test_many_to_many (model_forms.tests.ModelToDictTests.test_many_to_many) Data for a ManyToManyField is a list rather than a lazy QuerySet. ... ok test_callable_field_default (model_forms.tests.OtherModelFormTests.test_callable_field_default) ... ok test_choices_type (model_forms.tests.OtherModelFormTests.test_choices_type) ... ok test_foreignkeys_which_use_to_field (model_forms.tests.OtherModelFormTests.test_foreignkeys_which_use_to_field) ... ok test_iterable_model_m2m (model_forms.tests.OtherModelFormTests.test_iterable_model_m2m) ... ok test_media_on_modelform (model_forms.tests.OtherModelFormTests.test_media_on_modelform) ... ok test_model_field_that_returns_none_to_exclude_itself_with_explicit_fields (model_forms.tests.OtherModelFormTests.test_model_field_that_returns_none_to_exclude_itself_with_explicit_fields) ... ok test_prefetch_related_queryset (model_forms.tests.OtherModelFormTests.test_prefetch_related_queryset) ModelChoiceField should respect a prefetch_related() on its queryset. ... ok test_abstract_inherited_unique (model_forms.tests.UniqueTest.test_abstract_inherited_unique) ... ok test_abstract_inherited_unique_together (model_forms.tests.UniqueTest.test_abstract_inherited_unique_together) ... ok test_explicitpk_unique (model_forms.tests.UniqueTest.test_explicitpk_unique) Ensure keys and blank character strings are tested for uniqueness. ... ok test_explicitpk_unspecified (model_forms.tests.UniqueTest.test_explicitpk_unspecified) Test for primary_key being in the form and failing validation. ... ok test_inherited_unique (model_forms.tests.UniqueTest.test_inherited_unique) ... ok test_inherited_unique_for_date (model_forms.tests.UniqueTest.test_inherited_unique_for_date) ... ok test_inherited_unique_together (model_forms.tests.UniqueTest.test_inherited_unique_together) ... ok test_multiple_field_unique_together (model_forms.tests.UniqueTest.test_multiple_field_unique_together) When the same field is involved in multiple unique_together ... ok test_override_unique_for_date_message (model_forms.tests.UniqueTest.test_override_unique_for_date_message) ... ok test_override_unique_message (model_forms.tests.UniqueTest.test_override_unique_message) ... ok test_override_unique_together_message (model_forms.tests.UniqueTest.test_override_unique_together_message) ... ok test_simple_unique (model_forms.tests.UniqueTest.test_simple_unique) ... ok test_unique_for_date (model_forms.tests.UniqueTest.test_unique_for_date) ... ok test_unique_for_date_in_exclude (model_forms.tests.UniqueTest.test_unique_for_date_in_exclude) If the date for unique_for_* constraints is excluded from the ... ok test_unique_for_date_with_nullable_date (model_forms.tests.UniqueTest.test_unique_for_date_with_nullable_date) ... ok test_unique_null (model_forms.tests.UniqueTest.test_unique_null) ... ok test_unique_together (model_forms.tests.UniqueTest.test_unique_together) ModelForm test of unique_together constraint ... ok test_unique_together_exclusion (model_forms.tests.UniqueTest.test_unique_together_exclusion) Forms don't validate unique_together constraints when only part of the ... ok test_article_form (model_forms.tests.ModelFormBaseTest.test_article_form) ... ok test_bad_form (model_forms.tests.ModelFormBaseTest.test_bad_form) ... ok test_base_form (model_forms.tests.ModelFormBaseTest.test_base_form) ... ok test_blank_false_with_null_true_foreign_key_field (model_forms.tests.ModelFormBaseTest.test_blank_false_with_null_true_foreign_key_field) A ModelForm with a model having ForeignKey(blank=False, null=True) ... ok test_blank_foreign_key_with_radio (model_forms.tests.ModelFormBaseTest.test_blank_foreign_key_with_radio) ... ok test_blank_with_null_foreign_key_field (model_forms.tests.ModelFormBaseTest.test_blank_with_null_foreign_key_field) #13776 -- ModelForm's with models having a FK set to null=False and ... ok test_confused_form (model_forms.tests.ModelFormBaseTest.test_confused_form) ... ok test_default_filefield (model_forms.tests.ModelFormBaseTest.test_default_filefield) ... ok test_default_not_populated_on_checkboxselectmultiple (model_forms.tests.ModelFormBaseTest.test_default_not_populated_on_checkboxselectmultiple) ... ok test_default_not_populated_on_non_empty_value_in_cleaned_data (model_forms.tests.ModelFormBaseTest.test_default_not_populated_on_non_empty_value_in_cleaned_data) ... ok test_default_not_populated_on_optional_checkbox_input (model_forms.tests.ModelFormBaseTest.test_default_not_populated_on_optional_checkbox_input) ... ok test_default_not_populated_on_selectmultiple (model_forms.tests.ModelFormBaseTest.test_default_not_populated_on_selectmultiple) ... ok test_default_populated_on_optional_field (model_forms.tests.ModelFormBaseTest.test_default_populated_on_optional_field) ... ok test_default_selectdatewidget (model_forms.tests.ModelFormBaseTest.test_default_selectdatewidget) ... ok test_default_splitdatetime_field (model_forms.tests.ModelFormBaseTest.test_default_splitdatetime_field) ... ok test_empty_fields_on_modelform (model_forms.tests.ModelFormBaseTest.test_empty_fields_on_modelform) No fields on a ModelForm should actually result in no fields. ... ok test_empty_fields_to_construct_instance (model_forms.tests.ModelFormBaseTest.test_empty_fields_to_construct_instance) No fields should be set on a model instance if construct_instance receives fields=(). ... ok test_empty_fields_to_fields_for_model (model_forms.tests.ModelFormBaseTest.test_empty_fields_to_fields_for_model) An argument of fields=() to fields_for_model should return an empty dictionary ... ok test_exclude_and_validation (model_forms.tests.ModelFormBaseTest.test_exclude_and_validation) ... ok test_exclude_fields (model_forms.tests.ModelFormBaseTest.test_exclude_fields) ... ok test_exclude_fields_with_string (model_forms.tests.ModelFormBaseTest.test_exclude_fields_with_string) ... ok test_exclude_nonexistent_field (model_forms.tests.ModelFormBaseTest.test_exclude_nonexistent_field) ... ok test_extra_declared_field_model_form (model_forms.tests.ModelFormBaseTest.test_extra_declared_field_model_form) ... ok test_extra_field_model_form (model_forms.tests.ModelFormBaseTest.test_extra_field_model_form) ... ok test_extra_field_modelform_factory (model_forms.tests.ModelFormBaseTest.test_extra_field_modelform_factory) ... ok test_extra_fields (model_forms.tests.ModelFormBaseTest.test_extra_fields) ... ok test_invalid_meta_model (model_forms.tests.ModelFormBaseTest.test_invalid_meta_model) ... ok test_limit_fields_with_string (model_forms.tests.ModelFormBaseTest.test_limit_fields_with_string) ... ok test_limit_nonexistent_field (model_forms.tests.ModelFormBaseTest.test_limit_nonexistent_field) ... ok test_missing_fields_attribute (model_forms.tests.ModelFormBaseTest.test_missing_fields_attribute) ... ok test_mixmodel_form (model_forms.tests.ModelFormBaseTest.test_mixmodel_form) ... ok test_no_model_class (model_forms.tests.ModelFormBaseTest.test_no_model_class) ... ok test_non_blank_foreign_key_with_radio (model_forms.tests.ModelFormBaseTest.test_non_blank_foreign_key_with_radio) ... ok test_orderfields2_form (model_forms.tests.ModelFormBaseTest.test_orderfields2_form) ... ok test_orderfields_form (model_forms.tests.ModelFormBaseTest.test_orderfields_form) ... ok test_override_field (model_forms.tests.ModelFormBaseTest.test_override_field) ... ok test_prefixed_form_with_default_field (model_forms.tests.ModelFormBaseTest.test_prefixed_form_with_default_field) ... ok test_renderer_kwarg (model_forms.tests.ModelFormBaseTest.test_renderer_kwarg) ... ok test_replace_field (model_forms.tests.ModelFormBaseTest.test_replace_field) ... ok test_replace_field_variant_2 (model_forms.tests.ModelFormBaseTest.test_replace_field_variant_2) ... ok test_replace_field_variant_3 (model_forms.tests.ModelFormBaseTest.test_replace_field_variant_3) ... ok test_save_blank_false_with_required_false (model_forms.tests.ModelFormBaseTest.test_save_blank_false_with_required_false) A ModelForm with a model with a field set to blank=False and the form ... ok test_save_blank_null_unique_charfield_saves_null (model_forms.tests.ModelFormBaseTest.test_save_blank_null_unique_charfield_saves_null) ... ok test_subcategory_form (model_forms.tests.ModelFormBaseTest.test_subcategory_form) ... ok test_subclassmeta_form (model_forms.tests.ModelFormBaseTest.test_subclassmeta_form) ... ok test_altering_serialized_output (serializers.test_json.JsonSerializerTestCase.test_altering_serialized_output) The ability to create new objects by modifying serialized content. ... ok test_custom_encoder (serializers.test_json.JsonSerializerTestCase.test_custom_encoder) ... ok test_custom_field_serialization (serializers.test_json.JsonSerializerTestCase.test_custom_field_serialization) Custom fields serialize and deserialize intact ... ok test_deferred_field_serialization (serializers.test_json.JsonSerializerTestCase.test_deferred_field_serialization) ... ok test_deserialize_force_insert (serializers.test_json.JsonSerializerTestCase.test_deserialize_force_insert) Deserialized content can be saved with force_insert as a parameter. ... ok test_deterministic_mapping_ordering (serializers.test_json.JsonSerializerTestCase.test_deterministic_mapping_ordering) Mapping such as fields should be deterministically ordered. (#24558) ... ok test_float_serialization (serializers.test_json.JsonSerializerTestCase.test_float_serialization) Float values serialize and deserialize intact ... ok test_helpful_error_message_for_foreign_keys (serializers.test_json.JsonSerializerTestCase.test_helpful_error_message_for_foreign_keys) Invalid foreign keys with a natural key should throw a helpful error ... ok test_helpful_error_message_for_many2many_natural1 (serializers.test_json.JsonSerializerTestCase.test_helpful_error_message_for_many2many_natural1) Invalid many-to-many keys should throw a helpful error message. ... ok test_helpful_error_message_for_many2many_natural2 (serializers.test_json.JsonSerializerTestCase.test_helpful_error_message_for_many2many_natural2) Invalid many-to-many keys should throw a helpful error message. This ... ok test_helpful_error_message_for_many2many_non_natural (serializers.test_json.JsonSerializerTestCase.test_helpful_error_message_for_many2many_non_natural) Invalid many-to-many keys should throw a helpful error message. ... ok test_helpful_error_message_for_many2many_not_iterable (serializers.test_json.JsonSerializerTestCase.test_helpful_error_message_for_many2many_not_iterable) Not iterable many-to-many field value throws a helpful error message. ... ok test_helpful_error_message_invalid_field (serializers.test_json.JsonSerializerTestCase.test_helpful_error_message_invalid_field) If there is an invalid field value, the error message should contain ... ok test_helpful_error_message_invalid_pk (serializers.test_json.JsonSerializerTestCase.test_helpful_error_message_invalid_pk) If there is an invalid primary key, the error message should contain ... ok test_indentation_whitespace (serializers.test_json.JsonSerializerTestCase.test_indentation_whitespace) ... ok test_json_deserializer_exception (serializers.test_json.JsonSerializerTestCase.test_json_deserializer_exception) ... ok test_one_to_one_as_pk (serializers.test_json.JsonSerializerTestCase.test_one_to_one_as_pk) If you use your own primary key field (such as a OneToOneField), it ... ok test_pkless_serialized_strings (serializers.test_json.JsonSerializerTestCase.test_pkless_serialized_strings) Serialized strings without PKs can be turned into models ... ok test_pre_1000ad_date (serializers.test_json.JsonSerializerTestCase.test_pre_1000ad_date) Year values before 1000AD are properly formatted ... ok test_serialize (serializers.test_json.JsonSerializerTestCase.test_serialize) Basic serialization works. ... ok test_serialize_field_subset (serializers.test_json.JsonSerializerTestCase.test_serialize_field_subset) Output can be restricted to a subset of fields ... ok test_serialize_inherited_fields (serializers.test_json.JsonSerializerTestCase.test_serialize_inherited_fields) ... ok test_serialize_prefetch_related_m2m (serializers.test_json.JsonSerializerTestCase.test_serialize_prefetch_related_m2m) ... ok test_serialize_progressbar (serializers.test_json.JsonSerializerTestCase.test_serialize_progressbar) ... ok test_serialize_proxy_model (serializers.test_json.JsonSerializerTestCase.test_serialize_proxy_model) ... ok test_serialize_specific_fields (serializers.test_json.JsonSerializerTestCase.test_serialize_specific_fields) ... ok test_serialize_superfluous_queries (serializers.test_json.JsonSerializerTestCase.test_serialize_superfluous_queries) Ensure no superfluous queries are made when serializing ForeignKeys ... ok test_serialize_to_stream (serializers.test_json.JsonSerializerTestCase.test_serialize_to_stream) ... ok test_serialize_unicode_roundtrip (serializers.test_json.JsonSerializerTestCase.test_serialize_unicode_roundtrip) Unicode makes the roundtrip intact ... ok test_serialize_with_null_pk (serializers.test_json.JsonSerializerTestCase.test_serialize_with_null_pk) Serialized data with no primary key results ... ok test_serializer_roundtrip (serializers.test_json.JsonSerializerTestCase.test_serializer_roundtrip) Serialized content can be deserialized. ... ok test_unicode_serialization (serializers.test_json.JsonSerializerTestCase.test_unicode_serialization) ... ok test_json_serializer (serializers.test_data.SerializerDataTests.test_json_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_serializer (serializers.test_data.SerializerDataTests.test_jsonl_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_python_serializer (serializers.test_data.SerializerDataTests.test_python_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_serializer (serializers.test_data.SerializerDataTests.test_xml_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_serializer (serializers.test_data.SerializerDataTests.test_yaml_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_altering_serialized_output (serializers.test_jsonl.JsonlSerializerTestCase.test_altering_serialized_output) The ability to create new objects by modifying serialized content. ... ok test_custom_encoder (serializers.test_jsonl.JsonlSerializerTestCase.test_custom_encoder) ... ok test_custom_field_serialization (serializers.test_jsonl.JsonlSerializerTestCase.test_custom_field_serialization) Custom fields serialize and deserialize intact ... ok test_deferred_field_serialization (serializers.test_jsonl.JsonlSerializerTestCase.test_deferred_field_serialization) ... ok test_deserialize_force_insert (serializers.test_jsonl.JsonlSerializerTestCase.test_deserialize_force_insert) Deserialized content can be saved with force_insert as a parameter. ... ok test_deterministic_mapping_ordering (serializers.test_jsonl.JsonlSerializerTestCase.test_deterministic_mapping_ordering) Mapping such as fields should be deterministically ordered. (#24558) ... ok test_float_serialization (serializers.test_jsonl.JsonlSerializerTestCase.test_float_serialization) Float values serialize and deserialize intact ... ok test_helpful_error_message_for_foreign_keys (serializers.test_jsonl.JsonlSerializerTestCase.test_helpful_error_message_for_foreign_keys) Invalid foreign keys with a natural key throws a helpful error message, ... ok test_helpful_error_message_for_many2many_natural1 (serializers.test_jsonl.JsonlSerializerTestCase.test_helpful_error_message_for_many2many_natural1) Invalid many-to-many keys throws a helpful error message where one of a ... ok test_helpful_error_message_for_many2many_natural2 (serializers.test_jsonl.JsonlSerializerTestCase.test_helpful_error_message_for_many2many_natural2) Invalid many-to-many keys throws a helpful error message where a ... ok test_helpful_error_message_for_many2many_non_natural (serializers.test_jsonl.JsonlSerializerTestCase.test_helpful_error_message_for_many2many_non_natural) Invalid many-to-many keys throws a helpful error message. ... ok test_helpful_error_message_for_many2many_not_iterable (serializers.test_jsonl.JsonlSerializerTestCase.test_helpful_error_message_for_many2many_not_iterable) Not iterable many-to-many field value throws a helpful error message. ... ok test_helpful_error_message_invalid_field (serializers.test_jsonl.JsonlSerializerTestCase.test_helpful_error_message_invalid_field) If there is an invalid field value, the error message contains the ... ok test_helpful_error_message_invalid_pk (serializers.test_jsonl.JsonlSerializerTestCase.test_helpful_error_message_invalid_pk) If there is an invalid primary key, the error message contains the ... ok test_json_deserializer_exception (serializers.test_jsonl.JsonlSerializerTestCase.test_json_deserializer_exception) ... ok test_no_indentation (serializers.test_jsonl.JsonlSerializerTestCase.test_no_indentation) ... ok test_one_to_one_as_pk (serializers.test_jsonl.JsonlSerializerTestCase.test_one_to_one_as_pk) If you use your own primary key field (such as a OneToOneField), it ... ok test_pkless_serialized_strings (serializers.test_jsonl.JsonlSerializerTestCase.test_pkless_serialized_strings) Serialized strings without PKs can be turned into models ... ok test_pre_1000ad_date (serializers.test_jsonl.JsonlSerializerTestCase.test_pre_1000ad_date) Year values before 1000AD are properly formatted ... ok test_serialize (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize) Basic serialization works. ... ok test_serialize_field_subset (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_field_subset) Output can be restricted to a subset of fields ... ok test_serialize_inherited_fields (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_inherited_fields) ... ok test_serialize_prefetch_related_m2m (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_prefetch_related_m2m) ... ok test_serialize_progressbar (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_progressbar) ... ok test_serialize_proxy_model (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_proxy_model) ... ok test_serialize_specific_fields (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_specific_fields) ... ok test_serialize_superfluous_queries (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_superfluous_queries) Ensure no superfluous queries are made when serializing ForeignKeys ... ok test_serialize_to_stream (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_to_stream) ... ok test_serialize_unicode_roundtrip (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_unicode_roundtrip) Unicode makes the roundtrip intact ... ok test_serialize_with_null_pk (serializers.test_jsonl.JsonlSerializerTestCase.test_serialize_with_null_pk) Serialized data with no primary key results ... ok test_serializer_roundtrip (serializers.test_jsonl.JsonlSerializerTestCase.test_serializer_roundtrip) Serialized content can be deserialized. ... ok test_unicode_serialization (serializers.test_jsonl.JsonlSerializerTestCase.test_unicode_serialization) ... ok test_defaults (str.tests.SimpleTests.test_defaults) The default implementation of __str__ and __repr__ should return ... ok test_international (str.tests.SimpleTests.test_international) ... ok test_complex_filter (or_lookups.tests.OrLookupsTests.test_complex_filter) ... ok test_empty_in (or_lookups.tests.OrLookupsTests.test_empty_in) ... ok test_filter_or (or_lookups.tests.OrLookupsTests.test_filter_or) ... ok test_other_arg_queries (or_lookups.tests.OrLookupsTests.test_other_arg_queries) ... ok test_pk_in (or_lookups.tests.OrLookupsTests.test_pk_in) ... ok test_pk_q (or_lookups.tests.OrLookupsTests.test_pk_q) ... ok test_q_and (or_lookups.tests.OrLookupsTests.test_q_and) ... ok test_q_exclude (or_lookups.tests.OrLookupsTests.test_q_exclude) ... ok test_q_negated (or_lookups.tests.OrLookupsTests.test_q_negated) ... ok test_q_repr (or_lookups.tests.OrLookupsTests.test_q_repr) ... ok test_stages (or_lookups.tests.OrLookupsTests.test_stages) ... ok test_altering_serialized_output (serializers.test_xml.XmlSerializerTestCase.test_altering_serialized_output) The ability to create new objects by modifying serialized content. ... ok test_control_char_failure (serializers.test_xml.XmlSerializerTestCase.test_control_char_failure) Serializing control characters with XML should fail as those characters ... ok test_custom_field_serialization (serializers.test_xml.XmlSerializerTestCase.test_custom_field_serialization) Custom fields serialize and deserialize intact ... ok test_deferred_field_serialization (serializers.test_xml.XmlSerializerTestCase.test_deferred_field_serialization) ... ok test_deserialize_force_insert (serializers.test_xml.XmlSerializerTestCase.test_deserialize_force_insert) Deserialized content can be saved with force_insert as a parameter. ... ok test_deterministic_mapping_ordering (serializers.test_xml.XmlSerializerTestCase.test_deterministic_mapping_ordering) Mapping such as fields should be deterministically ordered. (#24558) ... ok test_float_serialization (serializers.test_xml.XmlSerializerTestCase.test_float_serialization) Float values serialize and deserialize intact ... ok test_no_dtd (serializers.test_xml.XmlSerializerTestCase.test_no_dtd) The XML deserializer shouldn't allow a DTD. ... ok test_one_to_one_as_pk (serializers.test_xml.XmlSerializerTestCase.test_one_to_one_as_pk) If you use your own primary key field (such as a OneToOneField), it ... ok test_pkless_serialized_strings (serializers.test_xml.XmlSerializerTestCase.test_pkless_serialized_strings) Serialized strings without PKs can be turned into models ... ok test_pre_1000ad_date (serializers.test_xml.XmlSerializerTestCase.test_pre_1000ad_date) Year values before 1000AD are properly formatted ... ok test_serialize (serializers.test_xml.XmlSerializerTestCase.test_serialize) Basic serialization works. ... ok test_serialize_field_subset (serializers.test_xml.XmlSerializerTestCase.test_serialize_field_subset) Output can be restricted to a subset of fields ... ok test_serialize_inherited_fields (serializers.test_xml.XmlSerializerTestCase.test_serialize_inherited_fields) ... ok test_serialize_prefetch_related_m2m (serializers.test_xml.XmlSerializerTestCase.test_serialize_prefetch_related_m2m) ... ok test_serialize_progressbar (serializers.test_xml.XmlSerializerTestCase.test_serialize_progressbar) ... ok test_serialize_proxy_model (serializers.test_xml.XmlSerializerTestCase.test_serialize_proxy_model) ... ok test_serialize_specific_fields (serializers.test_xml.XmlSerializerTestCase.test_serialize_specific_fields) ... ok test_serialize_superfluous_queries (serializers.test_xml.XmlSerializerTestCase.test_serialize_superfluous_queries) Ensure no superfluous queries are made when serializing ForeignKeys ... ok test_serialize_to_stream (serializers.test_xml.XmlSerializerTestCase.test_serialize_to_stream) ... ok test_serialize_unicode_roundtrip (serializers.test_xml.XmlSerializerTestCase.test_serialize_unicode_roundtrip) Unicode makes the roundtrip intact ... ok test_serialize_with_null_pk (serializers.test_xml.XmlSerializerTestCase.test_serialize_with_null_pk) Serialized data with no primary key results ... ok test_serializer_roundtrip (serializers.test_xml.XmlSerializerTestCase.test_serializer_roundtrip) Serialized content can be deserialized. ... ok test_unicode_serialization (serializers.test_xml.XmlSerializerTestCase.test_unicode_serialization) ... ok test_altering_serialized_output (serializers.test_yaml.YamlSerializerTestCase.test_altering_serialized_output) The ability to create new objects by modifying serialized content. ... ok test_custom_field_serialization (serializers.test_yaml.YamlSerializerTestCase.test_custom_field_serialization) Custom fields serialize and deserialize intact ... ok test_deferred_field_serialization (serializers.test_yaml.YamlSerializerTestCase.test_deferred_field_serialization) ... ok test_deserialize_force_insert (serializers.test_yaml.YamlSerializerTestCase.test_deserialize_force_insert) Deserialized content can be saved with force_insert as a parameter. ... ok test_deterministic_mapping_ordering (serializers.test_yaml.YamlSerializerTestCase.test_deterministic_mapping_ordering) Mapping such as fields should be deterministically ordered. (#24558) ... ok test_float_serialization (serializers.test_yaml.YamlSerializerTestCase.test_float_serialization) Float values serialize and deserialize intact ... ok test_one_to_one_as_pk (serializers.test_yaml.YamlSerializerTestCase.test_one_to_one_as_pk) If you use your own primary key field (such as a OneToOneField), it ... ok test_pkless_serialized_strings (serializers.test_yaml.YamlSerializerTestCase.test_pkless_serialized_strings) Serialized strings without PKs can be turned into models ... ok test_pre_1000ad_date (serializers.test_yaml.YamlSerializerTestCase.test_pre_1000ad_date) Year values before 1000AD are properly formatted ... ok test_serialize (serializers.test_yaml.YamlSerializerTestCase.test_serialize) Basic serialization works. ... ok test_serialize_field_subset (serializers.test_yaml.YamlSerializerTestCase.test_serialize_field_subset) Output can be restricted to a subset of fields ... ok test_serialize_inherited_fields (serializers.test_yaml.YamlSerializerTestCase.test_serialize_inherited_fields) ... ok test_serialize_prefetch_related_m2m (serializers.test_yaml.YamlSerializerTestCase.test_serialize_prefetch_related_m2m) ... ok test_serialize_progressbar (serializers.test_yaml.YamlSerializerTestCase.test_serialize_progressbar) ... ok test_serialize_proxy_model (serializers.test_yaml.YamlSerializerTestCase.test_serialize_proxy_model) ... ok test_serialize_specific_fields (serializers.test_yaml.YamlSerializerTestCase.test_serialize_specific_fields) ... ok test_serialize_superfluous_queries (serializers.test_yaml.YamlSerializerTestCase.test_serialize_superfluous_queries) Ensure no superfluous queries are made when serializing ForeignKeys ... ok test_serialize_to_stream (serializers.test_yaml.YamlSerializerTestCase.test_serialize_to_stream) ... ok test_serialize_unicode_roundtrip (serializers.test_yaml.YamlSerializerTestCase.test_serialize_unicode_roundtrip) Unicode makes the roundtrip intact ... ok test_serialize_with_null_pk (serializers.test_yaml.YamlSerializerTestCase.test_serialize_with_null_pk) Serialized data with no primary key results ... ok test_serializer_roundtrip (serializers.test_yaml.YamlSerializerTestCase.test_serializer_roundtrip) Serialized content can be deserialized. ... ok test_unicode_serialization (serializers.test_yaml.YamlSerializerTestCase.test_unicode_serialization) ... ok test_yaml_deserializer_exception (serializers.test_yaml.YamlSerializerTestCase.test_yaml_deserializer_exception) ... ok test_circular_reference (fixtures.tests.CircularReferenceTests.test_circular_reference) ... ok test_circular_reference_natural_key (fixtures.tests.CircularReferenceTests.test_circular_reference_natural_key) ... ok test_loaddata_not_existent_fixture_file (fixtures.tests.NonexistentFixtureTests.test_loaddata_not_existent_fixture_file) ... ok test_nonexistent_fixture_no_constraint_checking (fixtures.tests.NonexistentFixtureTests.test_nonexistent_fixture_no_constraint_checking) If no fixtures match the loaddata command, constraints checks on the ... ok test_forward_reference_fk (fixtures.tests.ForwardReferenceTests.test_forward_reference_fk) ... ok test_forward_reference_fk_natural_key (fixtures.tests.ForwardReferenceTests.test_forward_reference_fk_natural_key) ... ok test_forward_reference_m2m (fixtures.tests.ForwardReferenceTests.test_forward_reference_m2m) ... ok test_forward_reference_m2m_natural_key (fixtures.tests.ForwardReferenceTests.test_forward_reference_m2m_natural_key) ... ok test_class_fixtures (fixtures.tests.SubclassTestCaseFixtureLoadingTests.test_class_fixtures) There were no fixture objects installed ... ok test_class_fixtures (fixtures.tests.TestCaseFixtureLoadingTests.test_class_fixtures) Test case has installed 3 fixture objects ... ok test_getter (properties.tests.PropertyTests.test_getter) ... ok test_setter (properties.tests.PropertyTests.test_setter) ... ok test_json_fk_as_pk_natural_key_not_called (serializers.test_natural.NaturalKeySerializerTests.test_json_fk_as_pk_natural_key_not_called) partial(func, *args, **keywords) - new function with partial application ... ok test_json_forward_references_fk_errors (serializers.test_natural.NaturalKeySerializerTests.test_json_forward_references_fk_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_json_forward_references_fks (serializers.test_natural.NaturalKeySerializerTests.test_json_forward_references_fks) partial(func, *args, **keywords) - new function with partial application ... ok test_json_forward_references_m2m_errors (serializers.test_natural.NaturalKeySerializerTests.test_json_forward_references_m2m_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_json_forward_references_m2ms (serializers.test_natural.NaturalKeySerializerTests.test_json_forward_references_m2ms) partial(func, *args, **keywords) - new function with partial application ... ok test_json_natural_key_serializer (serializers.test_natural.NaturalKeySerializerTests.test_json_natural_key_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_json_pk_with_default (serializers.test_natural.NaturalKeySerializerTests.test_json_pk_with_default) partial(func, *args, **keywords) - new function with partial application ... ok test_json_serializer_natural_keys (serializers.test_natural.NaturalKeySerializerTests.test_json_serializer_natural_keys) partial(func, *args, **keywords) - new function with partial application ... ok test_json_serializer_natural_pks_mti (serializers.test_natural.NaturalKeySerializerTests.test_json_serializer_natural_pks_mti) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_fk_as_pk_natural_key_not_called (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_fk_as_pk_natural_key_not_called) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_forward_references_fk_errors (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_forward_references_fk_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_forward_references_fks (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_forward_references_fks) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_forward_references_m2m_errors (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_forward_references_m2m_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_forward_references_m2ms (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_forward_references_m2ms) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_natural_key_serializer (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_natural_key_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_pk_with_default (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_pk_with_default) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_serializer_natural_keys (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_serializer_natural_keys) partial(func, *args, **keywords) - new function with partial application ... ok test_jsonl_serializer_natural_pks_mti (serializers.test_natural.NaturalKeySerializerTests.test_jsonl_serializer_natural_pks_mti) partial(func, *args, **keywords) - new function with partial application ... ok test_python_fk_as_pk_natural_key_not_called (serializers.test_natural.NaturalKeySerializerTests.test_python_fk_as_pk_natural_key_not_called) partial(func, *args, **keywords) - new function with partial application ... ok test_python_forward_references_fk_errors (serializers.test_natural.NaturalKeySerializerTests.test_python_forward_references_fk_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_python_forward_references_fks (serializers.test_natural.NaturalKeySerializerTests.test_python_forward_references_fks) partial(func, *args, **keywords) - new function with partial application ... ok test_python_forward_references_m2m_errors (serializers.test_natural.NaturalKeySerializerTests.test_python_forward_references_m2m_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_python_forward_references_m2ms (serializers.test_natural.NaturalKeySerializerTests.test_python_forward_references_m2ms) partial(func, *args, **keywords) - new function with partial application ... ok test_python_natural_key_serializer (serializers.test_natural.NaturalKeySerializerTests.test_python_natural_key_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_python_pk_with_default (serializers.test_natural.NaturalKeySerializerTests.test_python_pk_with_default) partial(func, *args, **keywords) - new function with partial application ... ok test_python_serializer_natural_keys (serializers.test_natural.NaturalKeySerializerTests.test_python_serializer_natural_keys) partial(func, *args, **keywords) - new function with partial application ... ok test_python_serializer_natural_pks_mti (serializers.test_natural.NaturalKeySerializerTests.test_python_serializer_natural_pks_mti) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_fk_as_pk_natural_key_not_called (serializers.test_natural.NaturalKeySerializerTests.test_xml_fk_as_pk_natural_key_not_called) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_forward_references_fk_errors (serializers.test_natural.NaturalKeySerializerTests.test_xml_forward_references_fk_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_forward_references_fks (serializers.test_natural.NaturalKeySerializerTests.test_xml_forward_references_fks) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_forward_references_m2m_errors (serializers.test_natural.NaturalKeySerializerTests.test_xml_forward_references_m2m_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_forward_references_m2ms (serializers.test_natural.NaturalKeySerializerTests.test_xml_forward_references_m2ms) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_natural_key_serializer (serializers.test_natural.NaturalKeySerializerTests.test_xml_natural_key_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_pk_with_default (serializers.test_natural.NaturalKeySerializerTests.test_xml_pk_with_default) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_serializer_natural_keys (serializers.test_natural.NaturalKeySerializerTests.test_xml_serializer_natural_keys) partial(func, *args, **keywords) - new function with partial application ... ok test_xml_serializer_natural_pks_mti (serializers.test_natural.NaturalKeySerializerTests.test_xml_serializer_natural_pks_mti) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_fk_as_pk_natural_key_not_called (serializers.test_natural.NaturalKeySerializerTests.test_yaml_fk_as_pk_natural_key_not_called) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_forward_references_fk_errors (serializers.test_natural.NaturalKeySerializerTests.test_yaml_forward_references_fk_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_forward_references_fks (serializers.test_natural.NaturalKeySerializerTests.test_yaml_forward_references_fks) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_forward_references_m2m_errors (serializers.test_natural.NaturalKeySerializerTests.test_yaml_forward_references_m2m_errors) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_forward_references_m2ms (serializers.test_natural.NaturalKeySerializerTests.test_yaml_forward_references_m2ms) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_natural_key_serializer (serializers.test_natural.NaturalKeySerializerTests.test_yaml_natural_key_serializer) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_pk_with_default (serializers.test_natural.NaturalKeySerializerTests.test_yaml_pk_with_default) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_serializer_natural_keys (serializers.test_natural.NaturalKeySerializerTests.test_yaml_serializer_natural_keys) partial(func, *args, **keywords) - new function with partial application ... ok test_yaml_serializer_natural_pks_mti (serializers.test_natural.NaturalKeySerializerTests.test_yaml_serializer_natural_pks_mti) partial(func, *args, **keywords) - new function with partial application ... ok test_dates_query (extra_regress.tests.ExtraRegressTests.test_dates_query) When calling the dates() method on a queryset with extra selection ... ok test_extra_stay_tied (extra_regress.tests.ExtraRegressTests.test_extra_stay_tied) ... ok test_extra_values_distinct_ordering (extra_regress.tests.ExtraRegressTests.test_extra_values_distinct_ordering) ... ok test_regression_10847 (extra_regress.tests.ExtraRegressTests.test_regression_10847) Regression for #10847: the list of extra columns can always be ... ok test_regression_17877 (extra_regress.tests.ExtraRegressTests.test_regression_17877) Extra WHERE clauses get correctly ANDed, even when they ... ok test_regression_7314_7372 (extra_regress.tests.ExtraRegressTests.test_regression_7314_7372) Regression tests for #7314 and #7372 ... ok test_regression_7957 (extra_regress.tests.ExtraRegressTests.test_regression_7957) Regression test for #7957: Combining extra() calls should leave the ... ok test_regression_7961 (extra_regress.tests.ExtraRegressTests.test_regression_7961) Regression test for #7961: When not using a portion of an ... ok test_regression_8039 (extra_regress.tests.ExtraRegressTests.test_regression_8039) Regression test for #8039: Ordering sometimes removed relevant tables ... ok test_regression_8063 (extra_regress.tests.ExtraRegressTests.test_regression_8063) Regression test for #8063: limiting a query shouldn't discard any ... ok test_regression_8819 (extra_regress.tests.ExtraRegressTests.test_regression_8819) Regression test for #8819: Fields in the extra(select=...) list ... ok test_values_with_extra (extra_regress.tests.ExtraRegressTests.test_values_with_extra) Regression test for #10256... If there is a values() clause, Extra ... ok test_m2o_recursive (m2o_recursive.tests.ManyToOneRecursiveTests.test_m2o_recursive) ... ok test_m2o_recursive2 (m2o_recursive.tests.MultipleManyToOneRecursiveTests.test_m2o_recursive2) ... ok test_m2m_relations_add_remove_clear (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_add_remove_clear) ... ok test_m2m_relations_signals_all_the_doors_off_of_cars (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_all_the_doors_off_of_cars) ... ok test_m2m_relations_signals_alternative_ways (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_alternative_ways) ... ok test_m2m_relations_signals_clear_all_parts_of_the_self_vw (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_clear_all_parts_of_the_self_vw) ... ok test_m2m_relations_signals_clearing_removing (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_clearing_removing) ... ok test_m2m_relations_signals_give_the_self_vw_some_optional_parts (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_give_the_self_vw_some_optional_parts) ... ok test_m2m_relations_signals_remove_relation (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_remove_relation) ... ok test_m2m_relations_signals_reverse_relation (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_reverse_relation) ... ok test_m2m_relations_signals_reverse_relation_with_custom_related_name (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_reverse_relation_with_custom_related_name) ... ok test_m2m_relations_signals_when_inheritance (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_signals_when_inheritance) ... ok test_m2m_relations_with_self_add_fan (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_with_self_add_fan) ... ok test_m2m_relations_with_self_add_friends (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_with_self_add_friends) ... ok test_m2m_relations_with_self_add_idols (m2m_signals.tests.ManyToManySignalsTest.test_m2m_relations_with_self_add_idols) ... ok test_pk_set_on_repeated_add_remove (m2m_signals.tests.ManyToManySignalsTest.test_pk_set_on_repeated_add_remove) m2m_changed is always fired, even for repeated calls to the same ... ok test_default_related_name (model_options.test_default_related_name.DefaultRelatedNameTests.test_default_related_name) ... ok test_default_related_name_in_queryset_lookup (model_options.test_default_related_name.DefaultRelatedNameTests.test_default_related_name_in_queryset_lookup) ... ok test_inheritance (model_options.test_default_related_name.DefaultRelatedNameTests.test_inheritance) ... ok test_inheritance_with_overridden_default_related_name (model_options.test_default_related_name.DefaultRelatedNameTests.test_inheritance_with_overridden_default_related_name) ... ok test_model_name_not_available_in_queryset_lookup (model_options.test_default_related_name.DefaultRelatedNameTests.test_model_name_not_available_in_queryset_lookup) ... ok test_no_default_related_name (model_options.test_default_related_name.DefaultRelatedNameTests.test_no_default_related_name) ... ok test_related_name_overrides_default_related_name (model_options.test_default_related_name.DefaultRelatedNameTests.test_related_name_overrides_default_related_name) ... ok test_create_with_duplicate_primary_key (get_or_create.tests.GetOrCreateTestsWithManualPKs.test_create_with_duplicate_primary_key) If you specify an existing primary key, but different other fields, ... ok test_get_or_create_empty (get_or_create.tests.GetOrCreateTestsWithManualPKs.test_get_or_create_empty) If all the attributes on a model have defaults, get_or_create() doesn't ... ok test_get_or_create_raises_IntegrityError_plus_traceback (get_or_create.tests.GetOrCreateTestsWithManualPKs.test_get_or_create_raises_IntegrityError_plus_traceback) get_or_create should raise IntegrityErrors with the full traceback. ... ok test_savepoint_rollback (get_or_create.tests.GetOrCreateTestsWithManualPKs.test_savepoint_rollback) The database connection is still usable after a DatabaseError in ... ok test_create_get_or_create (get_or_create.tests.GetOrCreateThroughManyToMany.test_create_get_or_create) ... ok test_get_get_or_create (get_or_create.tests.GetOrCreateThroughManyToMany.test_get_get_or_create) ... ok test_something (get_or_create.tests.GetOrCreateThroughManyToMany.test_something) ... ok test_callable_defaults (get_or_create.tests.GetOrCreateTests.test_callable_defaults) Callables in `defaults` are evaluated if the instance is created. ... ok test_callable_defaults_not_called (get_or_create.tests.GetOrCreateTests.test_callable_defaults_not_called) ... ok test_defaults_exact (get_or_create.tests.GetOrCreateTests.test_defaults_exact) If you have a field named defaults and want to use it as an exact ... ok test_defaults_not_evaluated_unless_needed (get_or_create.tests.GetOrCreateTests.test_defaults_not_evaluated_unless_needed) `defaults` aren't evaluated if the instance isn't created. ... ok test_get_or_create_invalid_params (get_or_create.tests.GetOrCreateTests.test_get_or_create_invalid_params) If you don't specify a value or default value for all required ... ok test_get_or_create_method_with_create (get_or_create.tests.GetOrCreateTests.test_get_or_create_method_with_create) ... ok test_get_or_create_method_with_get (get_or_create.tests.GetOrCreateTests.test_get_or_create_method_with_get) ... ok test_get_or_create_on_related_manager (get_or_create.tests.GetOrCreateTests.test_get_or_create_on_related_manager) ... ok test_get_or_create_redundant_instance (get_or_create.tests.GetOrCreateTests.test_get_or_create_redundant_instance) If we execute the exact same statement twice, the second time, ... ok test_get_or_create_with_model_property_defaults (get_or_create.tests.GetOrCreateTests.test_get_or_create_with_model_property_defaults) Using a property with a setter implemented is allowed. ... ok test_get_or_create_with_pk_property (get_or_create.tests.GetOrCreateTests.test_get_or_create_with_pk_property) Using the pk property of a model is allowed. ... ok test_create_with_duplicate_primary_key (get_or_create.tests.UpdateOrCreateTestsWithManualPKs.test_create_with_duplicate_primary_key) If an existing primary key is specified with different values for other ... ok test_create (get_or_create.tests.UpdateOrCreateTests.test_create) ... ok test_create_callable_default (get_or_create.tests.UpdateOrCreateTests.test_create_callable_default) ... ok test_create_twice (get_or_create.tests.UpdateOrCreateTests.test_create_twice) ... ok test_create_with_many (get_or_create.tests.UpdateOrCreateTests.test_create_with_many) Should be able to use update_or_create from the m2m related manager to ... ok test_create_with_related_manager (get_or_create.tests.UpdateOrCreateTests.test_create_with_related_manager) Should be able to use update_or_create from the related manager to ... ok test_defaults_exact (get_or_create.tests.UpdateOrCreateTests.test_defaults_exact) If you have a field named defaults and want to use it as an exact ... ok test_defaults_not_evaluated_unless_needed (get_or_create.tests.UpdateOrCreateTests.test_defaults_not_evaluated_unless_needed) `defaults` aren't evaluated if the instance isn't created. ... ok test_error_contains_full_traceback (get_or_create.tests.UpdateOrCreateTests.test_error_contains_full_traceback) update_or_create should raise IntegrityErrors with the full traceback. ... ok test_integrity (get_or_create.tests.UpdateOrCreateTests.test_integrity) If you don't specify a value or default value for all required ... ok test_manual_primary_key_test (get_or_create.tests.UpdateOrCreateTests.test_manual_primary_key_test) If you specify an existing primary key, but different other fields, ... ok test_update (get_or_create.tests.UpdateOrCreateTests.test_update) ... ok test_update_callable_default (get_or_create.tests.UpdateOrCreateTests.test_update_callable_default) ... ok test_update_or_create_with_model_property_defaults (get_or_create.tests.UpdateOrCreateTests.test_update_or_create_with_model_property_defaults) Using a property with a setter implemented is allowed. ... ok test_update_with_many (get_or_create.tests.UpdateOrCreateTests.test_update_with_many) Should be able to use update_or_create from the m2m related manager to ... ok test_update_with_related_manager (get_or_create.tests.UpdateOrCreateTests.test_update_with_related_manager) Should be able to use update_or_create from the related manager to ... ok test_with_pk_property (get_or_create.tests.UpdateOrCreateTests.test_with_pk_property) Using the pk property of a model is allowed. ... ok test_ambiguous_compressed_fixture (fixtures.tests.FixtureLoadingTests.test_ambiguous_compressed_fixture) ... ok test_compress_format_loading (fixtures.tests.FixtureLoadingTests.test_compress_format_loading) ... ok test_compressed_loading (fixtures.tests.FixtureLoadingTests.test_compressed_loading) ... ok test_compressed_loading_bz2 (fixtures.tests.FixtureLoadingTests.test_compressed_loading_bz2) ... ok test_compressed_loading_gzip (fixtures.tests.FixtureLoadingTests.test_compressed_loading_gzip) ... ok test_compressed_loading_lzma (fixtures.tests.FixtureLoadingTests.test_compressed_loading_lzma) ... ok test_compressed_loading_xz (fixtures.tests.FixtureLoadingTests.test_compressed_loading_xz) ... ok test_compressed_specified_loading (fixtures.tests.FixtureLoadingTests.test_compressed_specified_loading) ... ok test_db_loading (fixtures.tests.FixtureLoadingTests.test_db_loading) ... ok test_dumpdata_progressbar (fixtures.tests.FixtureLoadingTests.test_dumpdata_progressbar) Dumpdata shows a progress bar on the command line when --output is set, ... ok test_dumpdata_proxy_with_concrete (fixtures.tests.FixtureLoadingTests.test_dumpdata_proxy_with_concrete) A warning isn't displayed if a proxy model is dumped with its concrete ... ok test_dumpdata_proxy_without_concrete (fixtures.tests.FixtureLoadingTests.test_dumpdata_proxy_without_concrete) A warning is displayed if a proxy model is dumped without its concrete ... ok test_dumpdata_with_excludes (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_excludes) ... ok test_dumpdata_with_file_bz2_output (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_file_bz2_output) ... ok test_dumpdata_with_file_gzip_output (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_file_gzip_output) ... ok test_dumpdata_with_file_lzma_output (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_file_lzma_output) ... ok test_dumpdata_with_file_output (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_file_output) ... ok test_dumpdata_with_file_xz_output (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_file_xz_output) ... ok test_dumpdata_with_file_zip_output (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_file_zip_output) ... ok test_dumpdata_with_filtering_manager (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_filtering_manager) ... ok test_dumpdata_with_pks (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_pks) ... ok test_dumpdata_with_uuid_pks (fixtures.tests.FixtureLoadingTests.test_dumpdata_with_uuid_pks) ... ok test_exclude_option_errors (fixtures.tests.FixtureLoadingTests.test_exclude_option_errors) Excluding a bogus app or model should raise an error. ... ok test_load_fixture_with_special_characters (fixtures.tests.FixtureLoadingTests.test_load_fixture_with_special_characters) ... ok test_loaddata_app_option (fixtures.tests.FixtureLoadingTests.test_loaddata_app_option) ... ok test_loaddata_error_message (fixtures.tests.FixtureLoadingTests.test_loaddata_error_message) Loading a fixture which contains an invalid object outputs an error ... ok test_loaddata_null_characters_on_postgresql (fixtures.tests.FixtureLoadingTests.test_loaddata_null_characters_on_postgresql) ... skipped 'psycopg2 prohibits null characters in data.' test_loaddata_verbosity_three (fixtures.tests.FixtureLoadingTests.test_loaddata_verbosity_three) ... ok test_loading_and_dumping (fixtures.tests.FixtureLoadingTests.test_loading_and_dumping) ... ok test_loading_stdin (fixtures.tests.FixtureLoadingTests.test_loading_stdin) Loading fixtures from stdin with json and xml. ... ok test_loading_using (fixtures.tests.FixtureLoadingTests.test_loading_using) ... ok test_loading_with_exclude_app (fixtures.tests.FixtureLoadingTests.test_loading_with_exclude_app) ... ok test_loading_with_exclude_model (fixtures.tests.FixtureLoadingTests.test_loading_with_exclude_model) ... ok test_output_formats (fixtures.tests.FixtureLoadingTests.test_output_formats) ... ok test_stdin_without_format (fixtures.tests.FixtureLoadingTests.test_stdin_without_format) Reading from stdin raises an error if format isn't specified. ... ok test_unmatched_identifier_loading (fixtures.tests.FixtureLoadingTests.test_unmatched_identifier_loading) ... ok test_database_queried (backends.base.test_base.ExecuteWrapperTests.test_database_queried) ... ok test_nested_wrapper_invoked (backends.base.test_base.ExecuteWrapperTests.test_nested_wrapper_invoked) ... ok test_outer_wrapper_blocks (backends.base.test_base.ExecuteWrapperTests.test_outer_wrapper_blocks) ... ok test_wrapper_connection_specific (backends.base.test_base.ExecuteWrapperTests.test_wrapper_connection_specific) ... ok test_wrapper_gets_sql (backends.base.test_base.ExecuteWrapperTests.test_wrapper_gets_sql) ... ok test_wrapper_invoked (backends.base.test_base.ExecuteWrapperTests.test_wrapper_invoked) ... ok test_wrapper_invoked_many (backends.base.test_base.ExecuteWrapperTests.test_wrapper_invoked_many) ... ok test_allows_auto_pk_0 (backends.mysql.test_features.TestFeatures.test_allows_auto_pk_0) ... skipped 'MySQL tests' test_skip_locked_no_wait (backends.mysql.test_features.TestFeatures.test_skip_locked_no_wait) ... skipped 'MySQL tests' test_supports_transactions (backends.mysql.test_features.TestFeatures.test_supports_transactions) All storage engines except MyISAM support transactions. ... skipped 'MySQL tests' test_distinct_on_fields (backends.base.test_operations.DatabaseOperationTests.test_distinct_on_fields) ... ok test_subtract_temporals (backends.base.test_operations.DatabaseOperationTests.test_subtract_temporals) ... skipped 'Database has feature(s) supports_temporal_subtraction' test_window_frame_raise_not_supported_error (backends.base.test_operations.DatabaseOperationTests.test_window_frame_raise_not_supported_error) ... skipped 'Database has feature(s) supports_over_clause' test_parse_constraint_columns (backends.mysql.test_introspection.ParsingTests.test_parse_constraint_columns) ... skipped 'MySQL tests' test_quote_value (backends.mysql.test_schema.SchemaEditorTests.test_quote_value) ... skipped 'MySQL tests' test_auto_is_null_auto_config (backends.mysql.tests.IsolationLevelTests.test_auto_is_null_auto_config) ... skipped 'MySQL tests' test_connect_isolation_level (backends.mysql.tests.IsolationLevelTests.test_connect_isolation_level) ... skipped 'MySQL tests' test_default_isolation_level (backends.mysql.tests.IsolationLevelTests.test_default_isolation_level) ... skipped 'MySQL tests' test_isolation_level_validation (backends.mysql.tests.IsolationLevelTests.test_isolation_level_validation) ... skipped 'MySQL tests' test_setting_isolation_level (backends.mysql.tests.IsolationLevelTests.test_setting_isolation_level) ... skipped 'MySQL tests' test_uppercase_isolation_level (backends.mysql.tests.IsolationLevelTests.test_uppercase_isolation_level) ... skipped 'MySQL tests' test_create_test_db (backends.oracle.test_creation.DatabaseCreationTests.test_create_test_db) ... skipped 'Oracle tests' test_create_test_user (backends.oracle.test_creation.DatabaseCreationTests.test_create_test_user) ... skipped 'Oracle tests' test_oracle_managed_files (backends.oracle.test_creation.DatabaseCreationTests.test_oracle_managed_files) ... skipped 'Oracle tests' test_get_sequences (backends.postgresql.test_introspection.DatabaseSequenceTests.test_get_sequences) ... skipped 'Test only for PostgreSQL' test_closed_server_side_cursor (backends.postgresql.test_server_side_cursors.ServerSideCursorsPostgres.test_closed_server_side_cursor) ... skipped 'PostgreSQL tests' test_server_side_cursor (backends.postgresql.test_server_side_cursors.ServerSideCursorsPostgres.test_server_side_cursor) ... skipped 'PostgreSQL tests' test_server_side_cursor_many_cursors (backends.postgresql.test_server_side_cursors.ServerSideCursorsPostgres.test_server_side_cursor_many_cursors) ... skipped 'PostgreSQL tests' test_server_side_cursors_setting (backends.postgresql.test_server_side_cursors.ServerSideCursorsPostgres.test_server_side_cursors_setting) ... skipped 'PostgreSQL tests' test_values (backends.postgresql.test_server_side_cursors.ServerSideCursorsPostgres.test_values) ... skipped 'PostgreSQL tests' test_values_list (backends.postgresql.test_server_side_cursors.ServerSideCursorsPostgres.test_values_list) ... skipped 'PostgreSQL tests' test_values_list_fields_not_equal_to_names (backends.postgresql.test_server_side_cursors.ServerSideCursorsPostgres.test_values_list_fields_not_equal_to_names) ... skipped 'PostgreSQL tests' test_values_list_flat (backends.postgresql.test_server_side_cursors.ServerSideCursorsPostgres.test_values_list_flat) ... skipped 'PostgreSQL tests' test_connect_and_rollback (backends.postgresql.tests.Tests.test_connect_and_rollback) PostgreSQL shouldn't roll back SET TIME ZONE, even if the first ... skipped 'PostgreSQL tests' test_connect_isolation_level (backends.postgresql.tests.Tests.test_connect_isolation_level) The transaction level can be configured with ... skipped 'PostgreSQL tests' test_connect_no_is_usable_checks (backends.postgresql.tests.Tests.test_connect_no_is_usable_checks) ... skipped 'PostgreSQL tests' test_connect_non_autocommit (backends.postgresql.tests.Tests.test_connect_non_autocommit) The connection wrapper shouldn't believe that autocommit is enabled ... skipped 'PostgreSQL tests' test_copy_cursors (backends.postgresql.tests.Tests.test_copy_cursors) ... skipped 'PostgreSQL tests' test_correct_extraction_psycopg2_version (backends.postgresql.tests.Tests.test_correct_extraction_psycopg2_version) ... skipped 'PostgreSQL tests' test_database_name_too_long (backends.postgresql.tests.Tests.test_database_name_too_long) ... skipped 'PostgreSQL tests' test_lookup_cast (backends.postgresql.tests.Tests.test_lookup_cast) ... skipped 'PostgreSQL tests' test_nodb_cursor (backends.postgresql.tests.Tests.test_nodb_cursor) The _nodb_cursor() fallbacks to the default connection database when ... skipped 'PostgreSQL tests' test_nodb_cursor_raises_postgres_authentication_failure (backends.postgresql.tests.Tests.test_nodb_cursor_raises_postgres_authentication_failure) _nodb_cursor() re-raises authentication failure to the 'postgres' db ... skipped 'PostgreSQL tests' test_select_ascii_array (backends.postgresql.tests.Tests.test_select_ascii_array) ... skipped 'PostgreSQL tests' test_select_unicode_array (backends.postgresql.tests.Tests.test_select_unicode_array) ... skipped 'PostgreSQL tests' test_supports_json_field_operational_error (backends.sqlite.test_features.FeaturesTests.test_supports_json_field_operational_error) ... ok test_get_primary_key_column (backends.sqlite.test_introspection.IntrospectionTests.test_get_primary_key_column) Get the primary key column regardless of whether or not it has ... ok test_aggregate_alias (annotations.tests.AliasTests.test_aggregate_alias) ... ok test_alias_after_annotation (annotations.tests.AliasTests.test_alias_after_annotation) ... ok test_alias_annotate_with_aggregation (annotations.tests.AliasTests.test_alias_annotate_with_aggregation) ... ok test_alias_annotation_expression (annotations.tests.AliasTests.test_alias_annotation_expression) ... ok test_alias_default_alias_expression (annotations.tests.AliasTests.test_alias_default_alias_expression) ... ok test_alias_sql_injection (annotations.tests.AliasTests.test_alias_sql_injection) ... ok test_basic_alias (annotations.tests.AliasTests.test_basic_alias) ... ok test_basic_alias_annotation (annotations.tests.AliasTests.test_basic_alias_annotation) ... ok test_basic_alias_f_annotation (annotations.tests.AliasTests.test_basic_alias_f_annotation) ... ok test_basic_alias_f_transform_annotation (annotations.tests.AliasTests.test_basic_alias_f_transform_annotation) ... ok test_dates_alias (annotations.tests.AliasTests.test_dates_alias) ... ok test_datetimes_alias (annotations.tests.AliasTests.test_datetimes_alias) ... ok test_defer_only_alias (annotations.tests.AliasTests.test_defer_only_alias) ... ok test_distinct_on_alias (annotations.tests.AliasTests.test_distinct_on_alias) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_filter_alias_agg_with_double_f (annotations.tests.AliasTests.test_filter_alias_agg_with_double_f) ... ok test_filter_alias_with_double_f (annotations.tests.AliasTests.test_filter_alias_with_double_f) ... ok test_filter_alias_with_f (annotations.tests.AliasTests.test_filter_alias_with_f) ... ok test_joined_alias_annotation (annotations.tests.AliasTests.test_joined_alias_annotation) ... ok test_order_by_alias (annotations.tests.AliasTests.test_order_by_alias) ... ok test_order_by_alias_aggregate (annotations.tests.AliasTests.test_order_by_alias_aggregate) ... ok test_overwrite_alias_with_annotation (annotations.tests.AliasTests.test_overwrite_alias_with_annotation) ... ok test_overwrite_annotation_with_alias (annotations.tests.AliasTests.test_overwrite_annotation_with_alias) ... ok test_update_with_alias (annotations.tests.AliasTests.test_update_with_alias) ... ok test_values_alias (annotations.tests.AliasTests.test_values_alias) ... ok test_parameter_escaping (backends.sqlite.tests.EscapingChecks.test_parameter_escaping) ... ok test_parameter_escaping (backends.sqlite.tests.EscapingChecksDebug.test_parameter_escaping) ... ok test_sql_flush (backends.sqlite.test_operations.SQLiteOperationsTests.test_sql_flush) ... ok test_sql_flush_allow_cascade (backends.sqlite.test_operations.SQLiteOperationsTests.test_sql_flush_allow_cascade) ... ok test_sql_flush_sequences (backends.sqlite.test_operations.SQLiteOperationsTests.test_sql_flush_sequences) ... ok test_sql_flush_sequences_allow_cascade (backends.sqlite.test_operations.SQLiteOperationsTests.test_sql_flush_sequences_allow_cascade) ... ok test_check_and_unique_column (backends.sqlite.test_introspection.ParsingTests.test_check_and_unique_column) ... ok test_check_column (backends.sqlite.test_introspection.ParsingTests.test_check_column) ... ok test_check_column_with_operators_and_functions (backends.sqlite.test_introspection.ParsingTests.test_check_column_with_operators_and_functions) ... ok test_check_constraint (backends.sqlite.test_introspection.ParsingTests.test_check_constraint) ... ok test_unique_column (backends.sqlite.test_introspection.ParsingTests.test_unique_column) ... ok test_unique_constraint (backends.sqlite.test_introspection.ParsingTests.test_unique_constraint) ... ok test_unique_constraint_multicolumn (backends.sqlite.test_introspection.ParsingTests.test_unique_constraint_multicolumn) ... ok test_large_number_of_parameters (backends.sqlite.tests.LastExecutedQueryTest.test_large_number_of_parameters) ... ok test_no_interpolation (backends.sqlite.tests.LastExecutedQueryTest.test_no_interpolation) ... ok test_parameter_quoting (backends.sqlite.tests.LastExecutedQueryTest.test_parameter_quoting) ... ok test_can_reference_existent (backends.tests.DBConstraintTestCase.test_can_reference_existent) ... ok test_can_reference_non_existent (backends.tests.DBConstraintTestCase.test_can_reference_non_existent) ... ok test_many_to_many (backends.tests.DBConstraintTestCase.test_many_to_many) ... ok test_django_date_extract (backends.tests.DateQuotingTest.test_django_date_extract) Test the custom ``django_date_extract method``, in particular against fields ... ok test_django_date_trunc (backends.tests.DateQuotingTest.test_django_date_trunc) Test the custom ``django_date_trunc method``, in particular against ... ok test_aggregation (backends.sqlite.tests.Tests.test_aggregation) Raise NotSupportedError when aggregating on date/time fields. ... ok test_check_sqlite_version (backends.sqlite.tests.Tests.test_check_sqlite_version) ... ok test_distinct_aggregation (backends.sqlite.tests.Tests.test_distinct_aggregation) ... ok test_distinct_aggregation_multiple_args_no_distinct (backends.sqlite.tests.Tests.test_distinct_aggregation_multiple_args_no_distinct) ... ok test_memory_db_test_name (backends.sqlite.tests.Tests.test_memory_db_test_name) A named in-memory db should be allowed where supported. ... ok test_pathlib_name (backends.sqlite.tests.Tests.test_pathlib_name) ... ok test_regexp_function (backends.sqlite.tests.Tests.test_regexp_function) ... ok test_parameter_escaping (backends.tests.EscapingChecksDebug.test_parameter_escaping) ... ok test_paramless_no_escaping (backends.tests.EscapingChecksDebug.test_paramless_no_escaping) ... ok test_parameter_escaping (backends.tests.EscapingChecks.test_parameter_escaping) ... ok test_paramless_no_escaping (backends.tests.EscapingChecks.test_paramless_no_escaping) ... ok test_zero_as_autoval (backends.tests.MySQLPKZeroTests.test_zero_as_autoval) ... skipped 'Database has feature(s) allows_auto_pk_0' test_bad_parameter_count (backends.tests.ParameterHandlingTest.test_bad_parameter_count) An executemany call with too many/not enough parameters will raise an exception (Refs #12612) ... ok test_generic_relation (backends.tests.SequenceResetTest.test_generic_relation) Sequence names are correct when resetting generic relations (Ref #13941) ... ok test_debug_sql (backends.tests.LastExecutedQueryTest.test_debug_sql) ... ok test_last_executed_query (backends.tests.LastExecutedQueryTest.test_last_executed_query) ... ok test_last_executed_query_dict (backends.tests.LastExecutedQueryTest.test_last_executed_query_dict) ... skipped "Database doesn't support feature(s): supports_paramstyle_pyformat" test_last_executed_query_without_previous_query (backends.tests.LastExecutedQueryTest.test_last_executed_query_without_previous_query) last_executed_query should not raise an exception even if no previous ... ok test_query_encoding (backends.tests.LastExecutedQueryTest.test_query_encoding) last_executed_query() returns a string. ... ok test_request (sites_tests.tests.MiddlewareTest.test_request) ... ok test_none_as_null (null_queries.tests.NullQueriesTests.test_none_as_null) Regression test for the use of None as a query value. ... ok test_reverse_relations (null_queries.tests.NullQueriesTests.test_reverse_relations) Querying across reverse relations and then another relation should ... ok test_reverse_by_field (reverse_lookup.tests.ReverseLookupTests.test_reverse_by_field) ... ok test_reverse_by_related_name (reverse_lookup.tests.ReverseLookupTests.test_reverse_by_related_name) ... ok test_reverse_field_name_disallowed (reverse_lookup.tests.ReverseLookupTests.test_reverse_field_name_disallowed) If a related_name is given you can't use the field name instead ... ok test_basic (sites_tests.tests.CreateDefaultSiteTests.test_basic) #15346, #15573 - create_default_site() creates an example site only if ... ok test_custom_site_id (sites_tests.tests.CreateDefaultSiteTests.test_custom_site_id) #23945 - The configured ``SITE_ID`` should be respected. ... ok test_multi_db (sites_tests.tests.CreateDefaultSiteTests.test_multi_db) ... ok test_multi_db_with_router (sites_tests.tests.CreateDefaultSiteTests.test_multi_db_with_router) #16353, #16828 - The default site creation should respect db routing. ... ok test_no_site_id (sites_tests.tests.CreateDefaultSiteTests.test_no_site_id) #24488 - The pk should default to 1 if no ``SITE_ID`` is configured. ... ok test_save_another (sites_tests.tests.CreateDefaultSiteTests.test_save_another) #17415 - Another site can be created right after the default one. ... ok test_signal (sites_tests.tests.CreateDefaultSiteTests.test_signal) #23641 - Sending the ``post_migrate`` signal triggers creation of the ... ok test_unavailable_site_model (sites_tests.tests.CreateDefaultSiteTests.test_unavailable_site_model) #24075 - A Site shouldn't be created if the model isn't available. ... ok test_aggregate_over_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_aggregate_over_annotation) ... ok test_alias_forbidden_chars (annotations.tests.NonAggregateAnnotationTestCase.test_alias_forbidden_chars) ... ok test_alias_sql_injection (annotations.tests.NonAggregateAnnotationTestCase.test_alias_sql_injection) ... ok test_annotate_exists (annotations.tests.NonAggregateAnnotationTestCase.test_annotate_exists) ... ok test_annotate_with_aggregation (annotations.tests.NonAggregateAnnotationTestCase.test_annotate_with_aggregation) ... ok test_annotation_aggregate_with_m2o (annotations.tests.NonAggregateAnnotationTestCase.test_annotation_aggregate_with_m2o) ... ok test_annotation_exists_aggregate_values_chaining (annotations.tests.NonAggregateAnnotationTestCase.test_annotation_exists_aggregate_values_chaining) ... ok test_annotation_filter_with_subquery (annotations.tests.NonAggregateAnnotationTestCase.test_annotation_filter_with_subquery) ... ok test_annotation_in_f_grouped_by_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_annotation_in_f_grouped_by_annotation) ... ok test_annotation_reverse_m2m (annotations.tests.NonAggregateAnnotationTestCase.test_annotation_reverse_m2m) ... ok test_annotation_subquery_and_aggregate_values_chaining (annotations.tests.NonAggregateAnnotationTestCase.test_annotation_subquery_and_aggregate_values_chaining) ... ok test_annotation_subquery_outerref_transform (annotations.tests.NonAggregateAnnotationTestCase.test_annotation_subquery_outerref_transform) ... ok test_annotation_with_m2m (annotations.tests.NonAggregateAnnotationTestCase.test_annotation_with_m2m) ... ok test_arguments_must_be_expressions (annotations.tests.NonAggregateAnnotationTestCase.test_arguments_must_be_expressions) ... ok test_basic_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_basic_annotation) ... ok test_basic_f_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_basic_f_annotation) ... ok test_boolean_value_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_boolean_value_annotation) ... ok test_chaining_annotation_filter_with_m2m (annotations.tests.NonAggregateAnnotationTestCase.test_chaining_annotation_filter_with_m2m) ... ok test_chaining_transforms (annotations.tests.NonAggregateAnnotationTestCase.test_chaining_transforms) ... ok test_column_field_ordering (annotations.tests.NonAggregateAnnotationTestCase.test_column_field_ordering) Columns are aligned in the correct order for resolve_columns. This test ... ok test_column_field_ordering_with_deferred (annotations.tests.NonAggregateAnnotationTestCase.test_column_field_ordering_with_deferred) ... ok test_combined_annotation_commutative (annotations.tests.NonAggregateAnnotationTestCase.test_combined_annotation_commutative) ... ok test_combined_expression_annotation_with_aggregation (annotations.tests.NonAggregateAnnotationTestCase.test_combined_expression_annotation_with_aggregation) ... ok test_combined_f_expression_annotation_with_aggregation (annotations.tests.NonAggregateAnnotationTestCase.test_combined_f_expression_annotation_with_aggregation) ... ok test_custom_functions (annotations.tests.NonAggregateAnnotationTestCase.test_custom_functions) ... ok test_custom_functions_can_ref_other_functions (annotations.tests.NonAggregateAnnotationTestCase.test_custom_functions_can_ref_other_functions) ... ok test_custom_transform_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_custom_transform_annotation) ... ok test_decimal_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_decimal_annotation) ... ok test_defer_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_defer_annotation) Deferred attributes can be referenced by an annotation, ... ok test_distinct_on_with_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_distinct_on_with_annotation) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_empty_expression_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_empty_expression_annotation) ... ok test_filter_agg_with_double_f (annotations.tests.NonAggregateAnnotationTestCase.test_filter_agg_with_double_f) ... ok test_filter_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_filter_annotation) ... ok test_filter_annotation_with_double_f (annotations.tests.NonAggregateAnnotationTestCase.test_filter_annotation_with_double_f) ... ok test_filter_annotation_with_f (annotations.tests.NonAggregateAnnotationTestCase.test_filter_annotation_with_f) ... ok test_filter_decimal_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_filter_decimal_annotation) ... ok test_filter_wrong_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_filter_wrong_annotation) ... ok test_grouping_by_q_expression_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_grouping_by_q_expression_annotation) ... ok test_joined_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_joined_annotation) ... ok test_joined_transformed_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_joined_transformed_annotation) ... ok test_mixed_type_annotation_date_interval (annotations.tests.NonAggregateAnnotationTestCase.test_mixed_type_annotation_date_interval) ... ok test_mixed_type_annotation_numbers (annotations.tests.NonAggregateAnnotationTestCase.test_mixed_type_annotation_numbers) ... ok test_mti_annotations (annotations.tests.NonAggregateAnnotationTestCase.test_mti_annotations) Fields on an inherited model can be referenced by an ... ok test_null_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_null_annotation) Annotating None onto a model round-trips ... ok test_order_by_aggregate (annotations.tests.NonAggregateAnnotationTestCase.test_order_by_aggregate) ... ok test_order_by_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_order_by_annotation) ... ok test_q_expression_annotation_with_aggregation (annotations.tests.NonAggregateAnnotationTestCase.test_q_expression_annotation_with_aggregation) ... ok test_raw_sql_with_inherited_field (annotations.tests.NonAggregateAnnotationTestCase.test_raw_sql_with_inherited_field) ... ok test_rawsql_group_by_collapse (annotations.tests.NonAggregateAnnotationTestCase.test_rawsql_group_by_collapse) ... skipped "Database doesn't support feature(s): allows_group_by_pk" test_update_with_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_update_with_annotation) ... ok test_values_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_values_annotation) Annotations can reference fields in a values clause, ... ok test_values_with_pk_annotation (annotations.tests.NonAggregateAnnotationTestCase.test_values_with_pk_annotation) ... ok test_defer_annotate_select_related (defer_regress.tests.DeferAnnotateSelectRelatedTest.test_defer_annotate_select_related) ... ok test_delete_defered_model (defer_regress.tests.DeferDeletionSignalsTests.test_delete_defered_model) ... ok test_delete_defered_proxy_model (defer_regress.tests.DeferDeletionSignalsTests.test_delete_defered_proxy_model) ... ok test_empty_update_fields (update_only_fields.tests.UpdateOnlyFieldsTests.test_empty_update_fields) ... ok test_num_queries_inheritance (update_only_fields.tests.UpdateOnlyFieldsTests.test_num_queries_inheritance) ... ok test_select_related_only_interaction (update_only_fields.tests.UpdateOnlyFieldsTests.test_select_related_only_interaction) ... ok test_update_fields_basic (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_basic) ... ok test_update_fields_deferred (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_deferred) ... ok test_update_fields_fk_defer (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_fk_defer) ... ok test_update_fields_incorrect_params (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_incorrect_params) ... ok test_update_fields_inheritance (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_inheritance) ... ok test_update_fields_inheritance_defer (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_inheritance_defer) ... ok test_update_fields_inheritance_with_proxy_model (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_inheritance_with_proxy_model) ... ok test_update_fields_m2m (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_m2m) ... ok test_update_fields_only_1 (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_only_1) ... ok test_update_fields_only_2 (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_only_2) ... ok test_update_fields_only_repeated (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_only_repeated) ... ok test_update_fields_signals (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_fields_signals) ... ok test_update_non_concrete_field (update_only_fields.tests.UpdateOnlyFieldsTests.test_update_non_concrete_field) ... ok test_check_site_id (sites_tests.tests.SitesFrameworkTests.test_check_site_id) ... ok test_clear_site_cache (sites_tests.tests.SitesFrameworkTests.test_clear_site_cache) ... ok test_clear_site_cache_domain (sites_tests.tests.SitesFrameworkTests.test_clear_site_cache_domain) ... ok test_delete_all_sites_clears_cache (sites_tests.tests.SitesFrameworkTests.test_delete_all_sites_clears_cache) ... ok test_domain_name_with_whitespaces (sites_tests.tests.SitesFrameworkTests.test_domain_name_with_whitespaces) ... ok test_get_current_site (sites_tests.tests.SitesFrameworkTests.test_get_current_site) ... ok test_get_current_site_host_with_trailing_dot (sites_tests.tests.SitesFrameworkTests.test_get_current_site_host_with_trailing_dot) The site is matched if the name in the request has a trailing dot. ... ok test_get_current_site_no_site_id (sites_tests.tests.SitesFrameworkTests.test_get_current_site_no_site_id) ... ok test_get_current_site_no_site_id_and_handle_port_fallback (sites_tests.tests.SitesFrameworkTests.test_get_current_site_no_site_id_and_handle_port_fallback) ... ok test_site_cache (sites_tests.tests.SitesFrameworkTests.test_site_cache) ... ok test_site_manager (sites_tests.tests.SitesFrameworkTests.test_site_manager) ... ok test_site_natural_key (sites_tests.tests.SitesFrameworkTests.test_site_natural_key) ... ok test_unique_domain (sites_tests.tests.SitesFrameworkTests.test_unique_domain) ... ok test_valid_site_id (sites_tests.tests.SitesFrameworkTests.test_valid_site_id) ... ok test_basic (defer_regress.tests.DeferRegressionTest.test_basic) ... ok test_defer_with_select_related (defer_regress.tests.DeferRegressionTest.test_defer_with_select_related) ... ok test_only_and_defer_usage_on_proxy_models (defer_regress.tests.DeferRegressionTest.test_only_and_defer_usage_on_proxy_models) ... ok test_only_with_select_related (defer_regress.tests.DeferRegressionTest.test_only_with_select_related) ... ok test_proxy_model_defer_with_select_related (defer_regress.tests.DeferRegressionTest.test_proxy_model_defer_with_select_related) ... ok test_resolve_columns (defer_regress.tests.DeferRegressionTest.test_resolve_columns) ... ok test_reverse_one_to_one_relations (defer_regress.tests.DeferRegressionTest.test_reverse_one_to_one_relations) ... ok test_ticket_12163 (defer_regress.tests.DeferRegressionTest.test_ticket_12163) ... ok test_ticket_16409 (defer_regress.tests.DeferRegressionTest.test_ticket_16409) ... ok test_ticket_23270 (defer_regress.tests.DeferRegressionTest.test_ticket_23270) ... ok test_bounded_params (admin_changelist.test_date_hierarchy.DateHierarchyTests.test_bounded_params) ... ok test_bounded_params_with_dst_time_zone (admin_changelist.test_date_hierarchy.DateHierarchyTests.test_bounded_params_with_dst_time_zone) ... ok test_bounded_params_with_time_zone (admin_changelist.test_date_hierarchy.DateHierarchyTests.test_bounded_params_with_time_zone) ... ok test_invalid_params (admin_changelist.test_date_hierarchy.DateHierarchyTests.test_invalid_params) ... ok test_attribute_error (custom_columns.tests.CustomColumnsTests.test_attribute_error) ... ok test_author_filtering (custom_columns.tests.CustomColumnsTests.test_author_filtering) ... ok test_author_get (custom_columns.tests.CustomColumnsTests.test_author_get) ... ok test_author_get_attributes (custom_columns.tests.CustomColumnsTests.test_author_get_attributes) ... ok test_author_querying (custom_columns.tests.CustomColumnsTests.test_author_querying) ... ok test_field_error (custom_columns.tests.CustomColumnsTests.test_field_error) ... ok test_filter_first_name (custom_columns.tests.CustomColumnsTests.test_filter_first_name) ... ok test_filter_on_nonexistent_field (custom_columns.tests.CustomColumnsTests.test_filter_on_nonexistent_field) ... ok test_get_all_articles_for_an_author (custom_columns.tests.CustomColumnsTests.test_get_all_articles_for_an_author) ... ok test_get_all_authors_for_an_article (custom_columns.tests.CustomColumnsTests.test_get_all_authors_for_an_article) ... ok test_get_author_m2m_relation (custom_columns.tests.CustomColumnsTests.test_get_author_m2m_relation) ... ok test_get_first_name (custom_columns.tests.CustomColumnsTests.test_get_first_name) ... ok test_m2m_table (custom_columns.tests.CustomColumnsTests.test_m2m_table) ... ok test_query_all_available_authors (custom_columns.tests.CustomColumnsTests.test_query_all_available_authors) ... ok test_custom_user_pk_not_named_id (admin_changelist.tests.GetAdminLogTests.test_custom_user_pk_not_named_id) {% get_admin_log %} works if the user model's primary key isn't named ... ok test_missing_args (admin_changelist.tests.GetAdminLogTests.test_missing_args) ... ok test_no_user (admin_changelist.tests.GetAdminLogTests.test_no_user) {% get_admin_log %} works without specifying a user. ... ok test_non_integer_limit (admin_changelist.tests.GetAdminLogTests.test_non_integer_limit) ... ok test_without_as (admin_changelist.tests.GetAdminLogTests.test_without_as) ... ok test_without_for_user (admin_changelist.tests.GetAdminLogTests.test_without_for_user) ... ok test_automatic_m2m_column_names (model_package.tests.ModelPackageTests.test_automatic_m2m_column_names) Regression for #12386 - field names on the autogenerated intermediate ... ok test_m2m_tables_in_subpackage_models (model_package.tests.ModelPackageTests.test_m2m_tables_in_subpackage_models) Regression for #12168: models split into subpackages still get M2M ... ok test_models_in_the_test_package (model_package.tests.ModelPackageTests.test_models_in_the_test_package) Regression for #12245 - Models can exist in the test package, too. ... ok test_response_gone_class (redirects_tests.tests.OverriddenRedirectMiddlewareTests.test_response_gone_class) ... ok test_response_redirect_class (redirects_tests.tests.OverriddenRedirectMiddlewareTests.test_response_redirect_class) ... ok test_model (redirects_tests.tests.RedirectTests.test_model) ... ok test_redirect (redirects_tests.tests.RedirectTests.test_redirect) ... ok test_redirect_not_found_with_append_slash (redirects_tests.tests.RedirectTests.test_redirect_not_found_with_append_slash) Exercise the second Redirect.DoesNotExist branch in ... ok test_redirect_shortcircuits_non_404_response (redirects_tests.tests.RedirectTests.test_redirect_shortcircuits_non_404_response) RedirectFallbackMiddleware short-circuits on non-404 requests. ... ok test_redirect_with_append_slash (redirects_tests.tests.RedirectTests.test_redirect_with_append_slash) ... ok test_redirect_with_append_slash_and_query_string (redirects_tests.tests.RedirectTests.test_redirect_with_append_slash_and_query_string) ... ok test_response_gone (redirects_tests.tests.RedirectTests.test_response_gone) When the redirect target is '', return a 410 ... ok test_sites_not_installed (redirects_tests.tests.RedirectTests.test_sites_not_installed) ... ok test_attribute_name_not_python_keyword (inspectdb.tests.InspectDBTestCase.test_attribute_name_not_python_keyword) ... ok test_char_field_db_collation (inspectdb.tests.InspectDBTestCase.test_char_field_db_collation) ... ok test_custom_fields (inspectdb.tests.InspectDBTestCase.test_custom_fields) Introspection of columns with a custom field (#21090) ... ok test_digits_column_name_introspection (inspectdb.tests.InspectDBTestCase.test_digits_column_name_introspection) Introspection of column names consist/start with digits (#16536/#17676) ... ok test_field_types (inspectdb.tests.InspectDBTestCase.test_field_types) Test introspection of various Django field types ... ok test_introspection_errors (inspectdb.tests.InspectDBTestCase.test_introspection_errors) Introspection errors should not crash the command, and the error should ... ok test_json_field (inspectdb.tests.InspectDBTestCase.test_json_field) ... ok test_managed_models (inspectdb.tests.InspectDBTestCase.test_managed_models) By default the command generates models with `Meta.managed = False` (#14305) ... ok test_number_field_types (inspectdb.tests.InspectDBTestCase.test_number_field_types) Test introspection of various Django field types ... ok test_special_column_name_introspection (inspectdb.tests.InspectDBTestCase.test_special_column_name_introspection) Introspection of column names containing special characters, ... ok test_stealth_table_name_filter_option (inspectdb.tests.InspectDBTestCase.test_stealth_table_name_filter_option) ... ok test_table_name_introspection (inspectdb.tests.InspectDBTestCase.test_table_name_introspection) Introspection of table names containing special characters, ... ok test_table_option (inspectdb.tests.InspectDBTestCase.test_table_option) inspectdb can inspect a subset of tables by passing the table names as ... ok test_text_field_db_collation (inspectdb.tests.InspectDBTestCase.test_text_field_db_collation) ... ok test_unique_together_meta (inspectdb.tests.InspectDBTestCase.test_unique_together_meta) ... ok test_unsupported_unique_together (inspectdb.tests.InspectDBTestCase.test_unsupported_unique_together) Unsupported index types (COALESCE here) are skipped. ... skipped 'PostgreSQL specific SQL' test_cyclic (admin_utils.tests.NestedObjectsTests.test_cyclic) ... ok test_non_added_parent (admin_utils.tests.NestedObjectsTests.test_non_added_parent) ... ok test_on_delete_do_nothing (admin_utils.tests.NestedObjectsTests.test_on_delete_do_nothing) The nested collector doesn't query for DO_NOTHING objects. ... ok test_queries (admin_utils.tests.NestedObjectsTests.test_queries) ... ok test_relation_on_abstract (admin_utils.tests.NestedObjectsTests.test_relation_on_abstract) NestedObjects.collect() doesn't trip (AttributeError) on the special ... ok test_siblings (admin_utils.tests.NestedObjectsTests.test_siblings) ... ok test_unrelated_roots (admin_utils.tests.NestedObjectsTests.test_unrelated_roots) ... ok test_template_detail_path_traversal (admin_docs.test_views.AdminDocViewDefaultEngineOnly.test_template_detail_path_traversal) ... ok test_action_flag_choices (admin_utils.test_logentry.LogEntryTests.test_action_flag_choices) ... ok test_log_action (admin_utils.test_logentry.LogEntryTests.test_log_action) ... ok test_logentry_change_message (admin_utils.test_logentry.LogEntryTests.test_logentry_change_message) LogEntry.change_message is stored as a dumped JSON structure to be able ... ok test_logentry_change_message_formsets (admin_utils.test_logentry.LogEntryTests.test_logentry_change_message_formsets) All messages for changed formsets are logged in a change message. ... ok test_logentry_change_message_localized_datetime_input (admin_utils.test_logentry.LogEntryTests.test_logentry_change_message_localized_datetime_input) Localized date/time inputs shouldn't affect changed form data detection. ... ok test_logentry_change_message_not_json (admin_utils.test_logentry.LogEntryTests.test_logentry_change_message_not_json) LogEntry.change_message was a string before Django 1.10. ... ok test_logentry_get_admin_url (admin_utils.test_logentry.LogEntryTests.test_logentry_get_admin_url) LogEntry.get_admin_url returns a URL to edit the entry's object or ... ok test_logentry_get_edited_object (admin_utils.test_logentry.LogEntryTests.test_logentry_get_edited_object) LogEntry.get_edited_object() returns the edited object of a LogEntry ... ok test_logentry_repr (admin_utils.test_logentry.LogEntryTests.test_logentry_repr) ... ok test_logentry_save (admin_utils.test_logentry.LogEntryTests.test_logentry_save) LogEntry.action_time is a timestamp of the date when the entry was ... ok test_logentry_unicode (admin_utils.test_logentry.LogEntryTests.test_logentry_unicode) ... ok test_proxy_model_content_type_is_used_for_log_entries (admin_utils.test_logentry.LogEntryTests.test_proxy_model_content_type_is_used_for_log_entries) Log entries for proxy models should have the proxy model's contenttype ... ok test_recentactions_without_content_type (admin_utils.test_logentry.LogEntryTests.test_recentactions_without_content_type) If a LogEntry is missing content_type it will not display it in span ... ok test_callable_object_view (admin_docs.test_middleware.XViewMiddlewareTest.test_callable_object_view) ... ok test_no_auth_middleware (admin_docs.test_middleware.XViewMiddlewareTest.test_no_auth_middleware) ... ok test_xview_class (admin_docs.test_middleware.XViewMiddlewareTest.test_xview_class) ... ok test_xview_func (admin_docs.test_middleware.XViewMiddlewareTest.test_xview_func) ... ok test_app_not_found (admin_docs.test_views.TestModelDetailView.test_app_not_found) ... ok test_descriptions_render_correctly (admin_docs.test_views.TestModelDetailView.test_descriptions_render_correctly) The ``description`` field should render correctly for each field type. ... ok test_instance_of_property_methods_are_displayed (admin_docs.test_views.TestModelDetailView.test_instance_of_property_methods_are_displayed) Model properties are displayed as fields. ... ok test_method_data_types (admin_docs.test_views.TestModelDetailView.test_method_data_types) ... ok test_method_excludes (admin_docs.test_views.TestModelDetailView.test_method_excludes) Methods that begin with strings defined in ... ok test_methods_with_arguments (admin_docs.test_views.TestModelDetailView.test_methods_with_arguments) Methods that take arguments should also displayed. ... ok test_methods_with_arguments_display_arguments (admin_docs.test_views.TestModelDetailView.test_methods_with_arguments_display_arguments) Methods with arguments should have their arguments displayed. ... ok test_methods_with_arguments_display_arguments_default_value (admin_docs.test_views.TestModelDetailView.test_methods_with_arguments_display_arguments_default_value) Methods with keyword arguments should have their arguments displayed. ... ok test_methods_with_multiple_arguments_display_arguments (admin_docs.test_views.TestModelDetailView.test_methods_with_multiple_arguments_display_arguments) Methods with multiple arguments should have all their arguments ... ok test_model_detail_title (admin_docs.test_views.TestModelDetailView.test_model_detail_title) ... ok test_model_docstring_renders_correctly (admin_docs.test_views.TestModelDetailView.test_model_docstring_renders_correctly) ... ok test_model_not_found (admin_docs.test_views.TestModelDetailView.test_model_not_found) ... ok test_model_with_many_to_one (admin_docs.test_views.TestModelDetailView.test_model_with_many_to_one) ... ok test_model_with_no_backward_relations_render_only_relevant_fields (admin_docs.test_views.TestModelDetailView.test_model_with_no_backward_relations_render_only_relevant_fields) A model with ``related_name`` of `+` shouldn't show backward ... ok test_empty (empty.tests.EmptyModelTests.test_empty) ... ok test_builtin_lookup_in_search_fields (admin_changelist.tests.ChangeListTests.test_builtin_lookup_in_search_fields) ... ok test_changelist_search_form_validation (admin_changelist.tests.ChangeListTests.test_changelist_search_form_validation) ... ok test_changelist_view_list_editable_changed_objects_uses_filter (admin_changelist.tests.ChangeListTests.test_changelist_view_list_editable_changed_objects_uses_filter) list_editable edits use a filtered queryset to limit memory usage. ... ok test_clear_all_filters_link (admin_changelist.tests.ChangeListTests.test_clear_all_filters_link) ... ok test_clear_all_filters_link_callable_filter (admin_changelist.tests.ChangeListTests.test_clear_all_filters_link_callable_filter) ... ok test_computed_list_display_localization (admin_changelist.tests.ChangeListTests.test_computed_list_display_localization) Regression test for #13196: output of functions should be localized ... ok test_custom_lookup_in_search_fields (admin_changelist.tests.ChangeListTests.test_custom_lookup_in_search_fields) ... ok test_custom_lookup_with_pk_shortcut (admin_changelist.tests.ChangeListTests.test_custom_lookup_with_pk_shortcut) ... ok test_custom_paginator (admin_changelist.tests.ChangeListTests.test_custom_paginator) ... ok test_deterministic_order_for_model_ordered_by_its_manager (admin_changelist.tests.ChangeListTests.test_deterministic_order_for_model_ordered_by_its_manager) The primary key is used in the ordering of the changelist's results to ... ok test_deterministic_order_for_unordered_model (admin_changelist.tests.ChangeListTests.test_deterministic_order_for_unordered_model) The primary key is used in the ordering of the changelist's results to ... ok test_dynamic_list_display (admin_changelist.tests.ChangeListTests.test_dynamic_list_display) Regression tests for #14206: dynamic list_display support. ... ok test_dynamic_list_display_links (admin_changelist.tests.ChangeListTests.test_dynamic_list_display_links) Regression tests for #16257: dynamic list_display_links support. ... ok test_dynamic_list_filter (admin_changelist.tests.ChangeListTests.test_dynamic_list_filter) Regression tests for ticket #17646: dynamic list_filter support. ... ok test_dynamic_search_fields (admin_changelist.tests.ChangeListTests.test_dynamic_search_fields) ... ok test_get_edited_object_ids (admin_changelist.tests.ChangeListTests.test_get_edited_object_ids) ... ok test_get_list_editable_queryset (admin_changelist.tests.ChangeListTests.test_get_list_editable_queryset) ... ok test_get_list_editable_queryset_with_regex_chars_in_prefix (admin_changelist.tests.ChangeListTests.test_get_list_editable_queryset_with_regex_chars_in_prefix) ... ok test_get_select_related_custom_method (admin_changelist.tests.ChangeListTests.test_get_select_related_custom_method) ... ok test_multiuser_edit (admin_changelist.tests.ChangeListTests.test_multiuser_edit) Simultaneous edits of list_editable fields on the changelist by ... ok test_no_clear_all_filters_link (admin_changelist.tests.ChangeListTests.test_no_clear_all_filters_link) ... ok test_no_duplicates_for_inherited_m2m_in_list_filter (admin_changelist.tests.ChangeListTests.test_no_duplicates_for_inherited_m2m_in_list_filter) Regression test for #13902: When using a ManyToMany in list_filter, ... ok test_no_duplicates_for_m2m_in_list_filter (admin_changelist.tests.ChangeListTests.test_no_duplicates_for_m2m_in_list_filter) Regression test for #13902: When using a ManyToMany in list_filter, ... ok test_no_duplicates_for_m2m_to_inherited_in_list_filter (admin_changelist.tests.ChangeListTests.test_no_duplicates_for_m2m_to_inherited_in_list_filter) Regression test for #13902: When using a ManyToMany in list_filter, ... ok test_no_duplicates_for_many_to_many_at_second_level_in_search_fields (admin_changelist.tests.ChangeListTests.test_no_duplicates_for_many_to_many_at_second_level_in_search_fields) When using a ManyToMany in search_fields at the second level behind a ... ok test_no_duplicates_for_non_unique_related_object_in_list_filter (admin_changelist.tests.ChangeListTests.test_no_duplicates_for_non_unique_related_object_in_list_filter) Regressions tests for #15819: If a field listed in list_filters is a ... ok test_no_duplicates_for_non_unique_related_object_in_search_fields (admin_changelist.tests.ChangeListTests.test_no_duplicates_for_non_unique_related_object_in_search_fields) Regressions tests for #15819: If a field listed in search_fields ... ok test_no_duplicates_for_through_m2m_at_second_level_in_list_filter (admin_changelist.tests.ChangeListTests.test_no_duplicates_for_through_m2m_at_second_level_in_list_filter) When using a ManyToMany in list_filter at the second level behind a ... ok test_no_duplicates_for_through_m2m_in_list_filter (admin_changelist.tests.ChangeListTests.test_no_duplicates_for_through_m2m_in_list_filter) Regression test for #13902: When using a ManyToMany in list_filter, ... ok test_no_exists_for_m2m_in_list_filter_without_params (admin_changelist.tests.ChangeListTests.test_no_exists_for_m2m_in_list_filter_without_params) If a ManyToManyField is in list_filter but isn't in any lookup params, ... ok test_no_list_display_links (admin_changelist.tests.ChangeListTests.test_no_list_display_links) #15185 -- Allow no links from the 'change list' view grid. ... ok test_object_tools_displayed_no_add_permission (admin_changelist.tests.ChangeListTests.test_object_tools_displayed_no_add_permission) When ModelAdmin.has_add_permission() returns False, the object-tools ... ok test_pagination (admin_changelist.tests.ChangeListTests.test_pagination) Regression tests for #12893: Pagination in admins changelist doesn't ... ok test_pagination_page_range (admin_changelist.tests.ChangeListTests.test_pagination_page_range) Regression tests for ticket #15653: ensure the number of pages ... ok test_pk_in_search_fields (admin_changelist.tests.ChangeListTests.test_pk_in_search_fields) ... ok test_result_list_editable (admin_changelist.tests.ChangeListTests.test_result_list_editable) Regression test for #14312: list_editable with pagination ... ok test_result_list_editable_html (admin_changelist.tests.ChangeListTests.test_result_list_editable_html) Regression tests for #11791: Inclusion tag result_list generates a ... ok test_result_list_empty_changelist_value (admin_changelist.tests.ChangeListTests.test_result_list_empty_changelist_value) Regression test for #14982: EMPTY_CHANGELIST_VALUE should be honored ... ok test_result_list_html (admin_changelist.tests.ChangeListTests.test_result_list_html) Inclusion tag result_list generates a table when with default ... ok test_result_list_set_empty_value_display_in_model_admin (admin_changelist.tests.ChangeListTests.test_result_list_set_empty_value_display_in_model_admin) Empty value display can be set in ModelAdmin or individual fields. ... ok test_result_list_set_empty_value_display_on_admin_site (admin_changelist.tests.ChangeListTests.test_result_list_set_empty_value_display_on_admin_site) Empty value display can be set on AdminSite. ... ok test_select_related_as_empty_tuple (admin_changelist.tests.ChangeListTests.test_select_related_as_empty_tuple) ... ok test_select_related_as_tuple (admin_changelist.tests.ChangeListTests.test_select_related_as_tuple) ... ok test_select_related_preserved (admin_changelist.tests.ChangeListTests.test_select_related_preserved) Regression test for #10348: ChangeList.get_queryset() shouldn't ... ok test_show_all (admin_changelist.tests.ChangeListTests.test_show_all) ... ok test_spanning_relations_with_custom_lookup_in_search_fields (admin_changelist.tests.ChangeListTests.test_spanning_relations_with_custom_lookup_in_search_fields) ... ok test_specified_ordering_by_f_expression (admin_changelist.tests.ChangeListTests.test_specified_ordering_by_f_expression) ... ok test_specified_ordering_by_f_expression_without_asc_desc (admin_changelist.tests.ChangeListTests.test_specified_ordering_by_f_expression_without_asc_desc) ... ok test_total_ordering_optimization (admin_changelist.tests.ChangeListTests.test_total_ordering_optimization) ... ok test_total_ordering_optimization_meta_constraints (admin_changelist.tests.ChangeListTests.test_total_ordering_optimization_meta_constraints) ... ok test_tuple_list_display (admin_changelist.tests.ChangeListTests.test_tuple_list_display) ... ok test_21432 (datetimes.tests.DateTimesTests.test_21432) ... ok test_datetimes_ambiguous_and_invalid_times (datetimes.tests.DateTimesTests.test_datetimes_ambiguous_and_invalid_times) ... ok test_datetimes_disallows_date_fields (datetimes.tests.DateTimesTests.test_datetimes_disallows_date_fields) ... ok test_datetimes_has_lazy_iterator (datetimes.tests.DateTimesTests.test_datetimes_has_lazy_iterator) ... ok test_datetimes_returns_available_dates_for_given_scope_and_given_field (datetimes.tests.DateTimesTests.test_datetimes_returns_available_dates_for_given_scope_and_given_field) ... ok test_related_model_traverse (datetimes.tests.DateTimesTests.test_related_model_traverse) ... ok test_dates_avoid_datetime_cast (dates.tests.DatesTests.test_dates_avoid_datetime_cast) ... skipped 'Test checks MySQL query syntax' test_dates_fails_when_given_invalid_field_argument (dates.tests.DatesTests.test_dates_fails_when_given_invalid_field_argument) ... ok test_dates_fails_when_given_invalid_kind_argument (dates.tests.DatesTests.test_dates_fails_when_given_invalid_kind_argument) ... ok test_dates_fails_when_given_invalid_order_argument (dates.tests.DatesTests.test_dates_fails_when_given_invalid_order_argument) ... ok test_dates_fails_when_no_arguments_are_provided (dates.tests.DatesTests.test_dates_fails_when_no_arguments_are_provided) ... ok test_dates_trunc_datetime_fields (dates.tests.DatesTests.test_dates_trunc_datetime_fields) ... ok test_related_model_traverse (dates.tests.DatesTests.test_related_model_traverse) ... ok test_case_aggregate (aggregation.test_filter_argument.FilteredAggregateTests.test_case_aggregate) ... ok test_double_filtered_aggregates (aggregation.test_filter_argument.FilteredAggregateTests.test_double_filtered_aggregates) ... ok test_excluded_aggregates (aggregation.test_filter_argument.FilteredAggregateTests.test_excluded_aggregates) ... ok test_filtered_aggregate_on_annotate (aggregation.test_filter_argument.FilteredAggregateTests.test_filtered_aggregate_on_annotate) ... ok test_filtered_aggregate_ref_annotation (aggregation.test_filter_argument.FilteredAggregateTests.test_filtered_aggregate_ref_annotation) ... ok test_filtered_aggregate_ref_multiple_subquery_annotation (aggregation.test_filter_argument.FilteredAggregateTests.test_filtered_aggregate_ref_multiple_subquery_annotation) ... ok test_filtered_aggregate_ref_subquery_annotation (aggregation.test_filter_argument.FilteredAggregateTests.test_filtered_aggregate_ref_subquery_annotation) ... ok test_filtered_aggregates (aggregation.test_filter_argument.FilteredAggregateTests.test_filtered_aggregates) ... ok test_filtered_numerical_aggregates (aggregation.test_filter_argument.FilteredAggregateTests.test_filtered_numerical_aggregates) ... ok test_filtered_reused_subquery (aggregation.test_filter_argument.FilteredAggregateTests.test_filtered_reused_subquery) ... ok test_plain_annotate (aggregation.test_filter_argument.FilteredAggregateTests.test_plain_annotate) ... ok test_related_aggregates_m2m (aggregation.test_filter_argument.FilteredAggregateTests.test_related_aggregates_m2m) ... ok test_related_aggregates_m2m_and_fk (aggregation.test_filter_argument.FilteredAggregateTests.test_related_aggregates_m2m_and_fk) ... ok test_sum_star_exception (aggregation.test_filter_argument.FilteredAggregateTests.test_sum_star_exception) ... ok test_batch_same_vals (bulk_create.tests.BulkCreateTests.test_batch_same_vals) ... ok test_bulk_insert_expressions (bulk_create.tests.BulkCreateTests.test_bulk_insert_expressions) ... ok test_bulk_insert_nullable_fields (bulk_create.tests.BulkCreateTests.test_bulk_insert_nullable_fields) ... ok test_efficiency (bulk_create.tests.BulkCreateTests.test_efficiency) ... ok test_empty_model (bulk_create.tests.BulkCreateTests.test_empty_model) ... ok test_explicit_batch_size (bulk_create.tests.BulkCreateTests.test_explicit_batch_size) ... ok test_explicit_batch_size_efficiency (bulk_create.tests.BulkCreateTests.test_explicit_batch_size_efficiency) ... ok test_explicit_batch_size_respects_max_batch_size (bulk_create.tests.BulkCreateTests.test_explicit_batch_size_respects_max_batch_size) ... ok test_ignore_conflicts_ignore (bulk_create.tests.BulkCreateTests.test_ignore_conflicts_ignore) ... ok test_ignore_conflicts_value_error (bulk_create.tests.BulkCreateTests.test_ignore_conflicts_value_error) ... skipped 'Database has feature(s) supports_ignore_conflicts' test_large_batch (bulk_create.tests.BulkCreateTests.test_large_batch) ... ok test_large_batch_efficiency (bulk_create.tests.BulkCreateTests.test_large_batch_efficiency) ... ok test_large_batch_mixed (bulk_create.tests.BulkCreateTests.test_large_batch_mixed) Test inserting a large batch with objects having primary key set ... ok test_large_batch_mixed_efficiency (bulk_create.tests.BulkCreateTests.test_large_batch_mixed_efficiency) Test inserting a large batch with objects having primary key set ... ok test_large_single_field_batch (bulk_create.tests.BulkCreateTests.test_large_single_field_batch) ... ok test_long_and_short_text (bulk_create.tests.BulkCreateTests.test_long_and_short_text) ... ok test_long_non_ascii_text (bulk_create.tests.BulkCreateTests.test_long_non_ascii_text) Inserting non-ASCII values with a length in the range 2001 to 4000 ... ok test_multi_table_inheritance_unsupported (bulk_create.tests.BulkCreateTests.test_multi_table_inheritance_unsupported) ... ok test_non_auto_increment_pk (bulk_create.tests.BulkCreateTests.test_non_auto_increment_pk) ... ok test_non_auto_increment_pk_efficiency (bulk_create.tests.BulkCreateTests.test_non_auto_increment_pk_efficiency) ... ok test_nullable_fk_after_parent (bulk_create.tests.BulkCreateTests.test_nullable_fk_after_parent) ... ok test_nullable_fk_after_parent_bulk_create (bulk_create.tests.BulkCreateTests.test_nullable_fk_after_parent_bulk_create) ... skipped "Database doesn't support feature(s): can_return_rows_from_bulk_insert" test_proxy_inheritance_supported (bulk_create.tests.BulkCreateTests.test_proxy_inheritance_supported) ... ok test_set_pk_and_insert_single_item (bulk_create.tests.BulkCreateTests.test_set_pk_and_insert_single_item) ... skipped "Database doesn't support feature(s): can_return_rows_from_bulk_insert" test_set_pk_and_query_efficiency (bulk_create.tests.BulkCreateTests.test_set_pk_and_query_efficiency) ... skipped "Database doesn't support feature(s): can_return_rows_from_bulk_insert" test_set_state (bulk_create.tests.BulkCreateTests.test_set_state) ... skipped "Database doesn't support feature(s): can_return_rows_from_bulk_insert" test_set_state_with_pk_specified (bulk_create.tests.BulkCreateTests.test_set_state_with_pk_specified) ... ok test_simple (bulk_create.tests.BulkCreateTests.test_simple) ... ok test_unsaved_parent (bulk_create.tests.BulkCreateTests.test_unsaved_parent) ... ok test_zero_as_autoval (bulk_create.tests.BulkCreateTests.test_zero_as_autoval) Zero as id for AutoField should raise exception in MySQL, because MySQL ... skipped 'Database has feature(s) allows_auto_pk_0' test_default_ordering (admin_ordering.tests.TestAdminOrdering.test_default_ordering) The default ordering should be by name, as specified in the inner Meta ... ok test_dynamic_ordering (admin_ordering.tests.TestAdminOrdering.test_dynamic_ordering) Let's use a custom ModelAdmin that changes the ordering dynamically. ... ok test_specified_ordering (admin_ordering.tests.TestAdminOrdering.test_specified_ordering) Let's use a custom ModelAdmin that changes the ordering, and make sure ... ok test_specified_ordering_by_f_expression (admin_ordering.tests.TestAdminOrdering.test_specified_ordering_by_f_expression) ... ok test_default_ordering (admin_ordering.tests.TestInlineModelAdminOrdering.test_default_ordering) The default ordering should be by name, as specified in the inner Meta ... ok test_specified_ordering (admin_ordering.tests.TestInlineModelAdminOrdering.test_specified_ordering) Let's check with ordering set to something different than the default. ... ok test_admin_ordering_beats_model_ordering (admin_ordering.tests.TestRelatedFieldsAdminOrdering.test_admin_ordering_beats_model_ordering) ... ok test_admin_with_no_ordering_fallback_to_model_ordering (admin_ordering.tests.TestRelatedFieldsAdminOrdering.test_admin_with_no_ordering_fallback_to_model_ordering) ... ok test_custom_queryset_still_wins (admin_ordering.tests.TestRelatedFieldsAdminOrdering.test_custom_queryset_still_wins) Custom queryset has still precedence (#21405) ... ok test_no_admin_fallback_to_model_ordering (admin_ordering.tests.TestRelatedFieldsAdminOrdering.test_no_admin_fallback_to_model_ordering) ... ok test_field_defaults (field_defaults.tests.DefaultTests.test_field_defaults) ... ok test_bookmarklets (admin_docs.test_views.AdminDocViewTests.test_bookmarklets) ... ok test_index (admin_docs.test_views.AdminDocViewTests.test_index) ... ok test_missing_docutils (admin_docs.test_views.AdminDocViewTests.test_missing_docutils) ... ok test_model_index (admin_docs.test_views.AdminDocViewTests.test_model_index) ... ok test_namespaced_view_detail (admin_docs.test_views.AdminDocViewTests.test_namespaced_view_detail) ... ok test_no_sites_framework (admin_docs.test_views.AdminDocViewTests.test_no_sites_framework) Without the sites framework, should not access SITE_ID or Site ... ok test_template_detail (admin_docs.test_views.AdminDocViewTests.test_template_detail) ... ok test_templatefilter_index (admin_docs.test_views.AdminDocViewTests.test_templatefilter_index) ... ok test_templatetag_index (admin_docs.test_views.AdminDocViewTests.test_templatetag_index) ... ok test_view_detail (admin_docs.test_views.AdminDocViewTests.test_view_detail) ... ok test_view_detail_as_method (admin_docs.test_views.AdminDocViewTests.test_view_detail_as_method) Views that are methods can be displayed. ... ok test_view_detail_illegal_import (admin_docs.test_views.AdminDocViewTests.test_view_detail_illegal_import) ... ok test_view_index (admin_docs.test_views.AdminDocViewTests.test_view_index) ... ok test_view_index_with_method (admin_docs.test_views.AdminDocViewTests.test_view_index_with_method) Views that are methods are listed correctly. ... ok test_backend_range_save (model_fields.test_autofield.BigAutoFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_autofield.BigAutoFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_autofield.BigAutoFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_autofield.BigAutoFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_autofield.BigAutoFieldTests.test_invalid_value) ... ok test_redundant_backend_range_validators (model_fields.test_autofield.BigAutoFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_autofield.BigAutoFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_autofield.BigAutoFieldTests.test_types) ... ok test_backend_range_save (model_fields.test_autofield.AutoFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_autofield.AutoFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_autofield.AutoFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_autofield.AutoFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_autofield.AutoFieldTests.test_invalid_value) ... ok test_redundant_backend_range_validators (model_fields.test_autofield.AutoFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_autofield.AutoFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_autofield.AutoFieldTests.test_types) ... ok test_backend_range_save (model_fields.test_integerfield.BigIntegerFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_integerfield.BigIntegerFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_integerfield.BigIntegerFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_integerfield.BigIntegerFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_integerfield.BigIntegerFieldTests.test_invalid_value) ... ok test_redundant_backend_range_validators (model_fields.test_integerfield.BigIntegerFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_integerfield.BigIntegerFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_integerfield.BigIntegerFieldTests.test_types) ... ok test_backend_range_save (model_fields.test_integerfield.IntegerFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_integerfield.IntegerFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_integerfield.IntegerFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_integerfield.IntegerFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_integerfield.IntegerFieldTests.test_invalid_value) ... ok test_redundant_backend_range_validators (model_fields.test_integerfield.IntegerFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_integerfield.IntegerFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_integerfield.IntegerFieldTests.test_types) ... ok test_bookmarklets (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_bookmarklets) ... ok test_index (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_index) ... ok test_missing_docutils (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_missing_docutils) ... ok test_model_index (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_model_index) ... ok test_namespaced_view_detail (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_namespaced_view_detail) ... ok test_no_sites_framework (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_no_sites_framework) Without the sites framework, should not access SITE_ID or Site ... ok test_template_detail (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_template_detail) ... ok test_templatefilter_index (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_templatefilter_index) ... ok test_templatetag_index (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_templatetag_index) ... ok test_view_detail (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_view_detail) ... ok test_view_detail_as_method (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_view_detail_as_method) Views that are methods can be displayed. ... ok test_view_detail_illegal_import (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_view_detail_illegal_import) ... ok test_view_index (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_view_index) ... ok test_view_index_with_method (admin_docs.test_views.AdminDocViewWithMultipleEngines.test_view_index_with_method) Views that are methods are listed correctly. ... ok test_backend_range_save (model_fields.test_autofield.SmallAutoFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_autofield.SmallAutoFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_autofield.SmallAutoFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_autofield.SmallAutoFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_autofield.SmallAutoFieldTests.test_invalid_value) ... ok test_redundant_backend_range_validators (model_fields.test_autofield.SmallAutoFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_autofield.SmallAutoFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_autofield.SmallAutoFieldTests.test_types) ... ok test_backend_range_save (model_fields.test_integerfield.SmallIntegerFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_integerfield.SmallIntegerFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_integerfield.SmallIntegerFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_integerfield.SmallIntegerFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_integerfield.SmallIntegerFieldTests.test_invalid_value) ... ok test_redundant_backend_range_validators (model_fields.test_integerfield.SmallIntegerFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_integerfield.SmallIntegerFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_integerfield.SmallIntegerFieldTests.test_types) ... ok test_editable (model_fields.test_binaryfield.BinaryFieldTests.test_editable) ... ok test_filter (model_fields.test_binaryfield.BinaryFieldTests.test_filter) ... ok test_filter_bytearray (model_fields.test_binaryfield.BinaryFieldTests.test_filter_bytearray) ... ok test_filter_memoryview (model_fields.test_binaryfield.BinaryFieldTests.test_filter_memoryview) ... ok test_max_length (model_fields.test_binaryfield.BinaryFieldTests.test_max_length) ... ok test_set_and_retrieve (model_fields.test_binaryfield.BinaryFieldTests.test_set_and_retrieve) ... ok test_add_implementation (aggregation.tests.AggregateTestCase.test_add_implementation) ... ok test_aggregate_alias (aggregation.tests.AggregateTestCase.test_aggregate_alias) ... ok test_aggregate_annotation (aggregation.tests.AggregateTestCase.test_aggregate_annotation) ... ok test_aggregate_in_order_by (aggregation.tests.AggregateTestCase.test_aggregate_in_order_by) ... ok test_aggregate_join_transform (aggregation.tests.AggregateTestCase.test_aggregate_join_transform) ... ok test_aggregate_multi_join (aggregation.tests.AggregateTestCase.test_aggregate_multi_join) ... ok test_aggregate_over_aggregate (aggregation.tests.AggregateTestCase.test_aggregate_over_aggregate) ... ok test_aggregate_over_complex_annotation (aggregation.tests.AggregateTestCase.test_aggregate_over_complex_annotation) ... ok test_aggregate_transform (aggregation.tests.AggregateTestCase.test_aggregate_transform) ... ok test_aggregation_exists_annotation (aggregation.tests.AggregateTestCase.test_aggregation_exists_annotation) ... ok test_aggregation_expressions (aggregation.tests.AggregateTestCase.test_aggregation_expressions) ... ok test_aggregation_nested_subquery_outerref (aggregation.tests.AggregateTestCase.test_aggregation_nested_subquery_outerref) ... ok test_aggregation_order_by_not_selected_annotation_values (aggregation.tests.AggregateTestCase.test_aggregation_order_by_not_selected_annotation_values) ... ok test_aggregation_random_ordering (aggregation.tests.AggregateTestCase.test_aggregation_random_ordering) Random() is not included in the GROUP BY when used for ordering. ... ok test_aggregation_subquery_annotation (aggregation.tests.AggregateTestCase.test_aggregation_subquery_annotation) Subquery annotations are excluded from the GROUP BY if they are ... ok test_aggregation_subquery_annotation_exists (aggregation.tests.AggregateTestCase.test_aggregation_subquery_annotation_exists) ... ok test_aggregation_subquery_annotation_multivalued (aggregation.tests.AggregateTestCase.test_aggregation_subquery_annotation_multivalued) Subquery annotations must be included in the GROUP BY if they use ... ok test_aggregation_subquery_annotation_related_field (aggregation.tests.AggregateTestCase.test_aggregation_subquery_annotation_related_field) ... ok test_aggregation_subquery_annotation_values (aggregation.tests.AggregateTestCase.test_aggregation_subquery_annotation_values) Subquery annotations and external aliases are excluded from the GROUP ... ok test_aggregation_subquery_annotation_values_collision (aggregation.tests.AggregateTestCase.test_aggregation_subquery_annotation_values_collision) ... ok test_alias_sql_injection (aggregation.tests.AggregateTestCase.test_alias_sql_injection) ... ok test_annotate_basic (aggregation.tests.AggregateTestCase.test_annotate_basic) ... ok test_annotate_defer (aggregation.tests.AggregateTestCase.test_annotate_defer) ... ok test_annotate_defer_select_related (aggregation.tests.AggregateTestCase.test_annotate_defer_select_related) ... ok test_annotate_m2m (aggregation.tests.AggregateTestCase.test_annotate_m2m) ... ok test_annotate_ordering (aggregation.tests.AggregateTestCase.test_annotate_ordering) ... ok test_annotate_over_annotate (aggregation.tests.AggregateTestCase.test_annotate_over_annotate) ... ok test_annotate_values (aggregation.tests.AggregateTestCase.test_annotate_values) ... ok test_annotate_values_aggregate (aggregation.tests.AggregateTestCase.test_annotate_values_aggregate) ... ok test_annotate_values_list (aggregation.tests.AggregateTestCase.test_annotate_values_list) ... ok test_annotated_aggregate_over_annotated_aggregate (aggregation.tests.AggregateTestCase.test_annotated_aggregate_over_annotated_aggregate) ... ok test_annotation (aggregation.tests.AggregateTestCase.test_annotation) ... ok test_annotation_expressions (aggregation.tests.AggregateTestCase.test_annotation_expressions) ... ok test_arguments_must_be_expressions (aggregation.tests.AggregateTestCase.test_arguments_must_be_expressions) ... ok test_avg_decimal_field (aggregation.tests.AggregateTestCase.test_avg_decimal_field) ... ok test_avg_duration_field (aggregation.tests.AggregateTestCase.test_avg_duration_field) ... ok test_backwards_m2m_annotate (aggregation.tests.AggregateTestCase.test_backwards_m2m_annotate) ... ok test_combine_different_types (aggregation.tests.AggregateTestCase.test_combine_different_types) ... ok test_complex_aggregations_require_kwarg (aggregation.tests.AggregateTestCase.test_complex_aggregations_require_kwarg) ... ok test_complex_values_aggregation (aggregation.tests.AggregateTestCase.test_complex_values_aggregation) ... ok test_count (aggregation.tests.AggregateTestCase.test_count) ... ok test_count_distinct_expression (aggregation.tests.AggregateTestCase.test_count_distinct_expression) ... ok test_count_star (aggregation.tests.AggregateTestCase.test_count_star) ... ok test_dates_with_aggregation (aggregation.tests.AggregateTestCase.test_dates_with_aggregation) .dates() returns a distinct set of dates when applied to a ... ok test_decimal_max_digits_has_no_effect (aggregation.tests.AggregateTestCase.test_decimal_max_digits_has_no_effect) ... ok test_distinct_on_aggregate (aggregation.tests.AggregateTestCase.test_distinct_on_aggregate) ... ok test_empty_aggregate (aggregation.tests.AggregateTestCase.test_empty_aggregate) ... ok test_even_more_aggregate (aggregation.tests.AggregateTestCase.test_even_more_aggregate) ... ok test_expression_on_aggregation (aggregation.tests.AggregateTestCase.test_expression_on_aggregation) ... ok test_filter_aggregate (aggregation.tests.AggregateTestCase.test_filter_aggregate) ... ok test_filter_in_subquery_or_aggregation (aggregation.tests.AggregateTestCase.test_filter_in_subquery_or_aggregation) Filtering against an aggregate requires the usage of the HAVING clause. ... ok test_filtering (aggregation.tests.AggregateTestCase.test_filtering) ... ok test_fkey_aggregate (aggregation.tests.AggregateTestCase.test_fkey_aggregate) ... ok test_group_by_exists_annotation (aggregation.tests.AggregateTestCase.test_group_by_exists_annotation) Exists annotations are included in the GROUP BY if they are ... ok test_group_by_subquery_annotation (aggregation.tests.AggregateTestCase.test_group_by_subquery_annotation) Subquery annotations are included in the GROUP BY if they are ... ok test_grouped_annotation_in_group_by (aggregation.tests.AggregateTestCase.test_grouped_annotation_in_group_by) An annotation included in values() before an aggregate should be ... ok test_more_aggregation (aggregation.tests.AggregateTestCase.test_more_aggregation) ... ok test_multi_arg_aggregate (aggregation.tests.AggregateTestCase.test_multi_arg_aggregate) ... ok test_multiple_aggregates (aggregation.tests.AggregateTestCase.test_multiple_aggregates) ... ok test_non_grouped_annotation_not_in_group_by (aggregation.tests.AggregateTestCase.test_non_grouped_annotation_not_in_group_by) An annotation not included in values() before an aggregate should be ... ok test_nonaggregate_aggregation_throws (aggregation.tests.AggregateTestCase.test_nonaggregate_aggregation_throws) ... ok test_nonfield_annotation (aggregation.tests.AggregateTestCase.test_nonfield_annotation) ... ok test_order_of_precedence (aggregation.tests.AggregateTestCase.test_order_of_precedence) ... ok test_related_aggregate (aggregation.tests.AggregateTestCase.test_related_aggregate) ... ok test_reverse_fkey_annotate (aggregation.tests.AggregateTestCase.test_reverse_fkey_annotate) ... ok test_single_aggregate (aggregation.tests.AggregateTestCase.test_single_aggregate) ... ok test_sum_distinct_aggregate (aggregation.tests.AggregateTestCase.test_sum_distinct_aggregate) Sum on a distinct() QuerySet should aggregate only the distinct items. ... ok test_sum_duration_field (aggregation.tests.AggregateTestCase.test_sum_duration_field) ... ok test_ticket11881 (aggregation.tests.AggregateTestCase.test_ticket11881) Subqueries do not needlessly contain ORDER BY, SELECT FOR UPDATE or ... ok test_ticket12886 (aggregation.tests.AggregateTestCase.test_ticket12886) Aggregation over sliced queryset works correctly. ... ok test_ticket17424 (aggregation.tests.AggregateTestCase.test_ticket17424) Doing exclude() on a foreign model after annotate() doesn't crash. ... ok test_values_aggregation (aggregation.tests.AggregateTestCase.test_values_aggregation) ... ok test_values_annotation_with_expression (aggregation.tests.AggregateTestCase.test_values_annotation_with_expression) ... ok test_assignment_from_choice_enum (model_fields.test_charfield.TestCharField.test_assignment_from_choice_enum) ... ok test_emoji (model_fields.test_charfield.TestCharField.test_emoji) ... ok test_lookup_integer_in_charfield (model_fields.test_charfield.TestCharField.test_lookup_integer_in_charfield) ... ok test_max_length_passed_to_formfield (model_fields.test_charfield.TestCharField.test_max_length_passed_to_formfield) CharField passes its max_length attribute to form fields created using ... ok test_exact (model_fields.test_durationfield.TestQuerying.test_exact) ... ok test_gt (model_fields.test_durationfield.TestQuerying.test_gt) ... ok test_datetimefield_to_python_microseconds (model_fields.test_datetimefield.DateTimeFieldTests.test_datetimefield_to_python_microseconds) DateTimeField.to_python() supports microseconds. ... ok test_datetimes_save_completely (model_fields.test_datetimefield.DateTimeFieldTests.test_datetimes_save_completely) ... ok test_lookup_date_with_use_tz (model_fields.test_datetimefield.DateTimeFieldTests.test_lookup_date_with_use_tz) ... ok test_lookup_date_without_use_tz (model_fields.test_datetimefield.DateTimeFieldTests.test_lookup_date_without_use_tz) ... ok test_timefield_to_python_microseconds (model_fields.test_datetimefield.DateTimeFieldTests.test_timefield_to_python_microseconds) TimeField.to_python() supports microseconds. ... ok test_create_empty (model_fields.test_durationfield.TestSaveLoad.test_create_empty) ... ok test_fractional_seconds (model_fields.test_durationfield.TestSaveLoad.test_fractional_seconds) ... ok test_simple_roundtrip (model_fields.test_durationfield.TestSaveLoad.test_simple_roundtrip) ... ok test_float_validates_object (model_fields.test_floatfield.TestFloatField.test_float_validates_object) ... ok test_invalid_value (model_fields.test_floatfield.TestFloatField.test_invalid_value) ... ok test_booleanfield_choices_blank (model_fields.test_booleanfield.BooleanFieldTests.test_booleanfield_choices_blank) BooleanField with choices and defaults doesn't generate a formfield ... ok test_booleanfield_choices_blank_desired (model_fields.test_booleanfield.BooleanFieldTests.test_booleanfield_choices_blank_desired) BooleanField with choices and no default should generated a formfield ... ok test_booleanfield_get_prep_value (model_fields.test_booleanfield.BooleanFieldTests.test_booleanfield_get_prep_value) ... ok test_booleanfield_to_python (model_fields.test_booleanfield.BooleanFieldTests.test_booleanfield_to_python) ... ok test_null_default (model_fields.test_booleanfield.BooleanFieldTests.test_null_default) A BooleanField defaults to None, which isn't a valid value (#15124). ... ok test_nullbooleanfield_formfield (model_fields.test_booleanfield.BooleanFieldTests.test_nullbooleanfield_formfield) ... ok test_nullbooleanfield_get_prep_value (model_fields.test_booleanfield.BooleanFieldTests.test_nullbooleanfield_get_prep_value) ... ok test_nullbooleanfield_old_get_prep_value (model_fields.test_booleanfield.BooleanFieldTests.test_nullbooleanfield_old_get_prep_value) ... ok test_nullbooleanfield_old_to_python (model_fields.test_booleanfield.BooleanFieldTests.test_nullbooleanfield_old_to_python) ... ok test_nullbooleanfield_to_python (model_fields.test_booleanfield.BooleanFieldTests.test_nullbooleanfield_to_python) ... ok test_return_type (model_fields.test_booleanfield.BooleanFieldTests.test_return_type) ... ok test_select_related (model_fields.test_booleanfield.BooleanFieldTests.test_select_related) Boolean fields retrieved via select_related() should return booleans. ... ok test_blank_string_saved_as_null (model_fields.test_genericipaddressfield.GenericIPAddressFieldTests.test_blank_string_saved_as_null) ... ok test_genericipaddressfield_formfield_protocol (model_fields.test_genericipaddressfield.GenericIPAddressFieldTests.test_genericipaddressfield_formfield_protocol) GenericIPAddressField with a specified protocol does not generate a ... ok test_null_value (model_fields.test_genericipaddressfield.GenericIPAddressFieldTests.test_null_value) Null values should be resolved to None. ... ok test_save_load (model_fields.test_genericipaddressfield.GenericIPAddressFieldTests.test_save_load) ... ok test_default (model_fields.test_decimalfield.DecimalFieldTests.test_default) ... ok test_fetch_from_db_without_float_rounding (model_fields.test_decimalfield.DecimalFieldTests.test_fetch_from_db_without_float_rounding) ... skipped 'SQLite stores values rounded to 15 significant digits.' test_filter_with_strings (model_fields.test_decimalfield.DecimalFieldTests.test_filter_with_strings) Should be able to filter decimal fields using strings (#8023). ... ok test_get_prep_value (model_fields.test_decimalfield.DecimalFieldTests.test_get_prep_value) ... ok test_invalid_value (model_fields.test_decimalfield.DecimalFieldTests.test_invalid_value) ... ok test_lookup_really_big_value (model_fields.test_decimalfield.DecimalFieldTests.test_lookup_really_big_value) Really big values can be used in a filter statement. ... ok test_max_decimal_places_validation (model_fields.test_decimalfield.DecimalFieldTests.test_max_decimal_places_validation) ... ok test_max_digits_validation (model_fields.test_decimalfield.DecimalFieldTests.test_max_digits_validation) ... ok test_max_whole_digits_validation (model_fields.test_decimalfield.DecimalFieldTests.test_max_whole_digits_validation) ... ok test_roundtrip_with_trailing_zeros (model_fields.test_decimalfield.DecimalFieldTests.test_roundtrip_with_trailing_zeros) Trailing zeros in the fractional part aren't truncated. ... ok test_save_without_float_conversion (model_fields.test_decimalfield.DecimalFieldTests.test_save_without_float_conversion) Ensure decimals don't go through a corrupting float conversion during ... ok test_to_python (model_fields.test_decimalfield.DecimalFieldTests.test_to_python) ... ok test_abstract_model_app_relative_foreign_key (model_fields.test_foreignkey.ForeignKeyTests.test_abstract_model_app_relative_foreign_key) ... ok test_abstract_model_pending_operations (model_fields.test_foreignkey.ForeignKeyTests.test_abstract_model_pending_operations) Foreign key fields declared on abstract models should not add lazy ... ok test_callable_default (model_fields.test_foreignkey.ForeignKeyTests.test_callable_default) A lazy callable may be used for ForeignKey.default. ... ok test_empty_string_fk (model_fields.test_foreignkey.ForeignKeyTests.test_empty_string_fk) Empty strings foreign key values don't get converted to None (#19299). ... ok test_fk_to_fk_get_col_output_field (model_fields.test_foreignkey.ForeignKeyTests.test_fk_to_fk_get_col_output_field) ... ok test_non_local_to_field (model_fields.test_foreignkey.ForeignKeyTests.test_non_local_to_field) ... ok test_recursive_fks_get_col (model_fields.test_foreignkey.ForeignKeyTests.test_recursive_fks_get_col) ... ok test_related_name_converted_to_text (model_fields.test_foreignkey.ForeignKeyTests.test_related_name_converted_to_text) ... ok test_to_python (model_fields.test_foreignkey.ForeignKeyTests.test_to_python) ... ok test_warning_when_unique_true_on_fk (model_fields.test_foreignkey.ForeignKeyTests.test_warning_when_unique_true_on_fk) ... ok test_abstract_filefield_model (model_fields.test_filefield.FileFieldTests.test_abstract_filefield_model) FileField.model returns the concrete model for fields defined in an ... ok test_changed (model_fields.test_filefield.FileFieldTests.test_changed) FileField.save_form_data(), if passed a truthy value, updates its ... ok test_clearable (model_fields.test_filefield.FileFieldTests.test_clearable) FileField.save_form_data() will clear its instance attribute value if ... ok test_defer (model_fields.test_filefield.FileFieldTests.test_defer) ... ok test_delete_when_file_unset (model_fields.test_filefield.FileFieldTests.test_delete_when_file_unset) Calling delete on an unset FileField should not call the file deletion ... ok test_media_root_pathlib (model_fields.test_filefield.FileFieldTests.test_media_root_pathlib) ... ok test_move_temporary_file (model_fields.test_filefield.FileFieldTests.test_move_temporary_file) The temporary uploaded file is moved rather than copied to the ... ok test_open_returns_self (model_fields.test_filefield.FileFieldTests.test_open_returns_self) FieldField.open() returns self so it can be used as a context manager. ... ok test_pickle (model_fields.test_filefield.FileFieldTests.test_pickle) ... ok test_refresh_from_db (model_fields.test_filefield.FileFieldTests.test_refresh_from_db) ... ok test_save_without_name (model_fields.test_filefield.FileFieldTests.test_save_without_name) ... ok test_unchanged (model_fields.test_filefield.FileFieldTests.test_unchanged) FileField.save_form_data() considers None to mean "no change" rather ... ok test_unique_when_same_filename (model_fields.test_filefield.FileFieldTests.test_unique_when_same_filename) A FileField with unique=True shouldn't allow two instances with the ... ok test_assignment_to_None (model_fields.test_imagefield.ImageFieldDimensionsFirstTests.test_assignment_to_None) Assigning ImageField to None clears dimensions. ... ok test_constructor (model_fields.test_imagefield.ImageFieldDimensionsFirstTests.test_constructor) Tests assigning an image field through the model's constructor. ... ok test_create (model_fields.test_imagefield.ImageFieldDimensionsFirstTests.test_create) Tests assigning an image in Manager.create(). ... ok test_default_value (model_fields.test_imagefield.ImageFieldDimensionsFirstTests.test_default_value) The default value for an ImageField is an instance of ... ok test_dimensions (model_fields.test_imagefield.ImageFieldDimensionsFirstTests.test_dimensions) Dimensions are updated correctly in various situations. ... ok test_field_save_and_delete_methods (model_fields.test_imagefield.ImageFieldDimensionsFirstTests.test_field_save_and_delete_methods) Tests assignment using the field's save method and deletion using ... ok test_image_after_constructor (model_fields.test_imagefield.ImageFieldDimensionsFirstTests.test_image_after_constructor) Tests behavior when image is not passed in constructor. ... ok test_assignment_to_None (model_fields.test_imagefield.ImageFieldNoDimensionsTests.test_assignment_to_None) Assigning ImageField to None clears dimensions. ... ok test_constructor (model_fields.test_imagefield.ImageFieldNoDimensionsTests.test_constructor) Tests assigning an image field through the model's constructor. ... ok test_create (model_fields.test_imagefield.ImageFieldNoDimensionsTests.test_create) Tests assigning an image in Manager.create(). ... ok test_default_value (model_fields.test_imagefield.ImageFieldNoDimensionsTests.test_default_value) The default value for an ImageField is an instance of ... ok test_dimensions (model_fields.test_imagefield.ImageFieldNoDimensionsTests.test_dimensions) Dimensions are updated correctly in various situations. ... ok test_field_save_and_delete_methods (model_fields.test_imagefield.ImageFieldNoDimensionsTests.test_field_save_and_delete_methods) Tests assignment using the field's save method and deletion using ... ok test_image_after_constructor (model_fields.test_imagefield.ImageFieldNoDimensionsTests.test_image_after_constructor) Tests behavior when image is not passed in constructor. ... ok test_assignment_to_None (model_fields.test_imagefield.ImageFieldOneDimensionTests.test_assignment_to_None) Assigning ImageField to None clears dimensions. ... ok test_constructor (model_fields.test_imagefield.ImageFieldOneDimensionTests.test_constructor) Tests assigning an image field through the model's constructor. ... ok test_create (model_fields.test_imagefield.ImageFieldOneDimensionTests.test_create) Tests assigning an image in Manager.create(). ... ok test_default_value (model_fields.test_imagefield.ImageFieldOneDimensionTests.test_default_value) The default value for an ImageField is an instance of ... ok test_dimensions (model_fields.test_imagefield.ImageFieldOneDimensionTests.test_dimensions) Dimensions are updated correctly in various situations. ... ok test_field_save_and_delete_methods (model_fields.test_imagefield.ImageFieldOneDimensionTests.test_field_save_and_delete_methods) Tests assignment using the field's save method and deletion using ... ok test_image_after_constructor (model_fields.test_imagefield.ImageFieldOneDimensionTests.test_image_after_constructor) Tests behavior when image is not passed in constructor. ... ok test_defer (model_fields.test_imagefield.ImageFieldTests.test_defer) ... ok test_delete_when_missing (model_fields.test_imagefield.ImageFieldTests.test_delete_when_missing) Bug #8175: correctly delete an object where the file no longer ... ok test_equal_notequal_hash (model_fields.test_imagefield.ImageFieldTests.test_equal_notequal_hash) Bug #9786: Ensure '==' and '!=' work correctly. ... ok test_instantiate_missing (model_fields.test_imagefield.ImageFieldTests.test_instantiate_missing) If the underlying file is unavailable, still create instantiate the ... ok test_pickle (model_fields.test_imagefield.ImageFieldTests.test_pickle) ImageField can be pickled, unpickled, and that the image of ... ok test_size_method (model_fields.test_imagefield.ImageFieldTests.test_size_method) Bug #8534: FileField.size should not leave the file open. ... ok test_backend_range_save (model_fields.test_integerfield.PositiveBigIntegerFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_integerfield.PositiveBigIntegerFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_integerfield.PositiveBigIntegerFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_integerfield.PositiveBigIntegerFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_integerfield.PositiveBigIntegerFieldTests.test_invalid_value) ... ok test_redundant_backend_range_validators (model_fields.test_integerfield.PositiveBigIntegerFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_integerfield.PositiveBigIntegerFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_integerfield.PositiveBigIntegerFieldTests.test_types) ... ok test_assignment_to_None (model_fields.test_imagefield.ImageFieldTwoDimensionsTests.test_assignment_to_None) Assigning ImageField to None clears dimensions. ... ok test_constructor (model_fields.test_imagefield.ImageFieldTwoDimensionsTests.test_constructor) Tests assigning an image field through the model's constructor. ... ok test_create (model_fields.test_imagefield.ImageFieldTwoDimensionsTests.test_create) Tests assigning an image in Manager.create(). ... ok test_default_value (model_fields.test_imagefield.ImageFieldTwoDimensionsTests.test_default_value) The default value for an ImageField is an instance of ... ok test_dimensions (model_fields.test_imagefield.ImageFieldTwoDimensionsTests.test_dimensions) Dimensions are updated correctly in various situations. ... ok test_field_save_and_delete_methods (model_fields.test_imagefield.ImageFieldTwoDimensionsTests.test_field_save_and_delete_methods) Tests assignment using the field's save method and deletion using ... ok test_image_after_constructor (model_fields.test_imagefield.ImageFieldTwoDimensionsTests.test_image_after_constructor) Tests behavior when image is not passed in constructor. ... ok test_backend_range_save (model_fields.test_integerfield.PositiveSmallIntegerFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_integerfield.PositiveSmallIntegerFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_integerfield.PositiveSmallIntegerFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_integerfield.PositiveSmallIntegerFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_integerfield.PositiveSmallIntegerFieldTests.test_invalid_value) ... ok test_redundant_backend_range_validators (model_fields.test_integerfield.PositiveSmallIntegerFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_integerfield.PositiveSmallIntegerFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_integerfield.PositiveSmallIntegerFieldTests.test_types) ... ok test_backend_range_save (model_fields.test_integerfield.PositiveIntegerFieldTests.test_backend_range_save) Backend specific ranges can be saved without corruption. ... ok test_backend_range_validation (model_fields.test_integerfield.PositiveIntegerFieldTests.test_backend_range_validation) Backend specific ranges are enforced at the model validation level ... ok test_coercing (model_fields.test_integerfield.PositiveIntegerFieldTests.test_coercing) ... ok test_documented_range (model_fields.test_integerfield.PositiveIntegerFieldTests.test_documented_range) Values within the documented safe range pass validation, and can be ... ok test_invalid_value (model_fields.test_integerfield.PositiveIntegerFieldTests.test_invalid_value) ... ok test_negative_values (model_fields.test_integerfield.PositiveIntegerFieldTests.test_negative_values) ... skipped "SQLite doesn't have a constraint." test_redundant_backend_range_validators (model_fields.test_integerfield.PositiveIntegerFieldTests.test_redundant_backend_range_validators) If there are stricter validators than the ones from the database ... ok test_rel_db_type (model_fields.test_integerfield.PositiveIntegerFieldTests.test_rel_db_type) ... ok test_types (model_fields.test_integerfield.PositiveIntegerFieldTests.test_types) ... ok test_assignment_to_None (model_fields.test_imagefield.ImageFieldUsingFileTests.test_assignment_to_None) Assigning ImageField to None clears dimensions. ... ok test_constructor (model_fields.test_imagefield.ImageFieldUsingFileTests.test_constructor) Tests assigning an image field through the model's constructor. ... ok test_create (model_fields.test_imagefield.ImageFieldUsingFileTests.test_create) Tests assigning an image in Manager.create(). ... ok test_default_value (model_fields.test_imagefield.ImageFieldUsingFileTests.test_default_value) The default value for an ImageField is an instance of ... ok test_dimensions (model_fields.test_imagefield.ImageFieldUsingFileTests.test_dimensions) Dimensions are updated correctly in various situations. ... ok test_field_save_and_delete_methods (model_fields.test_imagefield.ImageFieldUsingFileTests.test_field_save_and_delete_methods) Tests assignment using the field's save method and deletion using ... ok test_image_after_constructor (model_fields.test_imagefield.ImageFieldUsingFileTests.test_image_after_constructor) Tests behavior when image is not passed in constructor. ... ok test_custom_encoder_decoder (model_fields.test_jsonfield.JSONFieldTests.test_custom_encoder_decoder) ... ok test_db_check_constraints (model_fields.test_jsonfield.JSONFieldTests.test_db_check_constraints) ... ok test_invalid_value (model_fields.test_jsonfield.JSONFieldTests.test_invalid_value) ... ok test_value_from_object_instance_with_pk (model_fields.test_manytomanyfield.ManyToManyFieldDBTests.test_value_from_object_instance_with_pk) ... ok test_value_from_object_instance_without_pk (model_fields.test_manytomanyfield.ManyToManyFieldDBTests.test_value_from_object_instance_without_pk) ... ok test_slugfield_max_length (model_fields.test_slugfield.SlugFieldTests.test_slugfield_max_length) SlugField honors max_length. ... ok test_slugfield_unicode_max_length (model_fields.test_slugfield.SlugFieldTests.test_slugfield_unicode_max_length) SlugField with allow_unicode=True honors max_length. ... ok test_assignment (model_fields.test_imagefield.TwoImageFieldTests.test_assignment) ... ok test_constructor (model_fields.test_imagefield.TwoImageFieldTests.test_constructor) ... ok test_create (model_fields.test_imagefield.TwoImageFieldTests.test_create) ... ok test_dimensions (model_fields.test_imagefield.TwoImageFieldTests.test_dimensions) Dimensions are updated correctly in various situations. ... ok test_field_save_and_delete_methods (model_fields.test_imagefield.TwoImageFieldTests.test_field_save_and_delete_methods) ... ok test_dict (model_fields.test_jsonfield.TestSaveLoad.test_dict) ... ok test_json_null_different_from_sql_null (model_fields.test_jsonfield.TestSaveLoad.test_json_null_different_from_sql_null) ... ok test_list (model_fields.test_jsonfield.TestSaveLoad.test_list) ... ok test_null (model_fields.test_jsonfield.TestSaveLoad.test_null) ... ok test_primitives (model_fields.test_jsonfield.TestSaveLoad.test_primitives) ... ok test_realistic_object (model_fields.test_jsonfield.TestSaveLoad.test_realistic_object) ... ok test_choices_generates_select_widget (model_fields.test_textfield.TextFieldTests.test_choices_generates_select_widget) A TextField with choices uses a Select widget. ... ok test_emoji (model_fields.test_textfield.TextFieldTests.test_emoji) ... ok test_lookup_integer_in_textfield (model_fields.test_textfield.TextFieldTests.test_lookup_integer_in_textfield) ... ok test_max_length_passed_to_formfield (model_fields.test_textfield.TextFieldTests.test_max_length_passed_to_formfield) TextField passes its max_length attribute to form fields created using ... ok test_to_python (model_fields.test_textfield.TextFieldTests.test_to_python) TextField.to_python() should return a string. ... ok test_creation (model_fields.test_uuid.TestAsPrimaryKey.test_creation) ... ok test_two_level_foreign_keys (model_fields.test_uuid.TestAsPrimaryKey.test_two_level_foreign_keys) ... ok test_underlying_field (model_fields.test_uuid.TestAsPrimaryKey.test_underlying_field) ... ok test_update_with_related_model_id (model_fields.test_uuid.TestAsPrimaryKey.test_update_with_related_model_id) ... ok test_update_with_related_model_instance (model_fields.test_uuid.TestAsPrimaryKey.test_update_with_related_model_instance) ... ok test_uuid_pk_on_bulk_create (model_fields.test_uuid.TestAsPrimaryKey.test_uuid_pk_on_bulk_create) ... ok test_uuid_pk_on_save (model_fields.test_uuid.TestAsPrimaryKey.test_uuid_pk_on_save) ... ok test_contains (model_fields.test_uuid.TestQuerying.test_contains) ... ok test_endswith (model_fields.test_uuid.TestQuerying.test_endswith) ... ok test_exact (model_fields.test_uuid.TestQuerying.test_exact) ... ok test_filter_with_expr (model_fields.test_uuid.TestQuerying.test_filter_with_expr) ... ok test_icontains (model_fields.test_uuid.TestQuerying.test_icontains) ... ok test_iendswith (model_fields.test_uuid.TestQuerying.test_iendswith) ... ok test_iexact (model_fields.test_uuid.TestQuerying.test_iexact) ... ok test_isnull (model_fields.test_uuid.TestQuerying.test_isnull) ... ok test_istartswith (model_fields.test_uuid.TestQuerying.test_istartswith) ... ok test_startswith (model_fields.test_uuid.TestQuerying.test_startswith) ... ok test_get_choices (model_fields.tests.GetChoicesLimitChoicesToTests.test_get_choices) ... ok test_get_choices_reverse_related_field (model_fields.tests.GetChoicesLimitChoicesToTests.test_get_choices_reverse_related_field) ... ok test_null_handling (model_fields.test_uuid.TestSaveLoad.test_null_handling) ... ok test_pk_validated (model_fields.test_uuid.TestSaveLoad.test_pk_validated) ... ok test_str_instance_bad_hyphens (model_fields.test_uuid.TestSaveLoad.test_str_instance_bad_hyphens) ... ok test_str_instance_hyphens (model_fields.test_uuid.TestSaveLoad.test_str_instance_hyphens) ... ok test_str_instance_no_hyphens (model_fields.test_uuid.TestSaveLoad.test_str_instance_no_hyphens) ... ok test_uuid_instance (model_fields.test_uuid.TestSaveLoad.test_uuid_instance) ... ok test_wrong_value (model_fields.test_uuid.TestSaveLoad.test_wrong_value) ... ok test_get_choices (model_fields.tests.GetChoicesOrderingTests.test_get_choices) ... ok test_get_choices_default_ordering (model_fields.tests.GetChoicesOrderingTests.test_get_choices_default_ordering) ... ok test_get_choices_reverse_related_field (model_fields.tests.GetChoicesOrderingTests.test_get_choices_reverse_related_field) ... ok test_get_choices_reverse_related_field_default_ordering (model_fields.tests.GetChoicesOrderingTests.test_get_choices_reverse_related_field_default_ordering) ... ok test_optimizations (expressions.tests.ExistsTests.test_optimizations) ... ok test_chained_values_with_expression (expressions.test_queryset_values.ValuesExpressionsTests.test_chained_values_with_expression) ... ok test_values_expression (expressions.test_queryset_values.ValuesExpressionsTests.test_values_expression) ... ok test_values_expression_alias_sql_injection (expressions.test_queryset_values.ValuesExpressionsTests.test_values_expression_alias_sql_injection) ... ok test_values_expression_group_by (expressions.test_queryset_values.ValuesExpressionsTests.test_values_expression_group_by) ... ok test_values_list_expression (expressions.test_queryset_values.ValuesExpressionsTests.test_values_list_expression) ... ok test_values_list_expression_flat (expressions.test_queryset_values.ValuesExpressionsTests.test_values_list_expression_flat) ... ok test_complex_expressions (expressions.tests.ExpressionsNumericTests.test_complex_expressions) Complex expressions of different connection types are possible. ... ok test_decimal_expression (expressions.tests.ExpressionsNumericTests.test_decimal_expression) ... ok test_fill_with_value_from_same_object (expressions.tests.ExpressionsNumericTests.test_fill_with_value_from_same_object) We can fill a value in all objects with an other value of the ... ok test_filter_not_equals_other_field (expressions.tests.ExpressionsNumericTests.test_filter_not_equals_other_field) We can filter for objects, where a value is not equals the value ... ok test_increment_value (expressions.tests.ExpressionsNumericTests.test_increment_value) We can increment a value of all objects in a query set. ... ok test_F_reuse (expressions.tests.ExpressionsTests.test_F_reuse) ... ok test_insensitive_patterns_escape (expressions.tests.ExpressionsTests.test_insensitive_patterns_escape) Special characters (e.g. %, _ and \) stored in database are ... ok test_patterns_escape (expressions.tests.ExpressionsTests.test_patterns_escape) Special characters (e.g. %, _ and \) stored in database are ... ok test_lefthand_addition (expressions.tests.ExpressionOperatorTests.test_lefthand_addition) ... ok test_lefthand_bitwise_and (expressions.tests.ExpressionOperatorTests.test_lefthand_bitwise_and) ... ok test_lefthand_bitwise_left_shift_operator (expressions.tests.ExpressionOperatorTests.test_lefthand_bitwise_left_shift_operator) ... ok test_lefthand_bitwise_or (expressions.tests.ExpressionOperatorTests.test_lefthand_bitwise_or) ... ok test_lefthand_bitwise_right_shift_operator (expressions.tests.ExpressionOperatorTests.test_lefthand_bitwise_right_shift_operator) ... ok test_lefthand_bitwise_xor (expressions.tests.ExpressionOperatorTests.test_lefthand_bitwise_xor) ... ok test_lefthand_bitwise_xor_not_supported (expressions.tests.ExpressionOperatorTests.test_lefthand_bitwise_xor_not_supported) ... skipped "Oracle doesn't support bitwise XOR." test_lefthand_bitwise_xor_null (expressions.tests.ExpressionOperatorTests.test_lefthand_bitwise_xor_null) ... ok test_lefthand_division (expressions.tests.ExpressionOperatorTests.test_lefthand_division) ... ok test_lefthand_modulo (expressions.tests.ExpressionOperatorTests.test_lefthand_modulo) ... ok test_lefthand_multiplication (expressions.tests.ExpressionOperatorTests.test_lefthand_multiplication) ... ok test_lefthand_power (expressions.tests.ExpressionOperatorTests.test_lefthand_power) ... ok test_lefthand_subtraction (expressions.tests.ExpressionOperatorTests.test_lefthand_subtraction) ... ok test_lefthand_transformed_field_bitwise_or (expressions.tests.ExpressionOperatorTests.test_lefthand_transformed_field_bitwise_or) ... ok test_right_hand_addition (expressions.tests.ExpressionOperatorTests.test_right_hand_addition) ... ok test_right_hand_division (expressions.tests.ExpressionOperatorTests.test_right_hand_division) ... ok test_right_hand_modulo (expressions.tests.ExpressionOperatorTests.test_right_hand_modulo) ... ok test_right_hand_multiplication (expressions.tests.ExpressionOperatorTests.test_right_hand_multiplication) ... ok test_right_hand_subtraction (expressions.tests.ExpressionOperatorTests.test_right_hand_subtraction) ... ok test_righthand_power (expressions.tests.ExpressionOperatorTests.test_righthand_power) ... ok test_month_aggregation (expressions.tests.FieldTransformTests.test_month_aggregation) ... ok test_multiple_transforms_in_values (expressions.tests.FieldTransformTests.test_multiple_transforms_in_values) ... ok test_transform_in_values (expressions.tests.FieldTransformTests.test_transform_in_values) ... ok test_date_case_subtraction (expressions.tests.FTimeDeltaTests.test_date_case_subtraction) ... ok test_date_comparison (expressions.tests.FTimeDeltaTests.test_date_comparison) ... ok test_date_minus_duration (expressions.tests.FTimeDeltaTests.test_date_minus_duration) ... ok test_date_subquery_subtraction (expressions.tests.FTimeDeltaTests.test_date_subquery_subtraction) ... ok test_date_subtraction (expressions.tests.FTimeDeltaTests.test_date_subtraction) ... ok test_datetime_subquery_subtraction (expressions.tests.FTimeDeltaTests.test_datetime_subquery_subtraction) ... ok test_datetime_subtraction (expressions.tests.FTimeDeltaTests.test_datetime_subtraction) ... ok test_datetime_subtraction_microseconds (expressions.tests.FTimeDeltaTests.test_datetime_subtraction_microseconds) ... ok test_delta_add (expressions.tests.FTimeDeltaTests.test_delta_add) ... ok test_delta_subtract (expressions.tests.FTimeDeltaTests.test_delta_subtract) ... ok test_delta_update (expressions.tests.FTimeDeltaTests.test_delta_update) ... ok test_duration_expressions (expressions.tests.FTimeDeltaTests.test_duration_expressions) ... ok test_duration_with_datetime (expressions.tests.FTimeDeltaTests.test_duration_with_datetime) ... ok test_duration_with_datetime_microseconds (expressions.tests.FTimeDeltaTests.test_duration_with_datetime_microseconds) ... ok test_durationfield_add (expressions.tests.FTimeDeltaTests.test_durationfield_add) ... ok test_exclude (expressions.tests.FTimeDeltaTests.test_exclude) ... ok test_invalid_operator (expressions.tests.FTimeDeltaTests.test_invalid_operator) ... ok test_mixed_comparisons1 (expressions.tests.FTimeDeltaTests.test_mixed_comparisons1) ... skipped "Database doesn't support feature(s): supports_mixed_date_datetime_comparisons" test_mixed_comparisons2 (expressions.tests.FTimeDeltaTests.test_mixed_comparisons2) ... ok test_multiple_query_compilation (expressions.tests.FTimeDeltaTests.test_multiple_query_compilation) ... ok test_negative_timedelta_update (expressions.tests.FTimeDeltaTests.test_negative_timedelta_update) ... ok test_query_clone (expressions.tests.FTimeDeltaTests.test_query_clone) ... ok test_time_subquery_subtraction (expressions.tests.FTimeDeltaTests.test_time_subquery_subtraction) ... ok test_time_subtraction (expressions.tests.FTimeDeltaTests.test_time_subtraction) ... ok test_complex_expressions_do_not_introduce_sql_injection_via_untrusted_string_inclusion (expressions.tests.IterableLookupInnerExpressionsTests.test_complex_expressions_do_not_introduce_sql_injection_via_untrusted_string_inclusion) This tests that SQL injection isn't possible using compilation of ... ok test_expressions_in_lookups_join_choice (expressions.tests.IterableLookupInnerExpressionsTests.test_expressions_in_lookups_join_choice) ... ok test_in_lookup_allows_F_expressions_and_expressions_for_datetimes (expressions.tests.IterableLookupInnerExpressionsTests.test_in_lookup_allows_F_expressions_and_expressions_for_datetimes) ... ok test_in_lookup_allows_F_expressions_and_expressions_for_integers (expressions.tests.IterableLookupInnerExpressionsTests.test_in_lookup_allows_F_expressions_and_expressions_for_integers) ... ok test_range_lookup_allows_F_expressions_and_expressions_for_integers (expressions.tests.IterableLookupInnerExpressionsTests.test_range_lookup_allows_F_expressions_and_expressions_for_integers) ... ok test_range_lookup_namedtuple (expressions.tests.IterableLookupInnerExpressionsTests.test_range_lookup_namedtuple) ... ok test_array_key_contains (model_fields.test_jsonfield.TestQuerying.test_array_key_contains) ... skipped "Database doesn't support feature(s): supports_json_field_contains" test_contained_by (model_fields.test_jsonfield.TestQuerying.test_contained_by) ... skipped "Database doesn't support feature(s): supports_json_field_contains" test_contained_by_unsupported (model_fields.test_jsonfield.TestQuerying.test_contained_by_unsupported) ... ok test_contains (model_fields.test_jsonfield.TestQuerying.test_contains) ... skipped "Database doesn't support feature(s): supports_json_field_contains" test_contains_contained_by_with_key_transform (model_fields.test_jsonfield.TestQuerying.test_contains_contained_by_with_key_transform) ... skipped "Database doesn't support feature(s): supports_json_field_contains" test_contains_primitives (model_fields.test_jsonfield.TestQuerying.test_contains_primitives) ... skipped "Database doesn't support feature(s): supports_primitives_in_json_field, supports_json_field_contains" test_contains_unsupported (model_fields.test_jsonfield.TestQuerying.test_contains_unsupported) ... ok test_deep_distinct (model_fields.test_jsonfield.TestQuerying.test_deep_distinct) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_deep_lookup_array (model_fields.test_jsonfield.TestQuerying.test_deep_lookup_array) ... ok test_deep_lookup_mixed (model_fields.test_jsonfield.TestQuerying.test_deep_lookup_mixed) ... ok test_deep_lookup_objs (model_fields.test_jsonfield.TestQuerying.test_deep_lookup_objs) ... ok test_deep_lookup_transform (model_fields.test_jsonfield.TestQuerying.test_deep_lookup_transform) ... ok test_deep_values (model_fields.test_jsonfield.TestQuerying.test_deep_values) ... ok test_exact (model_fields.test_jsonfield.TestQuerying.test_exact) ... ok test_exact_complex (model_fields.test_jsonfield.TestQuerying.test_exact_complex) ... ok test_expression_wrapper_key_transform (model_fields.test_jsonfield.TestQuerying.test_expression_wrapper_key_transform) ... ok test_has_any_keys (model_fields.test_jsonfield.TestQuerying.test_has_any_keys) ... ok test_has_key (model_fields.test_jsonfield.TestQuerying.test_has_key) ... ok test_has_key_deep (model_fields.test_jsonfield.TestQuerying.test_has_key_deep) ... ok test_has_key_list (model_fields.test_jsonfield.TestQuerying.test_has_key_list) ... ok test_has_key_null_value (model_fields.test_jsonfield.TestQuerying.test_has_key_null_value) ... ok test_has_keys (model_fields.test_jsonfield.TestQuerying.test_has_keys) ... ok test_isnull (model_fields.test_jsonfield.TestQuerying.test_isnull) ... ok test_isnull_key (model_fields.test_jsonfield.TestQuerying.test_isnull_key) ... ok test_isnull_key_or_none (model_fields.test_jsonfield.TestQuerying.test_isnull_key_or_none) ... ok test_join_key_transform_annotation_expression (model_fields.test_jsonfield.TestQuerying.test_join_key_transform_annotation_expression) ... ok test_key_contains (model_fields.test_jsonfield.TestQuerying.test_key_contains) ... skipped "Database doesn't support feature(s): supports_json_field_contains" test_key_endswith (model_fields.test_jsonfield.TestQuerying.test_key_endswith) ... ok test_key_escape (model_fields.test_jsonfield.TestQuerying.test_key_escape) ... ok test_key_icontains (model_fields.test_jsonfield.TestQuerying.test_key_icontains) ... ok test_key_iendswith (model_fields.test_jsonfield.TestQuerying.test_key_iendswith) ... ok test_key_iexact (model_fields.test_jsonfield.TestQuerying.test_key_iexact) ... ok test_key_in (model_fields.test_jsonfield.TestQuerying.test_key_in) ... ok test_key_iregex (model_fields.test_jsonfield.TestQuerying.test_key_iregex) ... ok test_key_istartswith (model_fields.test_jsonfield.TestQuerying.test_key_istartswith) ... ok test_key_quoted_string (model_fields.test_jsonfield.TestQuerying.test_key_quoted_string) ... ok test_key_regex (model_fields.test_jsonfield.TestQuerying.test_key_regex) ... ok test_key_sql_injection (model_fields.test_jsonfield.TestQuerying.test_key_sql_injection) ... skipped "Database doesn't support feature(s): has_json_operators" test_key_sql_injection_escape (model_fields.test_jsonfield.TestQuerying.test_key_sql_injection_escape) ... ok test_key_startswith (model_fields.test_jsonfield.TestQuerying.test_key_startswith) ... ok test_key_transform_annotation_expression (model_fields.test_jsonfield.TestQuerying.test_key_transform_annotation_expression) ... ok test_key_transform_expression (model_fields.test_jsonfield.TestQuerying.test_key_transform_expression) ... ok test_key_transform_raw_expression (model_fields.test_jsonfield.TestQuerying.test_key_transform_raw_expression) ... ok test_key_values (model_fields.test_jsonfield.TestQuerying.test_key_values) ... ok test_lookup_exclude (model_fields.test_jsonfield.TestQuerying.test_lookup_exclude) ... ok test_lookup_exclude_nonexistent_key (model_fields.test_jsonfield.TestQuerying.test_lookup_exclude_nonexistent_key) ... ok test_lookups_with_key_transform (model_fields.test_jsonfield.TestQuerying.test_lookups_with_key_transform) ... ok test_nested_key_transform_annotation_expression (model_fields.test_jsonfield.TestQuerying.test_nested_key_transform_annotation_expression) ... ok test_nested_key_transform_expression (model_fields.test_jsonfield.TestQuerying.test_nested_key_transform_expression) ... ok test_nested_key_transform_on_subquery (model_fields.test_jsonfield.TestQuerying.test_nested_key_transform_on_subquery) ... ok test_nested_key_transform_raw_expression (model_fields.test_jsonfield.TestQuerying.test_nested_key_transform_raw_expression) ... ok test_none_key (model_fields.test_jsonfield.TestQuerying.test_none_key) ... ok test_none_key_and_exact_lookup (model_fields.test_jsonfield.TestQuerying.test_none_key_and_exact_lookup) ... ok test_none_key_exclude (model_fields.test_jsonfield.TestQuerying.test_none_key_exclude) ... ok test_obj_subquery_lookup (model_fields.test_jsonfield.TestQuerying.test_obj_subquery_lookup) ... ok test_order_grouping_custom_decoder (model_fields.test_jsonfield.TestQuerying.test_order_grouping_custom_decoder) ... ok test_ordering_by_transform (model_fields.test_jsonfield.TestQuerying.test_ordering_by_transform) ... ok test_ordering_grouping_by_count (model_fields.test_jsonfield.TestQuerying.test_ordering_grouping_by_count) ... ok test_ordering_grouping_by_key_transform (model_fields.test_jsonfield.TestQuerying.test_ordering_grouping_by_key_transform) ... ok test_shallow_list_lookup (model_fields.test_jsonfield.TestQuerying.test_shallow_list_lookup) ... ok test_shallow_lookup_obj_target (model_fields.test_jsonfield.TestQuerying.test_shallow_lookup_obj_target) ... ok test_shallow_obj_lookup (model_fields.test_jsonfield.TestQuerying.test_shallow_obj_lookup) ... ok test_usage_in_subquery (model_fields.test_jsonfield.TestQuerying.test_usage_in_subquery) ... ok test_persistence (migration_test_data_persistence.tests.MigrationDataNormalPersistenceTestCase.test_persistence) ... ok test_columns_list_sql (indexes.tests.SchemaIndexesTests.test_columns_list_sql) ... ok test_descending_columns_list_sql (indexes.tests.SchemaIndexesTests.test_descending_columns_list_sql) ... ok test_index_name (indexes.tests.SchemaIndexesTests.test_index_name) Index names on the built-in database backends:: ... ok test_index_name_hash (indexes.tests.SchemaIndexesTests.test_index_name_hash) Index names should be deterministic. ... ok test_index_together (indexes.tests.SchemaIndexesTests.test_index_together) ... ok test_index_together_single_list (indexes.tests.SchemaIndexesTests.test_index_together_single_list) ... ok test_db_tablespace (model_indexes.tests.IndexesTests.test_db_tablespace) ... skipped "Database doesn't support feature(s): supports_tablespaces" test_func_with_tablespace (model_indexes.tests.IndexesTests.test_func_with_tablespace) ... skipped "Database doesn't support feature(s): supports_tablespaces" test_aggregate_subquery_annotation (expressions.tests.BasicExpressionsTests.test_aggregate_subquery_annotation) ... ok test_annotate_values_aggregate (expressions.tests.BasicExpressionsTests.test_annotate_values_aggregate) ... ok test_annotate_values_count (expressions.tests.BasicExpressionsTests.test_annotate_values_count) ... ok test_annotate_values_filter (expressions.tests.BasicExpressionsTests.test_annotate_values_filter) ... ok test_annotation_with_nested_outerref (expressions.tests.BasicExpressionsTests.test_annotation_with_nested_outerref) ... ok test_annotation_with_outerref (expressions.tests.BasicExpressionsTests.test_annotation_with_outerref) ... ok test_annotations_within_subquery (expressions.tests.BasicExpressionsTests.test_annotations_within_subquery) ... ok test_arithmetic (expressions.tests.BasicExpressionsTests.test_arithmetic) ... ok test_boolean_expression_combined (expressions.tests.BasicExpressionsTests.test_boolean_expression_combined) ... ok test_boolean_expression_combined_with_empty_Q (expressions.tests.BasicExpressionsTests.test_boolean_expression_combined_with_empty_Q) ... ok test_case_in_filter_if_boolean_output_field (expressions.tests.BasicExpressionsTests.test_case_in_filter_if_boolean_output_field) ... ok test_exist_single_field_output_field (expressions.tests.BasicExpressionsTests.test_exist_single_field_output_field) ... ok test_exists_in_filter (expressions.tests.BasicExpressionsTests.test_exists_in_filter) ... ok test_explicit_output_field (expressions.tests.BasicExpressionsTests.test_explicit_output_field) ... ok test_filter_inter_attribute (expressions.tests.BasicExpressionsTests.test_filter_inter_attribute) ... ok test_filter_with_join (expressions.tests.BasicExpressionsTests.test_filter_with_join) ... ok test_filtering_on_annotate_that_uses_q (expressions.tests.BasicExpressionsTests.test_filtering_on_annotate_that_uses_q) ... ok test_filtering_on_q_that_is_boolean (expressions.tests.BasicExpressionsTests.test_filtering_on_q_that_is_boolean) ... ok test_filtering_on_rawsql_that_is_boolean (expressions.tests.BasicExpressionsTests.test_filtering_on_rawsql_that_is_boolean) ... ok test_in_subquery (expressions.tests.BasicExpressionsTests.test_in_subquery) ... ok test_incorrect_field_in_F_expression (expressions.tests.BasicExpressionsTests.test_incorrect_field_in_F_expression) ... ok test_incorrect_joined_field_in_F_expression (expressions.tests.BasicExpressionsTests.test_incorrect_joined_field_in_F_expression) ... ok test_nested_outerref_with_function (expressions.tests.BasicExpressionsTests.test_nested_outerref_with_function) ... ok test_nested_subquery (expressions.tests.BasicExpressionsTests.test_nested_subquery) ... ok test_nested_subquery_join_outer_ref (expressions.tests.BasicExpressionsTests.test_nested_subquery_join_outer_ref) ... ok test_nested_subquery_outer_ref_2 (expressions.tests.BasicExpressionsTests.test_nested_subquery_outer_ref_2) ... ok test_nested_subquery_outer_ref_with_autofield (expressions.tests.BasicExpressionsTests.test_nested_subquery_outer_ref_with_autofield) ... ok test_new_object_create (expressions.tests.BasicExpressionsTests.test_new_object_create) ... ok test_new_object_save (expressions.tests.BasicExpressionsTests.test_new_object_save) ... ok test_object_create_with_aggregate (expressions.tests.BasicExpressionsTests.test_object_create_with_aggregate) ... ok test_object_update (expressions.tests.BasicExpressionsTests.test_object_update) ... ok test_object_update_fk (expressions.tests.BasicExpressionsTests.test_object_update_fk) ... ok test_object_update_unsaved_objects (expressions.tests.BasicExpressionsTests.test_object_update_unsaved_objects) ... ok test_order_by_exists (expressions.tests.BasicExpressionsTests.test_order_by_exists) ... ok test_order_by_multiline_sql (expressions.tests.BasicExpressionsTests.test_order_by_multiline_sql) ... ok test_order_of_operations (expressions.tests.BasicExpressionsTests.test_order_of_operations) ... ok test_outerref (expressions.tests.BasicExpressionsTests.test_outerref) ... ok test_outerref_mixed_case_table_name (expressions.tests.BasicExpressionsTests.test_outerref_mixed_case_table_name) ... ok test_outerref_with_operator (expressions.tests.BasicExpressionsTests.test_outerref_with_operator) ... ok test_parenthesis_priority (expressions.tests.BasicExpressionsTests.test_parenthesis_priority) ... ok test_pickle_expression (expressions.tests.BasicExpressionsTests.test_pickle_expression) ... ok test_subquery (expressions.tests.BasicExpressionsTests.test_subquery) ... ok test_subquery_eq (expressions.tests.BasicExpressionsTests.test_subquery_eq) ... ok test_subquery_filter_by_aggregate (expressions.tests.BasicExpressionsTests.test_subquery_filter_by_aggregate) ... ok test_subquery_filter_by_lazy (expressions.tests.BasicExpressionsTests.test_subquery_filter_by_lazy) ... ok test_subquery_group_by_outerref_in_filter (expressions.tests.BasicExpressionsTests.test_subquery_group_by_outerref_in_filter) ... ok test_subquery_in_filter (expressions.tests.BasicExpressionsTests.test_subquery_in_filter) ... ok test_subquery_references_joined_table_twice (expressions.tests.BasicExpressionsTests.test_subquery_references_joined_table_twice) ... ok test_ticket_11722_iexact_lookup (expressions.tests.BasicExpressionsTests.test_ticket_11722_iexact_lookup) ... ok test_ticket_16731_startswith_lookup (expressions.tests.BasicExpressionsTests.test_ticket_16731_startswith_lookup) ... ok test_ticket_18375_chained_filters (expressions.tests.BasicExpressionsTests.test_ticket_18375_chained_filters) ... ok test_ticket_18375_join_reuse (expressions.tests.BasicExpressionsTests.test_ticket_18375_join_reuse) ... ok test_ticket_18375_kwarg_ordering (expressions.tests.BasicExpressionsTests.test_ticket_18375_kwarg_ordering) ... ok test_ticket_18375_kwarg_ordering_2 (expressions.tests.BasicExpressionsTests.test_ticket_18375_kwarg_ordering_2) ... ok test_update (expressions.tests.BasicExpressionsTests.test_update) ... ok test_update_inherited_field_value (expressions.tests.BasicExpressionsTests.test_update_inherited_field_value) ... ok test_update_with_fk (expressions.tests.BasicExpressionsTests.test_update_with_fk) ... ok test_update_with_none (expressions.tests.BasicExpressionsTests.test_update_with_none) ... ok test_uuid_pk_subquery (expressions.tests.BasicExpressionsTests.test_uuid_pk_subquery) ... ok test_compile_unresolved (expressions.tests.ValueTests.test_compile_unresolved) ... ok test_deconstruct (expressions.tests.ValueTests.test_deconstruct) ... ok test_deconstruct_output_field (expressions.tests.ValueTests.test_deconstruct_output_field) ... ok test_equal (expressions.tests.ValueTests.test_equal) ... ok test_equal_output_field (expressions.tests.ValueTests.test_equal_output_field) ... ok test_hash (expressions.tests.ValueTests.test_hash) ... ok test_raise_empty_expressionlist (expressions.tests.ValueTests.test_raise_empty_expressionlist) ... ok test_resolve_output_field (expressions.tests.ValueTests.test_resolve_output_field) ... ok test_resolve_output_field_failure (expressions.tests.ValueTests.test_resolve_output_field_failure) ... ok test_update_TimeField_using_Value (expressions.tests.ValueTests.test_update_TimeField_using_Value) ... ok test_update_UUIDField_using_Value (expressions.tests.ValueTests.test_update_UUIDField_using_Value) ... ok test_prefetch_related_from_uuid_model (prefetch_related.test_uuid.UUIDPrefetchRelated.test_prefetch_related_from_uuid_model) ... ok test_prefetch_related_from_uuid_model_to_uuid_model (prefetch_related.test_uuid.UUIDPrefetchRelated.test_prefetch_related_from_uuid_model_to_uuid_model) ... ok test_prefetch_related_from_uuid_model_to_uuid_model_with_values_flat (prefetch_related.test_uuid.UUIDPrefetchRelated.test_prefetch_related_from_uuid_model_to_uuid_model_with_values_flat) ... ok test_prefetch_related_to_uuid_model (prefetch_related.test_uuid.UUIDPrefetchRelated.test_prefetch_related_to_uuid_model) ... ok test_from_integer_pk_lookup_integer_pk_uuid_pk (prefetch_related.test_uuid.UUIDPrefetchRelatedLookups.test_from_integer_pk_lookup_integer_pk_uuid_pk) ... ok test_from_integer_pk_lookup_integer_pk_uuid_pk_uuid_pk (prefetch_related.test_uuid.UUIDPrefetchRelatedLookups.test_from_integer_pk_lookup_integer_pk_uuid_pk_uuid_pk) ... ok test_from_integer_pk_lookup_uuid_pk_integer_pk (prefetch_related.test_uuid.UUIDPrefetchRelatedLookups.test_from_integer_pk_lookup_uuid_pk_integer_pk) ... ok test_from_uuid_pk_lookup_integer_pk2_uuid_pk2 (prefetch_related.test_uuid.UUIDPrefetchRelatedLookups.test_from_uuid_pk_lookup_integer_pk2_uuid_pk2) ... ok test_from_uuid_pk_lookup_uuid_pk_integer_pk (prefetch_related.test_uuid.UUIDPrefetchRelatedLookups.test_from_uuid_pk_lookup_uuid_pk_integer_pk) ... ok test_foreignkey_forward (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_foreignkey_forward) ... ok test_foreignkey_reverse (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_foreignkey_reverse) ... ok test_m2m_forward (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_m2m_forward) ... ok test_m2m_reverse (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_m2m_reverse) ... ok test_m2m_then_m2m (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_m2m_then_m2m) A m2m can be followed through another m2m. ... ok test_prefetch_object (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_prefetch_object) ... ok test_prefetch_object_to_attr (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_prefetch_object_to_attr) ... ok test_prefetch_object_to_attr_twice (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_prefetch_object_to_attr_twice) ... ok test_prefetch_object_twice (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_prefetch_object_twice) ... ok test_prefetch_queryset (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_prefetch_queryset) ... ok test_unknown (prefetch_related.test_prefetch_related_objects.PrefetchRelatedObjectsTests.test_unknown) ... ok test_m2m_then_m2m (prefetch_related.tests.DefaultManagerTests.test_m2m_then_m2m) ... ok test_foreignkey (prefetch_related.tests.ForeignKeyToFieldTest.test_foreignkey) ... ok test_m2m (prefetch_related.tests.ForeignKeyToFieldTest.test_m2m) ... ok test_add_clears_prefetched_objects (prefetch_related.tests.DirectPrefetchedObjectCacheReuseTests.test_add_clears_prefetched_objects) ... ok test_detect_is_fetched (prefetch_related.tests.DirectPrefetchedObjectCacheReuseTests.test_detect_is_fetched) Nested prefetch_related() shouldn't trigger duplicate queries for the same ... ok test_detect_is_fetched_with_to_attr (prefetch_related.tests.DirectPrefetchedObjectCacheReuseTests.test_detect_is_fetched_with_to_attr) ... ok test_prefetch_reverse_foreign_key (prefetch_related.tests.DirectPrefetchedObjectCacheReuseTests.test_prefetch_reverse_foreign_key) ... ok test_remove_clears_prefetched_objects (prefetch_related.tests.DirectPrefetchedObjectCacheReuseTests.test_remove_clears_prefetched_objects) ... ok test_order (prefetch_related.tests.LookupOrderingTest.test_order) ... ok test_FK_raw_query (raw_query.tests.RawQueryTests.test_FK_raw_query) Test of a simple raw query against a model containing a foreign key ... ok test_annotations (raw_query.tests.RawQueryTests.test_annotations) ... ok test_bool (raw_query.tests.RawQueryTests.test_bool) ... ok test_db_column_handler (raw_query.tests.RawQueryTests.test_db_column_handler) Test of a simple raw query against a model containing a field with ... ok test_db_column_name_is_used_in_raw_query (raw_query.tests.RawQueryTests.test_db_column_name_is_used_in_raw_query) Regression test that ensures the `column` attribute on the field is ... ok test_decimal_parameter (raw_query.tests.RawQueryTests.test_decimal_parameter) ... ok test_escaped_percent (raw_query.tests.RawQueryTests.test_escaped_percent) ... ok test_extra_conversions (raw_query.tests.RawQueryTests.test_extra_conversions) Test to insure that extra translations are ignored. ... ok test_get_item (raw_query.tests.RawQueryTests.test_get_item) ... ok test_inheritance (raw_query.tests.RawQueryTests.test_inheritance) ... ok test_iterator (raw_query.tests.RawQueryTests.test_iterator) ... ok test_len (raw_query.tests.RawQueryTests.test_len) ... ok test_many_to_many (raw_query.tests.RawQueryTests.test_many_to_many) Test of a simple raw query against a model containing a m2m field ... ok test_missing_fields (raw_query.tests.RawQueryTests.test_missing_fields) ... ok test_missing_fields_without_PK (raw_query.tests.RawQueryTests.test_missing_fields_without_PK) ... ok test_multiple_iterations (raw_query.tests.RawQueryTests.test_multiple_iterations) ... ok test_order_handler (raw_query.tests.RawQueryTests.test_order_handler) Test of raw raw query's tolerance for columns being returned in any ... ok test_params (raw_query.tests.RawQueryTests.test_params) Test passing optional query parameters ... ok test_params_none (raw_query.tests.RawQueryTests.test_params_none) ... ok test_pk_with_mixed_case_db_column (raw_query.tests.RawQueryTests.test_pk_with_mixed_case_db_column) A raw query with a model that has a pk db_column with mixed case. ... ok test_pyformat_params (raw_query.tests.RawQueryTests.test_pyformat_params) Test passing optional query parameters ... skipped "Database doesn't support feature(s): supports_paramstyle_pyformat" test_query_count (raw_query.tests.RawQueryTests.test_query_count) ... ok test_query_representation (raw_query.tests.RawQueryTests.test_query_representation) Test representation of raw query with parameters ... ok test_raw_query_lazy (raw_query.tests.RawQueryTests.test_raw_query_lazy) Raw queries are lazy: they aren't actually executed until they're ... ok test_rawqueryset_repr (raw_query.tests.RawQueryTests.test_rawqueryset_repr) ... ok test_result_caching (raw_query.tests.RawQueryTests.test_result_caching) ... ok test_simple_raw_query (raw_query.tests.RawQueryTests.test_simple_raw_query) Basic test of raw query with a simple database query ... ok test_subquery_in_raw_sql (raw_query.tests.RawQueryTests.test_subquery_in_raw_sql) ... ok test_translations (raw_query.tests.RawQueryTests.test_translations) Test of raw query's optional ability to translate unexpected result ... ok test_white_space_query (raw_query.tests.RawQueryTests.test_white_space_query) ... ok test_charfield_GFK (prefetch_related.tests.GenericRelationTests.test_charfield_GFK) ... ok test_custom_queryset (prefetch_related.tests.GenericRelationTests.test_custom_queryset) ... ok test_generic_relation (prefetch_related.tests.GenericRelationTests.test_generic_relation) ... ok test_nullable_GFK (prefetch_related.tests.GenericRelationTests.test_nullable_GFK) ... ok test_prefetch_GFK (prefetch_related.tests.GenericRelationTests.test_prefetch_GFK) ... ok test_prefetch_GFK_fk_pk (prefetch_related.tests.GenericRelationTests.test_prefetch_GFK_fk_pk) ... ok test_prefetch_GFK_nonint_pk (prefetch_related.tests.GenericRelationTests.test_prefetch_GFK_nonint_pk) ... ok test_prefetch_GFK_uuid_pk (prefetch_related.tests.GenericRelationTests.test_prefetch_GFK_uuid_pk) ... ok test_traverse_GFK (prefetch_related.tests.GenericRelationTests.test_traverse_GFK) A 'content_object' can be traversed with prefetch_related() and ... ok test_in_bulk (prefetch_related.tests.NullableTest.test_in_bulk) In-bulk does correctly prefetch objects by not using .iterator() ... ok test_prefetch_nullable (prefetch_related.tests.NullableTest.test_prefetch_nullable) ... ok test_traverse_nullable (prefetch_related.tests.NullableTest.test_traverse_nullable) ... ok test_child_link_prefetch (prefetch_related.tests.MultiTableInheritanceTest.test_child_link_prefetch) ... ok test_foreignkey (prefetch_related.tests.MultiTableInheritanceTest.test_foreignkey) ... ok test_foreignkey_to_inherited (prefetch_related.tests.MultiTableInheritanceTest.test_foreignkey_to_inherited) ... ok test_m2m_to_inheriting_model (prefetch_related.tests.MultiTableInheritanceTest.test_m2m_to_inheriting_model) ... ok test_parent_link_prefetch (prefetch_related.tests.MultiTableInheritanceTest.test_parent_link_prefetch) ... ok test_using_is_honored_custom_qs (prefetch_related.tests.MultiDbTests.test_using_is_honored_custom_qs) ... ok test_using_is_honored_fkey (prefetch_related.tests.MultiDbTests.test_using_is_honored_fkey) ... ok test_using_is_honored_inheritance (prefetch_related.tests.MultiDbTests.test_using_is_honored_inheritance) ... ok test_using_is_honored_m2m (prefetch_related.tests.MultiDbTests.test_using_is_honored_m2m) ... ok test_retrieves_results_from_prefetched_objects_cache (prefetch_related.tests.ReadPrefetchedObjectsCacheTests.test_retrieves_results_from_prefetched_objects_cache) When intermediary results are prefetched without a destination ... ok test_basic (prefetch_related.tests.RawQuerySetTests.test_basic) ... ok test_clear (prefetch_related.tests.RawQuerySetTests.test_clear) ... ok test_prefetch_before_raw (prefetch_related.tests.RawQuerySetTests.test_prefetch_before_raw) ... ok test_bug (prefetch_related.tests.Ticket19607Tests.test_bug) ... ok test_bug (prefetch_related.tests.Ticket21410Tests.test_bug) ... ok test_bug (prefetch_related.tests.Ticket21760Tests.test_bug) ... ok test_ambiguous (prefetch_related.tests.CustomPrefetchTests.test_ambiguous) ... ok test_custom_qs (prefetch_related.tests.CustomPrefetchTests.test_custom_qs) ... ok test_filter_deferred (prefetch_related.tests.CustomPrefetchTests.test_filter_deferred) Related filtering of prefetched querysets is deferred until necessary. ... ok test_generic_rel (prefetch_related.tests.CustomPrefetchTests.test_generic_rel) ... ok test_m2m (prefetch_related.tests.CustomPrefetchTests.test_m2m) ... ok test_m2m_through_fk (prefetch_related.tests.CustomPrefetchTests.test_m2m_through_fk) ... ok test_m2m_through_gfk (prefetch_related.tests.CustomPrefetchTests.test_m2m_through_gfk) ... ok test_nested_prefetch_related_are_not_overwritten (prefetch_related.tests.CustomPrefetchTests.test_nested_prefetch_related_are_not_overwritten) ... ok test_nested_prefetch_related_with_duplicate_prefetcher (prefetch_related.tests.CustomPrefetchTests.test_nested_prefetch_related_with_duplicate_prefetcher) Nested prefetches whose name clashes with descriptor names ... ok test_o2m_through_m2m (prefetch_related.tests.CustomPrefetchTests.test_o2m_through_m2m) ... ok test_raw_queryset (prefetch_related.tests.CustomPrefetchTests.test_raw_queryset) ... ok test_reverse_m2m (prefetch_related.tests.CustomPrefetchTests.test_reverse_m2m) ... ok test_to_attr_cached_property (prefetch_related.tests.CustomPrefetchTests.test_to_attr_cached_property) ... ok test_to_attr_doesnt_cache_through_attr_as_list (prefetch_related.tests.CustomPrefetchTests.test_to_attr_doesnt_cache_through_attr_as_list) ... ok test_traverse_multiple_items_property (prefetch_related.tests.CustomPrefetchTests.test_traverse_multiple_items_property) ... ok test_traverse_qs (prefetch_related.tests.CustomPrefetchTests.test_traverse_qs) ... ok test_traverse_single_item_property (prefetch_related.tests.CustomPrefetchTests.test_traverse_single_item_property) ... ok test_values_queryset (prefetch_related.tests.CustomPrefetchTests.test_values_queryset) ... ok test_combine_isnull (null_fk.tests.NullFkTests.test_combine_isnull) ... ok test_null_fk (null_fk.tests.NullFkTests.test_null_fk) ... ok test_attribute_error (prefetch_related.tests.PrefetchRelatedTests.test_attribute_error) ... ok test_bool (prefetch_related.tests.PrefetchRelatedTests.test_bool) ... ok test_clear (prefetch_related.tests.PrefetchRelatedTests.test_clear) ... ok test_count (prefetch_related.tests.PrefetchRelatedTests.test_count) ... ok test_exists (prefetch_related.tests.PrefetchRelatedTests.test_exists) ... ok test_filter_deferred (prefetch_related.tests.PrefetchRelatedTests.test_filter_deferred) Related filtering of prefetched querysets is deferred on m2m and ... ok test_foreign_key_then_m2m (prefetch_related.tests.PrefetchRelatedTests.test_foreign_key_then_m2m) A m2m relation can be followed after a relation like ForeignKey that ... ok test_foreignkey_forward (prefetch_related.tests.PrefetchRelatedTests.test_foreignkey_forward) ... ok test_foreignkey_reverse (prefetch_related.tests.PrefetchRelatedTests.test_foreignkey_reverse) ... ok test_forward_m2m_to_attr_conflict (prefetch_related.tests.PrefetchRelatedTests.test_forward_m2m_to_attr_conflict) ... ok test_get (prefetch_related.tests.PrefetchRelatedTests.test_get) Objects retrieved with .get() get the prefetch behavior. ... ok test_in_and_prefetch_related (prefetch_related.tests.PrefetchRelatedTests.test_in_and_prefetch_related) Regression test for #20242 - QuerySet "in" didn't work the first time ... ok test_invalid_final_lookup (prefetch_related.tests.PrefetchRelatedTests.test_invalid_final_lookup) ... ok test_len (prefetch_related.tests.PrefetchRelatedTests.test_len) ... ok test_m2m_forward (prefetch_related.tests.PrefetchRelatedTests.test_m2m_forward) ... ok test_m2m_reverse (prefetch_related.tests.PrefetchRelatedTests.test_m2m_reverse) ... ok test_m2m_then_m2m (prefetch_related.tests.PrefetchRelatedTests.test_m2m_then_m2m) A m2m can be followed through another m2m. ... ok test_m2m_then_m2m_object_ids (prefetch_related.tests.PrefetchRelatedTests.test_m2m_then_m2m_object_ids) ... ok test_m2m_then_reverse_fk_object_ids (prefetch_related.tests.PrefetchRelatedTests.test_m2m_then_reverse_fk_object_ids) ... ok test_m2m_then_reverse_one_to_one_object_ids (prefetch_related.tests.PrefetchRelatedTests.test_m2m_then_reverse_one_to_one_object_ids) ... ok test_named_values_list (prefetch_related.tests.PrefetchRelatedTests.test_named_values_list) ... ok test_onetoone_reverse_no_match (prefetch_related.tests.PrefetchRelatedTests.test_onetoone_reverse_no_match) ... ok test_onetoone_reverse_with_to_field_pk (prefetch_related.tests.PrefetchRelatedTests.test_onetoone_reverse_with_to_field_pk) A model (Bio) with a OneToOneField primary key (author) that references ... ok test_overriding_prefetch (prefetch_related.tests.PrefetchRelatedTests.test_overriding_prefetch) ... ok test_prefetch_eq (prefetch_related.tests.PrefetchRelatedTests.test_prefetch_eq) ... ok test_reverse_m2m_to_attr_conflict (prefetch_related.tests.PrefetchRelatedTests.test_reverse_m2m_to_attr_conflict) ... ok test_reverse_one_to_one_then_m2m (prefetch_related.tests.PrefetchRelatedTests.test_reverse_one_to_one_then_m2m) A m2m relation can be followed after going through the select_related ... ok test_survives_clone (prefetch_related.tests.PrefetchRelatedTests.test_survives_clone) ... ok test_absolute_max (generic_relations.test_forms.GenericInlineFormsetTests.test_absolute_max) ... ok test_absolute_max_with_max_num (generic_relations.test_forms.GenericInlineFormsetTests.test_absolute_max_with_max_num) ... ok test_can_delete_extra (generic_relations.test_forms.GenericInlineFormsetTests.test_can_delete_extra) ... ok test_disable_delete_extra (generic_relations.test_forms.GenericInlineFormsetTests.test_disable_delete_extra) ... ok test_get_queryset_ordering (generic_relations.test_forms.GenericInlineFormsetTests.test_get_queryset_ordering) BaseGenericInlineFormSet.get_queryset() adds default ordering, if ... ok test_incorrect_content_type (generic_relations.test_forms.GenericInlineFormsetTests.test_incorrect_content_type) ... ok test_initial (generic_relations.test_forms.GenericInlineFormsetTests.test_initial) ... ok test_initial_count (generic_relations.test_forms.GenericInlineFormsetTests.test_initial_count) ... ok test_meta_widgets (generic_relations.test_forms.GenericInlineFormsetTests.test_meta_widgets) TaggedItemForm has a widget defined in Meta. ... ok test_options (generic_relations.test_forms.GenericInlineFormsetTests.test_options) ... ok test_output (generic_relations.test_forms.GenericInlineFormsetTests.test_output) ... ok test_save_as_new (generic_relations.test_forms.GenericInlineFormsetTests.test_save_as_new) The save_as_new parameter creates new items that are associated with ... ok test_save_new_for_concrete (generic_relations.test_forms.GenericInlineFormsetTests.test_save_new_for_concrete) ... ok test_save_new_for_proxy (generic_relations.test_forms.GenericInlineFormsetTests.test_save_new_for_proxy) ... ok test_save_new_uses_form_save (generic_relations.test_forms.GenericInlineFormsetTests.test_save_new_uses_form_save) ... ok test_default_behavior (generic_relations.tests.ProxyRelatedModelTest.test_default_behavior) The default for for_concrete_model should be True ... ok test_generic_relation (generic_relations.tests.ProxyRelatedModelTest.test_generic_relation) ... ok test_generic_relation_set (generic_relations.tests.ProxyRelatedModelTest.test_generic_relation_set) ... ok test_proxy_is_returned (generic_relations.tests.ProxyRelatedModelTest.test_proxy_is_returned) Instances of the proxy should be returned when ... ok test_query (generic_relations.tests.ProxyRelatedModelTest.test_query) ... ok test_query_proxy (generic_relations.tests.ProxyRelatedModelTest.test_query_proxy) ... ok test_works_normally (generic_relations.tests.ProxyRelatedModelTest.test_works_normally) When for_concrete_model is False, we should still be able to get ... ok test_basic_add_GET (generic_inline_admin.tests.GenericAdminViewTest.test_basic_add_GET) A smoke test to ensure GET on the add_view works. ... ok test_basic_add_POST (generic_inline_admin.tests.GenericAdminViewTest.test_basic_add_POST) A smoke test to ensure POST on add_view works. ... ok test_basic_edit_GET (generic_inline_admin.tests.GenericAdminViewTest.test_basic_edit_GET) A smoke test to ensure GET on the change_view works. ... ok test_basic_edit_POST (generic_inline_admin.tests.GenericAdminViewTest.test_basic_edit_POST) A smoke test to ensure POST on edit_view works. ... ok test_extra_param (generic_inline_admin.tests.GenericInlineAdminParametersTest.test_extra_param) With extra=0, there should be one form. ... ok test_get_extra (generic_inline_admin.tests.GenericInlineAdminParametersTest.test_get_extra) ... ok test_get_max_num (generic_inline_admin.tests.GenericInlineAdminParametersTest.test_get_max_num) ... ok test_get_min_num (generic_inline_admin.tests.GenericInlineAdminParametersTest.test_get_min_num) ... ok test_max_num_param (generic_inline_admin.tests.GenericInlineAdminParametersTest.test_max_num_param) With extra=5 and max_num=2, there should be only 2 forms. ... ok test_min_num_param (generic_inline_admin.tests.GenericInlineAdminParametersTest.test_min_num_param) With extra=3 and min_num=2, there should be five forms. ... ok test_no_param (generic_inline_admin.tests.GenericInlineAdminParametersTest.test_no_param) With one initial form, extra (default) at 3, there should be 4 forms. ... ok test_add (generic_inline_admin.tests.GenericInlineAdminWithUniqueTogetherTest.test_add) ... ok test_delete (generic_inline_admin.tests.GenericInlineAdminWithUniqueTogetherTest.test_delete) ... ok test_basic_distinct_on (distinct_on_fields.tests.DistinctOnTests.test_basic_distinct_on) QuerySet.distinct('field', ...) works ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_distinct_not_implemented_checks (distinct_on_fields.tests.DistinctOnTests.test_distinct_not_implemented_checks) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_distinct_on_get_ordering_preserved (distinct_on_fields.tests.DistinctOnTests.test_distinct_on_get_ordering_preserved) Ordering shouldn't be cleared when distinct on fields are specified. ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_distinct_on_in_ordered_subquery (distinct_on_fields.tests.DistinctOnTests.test_distinct_on_in_ordered_subquery) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_transform (distinct_on_fields.tests.DistinctOnTests.test_transform) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_allvaluesfieldlistfilter (admin_filters.tests.ListFiltersTests.test_allvaluesfieldlistfilter) ... ok test_allvaluesfieldlistfilter_custom_qs (admin_filters.tests.ListFiltersTests.test_allvaluesfieldlistfilter_custom_qs) ... ok test_booleanfieldlistfilter (admin_filters.tests.ListFiltersTests.test_booleanfieldlistfilter) ... ok test_booleanfieldlistfilter_choices (admin_filters.tests.ListFiltersTests.test_booleanfieldlistfilter_choices) ... ok test_booleanfieldlistfilter_nullbooleanfield (admin_filters.tests.ListFiltersTests.test_booleanfieldlistfilter_nullbooleanfield) ... ok test_booleanfieldlistfilter_tuple (admin_filters.tests.ListFiltersTests.test_booleanfieldlistfilter_tuple) ... ok test_booleanfieldlistfilter_tuple_choices (admin_filters.tests.ListFiltersTests.test_booleanfieldlistfilter_tuple_choices) ... ok test_choicesfieldlistfilter_has_none_choice (admin_filters.tests.ListFiltersTests.test_choicesfieldlistfilter_has_none_choice) The last choice is for the None value. ... ok test_datefieldlistfilter (admin_filters.tests.ListFiltersTests.test_datefieldlistfilter) ... ok test_datefieldlistfilter_with_time_zone_support (admin_filters.tests.ListFiltersTests.test_datefieldlistfilter_with_time_zone_support) ... ok test_emptylistfieldfilter (admin_filters.tests.ListFiltersTests.test_emptylistfieldfilter) ... ok test_emptylistfieldfilter_choices (admin_filters.tests.ListFiltersTests.test_emptylistfieldfilter_choices) ... ok test_emptylistfieldfilter_genericrelation (admin_filters.tests.ListFiltersTests.test_emptylistfieldfilter_genericrelation) ... ok test_emptylistfieldfilter_invalid_lookup_parameters (admin_filters.tests.ListFiltersTests.test_emptylistfieldfilter_invalid_lookup_parameters) ... ok test_emptylistfieldfilter_non_empty_field (admin_filters.tests.ListFiltersTests.test_emptylistfieldfilter_non_empty_field) ... ok test_emptylistfieldfilter_reverse_relationships (admin_filters.tests.ListFiltersTests.test_emptylistfieldfilter_reverse_relationships) ... ok test_fieldlistfilter_invalid_lookup_parameters (admin_filters.tests.ListFiltersTests.test_fieldlistfilter_invalid_lookup_parameters) Filtering by an invalid value. ... ok test_fieldlistfilter_underscorelookup_tuple (admin_filters.tests.ListFiltersTests.test_fieldlistfilter_underscorelookup_tuple) Ensure ('fieldpath', ClassName ) lookups pass lookup_allowed checks ... ok test_filter_with_failing_queryset (admin_filters.tests.ListFiltersTests.test_filter_with_failing_queryset) When a filter's queryset method fails, it fails loudly and ... ok test_fk_with_to_field (admin_filters.tests.ListFiltersTests.test_fk_with_to_field) A filter on a FK respects the FK's to_field attribute (#17972). ... ok test_list_filter_queryset_filtered_by_default (admin_filters.tests.ListFiltersTests.test_list_filter_queryset_filtered_by_default) A list filter that filters the queryset by default gives the correct ... ok test_listfilter_genericrelation (admin_filters.tests.ListFiltersTests.test_listfilter_genericrelation) ... ok test_listfilter_without_title (admin_filters.tests.ListFiltersTests.test_listfilter_without_title) Any filter must define a title. ... ok test_lookup_with_dynamic_value (admin_filters.tests.ListFiltersTests.test_lookup_with_dynamic_value) Ensure SimpleListFilter can access self.value() inside the lookup. ... ok test_lookup_with_non_string_value (admin_filters.tests.ListFiltersTests.test_lookup_with_non_string_value) Ensure choices are set the selected class when using non-string values ... ok test_lookup_with_non_string_value_underscored (admin_filters.tests.ListFiltersTests.test_lookup_with_non_string_value_underscored) Ensure SimpleListFilter lookups pass lookup_allowed checks when ... ok test_parameter_ends_with__in__or__isnull (admin_filters.tests.ListFiltersTests.test_parameter_ends_with__in__or__isnull) A SimpleListFilter's parameter name is not mistaken for a model field ... ok test_relatedfieldlistfilter_foreignkey (admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey) ... ok test_relatedfieldlistfilter_foreignkey_default_ordering (admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey_default_ordering) RelatedFieldListFilter ordering respects Model.ordering. ... ok test_relatedfieldlistfilter_foreignkey_ordering (admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey_ordering) RelatedFieldListFilter ordering respects ModelAdmin.ordering. ... ok test_relatedfieldlistfilter_foreignkey_ordering_reverse (admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_foreignkey_ordering_reverse) ... ok test_relatedfieldlistfilter_manytomany (admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_manytomany) ... ok test_relatedfieldlistfilter_reverse_relationships (admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_reverse_relationships) ... ok test_relatedfieldlistfilter_reverse_relationships_default_ordering (admin_filters.tests.ListFiltersTests.test_relatedfieldlistfilter_reverse_relationships_default_ordering) ... ok test_relatedonlyfieldlistfilter_foreignkey (admin_filters.tests.ListFiltersTests.test_relatedonlyfieldlistfilter_foreignkey) ... ok test_relatedonlyfieldlistfilter_foreignkey_default_ordering (admin_filters.tests.ListFiltersTests.test_relatedonlyfieldlistfilter_foreignkey_default_ordering) RelatedOnlyFieldListFilter ordering respects Meta.ordering. ... ok test_relatedonlyfieldlistfilter_foreignkey_ordering (admin_filters.tests.ListFiltersTests.test_relatedonlyfieldlistfilter_foreignkey_ordering) RelatedOnlyFieldListFilter ordering respects ModelAdmin.ordering. ... ok test_relatedonlyfieldlistfilter_foreignkey_reverse_relationships (admin_filters.tests.ListFiltersTests.test_relatedonlyfieldlistfilter_foreignkey_reverse_relationships) ... ok test_relatedonlyfieldlistfilter_manytomany (admin_filters.tests.ListFiltersTests.test_relatedonlyfieldlistfilter_manytomany) ... ok test_relatedonlyfieldlistfilter_manytomany_reverse_relationships (admin_filters.tests.ListFiltersTests.test_relatedonlyfieldlistfilter_manytomany_reverse_relationships) ... ok test_relatedonlyfieldlistfilter_underscorelookup_foreignkey (admin_filters.tests.ListFiltersTests.test_relatedonlyfieldlistfilter_underscorelookup_foreignkey) ... ok test_simplelistfilter (admin_filters.tests.ListFiltersTests.test_simplelistfilter) ... ok test_simplelistfilter_with_none_returning_lookups (admin_filters.tests.ListFiltersTests.test_simplelistfilter_with_none_returning_lookups) A SimpleListFilter lookups method can return None but disables the ... ok test_simplelistfilter_with_queryset_based_lookups (admin_filters.tests.ListFiltersTests.test_simplelistfilter_with_queryset_based_lookups) ... ok test_simplelistfilter_without_parameter (admin_filters.tests.ListFiltersTests.test_simplelistfilter_without_parameter) Any SimpleListFilter must define a parameter_name. ... ok test_two_characters_long_field (admin_filters.tests.ListFiltersTests.test_two_characters_long_field) list_filter works with two-characters long field names (#16080). ... ok test_closes_connections (servers.test_liveserverthread.LiveServerThreadTest.test_closes_connections) ... skipped "the sqlite backend's close() method is a no-op when using an in-memory database" test_ordering_across_null_fk (null_fk_ordering.tests.NullFkOrderingTests.test_ordering_across_null_fk) Regression test for #7512 ... ok test_access_content_object (generic_relations.tests.GenericRelationsTests.test_access_content_object) Test accessing the content object like a foreign key. ... ok test_access_via_content_type (generic_relations.tests.GenericRelationsTests.test_access_via_content_type) Test lookups through content type. ... ok test_add_after_prefetch (generic_relations.tests.GenericRelationsTests.test_add_after_prefetch) ... ok test_add_bulk (generic_relations.tests.GenericRelationsTests.test_add_bulk) ... ok test_add_bulk_false (generic_relations.tests.GenericRelationsTests.test_add_bulk_false) ... ok test_add_rejects_unsaved_objects (generic_relations.tests.GenericRelationsTests.test_add_rejects_unsaved_objects) ... ok test_add_rejects_wrong_instances (generic_relations.tests.GenericRelationsTests.test_add_rejects_wrong_instances) ... ok test_add_then_remove_after_prefetch (generic_relations.tests.GenericRelationsTests.test_add_then_remove_after_prefetch) ... ok test_assign (generic_relations.tests.GenericRelationsTests.test_assign) ... ok test_assign_content_object_in_init (generic_relations.tests.GenericRelationsTests.test_assign_content_object_in_init) ... ok test_assign_with_queryset (generic_relations.tests.GenericRelationsTests.test_assign_with_queryset) ... ok test_cache_invalidation_for_content_type_id (generic_relations.tests.GenericRelationsTests.test_cache_invalidation_for_content_type_id) ... ok test_cache_invalidation_for_object_id (generic_relations.tests.GenericRelationsTests.test_cache_invalidation_for_object_id) ... ok test_clear (generic_relations.tests.GenericRelationsTests.test_clear) ... ok test_clear_after_prefetch (generic_relations.tests.GenericRelationsTests.test_clear_after_prefetch) ... ok test_create_after_prefetch (generic_relations.tests.GenericRelationsTests.test_create_after_prefetch) ... ok test_exclude_generic_relations (generic_relations.tests.GenericRelationsTests.test_exclude_generic_relations) Test lookups over an object without GenericRelations. ... ok test_generic_get_or_create_when_created (generic_relations.tests.GenericRelationsTests.test_generic_get_or_create_when_created) Should be able to use get_or_create from the generic related manager ... ok test_generic_get_or_create_when_exists (generic_relations.tests.GenericRelationsTests.test_generic_get_or_create_when_exists) Should be able to use get_or_create from the generic related manager ... ok test_generic_relation_related_name_default (generic_relations.tests.GenericRelationsTests.test_generic_relation_related_name_default) ... ok test_generic_relation_to_inherited_child (generic_relations.tests.GenericRelationsTests.test_generic_relation_to_inherited_child) ... ok test_generic_relations_m2m_mimic (generic_relations.tests.GenericRelationsTests.test_generic_relations_m2m_mimic) Objects with declared GenericRelations can be tagged directly -- the ... ok test_generic_update_or_create_when_created (generic_relations.tests.GenericRelationsTests.test_generic_update_or_create_when_created) Should be able to use update_or_create from the generic related manager ... ok test_generic_update_or_create_when_updated (generic_relations.tests.GenericRelationsTests.test_generic_update_or_create_when_updated) Should be able to use update_or_create from the generic related manager ... ok test_get_or_create (generic_relations.tests.GenericRelationsTests.test_get_or_create) ... ok test_gfk_manager (generic_relations.tests.GenericRelationsTests.test_gfk_manager) ... ok test_gfk_subclasses (generic_relations.tests.GenericRelationsTests.test_gfk_subclasses) ... ok test_multiple_gfk (generic_relations.tests.GenericRelationsTests.test_multiple_gfk) ... ok test_object_deletion_with_generic_relation (generic_relations.tests.GenericRelationsTests.test_object_deletion_with_generic_relation) If you delete an object with an explicit Generic relation, the related ... ok test_object_deletion_without_generic_relation (generic_relations.tests.GenericRelationsTests.test_object_deletion_without_generic_relation) If Generic Relation is not explicitly defined, any related objects ... ok test_prefetch_related_custom_object_id (generic_relations.tests.GenericRelationsTests.test_prefetch_related_custom_object_id) ... ok test_prefetch_related_different_content_types (generic_relations.tests.GenericRelationsTests.test_prefetch_related_different_content_types) ... ok test_queries_across_generic_relations (generic_relations.tests.GenericRelationsTests.test_queries_across_generic_relations) Queries across generic relations respect the content types. Even though ... ok test_queries_content_type_restriction (generic_relations.tests.GenericRelationsTests.test_queries_content_type_restriction) Create another fatty tagged instance with different PK to ensure there ... ok test_query_content_object (generic_relations.tests.GenericRelationsTests.test_query_content_object) ... ok test_query_content_type (generic_relations.tests.GenericRelationsTests.test_query_content_type) ... ok test_remove (generic_relations.tests.GenericRelationsTests.test_remove) ... ok test_remove_after_prefetch (generic_relations.tests.GenericRelationsTests.test_remove_after_prefetch) ... ok test_set (generic_relations.tests.GenericRelationsTests.test_set) ... ok test_set_after_prefetch (generic_relations.tests.GenericRelationsTests.test_set_after_prefetch) ... ok test_set_foreign_key (generic_relations.tests.GenericRelationsTests.test_set_foreign_key) You can set a generic foreign key in the way you'd expect. ... ok test_subclasses_with_gen_rel (generic_relations.tests.GenericRelationsTests.test_subclasses_with_gen_rel) Concrete model subclasses with generic relations work ... ok test_subclasses_with_parent_gen_rel (generic_relations.tests.GenericRelationsTests.test_subclasses_with_parent_gen_rel) Generic relations on a base class (Vegetable) work correctly in ... ok test_tag_deletion_related_objects_unaffected (generic_relations.tests.GenericRelationsTests.test_tag_deletion_related_objects_unaffected) If you delete a tag, the objects using the tag are unaffected (other ... ok test_unsaved_instance_on_generic_foreign_key (generic_relations.tests.GenericRelationsTests.test_unsaved_instance_on_generic_foreign_key) Assigning an unsaved object to GenericForeignKey should raise an ... ok test_update_or_create_defaults (generic_relations.tests.GenericRelationsTests.test_update_or_create_defaults) ... ok test_inlineformset_custom_callback (model_formsets_regress.tests.FormfieldCallbackTests.test_inlineformset_custom_callback) ... ok test_inlineformset_factory_default (model_formsets_regress.tests.FormfieldCallbackTests.test_inlineformset_factory_default) ... ok test_modelformset_custom_callback (model_formsets_regress.tests.FormfieldCallbackTests.test_modelformset_custom_callback) ... ok test_modelformset_factory_default (model_formsets_regress.tests.FormfieldCallbackTests.test_modelformset_factory_default) ... ok test_error_class (model_formsets_regress.tests.FormsetTests.test_error_class) Test the type of Formset and Form error attributes ... ok test_extraneous_query_is_not_run (model_formsets_regress.tests.FormsetTests.test_extraneous_query_is_not_run) ... ok test_initial_data (model_formsets_regress.tests.FormsetTests.test_initial_data) ... ok test_all_delete (model_formsets_regress.tests.FormfieldShouldDeleteFormTests.test_all_delete) Verify base formset honors DELETE field ... ok test_custom_delete (model_formsets_regress.tests.FormfieldShouldDeleteFormTests.test_custom_delete) Verify DeleteFormset ignores DELETE field and uses form method ... ok test_init_database (model_formsets_regress.tests.FormfieldShouldDeleteFormTests.test_init_database) Add test data to database via formset ... ok test_no_delete (model_formsets_regress.tests.FormfieldShouldDeleteFormTests.test_no_delete) Verify base formset doesn't modify database ... ok test_delete_already_deleted (model_formsets_regress.tests.RedeleteTests.test_delete_already_deleted) ... ok test_resubmit (model_formsets_regress.tests.RedeleteTests.test_resubmit) ... ok test_empty_fields_on_modelformset (model_formsets_regress.tests.InlineFormsetTests.test_empty_fields_on_modelformset) No fields passed to modelformset_factory() should result in no fields ... ok test_formset_over_inherited_model (model_formsets_regress.tests.InlineFormsetTests.test_formset_over_inherited_model) A formset over a ForeignKey with a to_field can be saved. Regression for #11120 ... ok test_formset_over_to_field (model_formsets_regress.tests.InlineFormsetTests.test_formset_over_to_field) A formset over a ForeignKey with a to_field can be saved. Regression for #10243 ... ok test_formset_with_none_instance (model_formsets_regress.tests.InlineFormsetTests.test_formset_with_none_instance) A formset with instance=None can be created. Regression for #11872 ... ok test_initial_data (model_formsets_regress.tests.InlineFormsetTests.test_initial_data) ... ok test_inline_model_with_primary_to_field (model_formsets_regress.tests.InlineFormsetTests.test_inline_model_with_primary_to_field) An inline model with a OneToOneField with to_field & primary key. ... ok test_inline_model_with_to_field (model_formsets_regress.tests.InlineFormsetTests.test_inline_model_with_to_field) #13794 --- An inline model with a to_field of a formset with instance ... ok test_inline_model_with_to_field_to_rel (model_formsets_regress.tests.InlineFormsetTests.test_inline_model_with_to_field_to_rel) #13794 --- An inline model with a to_field to a related field of a ... ok test_save_as_new_with_new_inlines (model_formsets_regress.tests.InlineFormsetTests.test_save_as_new_with_new_inlines) Existing and new inlines are saved with save_as_new. ... ok test_defer_baseclass_when_subclass_has_added_field (defer.tests.BigChildDeferTests.test_defer_baseclass_when_subclass_has_added_field) ... ok test_defer_subclass (defer.tests.BigChildDeferTests.test_defer_subclass) ... ok test_defer_subclass_both (defer.tests.BigChildDeferTests.test_defer_subclass_both) ... ok test_only_baseclass_when_subclass_has_added_field (defer.tests.BigChildDeferTests.test_only_baseclass_when_subclass_has_added_field) ... ok test_only_subclass (defer.tests.BigChildDeferTests.test_only_subclass) ... ok test_custom_refresh_on_deferred_loading (defer.tests.TestDefer2.test_custom_refresh_on_deferred_loading) ... ok test_defer_inheritance_pk_chaining (defer.tests.TestDefer2.test_defer_inheritance_pk_chaining) When an inherited model is fetched from the DB, its PK is also fetched. ... ok test_defer_proxy (defer.tests.TestDefer2.test_defer_proxy) Ensure select_related together with only on a proxy model behaves ... ok test_eq (defer.tests.TestDefer2.test_eq) ... ok test_refresh_not_loading_deferred_fields (defer.tests.TestDefer2.test_refresh_not_loading_deferred_fields) ... ok test_set_order (order_with_respect_to.tests.TestOrderWithRespectToOneToOnePK.test_set_order) ... ok test_change_ordering (order_with_respect_to.tests.OrderWithRespectToBaseTests.test_change_ordering) ... ok test_default_to_insertion_order (order_with_respect_to.tests.OrderWithRespectToBaseTests.test_default_to_insertion_order) ... ok test_delete_and_insert (order_with_respect_to.tests.OrderWithRespectToBaseTests.test_delete_and_insert) ... ok test_item_ordering (order_with_respect_to.tests.OrderWithRespectToBaseTests.test_item_ordering) ... ok test_previous_and_next_in_order (order_with_respect_to.tests.OrderWithRespectToBaseTests.test_previous_and_next_in_order) ... ok test_recursive_ordering (order_with_respect_to.tests.OrderWithRespectToBaseTests.test_recursive_ordering) ... ok test_set_order_unrelated_object (order_with_respect_to.tests.OrderWithRespectToBaseTests.test_set_order_unrelated_object) An answer that's not related isn't updated. ... ok test_defer (defer.tests.DeferTests.test_defer) ... ok test_defer_baseclass_when_subclass_has_no_added_fields (defer.tests.DeferTests.test_defer_baseclass_when_subclass_has_no_added_fields) ... ok test_defer_extra (defer.tests.DeferTests.test_defer_extra) ... ok test_defer_foreign_keys_are_deferred_and_not_traversed (defer.tests.DeferTests.test_defer_foreign_keys_are_deferred_and_not_traversed) ... ok test_defer_none_to_clear_deferred_set (defer.tests.DeferTests.test_defer_none_to_clear_deferred_set) ... ok test_defer_on_an_already_deferred_field (defer.tests.DeferTests.test_defer_on_an_already_deferred_field) ... ok test_defer_only_chaining (defer.tests.DeferTests.test_defer_only_chaining) ... ok test_defer_select_related_raises_invalid_query (defer.tests.DeferTests.test_defer_select_related_raises_invalid_query) ... ok test_defer_values_does_not_defer (defer.tests.DeferTests.test_defer_values_does_not_defer) ... ok test_defer_with_select_related (defer.tests.DeferTests.test_defer_with_select_related) ... ok test_get (defer.tests.DeferTests.test_get) ... ok test_only (defer.tests.DeferTests.test_only) ... ok test_only_baseclass_when_subclass_has_no_added_fields (defer.tests.DeferTests.test_only_baseclass_when_subclass_has_no_added_fields) ... ok test_only_none_raises_error (defer.tests.DeferTests.test_only_none_raises_error) ... ok test_only_select_related_raises_invalid_query (defer.tests.DeferTests.test_only_select_related_raises_invalid_query) ... ok test_only_values_does_not_defer (defer.tests.DeferTests.test_only_values_does_not_defer) ... ok test_only_with_select_related (defer.tests.DeferTests.test_only_with_select_related) ... ok test_saving_object_with_deferred_field (defer.tests.DeferTests.test_saving_object_with_deferred_field) ... ok test_generic_sitemap (sitemaps_tests.test_generic.GenericViewsSitemapTests.test_generic_sitemap) A minimal generic sitemap can be rendered ... ok test_generic_sitemap_attributes (sitemaps_tests.test_generic.GenericViewsSitemapTests.test_generic_sitemap_attributes) ... ok test_generic_sitemap_lastmod (sitemaps_tests.test_generic.GenericViewsSitemapTests.test_generic_sitemap_lastmod) ... ok test_sitemap_index_with_https_request (sitemaps_tests.test_https.HTTPSDetectionSitemapTests.test_sitemap_index_with_https_request) A sitemap index requested in HTTPS is rendered with HTTPS links ... ok test_sitemap_section_with_https_request (sitemaps_tests.test_https.HTTPSDetectionSitemapTests.test_sitemap_section_with_https_request) A sitemap section requested in HTTPS is rendered with HTTPS links ... ok test_secure_sitemap_index (sitemaps_tests.test_https.HTTPSSitemapTests.test_secure_sitemap_index) A secure sitemap index can be rendered ... ok test_secure_sitemap_section (sitemaps_tests.test_https.HTTPSSitemapTests.test_secure_sitemap_section) A secure sitemap section can be rendered ... ok test_args (sitemaps_tests.test_management.PingGoogleTests.test_args) ... ok test_default (sitemaps_tests.test_management.PingGoogleTests.test_default) ... ok test_case_insensitive (swappable_models.tests.SwappableModelTests.test_case_insensitive) Model names are case insensitive. Model swapping honors this. ... ok test_generated_data (swappable_models.tests.SwappableModelTests.test_generated_data) Permissions and content types are not created for a swapped model ... ok test_get_sitemap_full_url_exact_url (sitemaps_tests.test_utils.PingGoogleTests.test_get_sitemap_full_url_exact_url) ... ok test_get_sitemap_full_url_global (sitemaps_tests.test_utils.PingGoogleTests.test_get_sitemap_full_url_global) ... ok test_get_sitemap_full_url_index (sitemaps_tests.test_utils.PingGoogleTests.test_get_sitemap_full_url_index) ... ok test_get_sitemap_full_url_insecure (sitemaps_tests.test_utils.PingGoogleTests.test_get_sitemap_full_url_insecure) ... ok test_get_sitemap_full_url_no_sites (sitemaps_tests.test_utils.PingGoogleTests.test_get_sitemap_full_url_no_sites) ... ok test_get_sitemap_full_url_not_detected (sitemaps_tests.test_utils.PingGoogleTests.test_get_sitemap_full_url_not_detected) ... ok test_something (sitemaps_tests.test_utils.PingGoogleTests.test_something) ... ok test_available_apps (admin_views.test_adminsite.SiteEachContextTest.test_available_apps) ... ok test_each_context (admin_views.test_adminsite.SiteEachContextTest.test_each_context) ... ok test_each_context_site_url_with_script_name (admin_views.test_adminsite.SiteEachContextTest.test_each_context_site_url_with_script_name) ... ok test_alternate_i18n_sitemap_index (sitemaps_tests.test_http.HTTPSitemapTests.test_alternate_i18n_sitemap_index) A i18n sitemap with alternate/hreflang links can be rendered. ... ok test_alternate_i18n_sitemap_limited (sitemaps_tests.test_http.HTTPSitemapTests.test_alternate_i18n_sitemap_limited) A i18n sitemap index with limited languages can be rendered. ... ok test_alternate_i18n_sitemap_xdefault (sitemaps_tests.test_http.HTTPSitemapTests.test_alternate_i18n_sitemap_xdefault) A i18n sitemap index with x-default can be rendered. ... ok test_cached_sitemap_index (sitemaps_tests.test_http.HTTPSitemapTests.test_cached_sitemap_index) A cached sitemap index can be rendered (#2713). ... ok test_empty_page (sitemaps_tests.test_http.HTTPSitemapTests.test_empty_page) ... ok test_empty_sitemap (sitemaps_tests.test_http.HTTPSitemapTests.test_empty_sitemap) ... ok test_localized_priority (sitemaps_tests.test_http.HTTPSitemapTests.test_localized_priority) The priority value should not be localized. ... ok test_no_section (sitemaps_tests.test_http.HTTPSitemapTests.test_no_section) ... ok test_page_not_int (sitemaps_tests.test_http.HTTPSitemapTests.test_page_not_int) ... ok test_paged_sitemap (sitemaps_tests.test_http.HTTPSitemapTests.test_paged_sitemap) A sitemap may have multiple pages. ... ok test_requestsite_sitemap (sitemaps_tests.test_http.HTTPSitemapTests.test_requestsite_sitemap) ... ok test_simple_custom_sitemap (sitemaps_tests.test_http.HTTPSitemapTests.test_simple_custom_sitemap) A simple sitemap can be rendered with a custom template ... ok test_simple_i18n_sitemap_index (sitemaps_tests.test_http.HTTPSitemapTests.test_simple_i18n_sitemap_index) A simple i18n sitemap index can be rendered, without logging variable ... ok test_simple_sitemap (sitemaps_tests.test_http.HTTPSitemapTests.test_simple_sitemap) A simple sitemap can be rendered ... ok test_simple_sitemap_custom_index (sitemaps_tests.test_http.HTTPSitemapTests.test_simple_sitemap_custom_index) A simple sitemap index can be rendered with a custom template ... ok test_simple_sitemap_index (sitemaps_tests.test_http.HTTPSitemapTests.test_simple_sitemap_index) A simple sitemap index can be rendered ... ok test_simple_sitemap_section (sitemaps_tests.test_http.HTTPSitemapTests.test_simple_sitemap_section) A simple sitemap section can be rendered ... ok test_sitemap_get_urls_no_site_1 (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_get_urls_no_site_1) Check we get ImproperlyConfigured if we don't pass a site object to ... ok test_sitemap_get_urls_no_site_2 (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_get_urls_no_site_2) Check we get ImproperlyConfigured when we don't pass a site object to ... ok test_sitemap_item (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_item) Check to make sure that the raw item is included with each ... ok test_sitemap_last_modified (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_last_modified) Last-Modified header is set correctly ... ok test_sitemap_last_modified_date (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_last_modified_date) The Last-Modified header should be support dates (without time). ... ok test_sitemap_last_modified_missing (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_last_modified_missing) Last-Modified header is missing when sitemap has no lastmod ... ok test_sitemap_last_modified_mixed (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_last_modified_mixed) Last-Modified header is omitted when lastmod not on all items ... ok test_sitemap_last_modified_tz (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_last_modified_tz) The Last-Modified header should be converted from timezone aware dates ... ok test_sitemap_not_callable (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_not_callable) A sitemap may not be callable. ... ok test_sitemap_without_entries (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemap_without_entries) ... ok test_sitemaps_lastmod_ascending (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemaps_lastmod_ascending) The Last-Modified header is set to the most recent sitemap lastmod. ... ok test_sitemaps_lastmod_descending (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemaps_lastmod_descending) The Last-Modified header is set to the most recent sitemap lastmod. ... ok test_sitemaps_lastmod_mixed_ascending_last_modified_missing (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemaps_lastmod_mixed_ascending_last_modified_missing) The Last-Modified header is omitted when lastmod isn't found in all ... ok test_sitemaps_lastmod_mixed_descending_last_modified_missing (sitemaps_tests.test_http.HTTPSitemapTests.test_sitemaps_lastmod_mixed_descending_last_modified_missing) The Last-Modified header is omitted when lastmod isn't found in all ... ok test_x_robots_sitemap (sitemaps_tests.test_http.HTTPSitemapTests.test_x_robots_sitemap) ... ok test_inactive_user (admin_views.test_forms.AdminAuthenticationFormTests.test_inactive_user) ... ok test_custom_to_field (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_custom_to_field) ... ok test_custom_to_field_custom_pk (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_custom_to_field_custom_pk) ... ok test_custom_to_field_permission_denied (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_custom_to_field_permission_denied) ... ok test_field_does_not_allowed (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_field_does_not_allowed) ... ok test_field_does_not_exist (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_field_does_not_exist) ... ok test_field_no_related_field (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_field_no_related_field) ... ok test_get_paginator (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_get_paginator) Search results are paginated. ... ok test_has_view_or_change_permission_required (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_has_view_or_change_permission_required) Users require the change permission for the related model to the ... ok test_limit_choices_to (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_limit_choices_to) ... ok test_missing_search_fields (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_missing_search_fields) ... ok test_must_be_logged_in (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_must_be_logged_in) ... ok test_search_use_distinct (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_search_use_distinct) Searching across model relations use QuerySet.distinct() to avoid ... ok test_success (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_success) ... ok test_to_field_resolution_with_fk_pk (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_to_field_resolution_with_fk_pk) ... ok test_to_field_resolution_with_mti (admin_views.test_autocomplete_view.AutocompleteJsonViewTests.test_to_field_resolution_with_mti) to_field resolution should correctly resolve for target models using ... ok test_model_admin_no_delete_permission (admin_views.test_actions.AdminActionsPermissionTests.test_model_admin_no_delete_permission) Permission is denied if the user doesn't have delete permission for the ... ok test_model_admin_no_delete_permission_externalsubscriber (admin_views.test_actions.AdminActionsPermissionTests.test_model_admin_no_delete_permission_externalsubscriber) Permission is denied if the user doesn't have delete permission for a ... ok test_add_view (admin_views.test_multidb.MultiDatabaseTests.test_add_view) ... ok test_change_view (admin_views.test_multidb.MultiDatabaseTests.test_change_view) ... ok test_delete_view (admin_views.test_multidb.MultiDatabaseTests.test_delete_view) ... ok test_included_app_list_template_context_fully_set (admin_views.test_nav_sidebar.AdminSidebarTests.test_included_app_list_template_context_fully_set) ... ok test_sidebar_aria_current_page (admin_views.test_nav_sidebar.AdminSidebarTests.test_sidebar_aria_current_page) ... ok test_sidebar_aria_current_page_missing_without_request_context_processor (admin_views.test_nav_sidebar.AdminSidebarTests.test_sidebar_aria_current_page_missing_without_request_context_processor) ... ok test_sidebar_disabled (admin_views.test_nav_sidebar.AdminSidebarTests.test_sidebar_disabled) ... ok test_sidebar_not_on_index (admin_views.test_nav_sidebar.AdminSidebarTests.test_sidebar_not_on_index) ... ok test_sidebar_unauthenticated (admin_views.test_nav_sidebar.AdminSidebarTests.test_sidebar_unauthenticated) ... ok test_choice_links (admin_views.test_templatetags.DateHierarchyTests.test_choice_links) ... ok test_choice_links_datetime (admin_views.test_templatetags.DateHierarchyTests.test_choice_links_datetime) ... ok test_changed_message_uses_form_labels (admin_views.test_history_view.AdminHistoryViewTests.test_changed_message_uses_form_labels) Admin's model history change messages use form labels instead of ... ok test_action_column_class (admin_views.test_actions.AdminActionsTest.test_action_column_class) The checkbox column class is present in the response. ... ok test_actions_ordering (admin_views.test_actions.AdminActionsTest.test_actions_ordering) Actions are ordered as expected. ... ok test_custom_function_action_no_perm_response (admin_views.test_actions.AdminActionsTest.test_custom_function_action_no_perm_response) A custom action may returns an HttpResponse with a 403 code. ... ok test_custom_function_action_streaming_response (admin_views.test_actions.AdminActionsTest.test_custom_function_action_streaming_response) A custom action may return a StreamingHttpResponse. ... ok test_custom_function_action_with_redirect (admin_views.test_actions.AdminActionsTest.test_custom_function_action_with_redirect) Another custom action defined in a function. ... ok test_custom_function_mail_action (admin_views.test_actions.AdminActionsTest.test_custom_function_mail_action) A custom action may be defined in a function. ... ok test_default_delete_action_nonexistent_pk (admin_views.test_actions.AdminActionsTest.test_default_delete_action_nonexistent_pk) ... ok test_default_redirect (admin_views.test_actions.AdminActionsTest.test_default_redirect) Actions which don't return an HttpResponse are redirected to the same ... ok test_delete_queryset_hook (admin_views.test_actions.AdminActionsTest.test_delete_queryset_hook) ... ok test_delete_selected_uses_get_deleted_objects (admin_views.test_actions.AdminActionsTest.test_delete_selected_uses_get_deleted_objects) The delete_selected action uses ModelAdmin.get_deleted_objects(). ... ok test_media_from_actions_form (admin_views.test_actions.AdminActionsTest.test_media_from_actions_form) The action form's media is included in the changelist view's media. ... ok test_model_admin_custom_action (admin_views.test_actions.AdminActionsTest.test_model_admin_custom_action) A custom action defined in a ModelAdmin method. ... ok test_model_admin_default_delete_action (admin_views.test_actions.AdminActionsTest.test_model_admin_default_delete_action) ... ok test_model_admin_default_delete_action_no_change_url (admin_views.test_actions.AdminActionsTest.test_model_admin_default_delete_action_no_change_url) The default delete action doesn't break if a ModelAdmin removes the ... ok test_model_admin_default_delete_action_protected (admin_views.test_actions.AdminActionsTest.test_model_admin_default_delete_action_protected) The default delete action where some related objects are protected ... ok test_model_without_action (admin_views.test_actions.AdminActionsTest.test_model_without_action) A ModelAdmin might not have any actions. ... ok test_model_without_action_still_has_jquery (admin_views.test_actions.AdminActionsTest.test_model_without_action_still_has_jquery) A ModelAdmin without any actions still has jQuery included on the page. ... ok test_multiple_actions_form (admin_views.test_actions.AdminActionsTest.test_multiple_actions_form) Actions come from the form whose submit button was pressed (#10618). ... ok test_non_localized_pk (admin_views.test_actions.AdminActionsTest.test_non_localized_pk) If USE_THOUSAND_SEPARATOR is set, the ids for the objects selected for ... ok test_popup_actions (admin_views.test_actions.AdminActionsTest.test_popup_actions) Actions aren't shown in popups. ... ok test_popup_template_escaping (admin_views.test_actions.AdminActionsTest.test_popup_template_escaping) ... ok test_popup_template_response_on_add (admin_views.test_actions.AdminActionsTest.test_popup_template_response_on_add) Success on popups shall be rendered from template in order to allow ... ok test_popup_template_response_on_change (admin_views.test_actions.AdminActionsTest.test_popup_template_response_on_change) ... ok test_popup_template_response_on_delete (admin_views.test_actions.AdminActionsTest.test_popup_template_response_on_delete) ... ok test_selection_counter (admin_views.test_actions.AdminActionsTest.test_selection_counter) The selection counter is there. ... ok test_user_message_on_no_action (admin_views.test_actions.AdminActionsTest.test_user_message_on_no_action) User sees a warning when 'Go' is pressed and no action is selected. ... ok test_user_message_on_none_selected (admin_views.test_actions.AdminActionsTest.test_user_message_on_none_selected) User sees a warning when 'Go' is pressed and no items are selected. ... ok test_should_be_able_to_edit_related_objects_on_add_view (admin_views.tests.AdminCustomSaveRelatedTests.test_should_be_able_to_edit_related_objects_on_add_view) ... ok test_should_be_able_to_edit_related_objects_on_change_view (admin_views.tests.AdminCustomSaveRelatedTests.test_should_be_able_to_edit_related_objects_on_change_view) ... ok test_should_be_able_to_edit_related_objects_on_changelist_view (admin_views.tests.AdminCustomSaveRelatedTests.test_should_be_able_to_edit_related_objects_on_changelist_view) ... ok test_override_change_form_template_tags (admin_views.test_templatetags.AdminTemplateTagsTest.test_override_change_form_template_tags) admin_modify template tags follow the standard search pattern ... ok test_override_change_list_template_tags (admin_views.test_templatetags.AdminTemplateTagsTest.test_override_change_list_template_tags) admin_list template tags follow the standard search pattern ... ok test_override_show_save_and_add_another (admin_views.test_templatetags.AdminTemplateTagsTest.test_override_show_save_and_add_another) ... ok test_submit_row (admin_views.test_templatetags.AdminTemplateTagsTest.test_submit_row) submit_row template tag should pass whole context. ... ok test_inline (admin_views.tests.AdminInheritedInlinesTest.test_inline) Inline models which inherit from a common parent are correctly handled. ... ok test_add_model_modeladmin_defer_qs (admin_views.tests.AdminCustomQuerysetTest.test_add_model_modeladmin_defer_qs) ... ok test_add_model_modeladmin_only_qs (admin_views.tests.AdminCustomQuerysetTest.test_add_model_modeladmin_only_qs) ... ok test_change_view (admin_views.tests.AdminCustomQuerysetTest.test_change_view) ... ok test_changelist_view (admin_views.tests.AdminCustomQuerysetTest.test_changelist_view) ... ok test_changelist_view_count_queries (admin_views.tests.AdminCustomQuerysetTest.test_changelist_view_count_queries) ... ok test_edit_model_modeladmin_defer_qs (admin_views.tests.AdminCustomQuerysetTest.test_edit_model_modeladmin_defer_qs) ... ok test_edit_model_modeladmin_only_qs (admin_views.tests.AdminCustomQuerysetTest.test_edit_model_modeladmin_only_qs) ... ok test_history_view_custom_qs (admin_views.tests.AdminCustomQuerysetTest.test_history_view_custom_qs) Custom querysets are considered for the admin history view. ... ok test_form_has_multipart_enctype (admin_views.tests.AdminInlineFileUploadTest.test_form_has_multipart_enctype) ... ok test_inline_file_upload_edit_validation_error_post (admin_views.tests.AdminInlineFileUploadTest.test_inline_file_upload_edit_validation_error_post) Inline file uploads correctly display prior data (#10002). ... ok test_change_password_template (admin_views.tests.AdminCustomTemplateTests.test_change_password_template) ... ok test_custom_model_admin_templates (admin_views.tests.AdminCustomTemplateTests.test_custom_model_admin_templates) ... ok test_extended_bodyclass_change_list (admin_views.tests.AdminCustomTemplateTests.test_extended_bodyclass_change_list) The admin/change_list.html' template uses block.super ... ok test_extended_bodyclass_template_change_form (admin_views.tests.AdminCustomTemplateTests.test_extended_bodyclass_template_change_form) The admin/change_form.html template uses block.super in the ... ok test_extended_bodyclass_template_delete_confirmation (admin_views.tests.AdminCustomTemplateTests.test_extended_bodyclass_template_delete_confirmation) The admin/delete_confirmation.html template uses ... ok test_extended_bodyclass_template_delete_selected_confirmation (admin_views.tests.AdminCustomTemplateTests.test_extended_bodyclass_template_delete_selected_confirmation) The admin/delete_selected_confirmation.html template uses ... ok test_extended_bodyclass_template_index (admin_views.tests.AdminCustomTemplateTests.test_extended_bodyclass_template_index) The admin/index.html template uses block.super in the bodyclass block. ... ok test_extended_bodyclass_template_login (admin_views.tests.AdminCustomTemplateTests.test_extended_bodyclass_template_login) The admin/login.html template uses block.super in the ... ok test_filter_with_custom_template (admin_views.tests.AdminCustomTemplateTests.test_filter_with_custom_template) A custom template can be used to render an admin filter. ... ok test_js_minified_only_if_debug_is_false (admin_views.tests.AdminJavaScriptTest.test_js_minified_only_if_debug_is_false) The minified versions of the JS files are only used when DEBUG is False. ... ok test_filters (admin_views.tests.AdminDocsTest.test_filters) ... ok test_tags (admin_views.tests.AdminDocsTest.test_tags) ... ok test_char_pk_inline (admin_views.tests.AdminInlineTests.test_char_pk_inline) A model with a character PK can be saved as inlines. Regression for #10992 ... ok test_explicit_autofield_inline (admin_views.tests.AdminInlineTests.test_explicit_autofield_inline) A model with an explicit autofield primary key can be saved as inlines. Regression for #8093 ... ok test_inherited_inline (admin_views.tests.AdminInlineTests.test_inherited_inline) An inherited model can be saved as inlines. Regression for #11042 ... ok test_integer_pk_inline (admin_views.tests.AdminInlineTests.test_integer_pk_inline) A model with an integer PK can be saved as inlines. Regression for #10992 ... ok test_ordered_inline (admin_views.tests.AdminInlineTests.test_ordered_inline) An inline with an editable ordering fields is updated correctly. ... ok test_simple_inline (admin_views.tests.AdminInlineTests.test_simple_inline) A simple model can be saved as inlines ... ok test_known_url_missing_slash_redirects_login_if_not_authenticated (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_known_url_missing_slash_redirects_login_if_not_authenticated) ... ok test_known_url_missing_slash_redirects_with_slash_if_not_authenticated_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_known_url_missing_slash_redirects_with_slash_if_not_authenticated_without_final_catch_all_view) ... ok test_known_url_redirects_login_if_not_authenticated (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_known_url_redirects_login_if_not_authenticated) ... ok test_known_url_redirects_login_if_not_authenticated_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_known_url_redirects_login_if_not_authenticated_without_final_catch_all_view) ... ok test_missing_slash_append_slash_false (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_false) ... ok test_missing_slash_append_slash_false_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_false_without_final_catch_all_view) ... ok test_missing_slash_append_slash_true (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_true) ... ok test_missing_slash_append_slash_true_force_script_name (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_true_force_script_name) ... ok test_missing_slash_append_slash_true_non_staff_user (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_true_non_staff_user) ... ok test_missing_slash_append_slash_true_script_name (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_true_script_name) ... ok test_missing_slash_append_slash_true_unknown_url (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_true_unknown_url) ... ok test_missing_slash_append_slash_true_unknown_url_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_true_unknown_url_without_final_catch_all_view) ... ok test_missing_slash_append_slash_true_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_missing_slash_append_slash_true_without_final_catch_all_view) ... ok test_non_admin_url_404_if_not_authenticated (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_non_admin_url_404_if_not_authenticated) ... ok test_non_admin_url_shares_url_prefix (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_non_admin_url_shares_url_prefix) ... ok test_non_admin_url_shares_url_prefix_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_non_admin_url_shares_url_prefix_without_final_catch_all_view) ... ok test_single_model_no_append_slash (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_single_model_no_append_slash) ... ok test_unknown_url_404_if_authenticated (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_unknown_url_404_if_authenticated) ... ok test_unknown_url_404_if_authenticated_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_unknown_url_404_if_authenticated_without_final_catch_all_view) ... ok test_unknown_url_404_if_not_authenticated_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_unknown_url_404_if_not_authenticated_without_final_catch_all_view) ... ok test_unknown_url_redirects_login_if_not_authenticated (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_unknown_url_redirects_login_if_not_authenticated) ... ok test_unkown_url_without_trailing_slash_if_not_authenticated (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_unkown_url_without_trailing_slash_if_not_authenticated) ... ok test_unkown_url_without_trailing_slash_if_not_authenticated_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_unkown_url_without_trailing_slash_if_not_authenticated_without_final_catch_all_view) ... ok test_url_without_trailing_slash_if_not_authenticated (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_url_without_trailing_slash_if_not_authenticated) ... ok test_url_without_trailing_slash_if_not_authenticated_without_final_catch_all_view (admin_views.tests.AdminSiteFinalCatchAllPatternTests.test_url_without_trailing_slash_if_not_authenticated_without_final_catch_all_view) ... ok test_message_debug (admin_views.tests.AdminUserMessageTest.test_message_debug) ... ok test_message_error (admin_views.tests.AdminUserMessageTest.test_message_error) ... ok test_message_extra_tags (admin_views.tests.AdminUserMessageTest.test_message_extra_tags) ... ok test_message_info (admin_views.tests.AdminUserMessageTest.test_message_info) ... ok test_message_success (admin_views.tests.AdminUserMessageTest.test_message_success) ... ok test_message_warning (admin_views.tests.AdminUserMessageTest.test_message_warning) ... ok test_beginning_matches (admin_views.tests.AdminSearchTest.test_beginning_matches) ... ok test_exact_matches (admin_views.tests.AdminSearchTest.test_exact_matches) ... ok test_no_total_count (admin_views.tests.AdminSearchTest.test_no_total_count) #8408 -- "Show all" should be displayed instead of the total count if ... ok test_pluggable_search (admin_views.tests.AdminSearchTest.test_pluggable_search) ... ok test_reset_link (admin_views.tests.AdminSearchTest.test_reset_link) Test presence of reset link in search bar ("1 result (_x total_)"). ... ok test_search_on_sibling_models (admin_views.tests.AdminSearchTest.test_search_on_sibling_models) A search that mentions sibling models ... ok test_search_with_spaces (admin_views.tests.AdminSearchTest.test_search_with_spaces) ... ok test_with_fk_to_field (admin_views.tests.AdminSearchTest.test_with_fk_to_field) The to_field GET parameter is preserved when a search is performed. ... ok test_change_form_URL_has_correct_value (admin_views.tests.AdminViewFormUrlTest.test_change_form_URL_has_correct_value) change_view has form_url in response.context ... ok test_initial_data_can_be_overridden (admin_views.tests.AdminViewFormUrlTest.test_initial_data_can_be_overridden) The behavior for setting initial form data can be overridden in the ... ok test_cyclic (admin_views.tests.AdminViewDeletedObjectsTest.test_cyclic) Cyclic relationships should still cause each object to only be ... ok test_delete_view_uses_get_deleted_objects (admin_views.tests.AdminViewDeletedObjectsTest.test_delete_view_uses_get_deleted_objects) The delete view uses ModelAdmin.get_deleted_objects(). ... ok test_generic_relations (admin_views.tests.AdminViewDeletedObjectsTest.test_generic_relations) If a deleted object has GenericForeignKeys pointing to it, ... ok test_generic_relations_with_related_query_name (admin_views.tests.AdminViewDeletedObjectsTest.test_generic_relations_with_related_query_name) If a deleted object has GenericForeignKey with ... ok test_inheritance (admin_views.tests.AdminViewDeletedObjectsTest.test_inheritance) In the case of an inherited model, if either the child or ... ok test_multiple_fkeys_to_same_instance (admin_views.tests.AdminViewDeletedObjectsTest.test_multiple_fkeys_to_same_instance) If a deleted object has two relationships pointing to it from ... ok test_multiple_fkeys_to_same_model (admin_views.tests.AdminViewDeletedObjectsTest.test_multiple_fkeys_to_same_model) If a deleted object has two relationships from another model, ... ok test_nesting (admin_views.tests.AdminViewDeletedObjectsTest.test_nesting) Objects should be nested to display the relationships that ... ok test_not_registered (admin_views.tests.AdminViewDeletedObjectsTest.test_not_registered) ... ok test_perms_needed (admin_views.tests.AdminViewDeletedObjectsTest.test_perms_needed) ... ok test_post_delete_protected (admin_views.tests.AdminViewDeletedObjectsTest.test_post_delete_protected) A POST request to delete protected objects should display the page ... ok test_post_delete_restricted (admin_views.tests.AdminViewDeletedObjectsTest.test_post_delete_restricted) ... ok test_protected (admin_views.tests.AdminViewDeletedObjectsTest.test_protected) ... ok test_restricted (admin_views.tests.AdminViewDeletedObjectsTest.test_restricted) ... ok test_client_logout_url_can_be_used_to_login (admin_views.tests.AdminViewLogoutTests.test_client_logout_url_can_be_used_to_login) ... ok test_logout (admin_views.tests.AdminViewLogoutTests.test_logout) ... ok test_changelist_input_html (admin_views.tests.AdminViewListEditable.test_changelist_input_html) ... ok test_custom_pk (admin_views.tests.AdminViewListEditable.test_custom_pk) ... ok test_inheritance (admin_views.tests.AdminViewListEditable.test_inheritance) ... ok test_inheritance_2 (admin_views.tests.AdminViewListEditable.test_inheritance_2) ... ok test_list_editable_action_choices (admin_views.tests.AdminViewListEditable.test_list_editable_action_choices) ... ok test_list_editable_action_submit (admin_views.tests.AdminViewListEditable.test_list_editable_action_submit) ... ok test_list_editable_ordering (admin_views.tests.AdminViewListEditable.test_list_editable_ordering) ... ok test_list_editable_pagination (admin_views.tests.AdminViewListEditable.test_list_editable_pagination) Pagination works for list_editable items. ... ok test_list_editable_popup (admin_views.tests.AdminViewListEditable.test_list_editable_popup) Fields should not be list-editable in popups. ... ok test_non_field_errors (admin_views.tests.AdminViewListEditable.test_non_field_errors) Non-field errors are displayed for each of the forms in the ... ok test_non_form_errors (admin_views.tests.AdminViewListEditable.test_non_form_errors) ... ok test_non_form_errors_is_errorlist (admin_views.tests.AdminViewListEditable.test_non_form_errors_is_errorlist) ... ok test_pk_hidden_fields (admin_views.tests.AdminViewListEditable.test_pk_hidden_fields) hidden pk fields aren't displayed in the table body and their ... ok test_pk_hidden_fields_with_list_display_links (admin_views.tests.AdminViewListEditable.test_pk_hidden_fields_with_list_display_links) Similarly as test_pk_hidden_fields, but when the hidden pk fields are ... ok test_post_messages (admin_views.tests.AdminViewListEditable.test_post_messages) ... ok test_post_submission (admin_views.tests.AdminViewListEditable.test_post_submission) ... ok test_add_view_form_and_formsets_run_validation (admin_views.tests.AdminViewOnSiteTests.test_add_view_form_and_formsets_run_validation) Issue #20522 ... ok test_callable (admin_views.tests.AdminViewOnSiteTests.test_callable) The right link is displayed if view_on_site is a callable ... ok test_change_view_form_and_formsets_run_validation (admin_views.tests.AdminViewOnSiteTests.test_change_view_form_and_formsets_run_validation) Issue #20522 ... ok test_check (admin_views.tests.AdminViewOnSiteTests.test_check) The view_on_site value is either a boolean or a callable ... ok test_false (admin_views.tests.AdminViewOnSiteTests.test_false) The 'View on site' button is not displayed if view_on_site is False ... ok test_missing_get_absolute_url (admin_views.tests.AdminViewOnSiteTests.test_missing_get_absolute_url) None is returned if model doesn't have get_absolute_url ... ok test_true (admin_views.tests.AdminViewOnSiteTests.test_true) The default behavior is followed if view_on_site is True ... ok test_add (admin_views.tests.AdminViewProxyModelPermissionsTests.test_add) ... ok test_change (admin_views.tests.AdminViewProxyModelPermissionsTests.test_change) ... ok test_delete (admin_views.tests.AdminViewProxyModelPermissionsTests.test_delete) ... ok test_view (admin_views.tests.AdminViewProxyModelPermissionsTests.test_view) ... ok test_change_view_history_link (admin_views.tests.AdminViewStringPrimaryKeyTest.test_change_view_history_link) Object history button link should work and contain the pk value quoted. ... ok test_changelist_to_changeform_link (admin_views.tests.AdminViewStringPrimaryKeyTest.test_changelist_to_changeform_link) Link to the changeform of the object in changelist should use reverse() and be quoted -- #18072 ... ok test_deleteconfirmation_link (admin_views.tests.AdminViewStringPrimaryKeyTest.test_deleteconfirmation_link) The link from the delete confirmation page referring back to the changeform of the object should be quoted ... ok test_get_change_view (admin_views.tests.AdminViewStringPrimaryKeyTest.test_get_change_view) Retrieving the object using urlencoded form of primary key should work ... ok test_get_history_view (admin_views.tests.AdminViewStringPrimaryKeyTest.test_get_history_view) Retrieving the history for an object using urlencoded form of primary ... ok test_recentactions_link (admin_views.tests.AdminViewStringPrimaryKeyTest.test_recentactions_link) The link from the recent actions list referring to the changeform of the object should be quoted ... ok test_redirect_on_add_view_continue_button (admin_views.tests.AdminViewStringPrimaryKeyTest.test_redirect_on_add_view_continue_button) As soon as an object is added using "Save and continue editing" ... ok test_shortcut_view_with_escaping (admin_views.tests.AdminViewStringPrimaryKeyTest.test_shortcut_view_with_escaping) 'View on site should' work properly with char fields ... ok test_url_conflicts_with_add (admin_views.tests.AdminViewStringPrimaryKeyTest.test_url_conflicts_with_add) A model with a primary key that ends with add or is `add` should be visible ... ok test_url_conflicts_with_delete (admin_views.tests.AdminViewStringPrimaryKeyTest.test_url_conflicts_with_delete) A model with a primary key that ends with delete should be visible ... ok test_url_conflicts_with_history (admin_views.tests.AdminViewStringPrimaryKeyTest.test_url_conflicts_with_history) A model with a primary key that ends with history should be visible ... ok test_unicode_delete (admin_views.tests.AdminViewUnicodeTest.test_unicode_delete) The delete_view handles non-ASCII characters ... ok test_unicode_edit (admin_views.tests.AdminViewUnicodeTest.test_unicode_edit) A test to ensure that POST on edit_view handles non-ASCII characters. ... ok test_no_standard_modeladmin_urls (admin_views.tests.AdminViewsNoUrlTest.test_no_standard_modeladmin_urls) Admin index views don't break when user's ModelAdmin removes standard urls ... ok test_add_view (admin_views.tests.AdminViewPermissionsTest.test_add_view) Test add view restricts access and actually adds items. ... ok test_add_view_with_view_only_inlines (admin_views.tests.AdminViewPermissionsTest.test_add_view_with_view_only_inlines) User with add permission to a section but view-only for inlines. ... ok test_app_list_permissions (admin_views.tests.AdminViewPermissionsTest.test_app_list_permissions) If a user has no module perms, the app list returns a 404. ... ok test_change_view (admin_views.tests.AdminViewPermissionsTest.test_change_view) Change view should restrict access and allow users to edit items. ... ok test_change_view_save_as_new (admin_views.tests.AdminViewPermissionsTest.test_change_view_save_as_new) 'Save as new' should raise PermissionDenied for users without the 'add' ... ok test_change_view_with_view_and_add_inlines (admin_views.tests.AdminViewPermissionsTest.test_change_view_with_view_and_add_inlines) User has view and add permissions on the inline model. ... ok test_change_view_with_view_and_delete_inlines (admin_views.tests.AdminViewPermissionsTest.test_change_view_with_view_and_delete_inlines) User has view and delete permissions on the inline model. ... ok test_change_view_with_view_only_inlines (admin_views.tests.AdminViewPermissionsTest.test_change_view_with_view_only_inlines) User with change permission to a section but view-only for inlines. ... ok test_change_view_without_object_change_permission (admin_views.tests.AdminViewPermissionsTest.test_change_view_without_object_change_permission) The object should be read-only if the user has permission to view it ... ok test_conditionally_show_add_section_link (admin_views.tests.AdminViewPermissionsTest.test_conditionally_show_add_section_link) The foreign key widget should only show the "add related" button if the ... ok test_conditionally_show_change_section_link (admin_views.tests.AdminViewPermissionsTest.test_conditionally_show_change_section_link) The foreign key widget should only show the "change related" button if ... ok test_conditionally_show_delete_section_link (admin_views.tests.AdminViewPermissionsTest.test_conditionally_show_delete_section_link) The foreign key widget should only show the "delete related" button if ... ok test_delete_view (admin_views.tests.AdminViewPermissionsTest.test_delete_view) Delete view should restrict access and actually delete items. ... ok test_delete_view_nonexistent_obj (admin_views.tests.AdminViewPermissionsTest.test_delete_view_nonexistent_obj) ... ok test_delete_view_with_no_default_permissions (admin_views.tests.AdminViewPermissionsTest.test_delete_view_with_no_default_permissions) The delete view allows users to delete collected objects without a ... ok test_disabled_permissions_when_logged_in (admin_views.tests.AdminViewPermissionsTest.test_disabled_permissions_when_logged_in) ... ok test_disabled_staff_permissions_when_logged_in (admin_views.tests.AdminViewPermissionsTest.test_disabled_staff_permissions_when_logged_in) ... ok test_double_login_is_not_allowed (admin_views.tests.AdminViewPermissionsTest.test_double_login_is_not_allowed) Regression test for #19327 ... ok test_has_module_permission (admin_views.tests.AdminViewPermissionsTest.test_has_module_permission) has_module_permission() returns True for all users who ... ok test_history_view (admin_views.tests.AdminViewPermissionsTest.test_history_view) History view should restrict access. ... ok test_history_view_bad_url (admin_views.tests.AdminViewPermissionsTest.test_history_view_bad_url) ... ok test_login (admin_views.tests.AdminViewPermissionsTest.test_login) Make sure only staff members can log in. ... ok test_login_has_permission (admin_views.tests.AdminViewPermissionsTest.test_login_has_permission) ... ok test_login_page_notice_for_non_staff_users (admin_views.tests.AdminViewPermissionsTest.test_login_page_notice_for_non_staff_users) A logged-in non-staff user trying to access the admin index should be ... ok test_login_redirect_for_direct_get (admin_views.tests.AdminViewPermissionsTest.test_login_redirect_for_direct_get) Login redirect should be to the admin index page when going directly to ... ok test_login_successfully_redirects_to_original_URL (admin_views.tests.AdminViewPermissionsTest.test_login_successfully_redirects_to_original_URL) ... ok test_overriding_has_module_permission (admin_views.tests.AdminViewPermissionsTest.test_overriding_has_module_permission) If has_module_permission() always returns False, the module shouldn't ... ok test_post_save_message_no_forbidden_links_visible (admin_views.tests.AdminViewPermissionsTest.test_post_save_message_no_forbidden_links_visible) Post-save message shouldn't contain a link to the change form if the ... ok test_shortcut_view_only_available_to_staff (admin_views.tests.AdminViewPermissionsTest.test_shortcut_view_only_available_to_staff) Only admin users should be able to use the admin shortcut view. ... ok test_add_view (admin_views.tests.AdminKeepChangeListFiltersTests.test_add_view) ... ok test_add_view_without_preserved_filters (admin_views.tests.AdminKeepChangeListFiltersTests.test_add_view_without_preserved_filters) ... ok test_assert_url_equal (admin_views.tests.AdminKeepChangeListFiltersTests.test_assert_url_equal) ... ok test_change_view (admin_views.tests.AdminKeepChangeListFiltersTests.test_change_view) ... ok test_change_view_without_preserved_filters (admin_views.tests.AdminKeepChangeListFiltersTests.test_change_view_without_preserved_filters) ... ok test_changelist_view (admin_views.tests.AdminKeepChangeListFiltersTests.test_changelist_view) ... ok test_delete_view (admin_views.tests.AdminKeepChangeListFiltersTests.test_delete_view) ... ok test_url_prefix (admin_views.tests.AdminKeepChangeListFiltersTests.test_url_prefix) ... ok test_app_model_in_app_index_body_class (admin_views.tests.CSSTest.test_app_model_in_app_index_body_class) Ensure app and model tag are correctly read by app_index template ... ok test_app_model_in_delete_confirmation_body_class (admin_views.tests.CSSTest.test_app_model_in_delete_confirmation_body_class) Ensure app and model tag are correctly read by delete_confirmation ... ok test_app_model_in_delete_selected_confirmation_body_class (admin_views.tests.CSSTest.test_app_model_in_delete_selected_confirmation_body_class) Ensure app and model tag are correctly read by ... ok test_app_model_in_form_body_class (admin_views.tests.CSSTest.test_app_model_in_form_body_class) Ensure app and model tag are correctly read by change_form template ... ok test_app_model_in_list_body_class (admin_views.tests.CSSTest.test_app_model_in_list_body_class) Ensure app and model tag are correctly read by change_list template ... ok test_changelist_field_classes (admin_views.tests.CSSTest.test_changelist_field_classes) Cells of the change list table should contain the field name in their class attribute ... ok test_field_prefix_css_classes (admin_views.tests.CSSTest.test_field_prefix_css_classes) Fields have a CSS class name with a 'field-' prefix. ... ok test_index_css_classes (admin_views.tests.CSSTest.test_index_css_classes) CSS class names are used for each app and model on the admin index ... ok test_explicitly_provided_pk (admin_views.tests.GetFormsetsWithInlinesArgumentTest.test_explicitly_provided_pk) ... ok test_implicitly_generated_pk (admin_views.tests.GetFormsetsWithInlinesArgumentTest.test_implicitly_generated_pk) ... ok test_custom_admin_site_app_index_view_and_template (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_app_index_view_and_template) ... ok test_custom_admin_site_index_view_and_template (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_index_view_and_template) ... ok test_custom_admin_site_login_form (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_login_form) ... ok test_custom_admin_site_login_template (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_login_template) ... ok test_custom_admin_site_logout_template (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_logout_template) ... ok test_custom_admin_site_password_change_done_template (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_password_change_done_template) ... ok test_custom_admin_site_password_change_template (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_password_change_template) ... ok test_custom_admin_site_password_change_with_extra_context (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_password_change_with_extra_context) ... ok test_custom_admin_site_view (admin_views.tests.CustomModelAdminTest.test_custom_admin_site_view) ... ok test_pwd_change_custom_template (admin_views.tests.CustomModelAdminTest.test_pwd_change_custom_template) ... ok test_L10N_deactivated (admin_views.tests.AdminViewBasicTest.test_L10N_deactivated) Check if L10N is deactivated, the JavaScript i18n view doesn't ... ok test_add_with_GET_args (admin_views.tests.AdminViewBasicTest.test_add_with_GET_args) ... ok test_adminsite_display_site_url (admin_views.tests.AdminViewBasicTest.test_adminsite_display_site_url) #13749 - Admin should display link to front-end site 'View site' ... ok test_allowed_filtering_15103 (admin_views.tests.AdminViewBasicTest.test_allowed_filtering_15103) Regressions test for ticket 15103 - filtering on fields defined in a ... ok test_allows_attributeerror_to_bubble_up (admin_views.tests.AdminViewBasicTest.test_allows_attributeerror_to_bubble_up) AttributeErrors are allowed to bubble when raised inside a change list ... ok test_app_index_context (admin_views.tests.AdminViewBasicTest.test_app_index_context) ... ok test_basic_add_GET (admin_views.tests.AdminViewBasicTest.test_basic_add_GET) A smoke test to ensure GET on the add_view works. ... ok test_basic_add_POST (admin_views.tests.AdminViewBasicTest.test_basic_add_POST) A smoke test to ensure POST on add_view works. ... ok test_basic_edit_GET (admin_views.tests.AdminViewBasicTest.test_basic_edit_GET) A smoke test to ensure GET on the change_view works. ... ok test_basic_edit_GET_old_url_redirect (admin_views.tests.AdminViewBasicTest.test_basic_edit_GET_old_url_redirect) The change URL changed in Django 1.9, but the old one still redirects. ... ok test_basic_edit_GET_string_PK (admin_views.tests.AdminViewBasicTest.test_basic_edit_GET_string_PK) GET on the change_view (when passing a string as the PK argument for a ... ok test_basic_edit_POST (admin_views.tests.AdminViewBasicTest.test_basic_edit_POST) A smoke test to ensure POST on edit_view works. ... ok test_basic_inheritance_GET_string_PK (admin_views.tests.AdminViewBasicTest.test_basic_inheritance_GET_string_PK) GET on the change_view (for inherited models) redirects to the index ... ok test_change_list_column_field_classes (admin_views.tests.AdminViewBasicTest.test_change_list_column_field_classes) ... ok test_change_list_null_boolean_display (admin_views.tests.AdminViewBasicTest.test_change_list_null_boolean_display) ... ok test_change_list_sorting_callable (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_callable) Ensure we can sort on a list_display field that is a callable ... ok test_change_list_sorting_callable_query_expression (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_callable_query_expression) Query expressions may be used for admin_order_field. ... ok test_change_list_sorting_callable_query_expression_reverse (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_callable_query_expression_reverse) ... ok test_change_list_sorting_model (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_model) Ensure we can sort on a list_display field that is a Model method ... ok test_change_list_sorting_model_admin (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_model_admin) Ensure we can sort on a list_display field that is a ModelAdmin method ... ok test_change_list_sorting_model_admin_reverse (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_model_admin_reverse) Ensure we can sort on a list_display field that is a ModelAdmin ... ok test_change_list_sorting_model_meta (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_model_meta) ... ok test_change_list_sorting_multiple (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_multiple) ... ok test_change_list_sorting_override_model_admin (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_override_model_admin) ... ok test_change_list_sorting_preserve_queryset_ordering (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_preserve_queryset_ordering) If no ordering is defined in `ModelAdmin.ordering` or in the query ... ok test_change_list_sorting_property (admin_views.tests.AdminViewBasicTest.test_change_list_sorting_property) Sort on a list_display field that is a property (column 10 is ... ok test_change_view_logs_m2m_field_changes (admin_views.tests.AdminViewBasicTest.test_change_view_logs_m2m_field_changes) Changes to ManyToManyFields are included in the object's history. ... ok test_change_view_subtitle_per_object (admin_views.tests.AdminViewBasicTest.test_change_view_subtitle_per_object) ... ok test_change_view_with_show_delete_extra_context (admin_views.tests.AdminViewBasicTest.test_change_view_with_show_delete_extra_context) The 'show_delete' context variable in the admin's change view controls ... ok test_changelist_with_no_change_url (admin_views.tests.AdminViewBasicTest.test_changelist_with_no_change_url) ModelAdmin.changelist_view shouldn't result in a NoReverseMatch if url ... ok test_date_hierarchy_empty_queryset (admin_views.tests.AdminViewBasicTest.test_date_hierarchy_empty_queryset) ... ok test_date_hierarchy_local_date_differ_from_utc (admin_views.tests.AdminViewBasicTest.test_date_hierarchy_local_date_differ_from_utc) ... ok test_date_hierarchy_timezone_dst (admin_views.tests.AdminViewBasicTest.test_date_hierarchy_timezone_dst) ... ok test_disallowed_filtering (admin_views.tests.AdminViewBasicTest.test_disallowed_filtering) ... ok test_disallowed_to_field (admin_views.tests.AdminViewBasicTest.test_disallowed_to_field) ... ok test_display_decorator_with_boolean_and_empty_value (admin_views.tests.AdminViewBasicTest.test_display_decorator_with_boolean_and_empty_value) ... ok test_edit_save_as (admin_views.tests.AdminViewBasicTest.test_edit_save_as) Test "save as". ... ok test_edit_save_as_delete_inline (admin_views.tests.AdminViewBasicTest.test_edit_save_as_delete_inline) Should be able to "Save as new" while also deleting an inline. ... ok test_get_sortable_by_columns_subset (admin_views.tests.AdminViewBasicTest.test_get_sortable_by_columns_subset) ... ok test_get_sortable_by_no_column (admin_views.tests.AdminViewBasicTest.test_get_sortable_by_no_column) ... ok test_has_related_field_in_list_display_fk (admin_views.tests.AdminViewBasicTest.test_has_related_field_in_list_display_fk) Joins shouldn't be performed for _id fields in list display. ... ok test_has_related_field_in_list_display_o2o (admin_views.tests.AdminViewBasicTest.test_has_related_field_in_list_display_o2o) Joins shouldn't be performed for _id fields in list display. ... ok test_hide_change_password (admin_views.tests.AdminViewBasicTest.test_hide_change_password) Tests if the "change password" link in the admin is hidden if the User ... ok test_i18n_language_non_english_default (admin_views.tests.AdminViewBasicTest.test_i18n_language_non_english_default) Check if the JavaScript i18n view returns an empty language catalog ... ok test_i18n_language_non_english_fallback (admin_views.tests.AdminViewBasicTest.test_i18n_language_non_english_fallback) Makes sure that the fallback language is still working properly ... ok test_incorrect_lookup_parameters (admin_views.tests.AdminViewBasicTest.test_incorrect_lookup_parameters) Ensure incorrect lookup parameters are handled gracefully. ... ok test_invalid_appindex_url (admin_views.tests.AdminViewBasicTest.test_invalid_appindex_url) #21056 -- URL reversing shouldn't work for nonexistent apps. ... ok test_isnull_lookups (admin_views.tests.AdminViewBasicTest.test_isnull_lookups) Ensure is_null is handled correctly. ... ok test_jsi18n_with_context (admin_views.tests.AdminViewBasicTest.test_jsi18n_with_context) ... ok test_limited_filter (admin_views.tests.AdminViewBasicTest.test_limited_filter) Ensure admin changelist filters do not contain objects excluded via limit_choices_to. ... ok test_logout_and_password_change_URLs (admin_views.tests.AdminViewBasicTest.test_logout_and_password_change_URLs) ... ok test_multiple_sort_same_field (admin_views.tests.AdminViewBasicTest.test_multiple_sort_same_field) ... ok test_named_group_field_choices_change_list (admin_views.tests.AdminViewBasicTest.test_named_group_field_choices_change_list) Ensures the admin changelist shows correct values in the relevant column ... ok test_named_group_field_choices_filter (admin_views.tests.AdminViewBasicTest.test_named_group_field_choices_filter) Ensures the filter UI shows correctly when at least one named group has ... ok test_popup_add_POST (admin_views.tests.AdminViewBasicTest.test_popup_add_POST) Ensure http response from a popup is properly escaped. ... ok test_popup_dismiss_related (admin_views.tests.AdminViewBasicTest.test_popup_dismiss_related) Regression test for ticket 20664 - ensure the pk is properly quoted. ... ok test_relation_spanning_filters (admin_views.tests.AdminViewBasicTest.test_relation_spanning_filters) ... ok test_render_views_no_subtitle (admin_views.tests.AdminViewBasicTest.test_render_views_no_subtitle) ... ok test_resolve_admin_views (admin_views.tests.AdminViewBasicTest.test_resolve_admin_views) ... ok test_sort_indicators_admin_order (admin_views.tests.AdminViewBasicTest.test_sort_indicators_admin_order) The admin shows default sort indicators for all kinds of 'ordering' ... ok test_sortable_by_columns_subset (admin_views.tests.AdminViewBasicTest.test_sortable_by_columns_subset) ... ok test_sortable_by_no_column (admin_views.tests.AdminViewBasicTest.test_sortable_by_no_column) ... ok test_trailing_slash_required (admin_views.tests.AdminViewBasicTest.test_trailing_slash_required) If you leave off the trailing slash, app should redirect and add it. ... ok test_view_subtitle_per_object (admin_views.tests.AdminViewBasicTest.test_view_subtitle_per_object) ... ok test_limit_choices_to_as_callable (admin_views.tests.LimitChoicesToInAdminTest.test_limit_choices_to_as_callable) Test for ticket 2445 changes to admin. ... ok test_callable (admin_views.tests.InlineAdminViewOnSiteTest.test_callable) The right link is displayed if view_on_site is a callable ... ok test_false (admin_views.tests.InlineAdminViewOnSiteTest.test_false) The 'View on site' button is not displayed if view_on_site is False ... ok test_true (admin_views.tests.InlineAdminViewOnSiteTest.test_true) The 'View on site' button is displayed if view_on_site is True ... ok test_empty (admin_views.tests.DateHierarchyTests.test_empty) No date hierarchy links display with empty changelist. ... ok test_multiple_years (admin_views.tests.DateHierarchyTests.test_multiple_years) year-level links appear for year-spanning changelist. ... ok test_related_field (admin_views.tests.DateHierarchyTests.test_related_field) ... ok test_single (admin_views.tests.DateHierarchyTests.test_single) Single day-level date hierarchy appears for single object. ... ok test_within_month (admin_views.tests.DateHierarchyTests.test_within_month) day-level links appear for changelist within single month. ... ok test_within_year (admin_views.tests.DateHierarchyTests.test_within_year) month-level links appear for changelist within single year. ... ok test_prepopulated_maxlength_localized (admin_views.tests.PrePopulatedTest.test_prepopulated_maxlength_localized) Regression test for #15938: if USE_THOUSAND_SEPARATOR is set, make sure ... ok test_prepopulated_off (admin_views.tests.PrePopulatedTest.test_prepopulated_off) ... ok test_prepopulated_on (admin_views.tests.PrePopulatedTest.test_prepopulated_on) ... ok test_view_only_add_form (admin_views.tests.PrePopulatedTest.test_view_only_add_form) PrePopulatedPostReadOnlyAdmin.prepopulated_fields includes 'slug' ... ok test_view_only_change_form (admin_views.tests.PrePopulatedTest.test_view_only_change_form) PrePopulatedPostReadOnlyAdmin.prepopulated_fields includes 'slug'. That ... ok test_JS_i18n (admin_views.tests.NeverCacheTests.test_JS_i18n) Check the never-cache status of the JavaScript i18n view ... ok test_admin_index (admin_views.tests.NeverCacheTests.test_admin_index) Check the never-cache status of the main index ... ok test_app_index (admin_views.tests.NeverCacheTests.test_app_index) Check the never-cache status of an application index ... ok test_login (admin_views.tests.NeverCacheTests.test_login) Check the never-cache status of login views ... ok test_logout (admin_views.tests.NeverCacheTests.test_logout) Check the never-cache status of logout view ... ok test_model_add (admin_views.tests.NeverCacheTests.test_model_add) Check the never-cache status of a model add page ... ok test_model_delete (admin_views.tests.NeverCacheTests.test_model_delete) Check the never-cache status of a model delete page ... ok test_model_history (admin_views.tests.NeverCacheTests.test_model_history) Check the never-cache status of a model history page ... ok test_model_index (admin_views.tests.NeverCacheTests.test_model_index) Check the never-cache status of a model index ... ok test_model_view (admin_views.tests.NeverCacheTests.test_model_view) Check the never-cache status of a model edit page ... ok test_password_change (admin_views.tests.NeverCacheTests.test_password_change) Check the never-cache status of the password change view ... ok test_password_change_done (admin_views.tests.NeverCacheTests.test_password_change_done) Check the never-cache status of the password change done view ... ok test_group_permission_performance (admin_views.tests.GroupAdminTest.test_group_permission_performance) ... ok test_save_button (admin_views.tests.GroupAdminTest.test_save_button) ... ok test_limit_choices_to (admin_views.tests.RawIdFieldsTest.test_limit_choices_to) Regression test for 14880 ... ok test_limit_choices_to_isnull_false (admin_views.tests.RawIdFieldsTest.test_limit_choices_to_isnull_false) Regression test for 20182 ... ok test_limit_choices_to_isnull_true (admin_views.tests.RawIdFieldsTest.test_limit_choices_to_isnull_true) Regression test for 20182 ... ok test_list_display_method_same_name_as_reverse_accessor (admin_views.tests.RawIdFieldsTest.test_list_display_method_same_name_as_reverse_accessor) Should be able to use a ModelAdmin method in list_display that has the ... ok test_save_as_continue_false (admin_views.tests.SaveAsTests.test_save_as_continue_false) Saving a new object using "Save as new" redirects to the changelist ... ok test_save_as_duplication (admin_views.tests.SaveAsTests.test_save_as_duplication) 'save as' creates a new person ... ok test_save_as_new_with_inlines_with_validation_errors (admin_views.tests.SaveAsTests.test_save_as_new_with_inlines_with_validation_errors) ... ok test_save_as_new_with_validation_errors (admin_views.tests.SaveAsTests.test_save_as_new_with_validation_errors) When you click "Save as new" and have a validation error, ... ok test_save_as_new_with_validation_errors_with_inlines (admin_views.tests.SaveAsTests.test_save_as_new_with_validation_errors_with_inlines) ... ok test_secure_view_shows_login_if_not_logged_in (admin_views.tests.SecureViewTests.test_secure_view_shows_login_if_not_logged_in) ... ok test_staff_member_required_decorator_works_with_argument (admin_views.tests.SecureViewTests.test_staff_member_required_decorator_works_with_argument) Staff_member_required decorator works with an argument ... ok test_generic_content_object_in_list_display (admin_views.tests.TestGenericRelations.test_generic_content_object_in_list_display) ... ok test_custom_changelist (admin_views.tests.TestCustomChangeList.test_custom_changelist) Validate that a custom ChangeList class can be used (#9749) ... ok test_GET_parent_add (admin_views.tests.TestInlineNotEditable.test_GET_parent_add) InlineModelAdmin broken? ... ok test_change_form_renders_correct_null_choice_value (admin_views.tests.ReadonlyTest.test_change_form_renders_correct_null_choice_value) Regression test for #17911. ... ok test_correct_autoescaping (admin_views.tests.ReadonlyTest.test_correct_autoescaping) Make sure that non-field readonly elements are properly autoescaped (#24461) ... ok test_label_suffix_translated (admin_views.tests.ReadonlyTest.test_label_suffix_translated) ... ok test_readonly_field_overrides (admin_views.tests.ReadonlyTest.test_readonly_field_overrides) Regression test for #22087 - ModelForm Meta overrides are ignored by ... ok test_readonly_foreignkey_links_custom_admin_site (admin_views.tests.ReadonlyTest.test_readonly_foreignkey_links_custom_admin_site) ... ok test_readonly_foreignkey_links_default_admin_site (admin_views.tests.ReadonlyTest.test_readonly_foreignkey_links_default_admin_site) ... ok test_readonly_get (admin_views.tests.ReadonlyTest.test_readonly_get) ... ok test_readonly_manytomany (admin_views.tests.ReadonlyTest.test_readonly_manytomany) Regression test for #13004 ... ok test_readonly_manytomany_backwards_ref (admin_views.tests.ReadonlyTest.test_readonly_manytomany_backwards_ref) Regression test for #16433 - backwards references for related objects ... ok test_readonly_manytomany_forwards_ref (admin_views.tests.ReadonlyTest.test_readonly_manytomany_forwards_ref) ... ok test_readonly_onetoone_backwards_ref (admin_views.tests.ReadonlyTest.test_readonly_onetoone_backwards_ref) Can reference a reverse OneToOneField in ModelAdmin.readonly_fields. ... ok test_readonly_post (admin_views.tests.ReadonlyTest.test_readonly_post) ... ok test_readonly_text_field (admin_views.tests.ReadonlyTest.test_readonly_text_field) ... ok test_user_password_change_limited_queryset (admin_views.tests.ReadonlyTest.test_user_password_change_limited_queryset) ... ok test_all_fields_hidden (admin_views.tests.TestLabelVisibility.test_all_fields_hidden) ... ok test_all_fields_visible (admin_views.tests.TestLabelVisibility.test_all_fields_visible) ... ok test_mixin (admin_views.tests.TestLabelVisibility.test_mixin) ... ok test_primary_key_unique_check_not_performed_when_adding_and_pk_not_specified (validation.test_unique.PerformUniqueChecksTest.test_primary_key_unique_check_not_performed_when_adding_and_pk_not_specified) ... ok test_primary_key_unique_check_not_performed_when_not_adding (validation.test_unique.PerformUniqueChecksTest.test_primary_key_unique_check_not_performed_when_not_adding) ... ok test_primary_key_unique_check_performed_when_adding_and_pk_specified (validation.test_unique.PerformUniqueChecksTest.test_primary_key_unique_check_performed_when_adding_and_pk_specified) ... ok test_unique_errors (validation.test_unique.PerformUniqueChecksTest.test_unique_errors) ... ok test_unique_for_date (validation.test_unique.PerformUniqueChecksTest.test_unique_for_date) ... ok test_unique_for_date_with_nullable_date (validation.test_unique.PerformUniqueChecksTest.test_unique_for_date_with_nullable_date) unique_for_date/year/month checks shouldn't trigger when the ... ok test_lang_name_present (admin_views.tests.ValidXHTMLTests.test_lang_name_present) ... ok test_FK_validates_using_base_manager (validation.tests.BaseModelValidationTests.test_FK_validates_using_base_manager) ... ok test_correct_FK_value_validates (validation.tests.BaseModelValidationTests.test_correct_FK_value_validates) ... ok test_correct_email_value_passes (validation.tests.BaseModelValidationTests.test_correct_email_value_passes) ... ok test_custom_validate_method (validation.tests.BaseModelValidationTests.test_custom_validate_method) ... ok test_full_clean_does_not_mutate_exclude (validation.tests.BaseModelValidationTests.test_full_clean_does_not_mutate_exclude) ... ok test_limited_FK_raises_error (validation.tests.BaseModelValidationTests.test_limited_FK_raises_error) ... ok test_malformed_slug_raises_error (validation.tests.BaseModelValidationTests.test_malformed_slug_raises_error) ... ok test_missing_required_field_raises_error (validation.tests.BaseModelValidationTests.test_missing_required_field_raises_error) ... ok test_text_greater_that_charfields_max_length_raises_errors (validation.tests.BaseModelValidationTests.test_text_greater_that_charfields_max_length_raises_errors) ... ok test_with_correct_value_model_validates (validation.tests.BaseModelValidationTests.test_with_correct_value_model_validates) ... ok test_wrong_FK_value_raises_error (validation.tests.BaseModelValidationTests.test_wrong_FK_value_raises_error) ... ok test_wrong_email_value_raises_error (validation.tests.BaseModelValidationTests.test_wrong_email_value_raises_error) ... ok test_wrong_url_value_raises_error (validation.tests.BaseModelValidationTests.test_wrong_url_value_raises_error) ... ok test_correct_generic_ip_passes (validation.tests.GenericIPAddressFieldTests.test_correct_generic_ip_passes) ... ok test_correct_v4_ip_passes (validation.tests.GenericIPAddressFieldTests.test_correct_v4_ip_passes) ... ok test_correct_v6_ip_passes (validation.tests.GenericIPAddressFieldTests.test_correct_v6_ip_passes) ... ok test_empty_generic_ip_passes (validation.tests.GenericIPAddressFieldTests.test_empty_generic_ip_passes) ... ok test_invalid_generic_ip_raises_error (validation.tests.GenericIPAddressFieldTests.test_invalid_generic_ip_raises_error) ... ok test_invalid_v4_ip_raises_error (validation.tests.GenericIPAddressFieldTests.test_invalid_v4_ip_raises_error) ... ok test_invalid_v6_ip_raises_error (validation.tests.GenericIPAddressFieldTests.test_invalid_v6_ip_raises_error) ... ok test_v4_unpack_uniqueness_detection (validation.tests.GenericIPAddressFieldTests.test_v4_unpack_uniqueness_detection) ... ok test_v6_uniqueness_detection (validation.tests.GenericIPAddressFieldTests.test_v6_uniqueness_detection) ... ok test_partial_validation (validation.tests.ModelFormsTests.test_partial_validation) ... ok test_validation_with_empty_blank_field (validation.tests.ModelFormsTests.test_validation_with_empty_blank_field) ... ok test_validation_with_invalid_blank_field (validation.tests.ModelFormsTests.test_validation_with_invalid_blank_field) ... ok test_datetime_output_field (custom_lookups.tests.DateTimeLookupTests.test_datetime_output_field) ... skipped 'MySQL specific SQL used' test_bilateral_fexpr (custom_lookups.tests.BilateralTransformTests.test_bilateral_fexpr) ... ok test_bilateral_inner_qs (custom_lookups.tests.BilateralTransformTests.test_bilateral_inner_qs) ... ok test_bilateral_multi_value (custom_lookups.tests.BilateralTransformTests.test_bilateral_multi_value) ... ok test_bilateral_order (custom_lookups.tests.BilateralTransformTests.test_bilateral_order) ... ok test_bilateral_upper (custom_lookups.tests.BilateralTransformTests.test_bilateral_upper) ... ok test_div3_bilateral_extract (custom_lookups.tests.BilateralTransformTests.test_div3_bilateral_extract) ... ok test_transform_order_by (custom_lookups.tests.BilateralTransformTests.test_transform_order_by) ... ok test_subquery_usage (custom_lookups.tests.SubqueryTransformTests.test_subquery_usage) ... ok test_basic_lookup (custom_lookups.tests.LookupTests.test_basic_lookup) ... ok test_birthdate_month (custom_lookups.tests.LookupTests.test_birthdate_month) ... skipped 'PostgreSQL specific SQL used' test_custom_exact_lookup_none_rhs (custom_lookups.tests.LookupTests.test_custom_exact_lookup_none_rhs) __exact=None is transformed to __isnull=True if a custom lookup class ... ok test_custom_name_lookup (custom_lookups.tests.LookupTests.test_custom_name_lookup) ... ok test_div3_extract (custom_lookups.tests.LookupTests.test_div3_extract) ... ok test_foreignobject_lookup_registration (custom_lookups.tests.LookupTests.test_foreignobject_lookup_registration) ... ok test_lookups_caching (custom_lookups.tests.LookupTests.test_lookups_caching) ... ok test_custom_implementation_year_exact (custom_lookups.tests.YearLteTests.test_custom_implementation_year_exact) ... ok test_postgres_year_exact (custom_lookups.tests.YearLteTests.test_postgres_year_exact) ... ok test_year_lte (custom_lookups.tests.YearLteTests.test_year_lte) ... skipped 'PostgreSQL specific SQL used' test_year_lte_fexpr (custom_lookups.tests.YearLteTests.test_year_lte_fexpr) ... skipped 'PostgreSQL specific SQL used' test_year_lte_sql (custom_lookups.tests.YearLteTests.test_year_lte_sql) ... ok test_debug (context_processors.tests.DebugContextProcessorTests.test_debug) ... ok test_sql_queries (context_processors.tests.DebugContextProcessorTests.test_sql_queries) Test whether sql_queries represents the actual amount ... ok test_foreign_key (known_related_objects.tests.ExistingRelatedInstancesTests.test_foreign_key) ... ok test_foreign_key_multiple_prefetch (known_related_objects.tests.ExistingRelatedInstancesTests.test_foreign_key_multiple_prefetch) ... ok test_foreign_key_prefetch_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_foreign_key_prefetch_related) ... ok test_one_to_one (known_related_objects.tests.ExistingRelatedInstancesTests.test_one_to_one) ... ok test_one_to_one_multi_prefetch_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_one_to_one_multi_prefetch_related) ... ok test_one_to_one_multi_select_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_one_to_one_multi_select_related) ... ok test_one_to_one_prefetch_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_one_to_one_prefetch_related) ... ok test_one_to_one_select_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_one_to_one_select_related) ... ok test_queryset_and (known_related_objects.tests.ExistingRelatedInstancesTests.test_queryset_and) ... ok test_queryset_or (known_related_objects.tests.ExistingRelatedInstancesTests.test_queryset_or) ... ok test_queryset_or_different_cached_items (known_related_objects.tests.ExistingRelatedInstancesTests.test_queryset_or_different_cached_items) ... ok test_queryset_or_only_one_with_precache (known_related_objects.tests.ExistingRelatedInstancesTests.test_queryset_or_only_one_with_precache) ... ok test_reverse_one_to_one (known_related_objects.tests.ExistingRelatedInstancesTests.test_reverse_one_to_one) ... ok test_reverse_one_to_one_multi_prefetch_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_reverse_one_to_one_multi_prefetch_related) ... ok test_reverse_one_to_one_multi_select_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_reverse_one_to_one_multi_select_related) ... ok test_reverse_one_to_one_prefetch_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_reverse_one_to_one_prefetch_related) ... ok test_reverse_one_to_one_select_related (known_related_objects.tests.ExistingRelatedInstancesTests.test_reverse_one_to_one_select_related) ... ok test_aggregate (filtered_relation.tests.FilteredRelationAggregationTests.test_aggregate) filtered_relation() not only improves performance but also creates ... ok test_aggregate (filtered_relation.tests.FilteredRelationAnalyticalAggregationTests.test_aggregate) ... ok test_assign_none_null_reverse_relation (one_to_one.tests.OneToOneTests.test_assign_none_null_reverse_relation) ... ok test_assign_none_reverse_relation (one_to_one.tests.OneToOneTests.test_assign_none_reverse_relation) ... ok test_assign_none_to_null_cached_reverse_relation (one_to_one.tests.OneToOneTests.test_assign_none_to_null_cached_reverse_relation) ... ok test_assign_o2o_id_none (one_to_one.tests.OneToOneTests.test_assign_o2o_id_none) ... ok test_assign_o2o_id_value (one_to_one.tests.OneToOneTests.test_assign_o2o_id_value) ... ok test_cached_relation_invalidated_on_save (one_to_one.tests.OneToOneTests.test_cached_relation_invalidated_on_save) Model.save() invalidates stale OneToOneField relations after a primary ... ok test_create_models_m2m (one_to_one.tests.OneToOneTests.test_create_models_m2m) Models are created via the m2m relation if the remote model has a ... ok test_filter_one_to_one_relations (one_to_one.tests.OneToOneTests.test_filter_one_to_one_relations) Regression test for #9968 ... ok test_foreign_key (one_to_one.tests.OneToOneTests.test_foreign_key) ... ok test_get_reverse_on_unsaved_object (one_to_one.tests.OneToOneTests.test_get_reverse_on_unsaved_object) Regression for #18153 and #19089. ... ok test_getter (one_to_one.tests.OneToOneTests.test_getter) ... ok test_hasattr_related_object (one_to_one.tests.OneToOneTests.test_hasattr_related_object) ... ok test_hidden_accessor (one_to_one.tests.OneToOneTests.test_hidden_accessor) When a '+' ending related name is specified no reverse accessor should ... ok test_manager_all (one_to_one.tests.OneToOneTests.test_manager_all) ... ok test_manager_get (one_to_one.tests.OneToOneTests.test_manager_get) ... ok test_multiple_o2o (one_to_one.tests.OneToOneTests.test_multiple_o2o) ... ok test_nullable_o2o_delete (one_to_one.tests.OneToOneTests.test_nullable_o2o_delete) ... ok test_o2o_primary_key_delete (one_to_one.tests.OneToOneTests.test_o2o_primary_key_delete) ... ok test_primary_key_to_field_filter (one_to_one.tests.OneToOneTests.test_primary_key_to_field_filter) ... ok test_rel_pk_exact (one_to_one.tests.OneToOneTests.test_rel_pk_exact) ... ok test_rel_pk_subquery (one_to_one.tests.OneToOneTests.test_rel_pk_subquery) ... ok test_related_object (one_to_one.tests.OneToOneTests.test_related_object) ... ok test_related_object_cache (one_to_one.tests.OneToOneTests.test_related_object_cache) Regression test for #6886 (the related-object cache) ... ok test_related_object_cached_when_reverse_is_accessed (one_to_one.tests.OneToOneTests.test_related_object_cached_when_reverse_is_accessed) Regression for #13839 and #17439. ... ok test_reverse_object_cache (one_to_one.tests.OneToOneTests.test_reverse_object_cache) The name of the cache for the reverse object is correct (#7173). ... ok test_reverse_object_cached_when_related_is_accessed (one_to_one.tests.OneToOneTests.test_reverse_object_cached_when_related_is_accessed) Regression for #13839 and #17439. ... ok test_reverse_object_cached_when_related_is_set (one_to_one.tests.OneToOneTests.test_reverse_object_cached_when_related_is_set) Regression for #13839 and #17439. ... ok test_reverse_object_cached_when_related_is_unset (one_to_one.tests.OneToOneTests.test_reverse_object_cached_when_related_is_unset) Regression for #13839 and #17439. ... ok test_reverse_object_does_not_exist_cache (one_to_one.tests.OneToOneTests.test_reverse_object_does_not_exist_cache) Regression for #13839 and #17439. ... ok test_reverse_relationship_cache_cascade (one_to_one.tests.OneToOneTests.test_reverse_relationship_cache_cascade) Regression test for #9023: accessing the reverse relationship shouldn't ... ok test_save_nullable_o2o_after_parent (one_to_one.tests.OneToOneTests.test_save_nullable_o2o_after_parent) ... ok test_set_reverse_on_unsaved_object (one_to_one.tests.OneToOneTests.test_set_reverse_on_unsaved_object) Writing to the reverse relation on an unsaved object ... ok test_setter (one_to_one.tests.OneToOneTests.test_setter) ... ok test_unsaved_object (one_to_one.tests.OneToOneTests.test_unsaved_object) #10811 -- Assigning an unsaved object to a OneToOneField ... ok test_update_one_to_one_pk (one_to_one.tests.OneToOneTests.test_update_one_to_one_pk) ... ok test_reraising_backend_specific_database_exception (db_utils.tests.DatabaseErrorWrapperTests.test_reraising_backend_specific_database_exception) ... skipped 'PostgreSQL test' test_multiple_context (test_client_regress.tests.AssertTemplateUsedTests.test_multiple_context) Template assertions work when there are multiple contexts ... ok test_no_context (test_client_regress.tests.AssertTemplateUsedTests.test_no_context) Template usage assertions work then templates aren't in use ... ok test_single_context (test_client_regress.tests.AssertTemplateUsedTests.test_single_context) Template assertions work when there is a single context ... ok test_template_rendered_multiple_times (test_client_regress.tests.AssertTemplateUsedTests.test_template_rendered_multiple_times) Template assertions work when a template is rendered multiple times. ... ok test_15368 (test_client_regress.tests.ContextTests.test_15368) ... ok test_contextlist_get (test_client_regress.tests.ContextTests.test_contextlist_get) ... ok test_contextlist_keys (test_client_regress.tests.ContextTests.test_contextlist_keys) ... ok test_inherited_context (test_client_regress.tests.ContextTests.test_inherited_context) Context variables can be retrieved from a list of contexts ... ok test_nested_requests (test_client_regress.tests.ContextTests.test_nested_requests) response.context is not lost when view call another view. ... ok test_single_context (test_client_regress.tests.ContextTests.test_single_context) Context variables can be retrieved from a single context ... ok test_exception_cleared (test_client_regress.tests.ExceptionTests.test_exception_cleared) #5836 - A stale user exception isn't re-raised by the test client. ... ok test_login_different_client (test_client_regress.tests.LoginTests.test_login_different_client) Using a different test client doesn't violate authentication ... ok test_as_subquery (filtered_relation.tests.FilteredRelationTests.test_as_subquery) ... ok test_condition_deeper_relation_name (filtered_relation.tests.FilteredRelationTests.test_condition_deeper_relation_name) ... ok test_condition_outside_relation_name (filtered_relation.tests.FilteredRelationTests.test_condition_outside_relation_name) ... ok test_deep_nested_foreign_key (filtered_relation.tests.FilteredRelationTests.test_deep_nested_foreign_key) ... ok test_defer (filtered_relation.tests.FilteredRelationTests.test_defer) ... ok test_difference (filtered_relation.tests.FilteredRelationTests.test_difference) ... ok test_eq (filtered_relation.tests.FilteredRelationTests.test_eq) ... ok test_exclude_relation_with_join (filtered_relation.tests.FilteredRelationTests.test_exclude_relation_with_join) ... ok test_extra (filtered_relation.tests.FilteredRelationTests.test_extra) ... ok test_internal_queryset_alias_mapping (filtered_relation.tests.FilteredRelationTests.test_internal_queryset_alias_mapping) ... ok test_intersection (filtered_relation.tests.FilteredRelationTests.test_intersection) ... ok test_multiple_times (filtered_relation.tests.FilteredRelationTests.test_multiple_times) ... ok test_nested_chained_relations (filtered_relation.tests.FilteredRelationTests.test_nested_chained_relations) ... ok test_nested_foreign_key (filtered_relation.tests.FilteredRelationTests.test_nested_foreign_key) ... ok test_nested_foreign_key_filtered_base_object (filtered_relation.tests.FilteredRelationTests.test_nested_foreign_key_filtered_base_object) ... ok test_nested_foreign_key_nested_field (filtered_relation.tests.FilteredRelationTests.test_nested_foreign_key_nested_field) ... ok test_nested_m2m_filtered (filtered_relation.tests.FilteredRelationTests.test_nested_m2m_filtered) ... ok test_only_not_supported (filtered_relation.tests.FilteredRelationTests.test_only_not_supported) ... ok test_relation_name_lookup (filtered_relation.tests.FilteredRelationTests.test_relation_name_lookup) ... ok test_select_for_update (filtered_relation.tests.FilteredRelationTests.test_select_for_update) ... ok test_select_related (filtered_relation.tests.FilteredRelationTests.test_select_related) ... ok test_select_related_foreign_key (filtered_relation.tests.FilteredRelationTests.test_select_related_foreign_key) ... ok test_select_related_foreign_key_for_update_of (filtered_relation.tests.FilteredRelationTests.test_select_related_foreign_key_for_update_of) ... skipped "Database doesn't support feature(s): has_select_for_update, has_select_for_update_of" test_select_related_multiple (filtered_relation.tests.FilteredRelationTests.test_select_related_multiple) ... ok test_select_related_with_empty_relation (filtered_relation.tests.FilteredRelationTests.test_select_related_with_empty_relation) ... ok test_union (filtered_relation.tests.FilteredRelationTests.test_union) ... ok test_values (filtered_relation.tests.FilteredRelationTests.test_values) ... ok test_values_list (filtered_relation.tests.FilteredRelationTests.test_values_list) ... ok test_with_condition_as_expression_error (filtered_relation.tests.FilteredRelationTests.test_with_condition_as_expression_error) ... ok test_with_empty_relation_name_error (filtered_relation.tests.FilteredRelationTests.test_with_empty_relation_name_error) ... ok test_with_exclude (filtered_relation.tests.FilteredRelationTests.test_with_exclude) ... ok test_with_generic_foreign_key (filtered_relation.tests.FilteredRelationTests.test_with_generic_foreign_key) ... ok test_with_join (filtered_relation.tests.FilteredRelationTests.test_with_join) ... ok test_with_join_and_complex_condition (filtered_relation.tests.FilteredRelationTests.test_with_join_and_complex_condition) ... ok test_with_m2m (filtered_relation.tests.FilteredRelationTests.test_with_m2m) ... ok test_with_m2m_deep (filtered_relation.tests.FilteredRelationTests.test_with_m2m_deep) ... ok test_with_m2m_multijoin (filtered_relation.tests.FilteredRelationTests.test_with_m2m_multijoin) ... ok test_with_multiple_filter (filtered_relation.tests.FilteredRelationTests.test_with_multiple_filter) ... ok test_with_prefetch_related (filtered_relation.tests.FilteredRelationTests.test_with_prefetch_related) ... ok test_without_join (filtered_relation.tests.FilteredRelationTests.test_without_join) ... ok test_login (test_client_regress.tests.SessionEngineTests.test_login) A session engine that modifies the session key can be used to log in ... ok test_login_with_user (test_client_regress.tests.SessionTests.test_login_with_user) Login should send user_logged_in signal on successful login. ... ok test_login_without_signal (test_client_regress.tests.SessionTests.test_login_without_signal) Login shouldn't send signal if user wasn't logged in ... ok test_logout (test_client_regress.tests.SessionTests.test_logout) Logout should work whether the user is logged in or not (#9978). ... ok test_logout_with_custom_auth_backend (test_client_regress.tests.SessionTests.test_logout_with_custom_auth_backend) Request a logout after logging in with custom authentication backend ... ok test_logout_with_custom_user (test_client_regress.tests.SessionTests.test_logout_with_custom_user) Logout should send user_logged_out signal if custom user was logged in. ... ok test_logout_with_user (test_client_regress.tests.SessionTests.test_logout_with_user) Logout should send user_logged_out signal if user was logged in. ... ok test_logout_without_user (test_client_regress.tests.SessionTests.test_logout_without_user) Logout should send signal even if user not authenticated. ... ok test_session (test_client_regress.tests.SessionTests.test_session) The session isn't lost if a user logs in ... ok test_session_initiated (test_client_regress.tests.SessionTests.test_session_initiated) ... ok test_deep_mixed_backward (foreign_object.test_agnostic_order_trimjoin.TestLookupQuery.test_deep_mixed_backward) ... ok test_deep_mixed_forward (foreign_object.test_agnostic_order_trimjoin.TestLookupQuery.test_deep_mixed_forward) ... ok test_empty_join_conditions (foreign_object.test_empty_join.RestrictedConditionsTests.test_empty_join_conditions) ... ok test_restrictions_with_no_joining_columns (foreign_object.test_empty_join.RestrictedConditionsTests.test_restrictions_with_no_joining_columns) It's possible to create a working related field that doesn't ... ok test_foreign_object_form (foreign_object.test_forms.FormsTests.test_foreign_object_form) ... ok test_add (many_to_one.tests.ManyToOneTests.test_add) ... ok test_add_after_prefetch (many_to_one.tests.ManyToOneTests.test_add_after_prefetch) ... ok test_add_remove_set_by_pk_raises (many_to_one.tests.ManyToOneTests.test_add_remove_set_by_pk_raises) ... ok test_add_then_remove_after_prefetch (many_to_one.tests.ManyToOneTests.test_add_then_remove_after_prefetch) ... ok test_assign (many_to_one.tests.ManyToOneTests.test_assign) ... ok test_assign_fk_id_none (many_to_one.tests.ManyToOneTests.test_assign_fk_id_none) ... ok test_assign_fk_id_value (many_to_one.tests.ManyToOneTests.test_assign_fk_id_value) ... ok test_cached_foreign_key_with_to_field_not_cleared_by_save (many_to_one.tests.ManyToOneTests.test_cached_foreign_key_with_to_field_not_cleared_by_save) ... ok test_cached_relation_invalidated_on_save (many_to_one.tests.ManyToOneTests.test_cached_relation_invalidated_on_save) Model.save() invalidates stale ForeignKey relations after a primary key ... ok test_clear_after_prefetch (many_to_one.tests.ManyToOneTests.test_clear_after_prefetch) ... ok test_create (many_to_one.tests.ManyToOneTests.test_create) ... ok test_create_relation_with_gettext_lazy (many_to_one.tests.ManyToOneTests.test_create_relation_with_gettext_lazy) ... ok test_deepcopy_and_circular_references (many_to_one.tests.ManyToOneTests.test_deepcopy_and_circular_references) ... ok test_delete (many_to_one.tests.ManyToOneTests.test_delete) ... ok test_explicit_fk (many_to_one.tests.ManyToOneTests.test_explicit_fk) ... ok test_fk_assignment_and_related_object_cache (many_to_one.tests.ManyToOneTests.test_fk_assignment_and_related_object_cache) ... ok test_fk_instantiation_outside_model (many_to_one.tests.ManyToOneTests.test_fk_instantiation_outside_model) ... ok test_fk_to_bigautofield (many_to_one.tests.ManyToOneTests.test_fk_to_bigautofield) ... ok test_fk_to_smallautofield (many_to_one.tests.ManyToOneTests.test_fk_to_smallautofield) ... ok test_get (many_to_one.tests.ManyToOneTests.test_get) ... ok test_hasattr_related_object (many_to_one.tests.ManyToOneTests.test_hasattr_related_object) ... ok test_manager_class_caching (many_to_one.tests.ManyToOneTests.test_manager_class_caching) ... ok test_multiple_foreignkeys (many_to_one.tests.ManyToOneTests.test_multiple_foreignkeys) ... ok test_related_object (many_to_one.tests.ManyToOneTests.test_related_object) ... ok test_relation_unsaved (many_to_one.tests.ManyToOneTests.test_relation_unsaved) ... ok test_remove_after_prefetch (many_to_one.tests.ManyToOneTests.test_remove_after_prefetch) ... ok test_reverse_assignment_deprecation (many_to_one.tests.ManyToOneTests.test_reverse_assignment_deprecation) ... ok test_reverse_foreign_key_instance_to_field_caching (many_to_one.tests.ManyToOneTests.test_reverse_foreign_key_instance_to_field_caching) ... ok test_reverse_selects (many_to_one.tests.ManyToOneTests.test_reverse_selects) ... ok test_save_fk_after_parent_with_non_numeric_pk_set_on_child (many_to_one.tests.ManyToOneTests.test_save_fk_after_parent_with_non_numeric_pk_set_on_child) ... ok test_save_nullable_fk_after_parent (many_to_one.tests.ManyToOneTests.test_save_nullable_fk_after_parent) ... ok test_save_nullable_fk_after_parent_with_to_field (many_to_one.tests.ManyToOneTests.test_save_nullable_fk_after_parent_with_to_field) ... ok test_select_related (many_to_one.tests.ManyToOneTests.test_select_related) ... ok test_selects (many_to_one.tests.ManyToOneTests.test_selects) ... ok test_set (many_to_one.tests.ManyToOneTests.test_set) ... ok test_set_after_prefetch (many_to_one.tests.ManyToOneTests.test_set_after_prefetch) ... ok test_values_list_exception (many_to_one.tests.ManyToOneTests.test_values_list_exception) ... ok test_extra_join_filter_q (foreign_object.tests.TestExtraJoinFilterQ.test_extra_join_filter_q) ... ok test_list_error_message (forms_tests.tests.test_error_messages.DeprecationTests.test_list_error_message) ... ok test_list_error_message_warning (forms_tests.tests.test_error_messages.DeprecationTests.test_list_error_message_warning) ... ok test_batch_create_foreign_object (foreign_object.tests.MultiColumnFKTests.test_batch_create_foreign_object) ... ok test_double_nested_query (foreign_object.tests.MultiColumnFKTests.test_double_nested_query) ... ok test_foreign_key_raises_informative_does_not_exist (foreign_object.tests.MultiColumnFKTests.test_foreign_key_raises_informative_does_not_exist) ... ok test_foreign_key_related_query_name (foreign_object.tests.MultiColumnFKTests.test_foreign_key_related_query_name) ... ok test_forward_in_lookup_filters_correctly (foreign_object.tests.MultiColumnFKTests.test_forward_in_lookup_filters_correctly) ... ok test_get_fails_on_multicolumn_mismatch (foreign_object.tests.MultiColumnFKTests.test_get_fails_on_multicolumn_mismatch) ... ok test_get_succeeds_on_multicolumn_match (foreign_object.tests.MultiColumnFKTests.test_get_succeeds_on_multicolumn_match) ... ok test_inheritance (foreign_object.tests.MultiColumnFKTests.test_inheritance) ... ok test_isnull_lookup (foreign_object.tests.MultiColumnFKTests.test_isnull_lookup) ... ok test_m2m_through_forward_ignores_invalid_members (foreign_object.tests.MultiColumnFKTests.test_m2m_through_forward_ignores_invalid_members) ... ok test_m2m_through_forward_returns_valid_members (foreign_object.tests.MultiColumnFKTests.test_m2m_through_forward_returns_valid_members) ... ok test_m2m_through_on_self_ignores_mismatch_columns (foreign_object.tests.MultiColumnFKTests.test_m2m_through_on_self_ignores_mismatch_columns) ... ok test_m2m_through_on_self_works (foreign_object.tests.MultiColumnFKTests.test_m2m_through_on_self_works) ... ok test_m2m_through_reverse_ignores_invalid_members (foreign_object.tests.MultiColumnFKTests.test_m2m_through_reverse_ignores_invalid_members) ... ok test_m2m_through_reverse_returns_valid_members (foreign_object.tests.MultiColumnFKTests.test_m2m_through_reverse_returns_valid_members) ... ok test_many_to_many_related_query_name (foreign_object.tests.MultiColumnFKTests.test_many_to_many_related_query_name) ... ok test_prefetch_foreignkey_forward_works (foreign_object.tests.MultiColumnFKTests.test_prefetch_foreignkey_forward_works) ... ok test_prefetch_foreignkey_reverse_works (foreign_object.tests.MultiColumnFKTests.test_prefetch_foreignkey_reverse_works) ... ok test_prefetch_related_m2m_forward_works (foreign_object.tests.MultiColumnFKTests.test_prefetch_related_m2m_forward_works) ... ok test_prefetch_related_m2m_reverse_works (foreign_object.tests.MultiColumnFKTests.test_prefetch_related_m2m_reverse_works) ... ok test_query_filters_correctly (foreign_object.tests.MultiColumnFKTests.test_query_filters_correctly) ... ok test_reverse_query_filters_correctly (foreign_object.tests.MultiColumnFKTests.test_reverse_query_filters_correctly) ... ok test_reverse_query_returns_correct_result (foreign_object.tests.MultiColumnFKTests.test_reverse_query_returns_correct_result) ... ok test_select_related_foreignkey_forward_works (foreign_object.tests.MultiColumnFKTests.test_select_related_foreignkey_forward_works) ... ok test_translations (foreign_object.tests.MultiColumnFKTests.test_translations) ... ok test_modelchoicefield (forms_tests.tests.test_error_messages.ModelChoiceFieldErrorMessagesTestCase.test_modelchoicefield) ... ok test_boundary_conditions (forms_tests.tests.tests.FormsModelTestCase.test_boundary_conditions) ... ok test_formfield_initial (forms_tests.tests.tests.FormsModelTestCase.test_formfield_initial) ... ok test_unicode_filename (forms_tests.tests.tests.FormsModelTestCase.test_unicode_filename) ... ok test_empty_field_char (forms_tests.tests.tests.EmptyLabelTestCase.test_empty_field_char) ... ok test_empty_field_char_none (forms_tests.tests.tests.EmptyLabelTestCase.test_empty_field_char_none) ... ok test_empty_field_integer (forms_tests.tests.tests.EmptyLabelTestCase.test_empty_field_integer) ... ok test_get_display_value_on_none (forms_tests.tests.tests.EmptyLabelTestCase.test_get_display_value_on_none) ... ok test_html_rendering_of_prepopulated_models (forms_tests.tests.tests.EmptyLabelTestCase.test_html_rendering_of_prepopulated_models) ... ok test_save_empty_label_forms (forms_tests.tests.tests.EmptyLabelTestCase.test_save_empty_label_forms) ... ok test_m2m_field_exclusion (forms_tests.tests.tests.ManyToManyExclusionTestCase.test_m2m_field_exclusion) ... ok test_empty_queryset_return (forms_tests.tests.tests.TestTicket14567.test_empty_queryset_return) If a model's ManyToManyField has blank=True and is saved with no data, a queryset is returned. ... ok test_callable_initial_value (forms_tests.tests.tests.ModelFormCallableModelDefault.test_callable_initial_value) The initial value for a callable default returning a queryset is the pk (refs #13769) ... ok test_initial_instance_value (forms_tests.tests.tests.ModelFormCallableModelDefault.test_initial_instance_value) Initial instances for model fields may also be instances (refs #7287) ... ok test_no_empty_option (forms_tests.tests.tests.ModelFormCallableModelDefault.test_no_empty_option) If a model's ForeignKey has blank=False and a default, no empty option is created (Refs #10792). ... ok test_bad_request (view_tests.tests.test_defaults.DefaultsTests.test_bad_request) ... ok test_csrf_token_in_404 (view_tests.tests.test_defaults.DefaultsTests.test_csrf_token_in_404) The 404 page should have the csrf_token available in the context ... ok test_custom_templates (view_tests.tests.test_defaults.DefaultsTests.test_custom_templates) 404.html and 500.html templates are picked by their respective handler. ... ok test_custom_templates_wrong (view_tests.tests.test_defaults.DefaultsTests.test_custom_templates_wrong) Default error views should raise TemplateDoesNotExist when passed a ... ok test_error_pages (view_tests.tests.test_defaults.DefaultsTests.test_error_pages) ... ok test_get_absolute_url_attributes (view_tests.tests.test_defaults.DefaultsTests.test_get_absolute_url_attributes) A model can set attributes on the get_absolute_url method ... ok test_page_not_found (view_tests.tests.test_defaults.DefaultsTests.test_page_not_found) A 404 status is returned by the page_not_found view ... ok test_server_error (view_tests.tests.test_defaults.DefaultsTests.test_server_error) The server_error view raises a 500 status ... ok test_lang_from_translated_i18n_pattern (view_tests.tests.test_i18n.SetLanguageTests.test_lang_from_translated_i18n_pattern) ... ok test_session_language_deprecation (view_tests.tests.test_i18n.SetLanguageTests.test_session_language_deprecation) ... ok test_setlang (view_tests.tests.test_i18n.SetLanguageTests.test_setlang) The set_language view can be used to change the session language. ... ok test_setlang_cookie (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_cookie) ... ok test_setlang_decodes_http_referer_url (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_decodes_http_referer_url) The set_language view decodes the HTTP_REFERER URL and preserves an ... ok test_setlang_default_redirect (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_default_redirect) The set_language view redirects to '/' when there isn't a referer or ... ok test_setlang_doesnt_perform_a_default_redirect_for_ajax (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_doesnt_perform_a_default_redirect_for_ajax) The set_language view returns 204 by default for requests not accepting ... ok test_setlang_doesnt_perform_a_redirect_to_referer_for_ajax (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_doesnt_perform_a_redirect_to_referer_for_ajax) The set_language view doesn't redirect to the HTTP referer header if ... ok test_setlang_http_next (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_http_next) The set_language view only redirects to the 'next' argument if it is ... ok test_setlang_performs_redirect_for_ajax_if_explicitly_requested (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_performs_redirect_for_ajax_if_explicitly_requested) The set_language view redirects to the "next" parameter for requests ... ok test_setlang_redirect_to_referer (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_redirect_to_referer) The set_language view redirects to the URL in the referer header when ... ok test_setlang_reversal (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_reversal) ... ok test_setlang_unsafe_next (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_unsafe_next) The set_language view only redirects to the 'next' argument if it is ... ok test_setlang_unsafe_next_for_ajax (view_tests.tests.test_i18n.SetLanguageTests.test_setlang_unsafe_next_for_ajax) The fallback to root URL for the set_language view works for requests ... ok test_build_attrs (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_build_attrs) ... ok test_build_attrs_no_custom_class (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_build_attrs_no_custom_class) ... ok test_build_attrs_not_required_field (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_build_attrs_not_required_field) ... ok test_build_attrs_required_field (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_build_attrs_required_field) ... ok test_get_url (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_get_url) ... ok test_media (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_media) ... ok test_render_options (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_render_options) ... ok test_render_options_fk_as_pk (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_render_options_fk_as_pk) ... ok test_render_options_not_required_field (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_render_options_not_required_field) Empty option isn't present if the field isn't required. ... ok test_render_options_required_field (admin_widgets.test_autocomplete_widget.AutocompleteMixinTests.test_render_options_required_field) Empty option is present if the field isn't required. ... ok test_readonly_fields (admin_widgets.tests.AdminFileWidgetTests.test_readonly_fields) File widgets should render as a link when they're marked "read only." ... ok test_render (admin_widgets.tests.AdminFileWidgetTests.test_render) ... ok test_render_disabled (admin_widgets.tests.AdminFileWidgetTests.test_render_disabled) ... ok test_render_required (admin_widgets.tests.AdminFileWidgetTests.test_render_required) ... ok test_changelist_ForeignKey (admin_widgets.tests.AdminForeignKeyWidgetChangeList.test_changelist_ForeignKey) ... ok test_invalid_target_id (admin_widgets.tests.AdminForeignKeyRawIdWidget.test_invalid_target_id) ... ok test_label_and_url_for_value_invalid_uuid (admin_widgets.tests.AdminForeignKeyRawIdWidget.test_label_and_url_for_value_invalid_uuid) ... ok test_nonexistent_target_id (admin_widgets.tests.AdminForeignKeyRawIdWidget.test_nonexistent_target_id) ... ok test_url_params_from_lookup_dict_any_iterable (admin_widgets.tests.AdminForeignKeyRawIdWidget.test_url_params_from_lookup_dict_any_iterable) ... ok test_url_params_from_lookup_dict_callable (admin_widgets.tests.AdminForeignKeyRawIdWidget.test_url_params_from_lookup_dict_callable) ... ok test_filter_choices_by_request_user (admin_widgets.tests.AdminFormfieldForDBFieldWithRequestTests.test_filter_choices_by_request_user) Ensure the user can only see their own cars in the foreign key dropdown. ... ok test_m2m_related_model_not_in_admin (admin_widgets.tests.ManyToManyRawIdWidgetTest.test_m2m_related_model_not_in_admin) ... ok test_render (admin_widgets.tests.ManyToManyRawIdWidgetTest.test_render) ... ok test_custom_named_field (sites_framework.tests.SitesFrameworkTestCase.test_custom_named_field) ... ok test_site_fk (sites_framework.tests.SitesFrameworkTestCase.test_site_fk) ... ok test_sites_m2m (sites_framework.tests.SitesFrameworkTestCase.test_sites_m2m) ... ok test_fk_related_model_not_in_admin (admin_widgets.tests.ForeignKeyRawIdWidgetTest.test_fk_related_model_not_in_admin) ... ok test_fk_to_self_model_not_in_admin (admin_widgets.tests.ForeignKeyRawIdWidgetTest.test_fk_to_self_model_not_in_admin) ... ok test_proper_manager_for_label_lookup (admin_widgets.tests.ForeignKeyRawIdWidgetTest.test_proper_manager_for_label_lookup) ... ok test_relations_to_non_primary_key (admin_widgets.tests.ForeignKeyRawIdWidgetTest.test_relations_to_non_primary_key) ... ok test_render (admin_widgets.tests.ForeignKeyRawIdWidgetTest.test_render) ... ok test_render_fk_as_pk_model (admin_widgets.tests.ForeignKeyRawIdWidgetTest.test_render_fk_as_pk_model) ... ok test_render_unsafe_limit_choices_to (admin_widgets.tests.ForeignKeyRawIdWidgetTest.test_render_unsafe_limit_choices_to) ... ok test_model_with_evaluate_method (model_regress.tests.EvaluateMethodTest.test_model_with_evaluate_method) You can filter by objects that have an 'evaluate' attr ... ok test_fields_cache_reset_on_copy (model_regress.tests.ModelFieldsCacheTest.test_fields_cache_reset_on_copy) ... ok test_pk_validation (model_regress.tests.ModelValidationTest.test_pk_validation) ... ok test_add_view (admin_views.tests.NamespacedAdminKeepChangeListFiltersTests.test_add_view) ... ok test_add_view_without_preserved_filters (admin_views.tests.NamespacedAdminKeepChangeListFiltersTests.test_add_view_without_preserved_filters) ... ok test_assert_url_equal (admin_views.tests.NamespacedAdminKeepChangeListFiltersTests.test_assert_url_equal) ... ok test_change_view (admin_views.tests.NamespacedAdminKeepChangeListFiltersTests.test_change_view) ... ok test_change_view_without_preserved_filters (admin_views.tests.NamespacedAdminKeepChangeListFiltersTests.test_change_view_without_preserved_filters) ... ok test_changelist_view (admin_views.tests.NamespacedAdminKeepChangeListFiltersTests.test_changelist_view) ... ok test_delete_view (admin_views.tests.NamespacedAdminKeepChangeListFiltersTests.test_delete_view) ... ok test_url_prefix (admin_views.tests.NamespacedAdminKeepChangeListFiltersTests.test_url_prefix) ... ok test_in_lookup_query_evaluation (queryset_pickle.tests.InLookupTests.test_in_lookup_query_evaluation) ... ok test_in_lookup_queryset_evaluation (queryset_pickle.tests.InLookupTests.test_in_lookup_queryset_evaluation) Neither pickling nor unpickling a QuerySet.query with an __in=inner_qs ... ok test_chained_fks (model_regress.tests.ModelTests.test_chained_fks) Regression for #18432: Chained foreign keys with to_field produce incorrect query ... ok test_date_filter_null (model_regress.tests.ModelTests.test_date_filter_null) ... ok test_date_lookup (model_regress.tests.ModelTests.test_date_lookup) ... ok test_empty_choice (model_regress.tests.ModelTests.test_empty_choice) ... ok test_get_next_prev_by_field (model_regress.tests.ModelTests.test_get_next_prev_by_field) ... ok test_get_next_prev_by_field_unsaved (model_regress.tests.ModelTests.test_get_next_prev_by_field_unsaved) ... ok test_long_textfield (model_regress.tests.ModelTests.test_long_textfield) ... ok test_long_unicode_textfield (model_regress.tests.ModelTests.test_long_unicode_textfield) ... ok test_metaclass_can_access_attribute_dict (model_regress.tests.ModelTests.test_metaclass_can_access_attribute_dict) Model metaclasses have access to the class attribute dict in ... ok test_model_init_too_many_args (model_regress.tests.ModelTests.test_model_init_too_many_args) ... ok test_primary_key_foreign_key_types (model_regress.tests.ModelTests.test_primary_key_foreign_key_types) ... ok test_related_gte_lookup (model_regress.tests.ModelTests.test_related_gte_lookup) Regression test for #10153: foreign key __gte lookups. ... ok test_related_lte_lookup (model_regress.tests.ModelTests.test_related_lte_lookup) Regression test for #10153: foreign key __lte lookups. ... ok test_sql_insert_compiler_return_id_attribute (model_regress.tests.ModelTests.test_sql_insert_compiler_return_id_attribute) Regression test for #14019: SQLInsertCompiler.as_sql() failure ... ok test_timezones (model_regress.tests.ModelTests.test_timezones) ... skipped "Database doesn't support feature(s): supports_timezones" test_fast_delete_aggregation (delete.tests.FastDeleteTests.test_fast_delete_aggregation) ... ok test_fast_delete_all (delete.tests.FastDeleteTests.test_fast_delete_all) ... ok test_fast_delete_combined_relationships (delete.tests.FastDeleteTests.test_fast_delete_combined_relationships) ... ok test_fast_delete_empty_no_update_can_self_select (delete.tests.FastDeleteTests.test_fast_delete_empty_no_update_can_self_select) #25932 - Fast deleting on backends that don't have the ... ok test_fast_delete_fk (delete.tests.FastDeleteTests.test_fast_delete_fk) ... ok test_fast_delete_inheritance (delete.tests.FastDeleteTests.test_fast_delete_inheritance) ... ok test_fast_delete_instance_set_pk_none (delete.tests.FastDeleteTests.test_fast_delete_instance_set_pk_none) ... ok test_fast_delete_joined_qs (delete.tests.FastDeleteTests.test_fast_delete_joined_qs) ... ok test_fast_delete_large_batch (delete.tests.FastDeleteTests.test_fast_delete_large_batch) ... ok test_fast_delete_m2m (delete.tests.FastDeleteTests.test_fast_delete_m2m) ... ok test_fast_delete_qs (delete.tests.FastDeleteTests.test_fast_delete_qs) ... ok test_fast_delete_revm2m (delete.tests.FastDeleteTests.test_fast_delete_revm2m) ... ok test_annotation_values (queryset_pickle.tests.PickleabilityTestCase.test_annotation_values) ... ok test_annotation_values_list (queryset_pickle.tests.PickleabilityTestCase.test_annotation_values_list) ... ok test_annotation_with_callable_default (queryset_pickle.tests.PickleabilityTestCase.test_annotation_with_callable_default) ... ok test_binaryfield (queryset_pickle.tests.PickleabilityTestCase.test_binaryfield) ... ok test_datetime_callable_default_all (queryset_pickle.tests.PickleabilityTestCase.test_datetime_callable_default_all) ... ok test_datetime_callable_default_filter (queryset_pickle.tests.PickleabilityTestCase.test_datetime_callable_default_filter) ... ok test_doesnotexist_class (queryset_pickle.tests.PickleabilityTestCase.test_doesnotexist_class) ... ok test_doesnotexist_exception (queryset_pickle.tests.PickleabilityTestCase.test_doesnotexist_exception) ... ok test_filter_deferred (queryset_pickle.tests.PickleabilityTestCase.test_filter_deferred) ... ok test_filter_reverse_fk (queryset_pickle.tests.PickleabilityTestCase.test_filter_reverse_fk) ... ok test_forward_relatedobjectdoesnotexist_class (queryset_pickle.tests.PickleabilityTestCase.test_forward_relatedobjectdoesnotexist_class) ... ok test_manager_pickle (queryset_pickle.tests.PickleabilityTestCase.test_manager_pickle) ... ok test_missing_django_version_unpickling (queryset_pickle.tests.PickleabilityTestCase.test_missing_django_version_unpickling) #21430 -- Verifies a warning is raised for querysets that are ... ok test_model_pickle (queryset_pickle.tests.PickleabilityTestCase.test_model_pickle) A model not defined on module level is picklable. ... ok test_model_pickle_dynamic (queryset_pickle.tests.PickleabilityTestCase.test_model_pickle_dynamic) ... ok test_model_pickle_m2m (queryset_pickle.tests.PickleabilityTestCase.test_model_pickle_m2m) Test intentionally the automatically created through model. ... ok test_multipleobjectsreturned_class (queryset_pickle.tests.PickleabilityTestCase.test_multipleobjectsreturned_class) ... ok test_order_by_model_with_abstract_inheritance_and_meta_ordering (queryset_pickle.tests.PickleabilityTestCase.test_order_by_model_with_abstract_inheritance_and_meta_ordering) ... ok test_pickle_exists_kwargs_queryset_not_evaluated (queryset_pickle.tests.PickleabilityTestCase.test_pickle_exists_kwargs_queryset_not_evaluated) ... ok test_pickle_exists_queryset_not_evaluated (queryset_pickle.tests.PickleabilityTestCase.test_pickle_exists_queryset_not_evaluated) ... ok test_pickle_exists_queryset_still_usable (queryset_pickle.tests.PickleabilityTestCase.test_pickle_exists_queryset_still_usable) ... ok test_pickle_filteredrelation (queryset_pickle.tests.PickleabilityTestCase.test_pickle_filteredrelation) ... ok test_pickle_filteredrelation_m2m (queryset_pickle.tests.PickleabilityTestCase.test_pickle_filteredrelation_m2m) ... ok test_pickle_prefetch_queryset_not_evaluated (queryset_pickle.tests.PickleabilityTestCase.test_pickle_prefetch_queryset_not_evaluated) ... ok test_pickle_prefetch_queryset_still_usable (queryset_pickle.tests.PickleabilityTestCase.test_pickle_prefetch_queryset_still_usable) ... ok test_pickle_prefetch_queryset_usable_outside_of_prefetch (queryset_pickle.tests.PickleabilityTestCase.test_pickle_prefetch_queryset_usable_outside_of_prefetch) ... ok test_pickle_prefetch_related_idempotence (queryset_pickle.tests.PickleabilityTestCase.test_pickle_prefetch_related_idempotence) ... ok test_pickle_prefetch_related_with_m2m_and_objects_deletion (queryset_pickle.tests.PickleabilityTestCase.test_pickle_prefetch_related_with_m2m_and_objects_deletion) #24831 -- Cached properties on ManyToOneRel created in QuerySet.delete() ... ok test_pickle_subquery_queryset_not_evaluated (queryset_pickle.tests.PickleabilityTestCase.test_pickle_subquery_queryset_not_evaluated) ... ok test_related_field (queryset_pickle.tests.PickleabilityTestCase.test_related_field) ... ok test_reverse_one_to_one_relatedobjectdoesnotexist_class (queryset_pickle.tests.PickleabilityTestCase.test_reverse_one_to_one_relatedobjectdoesnotexist_class) ... ok test_specialized_queryset (queryset_pickle.tests.PickleabilityTestCase.test_specialized_queryset) ... ok test_standalone_method_as_default (queryset_pickle.tests.PickleabilityTestCase.test_standalone_method_as_default) ... ok test_staticmethod_as_default (queryset_pickle.tests.PickleabilityTestCase.test_staticmethod_as_default) ... ok test_string_as_default (queryset_pickle.tests.PickleabilityTestCase.test_string_as_default) ... ok test_unsupported_unpickle (queryset_pickle.tests.PickleabilityTestCase.test_unsupported_unpickle) #21430 -- Verifies a warning is raised for querysets that are ... ok test_bulk (delete.tests.DeletionTests.test_bulk) ... ok test_can_defer_constraint_checks (delete.tests.DeletionTests.test_can_defer_constraint_checks) ... ok test_cannot_defer_constraint_checks (delete.tests.DeletionTests.test_cannot_defer_constraint_checks) ... skipped 'Database has feature(s) can_defer_constraint_checks' test_delete_with_keeping_parents (delete.tests.DeletionTests.test_delete_with_keeping_parents) ... ok test_delete_with_keeping_parents_relationships (delete.tests.DeletionTests.test_delete_with_keeping_parents_relationships) ... ok test_deletion_order (delete.tests.DeletionTests.test_deletion_order) ... ok test_hidden_related (delete.tests.DeletionTests.test_hidden_related) ... ok test_instance_update (delete.tests.DeletionTests.test_instance_update) ... ok test_large_delete (delete.tests.DeletionTests.test_large_delete) ... ok test_large_delete_related (delete.tests.DeletionTests.test_large_delete_related) ... ok test_m2m (delete.tests.DeletionTests.test_m2m) ... ok test_model_delete_returns_num_rows (delete.tests.DeletionTests.test_model_delete_returns_num_rows) Model.delete() should return the number of deleted rows and a ... ok test_only_referenced_fields_selected (delete.tests.DeletionTests.test_only_referenced_fields_selected) Only referenced fields are selected during cascade deletion SELECT ... ok test_proxied_model_duplicate_queries (delete.tests.DeletionTests.test_proxied_model_duplicate_queries) #25685 - Deleting instances of a model with existing proxy ... ok test_queryset_delete_returns_num_rows (delete.tests.DeletionTests.test_queryset_delete_returns_num_rows) QuerySet.delete() should return the number of deleted rows and a ... ok test_relational_post_delete_signals_happen_before_parent_object (delete.tests.DeletionTests.test_relational_post_delete_signals_happen_before_parent_object) ... ok test_book_name_deutsh (test_utils.test_testcase.SetupTestDataIsolationTests.test_book_name_deutsh) ... ok test_book_name_french (test_utils.test_testcase.SetupTestDataIsolationTests.test_book_name_french) ... ok test_add_with_GET_args (admin_custom_urls.tests.AdminCustomUrlsTest.test_add_with_GET_args) Ensure GET on the add_view plus specifying a field value in the query ... ok test_admin_URLs_no_clash (admin_custom_urls.tests.AdminCustomUrlsTest.test_admin_URLs_no_clash) ... ok test_basic_add_GET (admin_custom_urls.tests.AdminCustomUrlsTest.test_basic_add_GET) Ensure GET on the add_view works. ... ok test_basic_add_POST (admin_custom_urls.tests.AdminCustomUrlsTest.test_basic_add_POST) Ensure POST on add_view works. ... ok test_post_save_add_redirect (admin_custom_urls.tests.AdminCustomUrlsTest.test_post_save_add_redirect) ModelAdmin.response_post_save_add() controls the redirection after ... ok test_post_save_change_redirect (admin_custom_urls.tests.AdminCustomUrlsTest.test_post_save_change_redirect) ModelAdmin.response_post_save_change() controls the redirection after ... ok test_post_url_continue (admin_custom_urls.tests.AdminCustomUrlsTest.test_post_url_continue) The ModelAdmin.response_add()'s parameter `post_url_continue` controls ... ok test_disallowed_database_connection (test_utils.test_testcase.TestTestCase.test_disallowed_database_connection) ... ok test_disallowed_database_queries (test_utils.test_testcase.TestTestCase.test_disallowed_database_queries) ... ok test_fixture_teardown_checks_constraints (test_utils.test_testcase.TestTestCase.test_fixture_teardown_checks_constraints) ... ok test_binaryfield_data_type (test_utils.test_testcase.TestDataTests.test_binaryfield_data_type) ... ok test_class_attribute_equality (test_utils.test_testcase.TestDataTests.test_class_attribute_equality) Class level test data is equal to instance level test data. ... ok test_class_attribute_identity (test_utils.test_testcase.TestDataTests.test_class_attribute_identity) Class level test data is not identical to instance level test data. ... ok test_identity_preservation (test_utils.test_testcase.TestDataTests.test_identity_preservation) Identity of test data is preserved between accesses. ... ok test_known_related_objects_identity_preservation (test_utils.test_testcase.TestDataTests.test_known_related_objects_identity_preservation) Known related objects identity is preserved. ... ok test_repr (test_utils.test_testcase.TestDataTests.test_repr) ... ok test_undeepcopyable (test_utils.test_testcase.TestDataTests.test_undeepcopyable) ... ok test_undeepcopyable_warning (test_utils.test_testcase.TestDataTests.test_undeepcopyable_warning) ... ok test_queries_cleared (test_utils.test_transactiontestcase.TransactionTestCaseDatabasesTests.test_queries_cleared) TransactionTestCase._pre_setup() clears the connections' queries_log ... ok test_failure (test_utils.tests.AssertNumQueriesContextManagerTests.test_failure) ... ok test_simple (test_utils.tests.AssertNumQueriesContextManagerTests.test_simple) ... ok test_with_client (test_utils.tests.AssertNumQueriesContextManagerTests.test_with_client) ... ok test_assert_num_queries (test_utils.tests.AssertNumQueriesTests.test_assert_num_queries) ... ok test_assert_num_queries_with_client (test_utils.tests.AssertNumQueriesTests.test_assert_num_queries_with_client) ... ok test_str_values (test_utils.tests.AssertQuerysetEqualDeprecationTests.test_str_values) ... ok test_str_values_warning (test_utils.tests.AssertQuerysetEqualDeprecationTests.test_str_values_warning) ... ok test_empty (test_utils.tests.AssertQuerysetEqualTests.test_empty) ... ok test_flat_values_list (test_utils.tests.AssertQuerysetEqualTests.test_flat_values_list) ... ok test_ordered (test_utils.tests.AssertQuerysetEqualTests.test_ordered) ... ok test_queryset (test_utils.tests.AssertQuerysetEqualTests.test_queryset) ... ok test_repeated_values (test_utils.tests.AssertQuerysetEqualTests.test_repeated_values) assertQuerysetEqual checks the number of appearance of each item ... ok test_repr_transform (test_utils.tests.AssertQuerysetEqualTests.test_repr_transform) ... ok test_transform (test_utils.tests.AssertQuerysetEqualTests.test_transform) ... ok test_undefined_order (test_utils.tests.AssertQuerysetEqualTests.test_undefined_order) ... ok test_unordered (test_utils.tests.AssertQuerysetEqualTests.test_unordered) ... ok test_different_using (test_utils.tests.CaptureOnCommitCallbacksTests.test_different_using) ... ok test_execute (test_utils.tests.CaptureOnCommitCallbacksTests.test_execute) ... ok test_no_arguments (test_utils.tests.CaptureOnCommitCallbacksTests.test_no_arguments) ... ok test_pre_callback (test_utils.tests.CaptureOnCommitCallbacksTests.test_pre_callback) ... ok test_using (test_utils.tests.CaptureOnCommitCallbacksTests.test_using) ... ok test_with_rolled_back_savepoint (test_utils.tests.CaptureOnCommitCallbacksTests.test_with_rolled_back_savepoint) ... ok test_auto (delete.tests.OnDeleteTests.test_auto) ... ok test_auto_nullable (delete.tests.OnDeleteTests.test_auto_nullable) ... ok test_cascade (delete.tests.OnDeleteTests.test_cascade) ... ok test_cascade_from_child (delete.tests.OnDeleteTests.test_cascade_from_child) ... ok test_cascade_from_parent (delete.tests.OnDeleteTests.test_cascade_from_parent) ... ok test_cascade_nullable (delete.tests.OnDeleteTests.test_cascade_nullable) ... ok test_do_nothing (delete.tests.OnDeleteTests.test_do_nothing) ... ok test_do_nothing_qscount (delete.tests.OnDeleteTests.test_do_nothing_qscount) A models.DO_NOTHING relation doesn't trigger a query. ... ok test_inheritance_cascade_down (delete.tests.OnDeleteTests.test_inheritance_cascade_down) ... ok test_inheritance_cascade_up (delete.tests.OnDeleteTests.test_inheritance_cascade_up) ... ok test_non_callable (delete.tests.OnDeleteTests.test_non_callable) ... ok test_o2o_setnull (delete.tests.OnDeleteTests.test_o2o_setnull) ... ok test_protect (delete.tests.OnDeleteTests.test_protect) ... ok test_protect_multiple (delete.tests.OnDeleteTests.test_protect_multiple) ... ok test_protect_path (delete.tests.OnDeleteTests.test_protect_path) ... ok test_restrict (delete.tests.OnDeleteTests.test_restrict) ... ok test_restrict_gfk_no_fast_delete (delete.tests.OnDeleteTests.test_restrict_gfk_no_fast_delete) ... ok test_restrict_multiple (delete.tests.OnDeleteTests.test_restrict_multiple) ... ok test_restrict_path_cascade_direct (delete.tests.OnDeleteTests.test_restrict_path_cascade_direct) ... ok test_restrict_path_cascade_indirect (delete.tests.OnDeleteTests.test_restrict_path_cascade_indirect) ... ok test_restrict_path_cascade_indirect_diamond (delete.tests.OnDeleteTests.test_restrict_path_cascade_indirect_diamond) ... ok test_setdefault (delete.tests.OnDeleteTests.test_setdefault) ... ok test_setdefault_none (delete.tests.OnDeleteTests.test_setdefault_none) ... ok test_setnull (delete.tests.OnDeleteTests.test_setnull) ... ok test_setnull_from_child (delete.tests.OnDeleteTests.test_setnull_from_child) ... ok test_setnull_from_parent (delete.tests.OnDeleteTests.test_setnull_from_parent) ... ok test_setvalue (delete.tests.OnDeleteTests.test_setvalue) ... ok test_failure (test_utils.tests.CaptureQueriesContextManagerTests.test_failure) ... ok test_nested (test_utils.tests.CaptureQueriesContextManagerTests.test_nested) ... ok test_simple (test_utils.tests.CaptureQueriesContextManagerTests.test_simple) ... ok test_with_client (test_utils.tests.CaptureQueriesContextManagerTests.test_with_client) ... ok test_within (test_utils.tests.CaptureQueriesContextManagerTests.test_within) ... ok test_fixtures_are_skipped (test_utils.tests.SkippingExtraTests.test_fixtures_are_skipped) ... skipped 'Fixture loading should not be performed for skipped tests.' test_missing_default_databases (test_utils.tests.SkippingClassTestCase.test_missing_default_databases) ... ok test_skip_class_unless_db_feature (test_utils.tests.SkippingClassTestCase.test_skip_class_unless_db_feature) ... ok test_failure_in_setUpTestData_should_rollback_transaction (test_utils.tests.TestBadSetUpTestData.test_failure_in_setUpTestData_should_rollback_transaction) ... ok test_intermediary (m2m_intermediary.tests.M2MIntermediaryTests.test_intermediary) ... ok test_verbose_name (i18n.contenttypes.tests.ContentTypeTests.test_verbose_name) ... ok test_language_not_saved_to_session (i18n.tests.LocaleMiddlewareTests.test_language_not_saved_to_session) The Current language isno' automatically saved to the session on every ... ok test_streaming_response (i18n.tests.LocaleMiddlewareTests.test_streaming_response) ... ok test_lazy (i18n.tests.TestModels.test_lazy) ... ok test_safestr (i18n.tests.TestModels.test_safestr) ... ok test_managers (custom_managers.tests.TestCars.test_managers) ... ok test_createcachetable_observes_database_router (cache.tests.CreateCacheTableForDBCacheTests.test_createcachetable_observes_database_router) ... ok test_delete_one_to_one_manager (custom_managers.tests.CustomManagersRegressTestCase.test_delete_one_to_one_manager) ... ok test_delete_related_on_filtered_manager (custom_managers.tests.CustomManagersRegressTestCase.test_delete_related_on_filtered_manager) Deleting related objects should also not be distracted by a ... ok test_filtered_default_manager (custom_managers.tests.CustomManagersRegressTestCase.test_filtered_default_manager) Even though the default manager filters out some records, ... ok test_queryset_with_custom_init (custom_managers.tests.CustomManagersRegressTestCase.test_queryset_with_custom_init) BaseManager.get_queryset() should use kwargs rather than args to allow ... ok test_refresh_from_db_when_default_manager_filters (custom_managers.tests.CustomManagersRegressTestCase.test_refresh_from_db_when_default_manager_filters) Model.refresh_from_db() works for instances hidden by the default ... ok test_save_clears_annotations_from_base_manager (custom_managers.tests.CustomManagersRegressTestCase.test_save_clears_annotations_from_base_manager) Model.save() clears annotations from the base manager. ... ok test_abstract_model_with_custom_manager_name (custom_managers.tests.CustomManagerTests.test_abstract_model_with_custom_manager_name) A custom manager may be defined on an abstract model. ... ok test_custom_manager_basic (custom_managers.tests.CustomManagerTests.test_custom_manager_basic) Test a custom Manager method. ... ok test_deconstruct_as_manager (custom_managers.tests.CustomManagerTests.test_deconstruct_as_manager) ... ok test_deconstruct_default (custom_managers.tests.CustomManagerTests.test_deconstruct_default) ... ok test_deconstruct_from_queryset (custom_managers.tests.CustomManagerTests.test_deconstruct_from_queryset) ... ok test_deconstruct_from_queryset_failing (custom_managers.tests.CustomManagerTests.test_deconstruct_from_queryset_failing) ... ok test_filtering (custom_managers.tests.CustomManagerTests.test_filtering) Custom managers respond to usual filtering methods ... ok test_fk_related_manager (custom_managers.tests.CustomManagerTests.test_fk_related_manager) ... ok test_gfk_related_manager (custom_managers.tests.CustomManagerTests.test_gfk_related_manager) ... ok test_init_args (custom_managers.tests.CustomManagerTests.test_init_args) The custom manager __init__() argument has been set. ... ok test_m2m_related_manager (custom_managers.tests.CustomManagerTests.test_m2m_related_manager) ... ok test_manager_attributes (custom_managers.tests.CustomManagerTests.test_manager_attributes) Custom manager method is only available on the manager and not on ... ok test_manager_honors_queryset_only (custom_managers.tests.CustomManagerTests.test_manager_honors_queryset_only) ... ok test_manager_use_queryset_methods (custom_managers.tests.CustomManagerTests.test_manager_use_queryset_methods) Custom manager will use the queryset methods ... ok test_no_objects (custom_managers.tests.CustomManagerTests.test_no_objects) The default manager, "objects", doesn't exist, because a custom one ... ok test_queryset_and_manager (custom_managers.tests.CustomManagerTests.test_queryset_and_manager) Queryset method doesn't override the custom manager method. ... ok test_queryset_copied_to_default (custom_managers.tests.CustomManagerTests.test_queryset_copied_to_default) The methods of a custom QuerySet are properly copied onto the ... ok test_related_manager (custom_managers.tests.CustomManagerTests.test_related_manager) The related managers extend the default manager. ... ok test_removal_through_default_fk_related_manager (custom_managers.tests.CustomManagerTests.test_removal_through_default_fk_related_manager) ... ok test_removal_through_default_gfk_related_manager (custom_managers.tests.CustomManagerTests.test_removal_through_default_gfk_related_manager) ... ok test_removal_through_default_m2m_related_manager (custom_managers.tests.CustomManagerTests.test_removal_through_default_m2m_related_manager) ... ok test_removal_through_specified_fk_related_manager (custom_managers.tests.CustomManagerTests.test_removal_through_specified_fk_related_manager) ... ok test_removal_through_specified_gfk_related_manager (custom_managers.tests.CustomManagerTests.test_removal_through_specified_gfk_related_manager) ... ok test_removal_through_specified_m2m_related_manager (custom_managers.tests.CustomManagerTests.test_removal_through_specified_m2m_related_manager) ... ok test_slow_removal_through_default_fk_related_manager (custom_managers.tests.CustomManagerTests.test_slow_removal_through_default_fk_related_manager) ... ok test_slow_removal_through_default_gfk_related_manager (custom_managers.tests.CustomManagerTests.test_slow_removal_through_default_gfk_related_manager) ... ok test_slow_removal_through_specified_fk_related_manager (custom_managers.tests.CustomManagerTests.test_slow_removal_through_specified_fk_related_manager) ... ok test_slow_removal_through_specified_gfk_related_manager (custom_managers.tests.CustomManagerTests.test_slow_removal_through_specified_gfk_related_manager) ... ok test_form_url_present_in_context (admin_views.tests.UserAdminTest.test_form_url_present_in_context) ... ok test_password_mismatch (admin_views.tests.UserAdminTest.test_password_mismatch) ... ok test_save_add_another_button (admin_views.tests.UserAdminTest.test_save_add_another_button) ... ok test_save_button (admin_views.tests.UserAdminTest.test_save_button) ... ok test_save_continue_editing_button (admin_views.tests.UserAdminTest.test_save_continue_editing_button) ... ok test_user_fk_add_popup (admin_views.tests.UserAdminTest.test_user_fk_add_popup) User addition through a FK popup should return the appropriate JavaScript response. ... ok test_user_fk_change_popup (admin_views.tests.UserAdminTest.test_user_fk_change_popup) User change through a FK popup should return the appropriate JavaScript response. ... ok test_user_fk_delete_popup (admin_views.tests.UserAdminTest.test_user_fk_delete_popup) User deletion through a FK popup should return the appropriate JavaScript response. ... ok test_user_permission_performance (admin_views.tests.UserAdminTest.test_user_permission_performance) ... ok test_add (cache.tests.MemcachedCacheTests.test_add) ... skipped 'MemcachedCache backend not configured' test_add_fail_on_pickleerror (cache.tests.MemcachedCacheTests.test_add_fail_on_pickleerror) ... skipped 'MemcachedCache backend not configured' test_binary_string (cache.tests.MemcachedCacheTests.test_binary_string) ... skipped 'MemcachedCache backend not configured' test_cache_read_for_model_instance (cache.tests.MemcachedCacheTests.test_cache_read_for_model_instance) ... skipped 'MemcachedCache backend not configured' test_cache_read_for_model_instance_with_deferred (cache.tests.MemcachedCacheTests.test_cache_read_for_model_instance_with_deferred) ... skipped 'MemcachedCache backend not configured' test_cache_versioning_add (cache.tests.MemcachedCacheTests.test_cache_versioning_add) ... skipped 'MemcachedCache backend not configured' test_cache_versioning_delete (cache.tests.MemcachedCacheTests.test_cache_versioning_delete) ... skipped 'MemcachedCache backend not configured' test_cache_versioning_get_set (cache.tests.MemcachedCacheTests.test_cache_versioning_get_set) ... skipped 'MemcachedCache backend not configured' test_cache_versioning_get_set_many (cache.tests.MemcachedCacheTests.test_cache_versioning_get_set_many) ... skipped 'MemcachedCache backend not configured' test_cache_versioning_has_key (cache.tests.MemcachedCacheTests.test_cache_versioning_has_key) ... skipped 'MemcachedCache backend not configured' test_cache_versioning_incr_decr (cache.tests.MemcachedCacheTests.test_cache_versioning_incr_decr) ... skipped 'MemcachedCache backend not configured' test_cache_write_for_model_instance_with_deferred (cache.tests.MemcachedCacheTests.test_cache_write_for_model_instance_with_deferred) ... skipped 'MemcachedCache backend not configured' test_cache_write_unpicklable_object (cache.tests.MemcachedCacheTests.test_cache_write_unpicklable_object) ... skipped 'MemcachedCache backend not configured' test_clear (cache.tests.MemcachedCacheTests.test_clear) ... skipped 'MemcachedCache backend not configured' test_close (cache.tests.MemcachedCacheTests.test_close) ... skipped 'MemcachedCache backend not configured' test_cull (cache.tests.MemcachedCacheTests.test_cull) ... skipped 'MemcachedCache backend not configured' test_cull_delete_when_store_empty (cache.tests.MemcachedCacheTests.test_cull_delete_when_store_empty) ... skipped 'MemcachedCache backend not configured' test_custom_key_func (cache.tests.MemcachedCacheTests.test_custom_key_func) ... skipped 'MemcachedCache backend not configured' test_data_types (cache.tests.MemcachedCacheTests.test_data_types) ... skipped 'MemcachedCache backend not configured' test_decr (cache.tests.MemcachedCacheTests.test_decr) ... skipped 'MemcachedCache backend not configured' test_decr_version (cache.tests.MemcachedCacheTests.test_decr_version) ... skipped 'MemcachedCache backend not configured' test_default_far_future_timeout (cache.tests.MemcachedCacheTests.test_default_far_future_timeout) ... skipped 'MemcachedCache backend not configured' test_default_never_expiring_timeout (cache.tests.MemcachedCacheTests.test_default_never_expiring_timeout) ... skipped 'MemcachedCache backend not configured' test_default_used_when_none_is_set (cache.tests.MemcachedCacheTests.test_default_used_when_none_is_set) python-memcached doesn't support default in get() so this test ... skipped 'MemcachedCache backend not configured' test_delete (cache.tests.MemcachedCacheTests.test_delete) ... skipped 'MemcachedCache backend not configured' test_delete_many (cache.tests.MemcachedCacheTests.test_delete_many) ... skipped 'MemcachedCache backend not configured' test_delete_nonexistent (cache.tests.MemcachedCacheTests.test_delete_nonexistent) ... skipped 'MemcachedCache backend not configured' test_expiration (cache.tests.MemcachedCacheTests.test_expiration) ... skipped 'MemcachedCache backend not configured' test_float_timeout (cache.tests.MemcachedCacheTests.test_float_timeout) ... skipped 'MemcachedCache backend not configured' test_forever_timeout (cache.tests.MemcachedCacheTests.test_forever_timeout) Passing in None into timeout results in a value that is cached forever ... skipped 'MemcachedCache backend not configured' test_get_many (cache.tests.MemcachedCacheTests.test_get_many) ... skipped 'MemcachedCache backend not configured' test_get_or_set (cache.tests.MemcachedCacheTests.test_get_or_set) ... skipped 'MemcachedCache backend not configured' test_get_or_set_callable (cache.tests.MemcachedCacheTests.test_get_or_set_callable) ... skipped 'MemcachedCache backend not configured' test_get_or_set_racing (cache.tests.MemcachedCacheTests.test_get_or_set_racing) ... skipped 'MemcachedCache backend not configured' test_get_or_set_version (cache.tests.MemcachedCacheTests.test_get_or_set_version) ... skipped 'MemcachedCache backend not configured' test_has_key (cache.tests.MemcachedCacheTests.test_has_key) ... skipped 'MemcachedCache backend not configured' test_in (cache.tests.MemcachedCacheTests.test_in) ... skipped 'MemcachedCache backend not configured' test_incr (cache.tests.MemcachedCacheTests.test_incr) ... skipped 'MemcachedCache backend not configured' test_incr_version (cache.tests.MemcachedCacheTests.test_incr_version) ... skipped 'MemcachedCache backend not configured' test_invalid_key_characters (cache.tests.MemcachedCacheTests.test_invalid_key_characters) ... skipped 'MemcachedCache backend not configured' test_invalid_key_length (cache.tests.MemcachedCacheTests.test_invalid_key_length) ... skipped 'MemcachedCache backend not configured' test_location_multiple_servers (cache.tests.MemcachedCacheTests.test_location_multiple_servers) ... skipped 'MemcachedCache backend not configured' test_long_timeout (cache.tests.MemcachedCacheTests.test_long_timeout) Follow memcached's convention where a timeout greater than 30 days is ... skipped 'MemcachedCache backend not configured' test_memcached_deletes_key_on_failed_set (cache.tests.MemcachedCacheTests.test_memcached_deletes_key_on_failed_set) ... skipped 'MemcachedCache backend not configured' test_memcached_options (cache.tests.MemcachedCacheTests.test_memcached_options) ... skipped 'MemcachedCache backend not configured' test_memcached_uses_highest_pickle_version (cache.tests.MemcachedCacheTests.test_memcached_uses_highest_pickle_version) ... skipped 'MemcachedCache backend not configured' test_non_existent (cache.tests.MemcachedCacheTests.test_non_existent) Nonexistent cache keys return as None/default. ... skipped 'MemcachedCache backend not configured' test_prefix (cache.tests.MemcachedCacheTests.test_prefix) ... skipped 'MemcachedCache backend not configured' test_set_fail_on_pickleerror (cache.tests.MemcachedCacheTests.test_set_fail_on_pickleerror) ... skipped 'MemcachedCache backend not configured' test_set_many (cache.tests.MemcachedCacheTests.test_set_many) ... skipped 'MemcachedCache backend not configured' test_set_many_expiration (cache.tests.MemcachedCacheTests.test_set_many_expiration) ... skipped 'MemcachedCache backend not configured' test_set_many_returns_empty_list_on_success (cache.tests.MemcachedCacheTests.test_set_many_returns_empty_list_on_success) set_many() returns an empty list when all keys are inserted. ... skipped 'MemcachedCache backend not configured' test_set_many_returns_failing_keys (cache.tests.MemcachedCacheTests.test_set_many_returns_failing_keys) ... skipped 'MemcachedCache backend not configured' test_simple (cache.tests.MemcachedCacheTests.test_simple) ... skipped 'MemcachedCache backend not configured' test_touch (cache.tests.MemcachedCacheTests.test_touch) ... skipped 'MemcachedCache backend not configured' test_unicode (cache.tests.MemcachedCacheTests.test_unicode) ... skipped 'MemcachedCache backend not configured' test_zero_cull (cache.tests.MemcachedCacheTests.test_zero_cull) ... skipped 'MemcachedCache backend not configured' test_zero_timeout (cache.tests.MemcachedCacheTests.test_zero_timeout) Passing in zero into timeout results in a value that is not cached ... skipped 'MemcachedCache backend not configured' test_add (cache.tests.PyLibMCCacheTests.test_add) ... skipped 'PyLibMCCache backend not configured' test_add_fail_on_pickleerror (cache.tests.PyLibMCCacheTests.test_add_fail_on_pickleerror) ... skipped 'PyLibMCCache backend not configured' test_binary_string (cache.tests.PyLibMCCacheTests.test_binary_string) ... skipped 'PyLibMCCache backend not configured' test_cache_read_for_model_instance (cache.tests.PyLibMCCacheTests.test_cache_read_for_model_instance) ... skipped 'PyLibMCCache backend not configured' test_cache_read_for_model_instance_with_deferred (cache.tests.PyLibMCCacheTests.test_cache_read_for_model_instance_with_deferred) ... skipped 'PyLibMCCache backend not configured' test_cache_versioning_add (cache.tests.PyLibMCCacheTests.test_cache_versioning_add) ... skipped 'PyLibMCCache backend not configured' test_cache_versioning_delete (cache.tests.PyLibMCCacheTests.test_cache_versioning_delete) ... skipped 'PyLibMCCache backend not configured' test_cache_versioning_get_set (cache.tests.PyLibMCCacheTests.test_cache_versioning_get_set) ... skipped 'PyLibMCCache backend not configured' test_cache_versioning_get_set_many (cache.tests.PyLibMCCacheTests.test_cache_versioning_get_set_many) ... skipped 'PyLibMCCache backend not configured' test_cache_versioning_has_key (cache.tests.PyLibMCCacheTests.test_cache_versioning_has_key) ... skipped 'PyLibMCCache backend not configured' test_cache_versioning_incr_decr (cache.tests.PyLibMCCacheTests.test_cache_versioning_incr_decr) ... skipped 'PyLibMCCache backend not configured' test_cache_write_for_model_instance_with_deferred (cache.tests.PyLibMCCacheTests.test_cache_write_for_model_instance_with_deferred) ... skipped 'PyLibMCCache backend not configured' test_cache_write_unpicklable_object (cache.tests.PyLibMCCacheTests.test_cache_write_unpicklable_object) ... skipped 'PyLibMCCache backend not configured' test_clear (cache.tests.PyLibMCCacheTests.test_clear) ... skipped 'PyLibMCCache backend not configured' test_close (cache.tests.PyLibMCCacheTests.test_close) ... skipped 'PyLibMCCache backend not configured' test_cull (cache.tests.PyLibMCCacheTests.test_cull) ... skipped 'PyLibMCCache backend not configured' test_cull_delete_when_store_empty (cache.tests.PyLibMCCacheTests.test_cull_delete_when_store_empty) ... skipped 'PyLibMCCache backend not configured' test_custom_key_func (cache.tests.PyLibMCCacheTests.test_custom_key_func) ... skipped 'PyLibMCCache backend not configured' test_data_types (cache.tests.PyLibMCCacheTests.test_data_types) ... skipped 'PyLibMCCache backend not configured' test_decr (cache.tests.PyLibMCCacheTests.test_decr) ... skipped 'PyLibMCCache backend not configured' test_decr_version (cache.tests.PyLibMCCacheTests.test_decr_version) ... skipped 'PyLibMCCache backend not configured' test_default_far_future_timeout (cache.tests.PyLibMCCacheTests.test_default_far_future_timeout) ... skipped 'PyLibMCCache backend not configured' test_default_never_expiring_timeout (cache.tests.PyLibMCCacheTests.test_default_never_expiring_timeout) ... skipped 'PyLibMCCache backend not configured' test_default_used_when_none_is_set (cache.tests.PyLibMCCacheTests.test_default_used_when_none_is_set) If None is cached, get() returns it instead of the default. ... skipped 'PyLibMCCache backend not configured' test_delete (cache.tests.PyLibMCCacheTests.test_delete) ... skipped 'PyLibMCCache backend not configured' test_delete_many (cache.tests.PyLibMCCacheTests.test_delete_many) ... skipped 'PyLibMCCache backend not configured' test_delete_nonexistent (cache.tests.PyLibMCCacheTests.test_delete_nonexistent) ... skipped 'PyLibMCCache backend not configured' test_expiration (cache.tests.PyLibMCCacheTests.test_expiration) ... skipped 'PyLibMCCache backend not configured' test_float_timeout (cache.tests.PyLibMCCacheTests.test_float_timeout) ... skipped 'PyLibMCCache backend not configured' test_forever_timeout (cache.tests.PyLibMCCacheTests.test_forever_timeout) Passing in None into timeout results in a value that is cached forever ... skipped 'PyLibMCCache backend not configured' test_get_many (cache.tests.PyLibMCCacheTests.test_get_many) ... skipped 'PyLibMCCache backend not configured' test_get_or_set (cache.tests.PyLibMCCacheTests.test_get_or_set) ... skipped 'PyLibMCCache backend not configured' test_get_or_set_callable (cache.tests.PyLibMCCacheTests.test_get_or_set_callable) ... skipped 'PyLibMCCache backend not configured' test_get_or_set_racing (cache.tests.PyLibMCCacheTests.test_get_or_set_racing) ... skipped 'PyLibMCCache backend not configured' test_get_or_set_version (cache.tests.PyLibMCCacheTests.test_get_or_set_version) ... skipped 'PyLibMCCache backend not configured' test_has_key (cache.tests.PyLibMCCacheTests.test_has_key) ... skipped 'PyLibMCCache backend not configured' test_in (cache.tests.PyLibMCCacheTests.test_in) ... skipped 'PyLibMCCache backend not configured' test_incr (cache.tests.PyLibMCCacheTests.test_incr) ... skipped 'PyLibMCCache backend not configured' test_incr_version (cache.tests.PyLibMCCacheTests.test_incr_version) ... skipped 'PyLibMCCache backend not configured' test_invalid_key_characters (cache.tests.PyLibMCCacheTests.test_invalid_key_characters) ... skipped 'PyLibMCCache backend not configured' test_invalid_key_length (cache.tests.PyLibMCCacheTests.test_invalid_key_length) ... skipped 'PyLibMCCache backend not configured' test_location_multiple_servers (cache.tests.PyLibMCCacheTests.test_location_multiple_servers) ... skipped 'PyLibMCCache backend not configured' test_long_timeout (cache.tests.PyLibMCCacheTests.test_long_timeout) Follow memcached's convention where a timeout greater than 30 days is ... skipped 'PyLibMCCache backend not configured' test_memcached_deletes_key_on_failed_set (cache.tests.PyLibMCCacheTests.test_memcached_deletes_key_on_failed_set) ... skipped 'PyLibMCCache backend not configured' test_non_existent (cache.tests.PyLibMCCacheTests.test_non_existent) Nonexistent cache keys return as None/default. ... skipped 'PyLibMCCache backend not configured' test_prefix (cache.tests.PyLibMCCacheTests.test_prefix) ... skipped 'PyLibMCCache backend not configured' test_pylibmc_client_servers (cache.tests.PyLibMCCacheTests.test_pylibmc_client_servers) ... skipped 'PyLibMCCache backend not configured' test_pylibmc_options (cache.tests.PyLibMCCacheTests.test_pylibmc_options) ... skipped 'PyLibMCCache backend not configured' test_set_fail_on_pickleerror (cache.tests.PyLibMCCacheTests.test_set_fail_on_pickleerror) ... skipped 'PyLibMCCache backend not configured' test_set_many (cache.tests.PyLibMCCacheTests.test_set_many) ... skipped 'PyLibMCCache backend not configured' test_set_many_expiration (cache.tests.PyLibMCCacheTests.test_set_many_expiration) ... skipped 'PyLibMCCache backend not configured' test_set_many_returns_empty_list_on_success (cache.tests.PyLibMCCacheTests.test_set_many_returns_empty_list_on_success) set_many() returns an empty list when all keys are inserted. ... skipped 'PyLibMCCache backend not configured' test_set_many_returns_failing_keys (cache.tests.PyLibMCCacheTests.test_set_many_returns_failing_keys) ... skipped 'PyLibMCCache backend not configured' test_simple (cache.tests.PyLibMCCacheTests.test_simple) ... skipped 'PyLibMCCache backend not configured' test_touch (cache.tests.PyLibMCCacheTests.test_touch) ... skipped 'PyLibMCCache backend not configured' test_unicode (cache.tests.PyLibMCCacheTests.test_unicode) ... skipped 'PyLibMCCache backend not configured' test_zero_cull (cache.tests.PyLibMCCacheTests.test_zero_cull) ... skipped 'PyLibMCCache backend not configured' test_zero_timeout (cache.tests.PyLibMCCacheTests.test_zero_timeout) Passing in zero into timeout results in a value that is not cached ... skipped 'PyLibMCCache backend not configured' test_add (cache.tests.PyMemcacheCacheTests.test_add) ... skipped 'PyMemcacheCache backend not configured' test_add_fail_on_pickleerror (cache.tests.PyMemcacheCacheTests.test_add_fail_on_pickleerror) ... skipped 'PyMemcacheCache backend not configured' test_binary_string (cache.tests.PyMemcacheCacheTests.test_binary_string) ... skipped 'PyMemcacheCache backend not configured' test_cache_read_for_model_instance (cache.tests.PyMemcacheCacheTests.test_cache_read_for_model_instance) ... skipped 'PyMemcacheCache backend not configured' test_cache_read_for_model_instance_with_deferred (cache.tests.PyMemcacheCacheTests.test_cache_read_for_model_instance_with_deferred) ... skipped 'PyMemcacheCache backend not configured' test_cache_versioning_add (cache.tests.PyMemcacheCacheTests.test_cache_versioning_add) ... skipped 'PyMemcacheCache backend not configured' test_cache_versioning_delete (cache.tests.PyMemcacheCacheTests.test_cache_versioning_delete) ... skipped 'PyMemcacheCache backend not configured' test_cache_versioning_get_set (cache.tests.PyMemcacheCacheTests.test_cache_versioning_get_set) ... skipped 'PyMemcacheCache backend not configured' test_cache_versioning_get_set_many (cache.tests.PyMemcacheCacheTests.test_cache_versioning_get_set_many) ... skipped 'PyMemcacheCache backend not configured' test_cache_versioning_has_key (cache.tests.PyMemcacheCacheTests.test_cache_versioning_has_key) ... skipped 'PyMemcacheCache backend not configured' test_cache_versioning_incr_decr (cache.tests.PyMemcacheCacheTests.test_cache_versioning_incr_decr) ... skipped 'PyMemcacheCache backend not configured' test_cache_write_for_model_instance_with_deferred (cache.tests.PyMemcacheCacheTests.test_cache_write_for_model_instance_with_deferred) ... skipped 'PyMemcacheCache backend not configured' test_cache_write_unpicklable_object (cache.tests.PyMemcacheCacheTests.test_cache_write_unpicklable_object) ... skipped 'PyMemcacheCache backend not configured' test_clear (cache.tests.PyMemcacheCacheTests.test_clear) ... skipped 'PyMemcacheCache backend not configured' test_close (cache.tests.PyMemcacheCacheTests.test_close) ... skipped 'PyMemcacheCache backend not configured' test_cull (cache.tests.PyMemcacheCacheTests.test_cull) ... skipped 'PyMemcacheCache backend not configured' test_cull_delete_when_store_empty (cache.tests.PyMemcacheCacheTests.test_cull_delete_when_store_empty) ... skipped 'PyMemcacheCache backend not configured' test_custom_key_func (cache.tests.PyMemcacheCacheTests.test_custom_key_func) ... skipped 'PyMemcacheCache backend not configured' test_data_types (cache.tests.PyMemcacheCacheTests.test_data_types) ... skipped 'PyMemcacheCache backend not configured' test_decr (cache.tests.PyMemcacheCacheTests.test_decr) ... skipped 'PyMemcacheCache backend not configured' test_decr_version (cache.tests.PyMemcacheCacheTests.test_decr_version) ... skipped 'PyMemcacheCache backend not configured' test_default_far_future_timeout (cache.tests.PyMemcacheCacheTests.test_default_far_future_timeout) ... skipped 'PyMemcacheCache backend not configured' test_default_never_expiring_timeout (cache.tests.PyMemcacheCacheTests.test_default_never_expiring_timeout) ... skipped 'PyMemcacheCache backend not configured' test_default_used_when_none_is_set (cache.tests.PyMemcacheCacheTests.test_default_used_when_none_is_set) If None is cached, get() returns it instead of the default. ... skipped 'PyMemcacheCache backend not configured' test_delete (cache.tests.PyMemcacheCacheTests.test_delete) ... skipped 'PyMemcacheCache backend not configured' test_delete_many (cache.tests.PyMemcacheCacheTests.test_delete_many) ... skipped 'PyMemcacheCache backend not configured' test_delete_nonexistent (cache.tests.PyMemcacheCacheTests.test_delete_nonexistent) ... skipped 'PyMemcacheCache backend not configured' test_expiration (cache.tests.PyMemcacheCacheTests.test_expiration) ... skipped 'PyMemcacheCache backend not configured' test_float_timeout (cache.tests.PyMemcacheCacheTests.test_float_timeout) ... skipped 'PyMemcacheCache backend not configured' test_forever_timeout (cache.tests.PyMemcacheCacheTests.test_forever_timeout) Passing in None into timeout results in a value that is cached forever ... skipped 'PyMemcacheCache backend not configured' test_get_many (cache.tests.PyMemcacheCacheTests.test_get_many) ... skipped 'PyMemcacheCache backend not configured' test_get_or_set (cache.tests.PyMemcacheCacheTests.test_get_or_set) ... skipped 'PyMemcacheCache backend not configured' test_get_or_set_callable (cache.tests.PyMemcacheCacheTests.test_get_or_set_callable) ... skipped 'PyMemcacheCache backend not configured' test_get_or_set_racing (cache.tests.PyMemcacheCacheTests.test_get_or_set_racing) ... skipped 'PyMemcacheCache backend not configured' test_get_or_set_version (cache.tests.PyMemcacheCacheTests.test_get_or_set_version) ... skipped 'PyMemcacheCache backend not configured' test_has_key (cache.tests.PyMemcacheCacheTests.test_has_key) ... skipped 'PyMemcacheCache backend not configured' test_in (cache.tests.PyMemcacheCacheTests.test_in) ... skipped 'PyMemcacheCache backend not configured' test_incr (cache.tests.PyMemcacheCacheTests.test_incr) ... skipped 'PyMemcacheCache backend not configured' test_incr_version (cache.tests.PyMemcacheCacheTests.test_incr_version) ... skipped 'PyMemcacheCache backend not configured' test_invalid_key_characters (cache.tests.PyMemcacheCacheTests.test_invalid_key_characters) ... skipped 'PyMemcacheCache backend not configured' test_invalid_key_length (cache.tests.PyMemcacheCacheTests.test_invalid_key_length) ... skipped 'PyMemcacheCache backend not configured' test_location_multiple_servers (cache.tests.PyMemcacheCacheTests.test_location_multiple_servers) ... skipped 'PyMemcacheCache backend not configured' test_long_timeout (cache.tests.PyMemcacheCacheTests.test_long_timeout) Follow memcached's convention where a timeout greater than 30 days is ... skipped 'PyMemcacheCache backend not configured' test_memcached_deletes_key_on_failed_set (cache.tests.PyMemcacheCacheTests.test_memcached_deletes_key_on_failed_set) ... skipped 'PyMemcacheCache backend not configured' test_non_existent (cache.tests.PyMemcacheCacheTests.test_non_existent) Nonexistent cache keys return as None/default. ... skipped 'PyMemcacheCache backend not configured' test_prefix (cache.tests.PyMemcacheCacheTests.test_prefix) ... skipped 'PyMemcacheCache backend not configured' test_pymemcache_highest_pickle_version (cache.tests.PyMemcacheCacheTests.test_pymemcache_highest_pickle_version) ... skipped 'PyMemcacheCache backend not configured' test_pymemcache_options (cache.tests.PyMemcacheCacheTests.test_pymemcache_options) ... skipped 'PyMemcacheCache backend not configured' test_set_fail_on_pickleerror (cache.tests.PyMemcacheCacheTests.test_set_fail_on_pickleerror) ... skipped 'PyMemcacheCache backend not configured' test_set_many (cache.tests.PyMemcacheCacheTests.test_set_many) ... skipped 'PyMemcacheCache backend not configured' test_set_many_expiration (cache.tests.PyMemcacheCacheTests.test_set_many_expiration) ... skipped 'PyMemcacheCache backend not configured' test_set_many_returns_empty_list_on_success (cache.tests.PyMemcacheCacheTests.test_set_many_returns_empty_list_on_success) set_many() returns an empty list when all keys are inserted. ... skipped 'PyMemcacheCache backend not configured' test_set_many_returns_failing_keys (cache.tests.PyMemcacheCacheTests.test_set_many_returns_failing_keys) ... skipped 'PyMemcacheCache backend not configured' test_simple (cache.tests.PyMemcacheCacheTests.test_simple) ... skipped 'PyMemcacheCache backend not configured' test_touch (cache.tests.PyMemcacheCacheTests.test_touch) ... skipped 'PyMemcacheCache backend not configured' test_unicode (cache.tests.PyMemcacheCacheTests.test_unicode) ... skipped 'PyMemcacheCache backend not configured' test_zero_cull (cache.tests.PyMemcacheCacheTests.test_zero_cull) ... skipped 'PyMemcacheCache backend not configured' test_zero_timeout (cache.tests.PyMemcacheCacheTests.test_zero_timeout) Passing in zero into timeout results in a value that is not cached ... skipped 'PyMemcacheCache backend not configured' test_abstract_name (constraints.tests.CheckConstraintTests.test_abstract_name) ... ok test_database_constraint (constraints.tests.CheckConstraintTests.test_database_constraint) ... ok test_database_constraint_expression (constraints.tests.CheckConstraintTests.test_database_constraint_expression) ... ok test_database_constraint_expressionwrapper (constraints.tests.CheckConstraintTests.test_database_constraint_expressionwrapper) ... ok test_database_constraint_unicode (constraints.tests.CheckConstraintTests.test_database_constraint_unicode) ... ok test_deconstruction (constraints.tests.CheckConstraintTests.test_deconstruction) ... ok test_eq (constraints.tests.CheckConstraintTests.test_eq) ... ok test_invalid_check_types (constraints.tests.CheckConstraintTests.test_invalid_check_types) ... ok test_name (constraints.tests.CheckConstraintTests.test_name) ... ok test_repr (constraints.tests.CheckConstraintTests.test_repr) ... ok test_condition_must_be_q (constraints.tests.UniqueConstraintTests.test_condition_must_be_q) ... ok test_database_constraint (constraints.tests.UniqueConstraintTests.test_database_constraint) ... ok test_database_constraint_with_condition (constraints.tests.UniqueConstraintTests.test_database_constraint_with_condition) ... ok test_deconstruction (constraints.tests.UniqueConstraintTests.test_deconstruction) ... ok test_deconstruction_with_condition (constraints.tests.UniqueConstraintTests.test_deconstruction_with_condition) ... ok test_deconstruction_with_deferrable (constraints.tests.UniqueConstraintTests.test_deconstruction_with_deferrable) ... ok test_deconstruction_with_include (constraints.tests.UniqueConstraintTests.test_deconstruction_with_include) ... ok test_deconstruction_with_opclasses (constraints.tests.UniqueConstraintTests.test_deconstruction_with_opclasses) ... ok test_deferrable_with_condition (constraints.tests.UniqueConstraintTests.test_deferrable_with_condition) ... ok test_deferrable_with_include (constraints.tests.UniqueConstraintTests.test_deferrable_with_include) ... ok test_deferrable_with_opclasses (constraints.tests.UniqueConstraintTests.test_deferrable_with_opclasses) ... ok test_eq (constraints.tests.UniqueConstraintTests.test_eq) ... ok test_eq_with_condition (constraints.tests.UniqueConstraintTests.test_eq_with_condition) ... ok test_eq_with_deferrable (constraints.tests.UniqueConstraintTests.test_eq_with_deferrable) ... ok test_eq_with_include (constraints.tests.UniqueConstraintTests.test_eq_with_include) ... ok test_eq_with_opclasses (constraints.tests.UniqueConstraintTests.test_eq_with_opclasses) ... ok test_include_database_constraint (constraints.tests.UniqueConstraintTests.test_include_database_constraint) ... skipped "Database doesn't support feature(s): supports_table_check_constraints, supports_covering_indexes" test_initially_deferred_database_constraint (constraints.tests.UniqueConstraintTests.test_initially_deferred_database_constraint) ... skipped "Database doesn't support feature(s): supports_deferrable_unique_constraints" test_initially_immediate_database_constraint (constraints.tests.UniqueConstraintTests.test_initially_immediate_database_constraint) ... skipped "Database doesn't support feature(s): supports_deferrable_unique_constraints" test_invalid_defer_argument (constraints.tests.UniqueConstraintTests.test_invalid_defer_argument) ... ok test_invalid_include_argument (constraints.tests.UniqueConstraintTests.test_invalid_include_argument) ... ok test_invalid_opclasses_argument (constraints.tests.UniqueConstraintTests.test_invalid_opclasses_argument) ... ok test_model_validation (constraints.tests.UniqueConstraintTests.test_model_validation) ... ok test_model_validation_with_condition (constraints.tests.UniqueConstraintTests.test_model_validation_with_condition) Partial unique constraints are ignored by Model.validate_unique(). ... ok test_name (constraints.tests.UniqueConstraintTests.test_name) ... ok test_opclasses_and_fields_same_length (constraints.tests.UniqueConstraintTests.test_opclasses_and_fields_same_length) ... ok test_repr (constraints.tests.UniqueConstraintTests.test_repr) ... ok test_repr_with_condition (constraints.tests.UniqueConstraintTests.test_repr_with_condition) ... ok test_repr_with_deferrable (constraints.tests.UniqueConstraintTests.test_repr_with_deferrable) ... ok test_repr_with_include (constraints.tests.UniqueConstraintTests.test_repr_with_include) ... ok test_repr_with_opclasses (constraints.tests.UniqueConstraintTests.test_repr_with_opclasses) ... ok test_conditional_aggregation_example (expressions_case.tests.CaseDocumentationExamples.test_conditional_aggregation_example) ... ok test_conditional_update_example (expressions_case.tests.CaseDocumentationExamples.test_conditional_update_example) ... ok test_filter_example (expressions_case.tests.CaseDocumentationExamples.test_filter_example) ... ok test_hash (expressions_case.tests.CaseDocumentationExamples.test_hash) ... ok test_lookup_example (expressions_case.tests.CaseDocumentationExamples.test_lookup_example) ... ok test_simple_example (expressions_case.tests.CaseDocumentationExamples.test_simple_example) ... ok test_aggregate (expressions_case.tests.CaseExpressionTests.test_aggregate) ... ok test_aggregate_with_expression_as_condition (expressions_case.tests.CaseExpressionTests.test_aggregate_with_expression_as_condition) ... ok test_aggregate_with_expression_as_value (expressions_case.tests.CaseExpressionTests.test_aggregate_with_expression_as_value) ... ok test_aggregation_empty_cases (expressions_case.tests.CaseExpressionTests.test_aggregation_empty_cases) ... ok test_annotate (expressions_case.tests.CaseExpressionTests.test_annotate) ... ok test_annotate_exclude (expressions_case.tests.CaseExpressionTests.test_annotate_exclude) ... ok test_annotate_values_not_in_order_by (expressions_case.tests.CaseExpressionTests.test_annotate_values_not_in_order_by) ... ok test_annotate_with_aggregation_in_condition (expressions_case.tests.CaseExpressionTests.test_annotate_with_aggregation_in_condition) ... ok test_annotate_with_aggregation_in_predicate (expressions_case.tests.CaseExpressionTests.test_annotate_with_aggregation_in_predicate) ... ok test_annotate_with_aggregation_in_value (expressions_case.tests.CaseExpressionTests.test_annotate_with_aggregation_in_value) ... ok test_annotate_with_annotation_in_condition (expressions_case.tests.CaseExpressionTests.test_annotate_with_annotation_in_condition) ... ok test_annotate_with_annotation_in_predicate (expressions_case.tests.CaseExpressionTests.test_annotate_with_annotation_in_predicate) ... ok test_annotate_with_annotation_in_value (expressions_case.tests.CaseExpressionTests.test_annotate_with_annotation_in_value) ... ok test_annotate_with_empty_when (expressions_case.tests.CaseExpressionTests.test_annotate_with_empty_when) ... ok test_annotate_with_expression_as_condition (expressions_case.tests.CaseExpressionTests.test_annotate_with_expression_as_condition) ... ok test_annotate_with_expression_as_value (expressions_case.tests.CaseExpressionTests.test_annotate_with_expression_as_value) ... ok test_annotate_with_in_clause (expressions_case.tests.CaseExpressionTests.test_annotate_with_in_clause) ... ok test_annotate_with_join_in_condition (expressions_case.tests.CaseExpressionTests.test_annotate_with_join_in_condition) ... ok test_annotate_with_join_in_predicate (expressions_case.tests.CaseExpressionTests.test_annotate_with_join_in_predicate) ... ok test_annotate_with_join_in_value (expressions_case.tests.CaseExpressionTests.test_annotate_with_join_in_value) ... ok test_annotate_without_default (expressions_case.tests.CaseExpressionTests.test_annotate_without_default) ... ok test_case_reuse (expressions_case.tests.CaseExpressionTests.test_case_reuse) ... ok test_combined_expression (expressions_case.tests.CaseExpressionTests.test_combined_expression) ... ok test_combined_q_object (expressions_case.tests.CaseExpressionTests.test_combined_q_object) ... ok test_condition_with_lookups (expressions_case.tests.CaseExpressionTests.test_condition_with_lookups) ... ok test_filter (expressions_case.tests.CaseExpressionTests.test_filter) ... ok test_filter_with_aggregation_in_condition (expressions_case.tests.CaseExpressionTests.test_filter_with_aggregation_in_condition) ... ok test_filter_with_aggregation_in_predicate (expressions_case.tests.CaseExpressionTests.test_filter_with_aggregation_in_predicate) ... ok test_filter_with_aggregation_in_value (expressions_case.tests.CaseExpressionTests.test_filter_with_aggregation_in_value) ... ok test_filter_with_annotation_in_condition (expressions_case.tests.CaseExpressionTests.test_filter_with_annotation_in_condition) ... ok test_filter_with_annotation_in_predicate (expressions_case.tests.CaseExpressionTests.test_filter_with_annotation_in_predicate) ... ok test_filter_with_annotation_in_value (expressions_case.tests.CaseExpressionTests.test_filter_with_annotation_in_value) ... ok test_filter_with_expression_as_condition (expressions_case.tests.CaseExpressionTests.test_filter_with_expression_as_condition) ... ok test_filter_with_expression_as_value (expressions_case.tests.CaseExpressionTests.test_filter_with_expression_as_value) ... ok test_filter_with_join_in_condition (expressions_case.tests.CaseExpressionTests.test_filter_with_join_in_condition) ... ok test_filter_with_join_in_predicate (expressions_case.tests.CaseExpressionTests.test_filter_with_join_in_predicate) ... ok test_filter_with_join_in_value (expressions_case.tests.CaseExpressionTests.test_filter_with_join_in_value) ... ok test_filter_without_default (expressions_case.tests.CaseExpressionTests.test_filter_without_default) ... ok test_in_subquery (expressions_case.tests.CaseExpressionTests.test_in_subquery) ... ok test_join_promotion (expressions_case.tests.CaseExpressionTests.test_join_promotion) ... ok test_join_promotion_multiple_annotations (expressions_case.tests.CaseExpressionTests.test_join_promotion_multiple_annotations) ... ok test_lookup_different_fields (expressions_case.tests.CaseExpressionTests.test_lookup_different_fields) ... ok test_lookup_in_condition (expressions_case.tests.CaseExpressionTests.test_lookup_in_condition) ... ok test_m2m_exclude (expressions_case.tests.CaseExpressionTests.test_m2m_exclude) ... ok test_m2m_reuse (expressions_case.tests.CaseExpressionTests.test_m2m_reuse) ... ok test_order_by_conditional_explicit (expressions_case.tests.CaseExpressionTests.test_order_by_conditional_explicit) ... ok test_order_by_conditional_implicit (expressions_case.tests.CaseExpressionTests.test_order_by_conditional_implicit) ... ok test_update (expressions_case.tests.CaseExpressionTests.test_update) ... ok test_update_big_integer (expressions_case.tests.CaseExpressionTests.test_update_big_integer) ... ok test_update_binary (expressions_case.tests.CaseExpressionTests.test_update_binary) ... ok test_update_boolean (expressions_case.tests.CaseExpressionTests.test_update_boolean) ... ok test_update_date (expressions_case.tests.CaseExpressionTests.test_update_date) ... ok test_update_date_time (expressions_case.tests.CaseExpressionTests.test_update_date_time) ... ok test_update_decimal (expressions_case.tests.CaseExpressionTests.test_update_decimal) ... ok test_update_duration (expressions_case.tests.CaseExpressionTests.test_update_duration) ... ok test_update_email (expressions_case.tests.CaseExpressionTests.test_update_email) ... ok test_update_file (expressions_case.tests.CaseExpressionTests.test_update_file) ... ok test_update_file_path (expressions_case.tests.CaseExpressionTests.test_update_file_path) ... ok test_update_fk (expressions_case.tests.CaseExpressionTests.test_update_fk) ... ok test_update_float (expressions_case.tests.CaseExpressionTests.test_update_float) ... ok test_update_generic_ip_address (expressions_case.tests.CaseExpressionTests.test_update_generic_ip_address) ... ok test_update_image (expressions_case.tests.CaseExpressionTests.test_update_image) ... ok test_update_null_boolean (expressions_case.tests.CaseExpressionTests.test_update_null_boolean) ... ok test_update_null_boolean_old (expressions_case.tests.CaseExpressionTests.test_update_null_boolean_old) ... ok test_update_positive_big_integer (expressions_case.tests.CaseExpressionTests.test_update_positive_big_integer) ... ok test_update_positive_integer (expressions_case.tests.CaseExpressionTests.test_update_positive_integer) ... ok test_update_positive_small_integer (expressions_case.tests.CaseExpressionTests.test_update_positive_small_integer) ... ok test_update_slug (expressions_case.tests.CaseExpressionTests.test_update_slug) ... ok test_update_small_integer (expressions_case.tests.CaseExpressionTests.test_update_small_integer) ... ok test_update_string (expressions_case.tests.CaseExpressionTests.test_update_string) ... ok test_update_text (expressions_case.tests.CaseExpressionTests.test_update_text) ... ok test_update_time (expressions_case.tests.CaseExpressionTests.test_update_time) ... ok test_update_url (expressions_case.tests.CaseExpressionTests.test_update_url) ... ok test_update_uuid (expressions_case.tests.CaseExpressionTests.test_update_uuid) ... ok test_update_with_expression_as_condition (expressions_case.tests.CaseExpressionTests.test_update_with_expression_as_condition) ... ok test_update_with_expression_as_value (expressions_case.tests.CaseExpressionTests.test_update_with_expression_as_value) ... ok test_update_with_join_in_condition_raise_field_error (expressions_case.tests.CaseExpressionTests.test_update_with_join_in_condition_raise_field_error) ... ok test_update_with_join_in_predicate_raise_field_error (expressions_case.tests.CaseExpressionTests.test_update_with_join_in_predicate_raise_field_error) ... ok test_update_without_default (expressions_case.tests.CaseExpressionTests.test_update_without_default) ... ok test_m2m_and_m2o (m2m_and_m2o.tests.RelatedObjectTests.test_m2m_and_m2o) ... ok test_related_objects_have_name_attribute (m2m_and_m2o.tests.RelatedObjectTests.test_related_objects_have_name_attribute) ... ok test_m2m_with_unicode_reference (m2m_and_m2o.tests.RelatedObjectUnicodeTests.test_m2m_with_unicode_reference) Regression test for #6045: references to other models can be ... ok test_loaddata (fixtures_model_package.tests.FixtureTestCase.test_loaddata) Fixtures can load data into models defined in packages ... ok test_class_fixtures (fixtures_model_package.tests.SampleTestCase.test_class_fixtures) Test cases can load fixture objects into models defined in packages ... ok test_add_form_deletion_when_invalid (inline_formsets.tests.DeletionTests.test_add_form_deletion_when_invalid) Make sure that an add form that is filled out, but marked for deletion ... ok test_change_form_deletion_when_invalid (inline_formsets.tests.DeletionTests.test_change_form_deletion_when_invalid) Make sure that a change form that is filled out, but marked for deletion ... ok test_deletion (inline_formsets.tests.DeletionTests.test_deletion) ... ok test_save_new (inline_formsets.tests.DeletionTests.test_save_new) Make sure inlineformsets respect commit=False ... ok test_any_iterable_allowed_as_argument_to_exclude (inline_formsets.tests.InlineFormsetFactoryTest.test_any_iterable_allowed_as_argument_to_exclude) ... ok test_exception_on_unspecified_foreign_key (inline_formsets.tests.InlineFormsetFactoryTest.test_exception_on_unspecified_foreign_key) Child has two ForeignKeys to Parent, so if we don't specify which one ... ok test_fk_in_all_formset_forms (inline_formsets.tests.InlineFormsetFactoryTest.test_fk_in_all_formset_forms) A foreign key field is in Meta for all forms in the formset (#26538). ... ok test_fk_name_not_foreign_key_field_from_child (inline_formsets.tests.InlineFormsetFactoryTest.test_fk_name_not_foreign_key_field_from_child) If we specify fk_name, but it isn't a ForeignKey from the child model ... ok test_fk_not_duplicated_in_form_fields (inline_formsets.tests.InlineFormsetFactoryTest.test_fk_not_duplicated_in_form_fields) A foreign key name isn't duplicated in form._meta fields (#21332). ... ok test_inline_formset_factory (inline_formsets.tests.InlineFormsetFactoryTest.test_inline_formset_factory) These should both work without a problem. ... ok test_non_foreign_key_field (inline_formsets.tests.InlineFormsetFactoryTest.test_non_foreign_key_field) If the field specified in fk_name is not a ForeignKey, we should get an ... ok test_unsaved_fk_validate_unique (inline_formsets.tests.InlineFormsetFactoryTest.test_unsaved_fk_validate_unique) ... ok test_zero_primary_key (inline_formsets.tests.InlineFormsetFactoryTest.test_zero_primary_key) ... ok test_add (many_to_many.tests.ManyToManyTests.test_add) ... ok test_add_after_prefetch (many_to_many.tests.ManyToManyTests.test_add_after_prefetch) ... ok test_add_existing_different_type (many_to_many.tests.ManyToManyTests.test_add_existing_different_type) ... skipped 'Database has feature(s) supports_ignore_conflicts' test_add_remove_invalid_type (many_to_many.tests.ManyToManyTests.test_add_remove_invalid_type) ... ok test_add_remove_set_by_pk (many_to_many.tests.ManyToManyTests.test_add_remove_set_by_pk) ... ok test_add_remove_set_by_to_field (many_to_many.tests.ManyToManyTests.test_add_remove_set_by_to_field) ... ok test_add_then_remove_after_prefetch (many_to_many.tests.ManyToManyTests.test_add_then_remove_after_prefetch) ... ok test_assign (many_to_many.tests.ManyToManyTests.test_assign) ... ok test_assign_forward (many_to_many.tests.ManyToManyTests.test_assign_forward) ... ok test_assign_ids (many_to_many.tests.ManyToManyTests.test_assign_ids) ... ok test_assign_reverse (many_to_many.tests.ManyToManyTests.test_assign_reverse) ... ok test_bulk_delete (many_to_many.tests.ManyToManyTests.test_bulk_delete) ... ok test_clear (many_to_many.tests.ManyToManyTests.test_clear) ... ok test_clear_after_prefetch (many_to_many.tests.ManyToManyTests.test_clear_after_prefetch) ... ok test_custom_default_manager_exists_count (many_to_many.tests.ManyToManyTests.test_custom_default_manager_exists_count) ... ok test_delete (many_to_many.tests.ManyToManyTests.test_delete) ... ok test_fast_add_ignore_conflicts (many_to_many.tests.ManyToManyTests.test_fast_add_ignore_conflicts) A single query is necessary to add auto-created through instances if ... ok test_forward_assign_with_queryset (many_to_many.tests.ManyToManyTests.test_forward_assign_with_queryset) ... ok test_inherited_models_selects (many_to_many.tests.ManyToManyTests.test_inherited_models_selects) #24156 - Objects from child models where the parent's m2m field uses ... ok test_related_sets (many_to_many.tests.ManyToManyTests.test_related_sets) ... ok test_remove (many_to_many.tests.ManyToManyTests.test_remove) ... ok test_remove_after_prefetch (many_to_many.tests.ManyToManyTests.test_remove_after_prefetch) ... ok test_reverse_add (many_to_many.tests.ManyToManyTests.test_reverse_add) ... ok test_reverse_assign_with_queryset (many_to_many.tests.ManyToManyTests.test_reverse_assign_with_queryset) ... ok test_reverse_selects (many_to_many.tests.ManyToManyTests.test_reverse_selects) ... ok test_selects (many_to_many.tests.ManyToManyTests.test_selects) ... ok test_set (many_to_many.tests.ManyToManyTests.test_set) ... ok test_set_after_prefetch (many_to_many.tests.ManyToManyTests.test_set_after_prefetch) ... ok test_set_existing_different_type (many_to_many.tests.ManyToManyTests.test_set_existing_different_type) ... ok test_slow_add_ignore_conflicts (many_to_many.tests.ManyToManyTests.test_slow_add_ignore_conflicts) ... ok test_autofields_generate_different_values_for_each_instance (basic.tests.ModelInstanceCreationTests.test_autofields_generate_different_values_for_each_instance) ... ok test_can_create_instance_using_kwargs (basic.tests.ModelInstanceCreationTests.test_can_create_instance_using_kwargs) ... ok test_can_initialize_model_instance_using_positional_arguments (basic.tests.ModelInstanceCreationTests.test_can_initialize_model_instance_using_positional_arguments) You can initialize a model instance using positional arguments, ... ok test_can_leave_off_value_for_autofield_and_it_gets_value_on_save (basic.tests.ModelInstanceCreationTests.test_can_leave_off_value_for_autofield_and_it_gets_value_on_save) You can leave off the value for an AutoField when creating an ... ok test_can_mix_and_match_position_and_kwargs (basic.tests.ModelInstanceCreationTests.test_can_mix_and_match_position_and_kwargs) ... ok test_cannot_create_instance_with_invalid_kwargs (basic.tests.ModelInstanceCreationTests.test_cannot_create_instance_with_invalid_kwargs) ... ok test_for_datetimefields_saves_as_much_precision_as_was_given (basic.tests.ModelInstanceCreationTests.test_for_datetimefields_saves_as_much_precision_as_was_given) as much precision in *seconds* ... ok test_leaving_off_a_field_with_default_set_the_default_will_be_saved (basic.tests.ModelInstanceCreationTests.test_leaving_off_a_field_with_default_set_the_default_will_be_saved) ... ok test_object_is_not_written_to_database_until_save_was_called (basic.tests.ModelInstanceCreationTests.test_object_is_not_written_to_database_until_save_was_called) ... ok test_querysets_checking_for_membership (basic.tests.ModelInstanceCreationTests.test_querysets_checking_for_membership) ... ok test_save_parent_primary_with_default (basic.tests.ModelInstanceCreationTests.test_save_parent_primary_with_default) ... ok test_save_primary_with_default (basic.tests.ModelInstanceCreationTests.test_save_primary_with_default) ... ok test_saving_an_object_again_does_not_create_a_new_object (basic.tests.ModelInstanceCreationTests.test_saving_an_object_again_does_not_create_a_new_object) ... ok test_all_lookup (basic.tests.ModelLookupTest.test_all_lookup) ... ok test_does_not_exist (basic.tests.ModelLookupTest.test_does_not_exist) ... ok test_equal_lookup (basic.tests.ModelLookupTest.test_equal_lookup) ... ok test_lookup_by_primary_key (basic.tests.ModelLookupTest.test_lookup_by_primary_key) ... ok test_rich_lookup (basic.tests.ModelLookupTest.test_rich_lookup) ... ok test_too_many (basic.tests.ModelLookupTest.test_too_many) ... ok test_lookup_in_fields (basic.tests.ModelRefreshTests.test_lookup_in_fields) ... ok test_prefetched_cache_cleared (basic.tests.ModelRefreshTests.test_prefetched_cache_cleared) ... ok test_refresh (basic.tests.ModelRefreshTests.test_refresh) ... ok test_refresh_clears_one_to_one_field (basic.tests.ModelRefreshTests.test_refresh_clears_one_to_one_field) ... ok test_refresh_clears_reverse_related (basic.tests.ModelRefreshTests.test_refresh_clears_reverse_related) refresh_from_db() clear cached reverse relations. ... ok test_refresh_fk (basic.tests.ModelRefreshTests.test_refresh_fk) ... ok test_refresh_fk_on_delete_set_null (basic.tests.ModelRefreshTests.test_refresh_fk_on_delete_set_null) ... ok test_refresh_no_fields (basic.tests.ModelRefreshTests.test_refresh_no_fields) ... ok test_refresh_null_fk (basic.tests.ModelRefreshTests.test_refresh_null_fk) ... ok test_refresh_unsaved (basic.tests.ModelRefreshTests.test_refresh_unsaved) ... ok test_unknown_kwarg (basic.tests.ModelRefreshTests.test_unknown_kwarg) ... ok test_create_method (basic.tests.ModelTest.test_create_method) ... ok test_create_relation_with_gettext_lazy (basic.tests.ModelTest.test_create_relation_with_gettext_lazy) gettext_lazy objects work when saving model instances ... ok test_delete_and_access_field (basic.tests.ModelTest.test_delete_and_access_field) ... ok test_emptyqs (basic.tests.ModelTest.test_emptyqs) ... ok test_emptyqs_customqs (basic.tests.ModelTest.test_emptyqs_customqs) ... ok test_emptyqs_distinct (basic.tests.ModelTest.test_emptyqs_distinct) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_emptyqs_values (basic.tests.ModelTest.test_emptyqs_values) ... ok test_emptyqs_values_order (basic.tests.ModelTest.test_emptyqs_values_order) ... ok test_eq (basic.tests.ModelTest.test_eq) ... ok test_extra_method_select_argument_with_dashes (basic.tests.ModelTest.test_extra_method_select_argument_with_dashes) ... ok test_extra_method_select_argument_with_dashes_and_values (basic.tests.ModelTest.test_extra_method_select_argument_with_dashes_and_values) ... ok test_hash (basic.tests.ModelTest.test_hash) ... ok test_hash_function (basic.tests.ModelTest.test_hash_function) ... ok test_manually_specify_primary_key (basic.tests.ModelTest.test_manually_specify_primary_key) ... ok test_microsecond_precision (basic.tests.ModelTest.test_microsecond_precision) ... ok test_missing_hash_not_inherited (basic.tests.ModelTest.test_missing_hash_not_inherited) ... ok test_multiple_objects_max_num_fetched (basic.tests.ModelTest.test_multiple_objects_max_num_fetched) ... ok test_not_equal_and_equal_operators_behave_as_expected_on_instances (basic.tests.ModelTest.test_not_equal_and_equal_operators_behave_as_expected_on_instances) ... ok test_objects_attribute_is_only_available_on_the_class_itself (basic.tests.ModelTest.test_objects_attribute_is_only_available_on_the_class_itself) ... ok test_queryset_delete_removes_all_items_in_that_queryset (basic.tests.ModelTest.test_queryset_delete_removes_all_items_in_that_queryset) ... ok test_specified_parent_hash_inherited (basic.tests.ModelTest.test_specified_parent_hash_inherited) ... ok test_ticket_20278 (basic.tests.ModelTest.test_ticket_20278) ... ok test_unicode_data (basic.tests.ModelTest.test_unicode_data) ... ok test_year_lookup_edge_case (basic.tests.ModelTest.test_year_lookup_edge_case) ... ok test_select_on_save (basic.tests.SelectOnSaveTests.test_select_on_save) ... ok test_select_on_save_lying_update (basic.tests.SelectOnSaveTests.test_select_on_save_lying_update) select_on_save works correctly if the database doesn't return correct ... ok test_add_view (auth_tests.test_admin_multidb.MultiDatabaseTests.test_add_view) ... ok test_authenticate (auth_tests.test_auth_backends.AllowAllUsersModelBackendTest.test_authenticate) ... ok test_get_user (auth_tests.test_auth_backends.AllowAllUsersModelBackendTest.test_get_user) ... ok test_authenticate_sensitive_variables (auth_tests.test_auth_backends.AuthenticateTests.test_authenticate_sensitive_variables) ... ok test_clean_credentials_sensitive_variables (auth_tests.test_auth_backends.AuthenticateTests.test_clean_credentials_sensitive_variables) ... ok test_skips_backends_with_decorated_method (auth_tests.test_auth_backends.AuthenticateTests.test_skips_backends_with_decorated_method) ... ok test_skips_backends_without_arguments (auth_tests.test_auth_backends.AuthenticateTests.test_skips_backends_without_arguments) A backend (SkippedBackend) is ignored if it doesn't accept the ... ok test_type_error_raised (auth_tests.test_auth_backends.AuthenticateTests.test_type_error_raised) A TypeError within a backend is propagated properly (#18171). ... ok test_get_all_permissions (auth_tests.test_auth_backends.BaseBackendTest.test_get_all_permissions) ... ok test_get_group_permissions (auth_tests.test_auth_backends.BaseBackendTest.test_get_group_permissions) ... ok test_get_user_permissions (auth_tests.test_auth_backends.BaseBackendTest.test_get_user_permissions) ... ok test_has_perm (auth_tests.test_auth_backends.BaseBackendTest.test_has_perm) ... ok test_changed_backend_settings (auth_tests.test_auth_backends.ChangedBackendSettingsTest.test_changed_backend_settings) Removing a backend configured in AUTHENTICATION_BACKENDS makes already ... ok test_anonymous_has_no_permissions (auth_tests.test_auth_backends.CustomPermissionsUserModelBackendTest.test_anonymous_has_no_permissions) #17903 -- Anonymous users shouldn't have permissions in ... ok test_authentication_timing (auth_tests.test_auth_backends.CustomPermissionsUserModelBackendTest.test_authentication_timing) Hasher is run once regardless of whether the user exists. Refs #20760. ... ok test_authentication_without_credentials (auth_tests.test_auth_backends.CustomPermissionsUserModelBackendTest.test_authentication_without_credentials) ... ok test_custom_perms (auth_tests.test_auth_backends.CustomPermissionsUserModelBackendTest.test_custom_perms) ... ok test_get_all_superuser_permissions (auth_tests.test_auth_backends.CustomPermissionsUserModelBackendTest.test_get_all_superuser_permissions) A superuser has all permissions. Refs #14795. ... ok test_has_no_object_perm (auth_tests.test_auth_backends.CustomPermissionsUserModelBackendTest.test_has_no_object_perm) Regressiontest for #12462 ... ok test_has_perm (auth_tests.test_auth_backends.CustomPermissionsUserModelBackendTest.test_has_perm) ... ok test_inactive_has_no_permissions (auth_tests.test_auth_backends.CustomPermissionsUserModelBackendTest.test_inactive_has_no_permissions) #17903 -- Inactive users shouldn't have permissions in ... ok test_authenticate (auth_tests.test_auth_backends.CustomUserModelBackendAuthenticateTest.test_authenticate) ... ok test_anonymous_has_no_permissions (auth_tests.test_auth_backends.ExtensionUserModelBackendTest.test_anonymous_has_no_permissions) #17903 -- Anonymous users shouldn't have permissions in ... ok test_authentication_timing (auth_tests.test_auth_backends.ExtensionUserModelBackendTest.test_authentication_timing) Hasher is run once regardless of whether the user exists. Refs #20760. ... ok test_authentication_without_credentials (auth_tests.test_auth_backends.ExtensionUserModelBackendTest.test_authentication_without_credentials) ... ok test_custom_perms (auth_tests.test_auth_backends.ExtensionUserModelBackendTest.test_custom_perms) ... ok test_get_all_superuser_permissions (auth_tests.test_auth_backends.ExtensionUserModelBackendTest.test_get_all_superuser_permissions) A superuser has all permissions. Refs #14795. ... ok test_has_no_object_perm (auth_tests.test_auth_backends.ExtensionUserModelBackendTest.test_has_no_object_perm) Regressiontest for #12462 ... ok test_has_perm (auth_tests.test_auth_backends.ExtensionUserModelBackendTest.test_has_perm) ... ok test_inactive_has_no_permissions (auth_tests.test_auth_backends.ExtensionUserModelBackendTest.test_inactive_has_no_permissions) #17903 -- Inactive users shouldn't have permissions in ... ok test_backend_path (auth_tests.test_auth_backends.ImportedBackendTests.test_backend_path) ... ok test_does_not_shadow_exception (auth_tests.test_auth_backends.ImproperlyConfiguredUserModelTest.test_does_not_shadow_exception) ... ok test_has_module_perms (auth_tests.test_auth_backends.InActiveUserBackendTest.test_has_module_perms) ... ok test_has_perm (auth_tests.test_auth_backends.InActiveUserBackendTest.test_has_perm) ... ok test_anonymous_has_no_permissions (auth_tests.test_auth_backends.ModelBackendTest.test_anonymous_has_no_permissions) #17903 -- Anonymous users shouldn't have permissions in ... ok test_authenticate_inactive (auth_tests.test_auth_backends.ModelBackendTest.test_authenticate_inactive) An inactive user can't authenticate. ... ok test_authenticate_user_without_is_active_field (auth_tests.test_auth_backends.ModelBackendTest.test_authenticate_user_without_is_active_field) A custom user without an `is_active` field is allowed to authenticate. ... ok test_authentication_timing (auth_tests.test_auth_backends.ModelBackendTest.test_authentication_timing) Hasher is run once regardless of whether the user exists. Refs #20760. ... ok test_authentication_without_credentials (auth_tests.test_auth_backends.ModelBackendTest.test_authentication_without_credentials) ... ok test_custom_perms (auth_tests.test_auth_backends.ModelBackendTest.test_custom_perms) ... ok test_get_all_superuser_permissions (auth_tests.test_auth_backends.ModelBackendTest.test_get_all_superuser_permissions) A superuser has all permissions. Refs #14795. ... ok test_has_no_object_perm (auth_tests.test_auth_backends.ModelBackendTest.test_has_no_object_perm) Regressiontest for #12462 ... ok test_has_perm (auth_tests.test_auth_backends.ModelBackendTest.test_has_perm) ... ok test_inactive_has_no_permissions (auth_tests.test_auth_backends.ModelBackendTest.test_inactive_has_no_permissions) #17903 -- Inactive users shouldn't have permissions in ... ok test_raises_exception (auth_tests.test_auth_backends.NoBackendsTest.test_raises_exception) ... ok test_authenticates (auth_tests.test_auth_backends.PermissionDeniedBackendTest.test_authenticates) ... ok test_has_perm (auth_tests.test_auth_backends.PermissionDeniedBackendTest.test_has_perm) ... ok test_has_perm_denied (auth_tests.test_auth_backends.PermissionDeniedBackendTest.test_has_perm_denied) ... ok test_permission_denied (auth_tests.test_auth_backends.PermissionDeniedBackendTest.test_permission_denied) user is not authenticated after a backend raises permission denied #2550 ... ok test_get_all_permissions (auth_tests.test_auth_backends.RowlevelBackendTest.test_get_all_permissions) ... ok test_get_group_permissions (auth_tests.test_auth_backends.RowlevelBackendTest.test_get_group_permissions) ... ok test_has_perm (auth_tests.test_auth_backends.RowlevelBackendTest.test_has_perm) ... ok test_backend_path_login_with_explicit_backends (auth_tests.test_auth_backends.SelectingBackendTests.test_backend_path_login_with_explicit_backends) ... ok test_backend_path_login_without_authenticate_multiple_backends (auth_tests.test_auth_backends.SelectingBackendTests.test_backend_path_login_without_authenticate_multiple_backends) ... ok test_backend_path_login_without_authenticate_single_backend (auth_tests.test_auth_backends.SelectingBackendTests.test_backend_path_login_without_authenticate_single_backend) ... ok test_non_string_backend (auth_tests.test_auth_backends.SelectingBackendTests.test_non_string_backend) ... ok test_login (auth_tests.test_auth_backends.UUIDUserTests.test_login) A custom user with a UUID primary key should be able to login. ... ok test_get_user_model (auth_tests.test_basic.BasicTestCase.test_get_user_model) The current user model can be retrieved ... ok test_superuser (auth_tests.test_basic.BasicTestCase.test_superuser) Check the creation and properties of a superuser ... ok test_superuser_no_email_or_password (auth_tests.test_basic.BasicTestCase.test_superuser_no_email_or_password) ... ok test_swappable_user (auth_tests.test_basic.BasicTestCase.test_swappable_user) The current user model can be swapped out for another ... ok test_swappable_user_bad_setting (auth_tests.test_basic.BasicTestCase.test_swappable_user_bad_setting) The alternate user setting must point to something in the format app.model ... ok test_swappable_user_nonexistent_model (auth_tests.test_basic.BasicTestCase.test_swappable_user_nonexistent_model) The current user model must point to an installed model ... ok test_unicode_username (auth_tests.test_basic.BasicTestCase.test_unicode_username) ... ok test_user (auth_tests.test_basic.BasicTestCase.test_user) Users can be created and can set their password ... ok test_user_no_email (auth_tests.test_basic.BasicTestCase.test_user_no_email) Users can be created without an email ... ok test_user_verbose_names_translatable (auth_tests.test_basic.BasicTestCase.test_user_verbose_names_translatable) Default User model verbose names are translatable (#19945) ... ok test_get_user (auth_tests.test_basic.TestGetUser.test_get_user) ... ok test_get_user_anonymous (auth_tests.test_basic.TestGetUser.test_get_user_anonymous) ... ok test_message_attrs (auth_tests.test_context_processors.AuthContextProcessorTests.test_message_attrs) ... ok test_perm_in_perms_attrs (auth_tests.test_context_processors.AuthContextProcessorTests.test_perm_in_perms_attrs) ... ok test_perms_attrs (auth_tests.test_context_processors.AuthContextProcessorTests.test_perms_attrs) ... ok test_session_is_accessed (auth_tests.test_context_processors.AuthContextProcessorTests.test_session_is_accessed) The session is accessed if the auth context processor ... ok test_session_not_accessed (auth_tests.test_context_processors.AuthContextProcessorTests.test_session_not_accessed) The session is not accessed simply by including ... ok test_user_attrs (auth_tests.test_context_processors.AuthContextProcessorTests.test_user_attrs) The lazy objects returned behave just like the wrapped objects. ... ok test_callable (auth_tests.test_decorators.LoginRequiredTestCase.test_callable) login_required is assignable to callable objects. ... ok test_login_required (auth_tests.test_decorators.LoginRequiredTestCase.test_login_required) login_required works on a simple view wrapped in a login_required ... ok test_login_required_next_url (auth_tests.test_decorators.LoginRequiredTestCase.test_login_required_next_url) login_required works on a simple view wrapped in a login_required ... ok test_view (auth_tests.test_decorators.LoginRequiredTestCase.test_view) login_required is assignable to normal views. ... ok test_many_permissions_in_set_pass (auth_tests.test_decorators.PermissionsRequiredDecoratorTest.test_many_permissions_in_set_pass) ... ok test_many_permissions_pass (auth_tests.test_decorators.PermissionsRequiredDecoratorTest.test_many_permissions_pass) ... ok test_permissioned_denied_exception_raised (auth_tests.test_decorators.PermissionsRequiredDecoratorTest.test_permissioned_denied_exception_raised) ... ok test_permissioned_denied_redirect (auth_tests.test_decorators.PermissionsRequiredDecoratorTest.test_permissioned_denied_redirect) ... ok test_single_permission_pass (auth_tests.test_decorators.PermissionsRequiredDecoratorTest.test_single_permission_pass) ... ok test_html_autocomplete_attributes (auth_tests.test_forms.AdminPasswordChangeFormTest.test_html_autocomplete_attributes) ... ok test_missing_passwords (auth_tests.test_forms.AdminPasswordChangeFormTest.test_missing_passwords) ... ok test_non_matching_passwords (auth_tests.test_forms.AdminPasswordChangeFormTest.test_non_matching_passwords) ... ok test_one_password (auth_tests.test_forms.AdminPasswordChangeFormTest.test_one_password) ... ok test_password_whitespace_not_stripped (auth_tests.test_forms.AdminPasswordChangeFormTest.test_password_whitespace_not_stripped) ... ok test_success (auth_tests.test_forms.AdminPasswordChangeFormTest.test_success) ... ok test_custom_login_allowed_policy (auth_tests.test_forms.AuthenticationFormTest.test_custom_login_allowed_policy) ... ok test_get_invalid_login_error (auth_tests.test_forms.AuthenticationFormTest.test_get_invalid_login_error) ... ok test_html_autocomplete_attributes (auth_tests.test_forms.AuthenticationFormTest.test_html_autocomplete_attributes) ... ok test_inactive_user (auth_tests.test_forms.AuthenticationFormTest.test_inactive_user) ... ok test_inactive_user_i18n (auth_tests.test_forms.AuthenticationFormTest.test_inactive_user_i18n) ... ok test_inactive_user_incorrect_password (auth_tests.test_forms.AuthenticationFormTest.test_inactive_user_incorrect_password) An invalid login doesn't leak the inactive status of a user. ... ok test_integer_username (auth_tests.test_forms.AuthenticationFormTest.test_integer_username) ... ok test_invalid_username (auth_tests.test_forms.AuthenticationFormTest.test_invalid_username) ... ok test_login_failed (auth_tests.test_forms.AuthenticationFormTest.test_login_failed) ... ok test_password_whitespace_not_stripped (auth_tests.test_forms.AuthenticationFormTest.test_password_whitespace_not_stripped) ... ok test_success (auth_tests.test_forms.AuthenticationFormTest.test_success) ... ok test_unicode_username (auth_tests.test_forms.AuthenticationFormTest.test_unicode_username) ... ok test_username_field_autocapitalize_none (auth_tests.test_forms.AuthenticationFormTest.test_username_field_autocapitalize_none) ... ok test_username_field_label (auth_tests.test_forms.AuthenticationFormTest.test_username_field_label) ... ok test_username_field_label_empty_string (auth_tests.test_forms.AuthenticationFormTest.test_username_field_label_empty_string) ... ok test_username_field_label_not_set (auth_tests.test_forms.AuthenticationFormTest.test_username_field_label_not_set) ... ok test_username_field_max_length_defaults_to_254 (auth_tests.test_forms.AuthenticationFormTest.test_username_field_max_length_defaults_to_254) ... ok test_username_field_max_length_matches_user_model (auth_tests.test_forms.AuthenticationFormTest.test_username_field_max_length_matches_user_model) ... ok test_field_order (auth_tests.test_forms.PasswordChangeFormTest.test_field_order) ... ok test_html_autocomplete_attributes (auth_tests.test_forms.PasswordChangeFormTest.test_html_autocomplete_attributes) ... ok test_incorrect_password (auth_tests.test_forms.PasswordChangeFormTest.test_incorrect_password) ... ok test_password_verification (auth_tests.test_forms.PasswordChangeFormTest.test_password_verification) ... ok test_password_whitespace_not_stripped (auth_tests.test_forms.PasswordChangeFormTest.test_password_whitespace_not_stripped) ... ok test_success (auth_tests.test_forms.PasswordChangeFormTest.test_success) ... ok test_cleaned_data (auth_tests.test_forms.PasswordResetFormTest.test_cleaned_data) ... ok test_custom_email_constructor (auth_tests.test_forms.PasswordResetFormTest.test_custom_email_constructor) ... ok test_custom_email_field (auth_tests.test_forms.PasswordResetFormTest.test_custom_email_field) ... ok test_custom_email_subject (auth_tests.test_forms.PasswordResetFormTest.test_custom_email_subject) ... ok test_html_autocomplete_attributes (auth_tests.test_forms.PasswordResetFormTest.test_html_autocomplete_attributes) ... ok test_inactive_user (auth_tests.test_forms.PasswordResetFormTest.test_inactive_user) Inactive user cannot receive password reset email. ... ok test_invalid_email (auth_tests.test_forms.PasswordResetFormTest.test_invalid_email) ... ok test_nonexistent_email (auth_tests.test_forms.PasswordResetFormTest.test_nonexistent_email) Test nonexistent email address. This should not fail because it would ... ok test_preserve_username_case (auth_tests.test_forms.PasswordResetFormTest.test_preserve_username_case) Preserve the case of the user name (before the @ in the email address) ... ok test_save_html_email_template_name (auth_tests.test_forms.PasswordResetFormTest.test_save_html_email_template_name) Test the PasswordResetForm.save() method with html_email_template_name ... ok test_save_plaintext_email (auth_tests.test_forms.PasswordResetFormTest.test_save_plaintext_email) Test the PasswordResetForm.save() method with no html_email_template_name ... ok test_unusable_password (auth_tests.test_forms.PasswordResetFormTest.test_unusable_password) ... ok test_user_email_domain_unicode_collision (auth_tests.test_forms.PasswordResetFormTest.test_user_email_domain_unicode_collision) ... ok test_user_email_domain_unicode_collision_nonexistent (auth_tests.test_forms.PasswordResetFormTest.test_user_email_domain_unicode_collision_nonexistent) ... ok test_user_email_unicode_collision (auth_tests.test_forms.PasswordResetFormTest.test_user_email_unicode_collision) ... ok test_user_email_unicode_collision_nonexistent (auth_tests.test_forms.PasswordResetFormTest.test_user_email_unicode_collision_nonexistent) ... ok test_help_text_translation (auth_tests.test_forms.SetPasswordFormTest.test_help_text_translation) ... ok test_html_autocomplete_attributes (auth_tests.test_forms.SetPasswordFormTest.test_html_autocomplete_attributes) ... ok test_password_verification (auth_tests.test_forms.SetPasswordFormTest.test_password_verification) ... ok test_password_whitespace_not_stripped (auth_tests.test_forms.SetPasswordFormTest.test_password_whitespace_not_stripped) ... ok test_success (auth_tests.test_forms.SetPasswordFormTest.test_success) ... ok test_validates_password (auth_tests.test_forms.SetPasswordFormTest.test_validates_password) ... ok test_bug_14242 (auth_tests.test_forms.UserChangeFormTest.test_bug_14242) ... ok test_bug_17944_empty_password (auth_tests.test_forms.UserChangeFormTest.test_bug_17944_empty_password) ... ok test_bug_17944_unknown_password_algorithm (auth_tests.test_forms.UserChangeFormTest.test_bug_17944_unknown_password_algorithm) ... ok test_bug_17944_unmanageable_password (auth_tests.test_forms.UserChangeFormTest.test_bug_17944_unmanageable_password) ... ok test_bug_19133 (auth_tests.test_forms.UserChangeFormTest.test_bug_19133) The change form does not return the password value ... ok test_bug_19349_bound_password_field (auth_tests.test_forms.UserChangeFormTest.test_bug_19349_bound_password_field) ... ok test_custom_form (auth_tests.test_forms.UserChangeFormTest.test_custom_form) ... ok test_password_excluded (auth_tests.test_forms.UserChangeFormTest.test_password_excluded) ... ok test_unusable_password (auth_tests.test_forms.UserChangeFormTest.test_unusable_password) ... ok test_username_field_autocapitalize_none (auth_tests.test_forms.UserChangeFormTest.test_username_field_autocapitalize_none) ... ok test_username_validity (auth_tests.test_forms.UserChangeFormTest.test_username_validity) ... ok test_both_passwords (auth_tests.test_forms.UserCreationFormTest.test_both_passwords) ... ok test_custom_form (auth_tests.test_forms.UserCreationFormTest.test_custom_form) ... ok test_custom_form_hidden_username_field (auth_tests.test_forms.UserCreationFormTest.test_custom_form_hidden_username_field) ... ok test_custom_form_with_different_username_field (auth_tests.test_forms.UserCreationFormTest.test_custom_form_with_different_username_field) ... ok test_duplicate_normalized_unicode (auth_tests.test_forms.UserCreationFormTest.test_duplicate_normalized_unicode) To prevent almost identical usernames, visually identical but differing ... ok test_html_autocomplete_attributes (auth_tests.test_forms.UserCreationFormTest.test_html_autocomplete_attributes) ... ok test_invalid_data (auth_tests.test_forms.UserCreationFormTest.test_invalid_data) ... ok test_normalize_username (auth_tests.test_forms.UserCreationFormTest.test_normalize_username) ... ok test_password_help_text (auth_tests.test_forms.UserCreationFormTest.test_password_help_text) ... ok test_password_verification (auth_tests.test_forms.UserCreationFormTest.test_password_verification) ... ok test_password_whitespace_not_stripped (auth_tests.test_forms.UserCreationFormTest.test_password_whitespace_not_stripped) ... ok test_success (auth_tests.test_forms.UserCreationFormTest.test_success) ... ok test_unicode_username (auth_tests.test_forms.UserCreationFormTest.test_unicode_username) ... ok test_user_already_exists (auth_tests.test_forms.UserCreationFormTest.test_user_already_exists) ... ok test_user_create_form_validates_password_with_all_data (auth_tests.test_forms.UserCreationFormTest.test_user_create_form_validates_password_with_all_data) UserCreationForm password validation uses all of the form's data. ... ok test_username_field_autocapitalize_none (auth_tests.test_forms.UserCreationFormTest.test_username_field_autocapitalize_none) ... ok test_validates_password (auth_tests.test_forms.UserCreationFormTest.test_validates_password) ... ok test_get_pass (auth_tests.test_management.ChangepasswordManagementCommandTestCase.test_get_pass) ... ok test_get_pass_no_input (auth_tests.test_management.ChangepasswordManagementCommandTestCase.test_get_pass_no_input) ... ok test_nonexistent_username (auth_tests.test_management.ChangepasswordManagementCommandTestCase.test_nonexistent_username) ... ok test_password_validation (auth_tests.test_management.ChangepasswordManagementCommandTestCase.test_password_validation) A CommandError should be raised if the user enters in passwords which ... ok test_system_username (auth_tests.test_management.ChangepasswordManagementCommandTestCase.test_system_username) The system username is used if --username isn't provided. ... ok test_that_changepassword_command_changes_joes_password (auth_tests.test_management.ChangepasswordManagementCommandTestCase.test_that_changepassword_command_changes_joes_password) Executing the changepassword management command should change joe's password ... ok test_that_changepassword_command_works_with_nonascii_output (auth_tests.test_management.ChangepasswordManagementCommandTestCase.test_that_changepassword_command_works_with_nonascii_output) #21627 -- Executing the changepassword management command should allow ... ok test_that_max_tries_exits_1 (auth_tests.test_management.ChangepasswordManagementCommandTestCase.test_that_max_tries_exits_1) A CommandError should be thrown by handle() if the user enters in ... ok test_create_permissions_checks_contenttypes_created (auth_tests.test_management.CreatePermissionsTests.test_create_permissions_checks_contenttypes_created) `post_migrate` handler ordering isn't guaranteed. Simulate a case ... ok test_default_permissions (auth_tests.test_management.CreatePermissionsTests.test_default_permissions) ... ok test_permission_with_proxy_content_type_created (auth_tests.test_management.CreatePermissionsTests.test_permission_with_proxy_content_type_created) A proxy model's permissions use its own content type rather than the ... ok test_unavailable_models (auth_tests.test_management.CreatePermissionsTests.test_unavailable_models) #24075 - Permissions shouldn't be created or deleted if the ContentType ... ok test_add (cache.tests.FileBasedCacheTests.test_add) ... ok test_add_fail_on_pickleerror (cache.tests.FileBasedCacheTests.test_add_fail_on_pickleerror) ... ok test_binary_string (cache.tests.FileBasedCacheTests.test_binary_string) ... ok test_cache_dir_permissions (cache.tests.FileBasedCacheTests.test_cache_dir_permissions) ... ok test_cache_read_for_model_instance (cache.tests.FileBasedCacheTests.test_cache_read_for_model_instance) ... ok test_cache_read_for_model_instance_with_deferred (cache.tests.FileBasedCacheTests.test_cache_read_for_model_instance_with_deferred) ... ok test_cache_versioning_add (cache.tests.FileBasedCacheTests.test_cache_versioning_add) ... ok test_cache_versioning_delete (cache.tests.FileBasedCacheTests.test_cache_versioning_delete) ... ok test_cache_versioning_get_set (cache.tests.FileBasedCacheTests.test_cache_versioning_get_set) ... ok test_cache_versioning_get_set_many (cache.tests.FileBasedCacheTests.test_cache_versioning_get_set_many) ... ok test_cache_versioning_has_key (cache.tests.FileBasedCacheTests.test_cache_versioning_has_key) ... ok test_cache_versioning_incr_decr (cache.tests.FileBasedCacheTests.test_cache_versioning_incr_decr) ... ok test_cache_write_for_model_instance_with_deferred (cache.tests.FileBasedCacheTests.test_cache_write_for_model_instance_with_deferred) ... ok test_cache_write_unpicklable_object (cache.tests.FileBasedCacheTests.test_cache_write_unpicklable_object) ... ok test_clear (cache.tests.FileBasedCacheTests.test_clear) ... ok test_clear_does_not_remove_cache_dir (cache.tests.FileBasedCacheTests.test_clear_does_not_remove_cache_dir) ... ok test_close (cache.tests.FileBasedCacheTests.test_close) ... ok test_creates_cache_dir_if_nonexistent (cache.tests.FileBasedCacheTests.test_creates_cache_dir_if_nonexistent) ... ok test_cull (cache.tests.FileBasedCacheTests.test_cull) ... ok test_cull_delete_when_store_empty (cache.tests.FileBasedCacheTests.test_cull_delete_when_store_empty) ... ok test_custom_key_func (cache.tests.FileBasedCacheTests.test_custom_key_func) ... ok test_data_types (cache.tests.FileBasedCacheTests.test_data_types) ... ok test_decr (cache.tests.FileBasedCacheTests.test_decr) ... ok test_decr_version (cache.tests.FileBasedCacheTests.test_decr_version) ... ok test_default_used_when_none_is_set (cache.tests.FileBasedCacheTests.test_default_used_when_none_is_set) If None is cached, get() returns it instead of the default. ... ok test_delete (cache.tests.FileBasedCacheTests.test_delete) ... ok test_delete_many (cache.tests.FileBasedCacheTests.test_delete_many) ... ok test_delete_nonexistent (cache.tests.FileBasedCacheTests.test_delete_nonexistent) ... ok test_empty_cache_file_considered_expired (cache.tests.FileBasedCacheTests.test_empty_cache_file_considered_expired) ... ok test_expiration (cache.tests.FileBasedCacheTests.test_expiration) ... ok test_float_timeout (cache.tests.FileBasedCacheTests.test_float_timeout) ... ok test_forever_timeout (cache.tests.FileBasedCacheTests.test_forever_timeout) Passing in None into timeout results in a value that is cached forever ... ok test_get_does_not_ignore_non_filenotfound_exceptions (cache.tests.FileBasedCacheTests.test_get_does_not_ignore_non_filenotfound_exceptions) ... ok test_get_ignores_enoent (cache.tests.FileBasedCacheTests.test_get_ignores_enoent) ... ok test_get_many (cache.tests.FileBasedCacheTests.test_get_many) ... ok test_get_or_set (cache.tests.FileBasedCacheTests.test_get_or_set) ... ok test_get_or_set_callable (cache.tests.FileBasedCacheTests.test_get_or_set_callable) ... ok test_get_or_set_racing (cache.tests.FileBasedCacheTests.test_get_or_set_racing) ... ok test_get_or_set_version (cache.tests.FileBasedCacheTests.test_get_or_set_version) ... ok test_has_key (cache.tests.FileBasedCacheTests.test_has_key) ... ok test_ignores_non_cache_files (cache.tests.FileBasedCacheTests.test_ignores_non_cache_files) ... ok test_in (cache.tests.FileBasedCacheTests.test_in) ... ok test_incr (cache.tests.FileBasedCacheTests.test_incr) ... ok test_incr_version (cache.tests.FileBasedCacheTests.test_incr_version) ... ok test_invalid_key_characters (cache.tests.FileBasedCacheTests.test_invalid_key_characters) ... ok test_invalid_key_length (cache.tests.FileBasedCacheTests.test_invalid_key_length) ... ok test_long_timeout (cache.tests.FileBasedCacheTests.test_long_timeout) Follow memcached's convention where a timeout greater than 30 days is ... ok test_non_existent (cache.tests.FileBasedCacheTests.test_non_existent) Nonexistent cache keys return as None/default. ... ok test_prefix (cache.tests.FileBasedCacheTests.test_prefix) ... ok test_set_fail_on_pickleerror (cache.tests.FileBasedCacheTests.test_set_fail_on_pickleerror) ... ok test_set_many (cache.tests.FileBasedCacheTests.test_set_many) ... ok test_set_many_expiration (cache.tests.FileBasedCacheTests.test_set_many_expiration) ... ok test_set_many_returns_empty_list_on_success (cache.tests.FileBasedCacheTests.test_set_many_returns_empty_list_on_success) set_many() returns an empty list when all keys are inserted. ... ok test_simple (cache.tests.FileBasedCacheTests.test_simple) ... ok test_touch (cache.tests.FileBasedCacheTests.test_touch) ... ok test_unicode (cache.tests.FileBasedCacheTests.test_unicode) ... ok test_zero_cull (cache.tests.FileBasedCacheTests.test_zero_cull) ... ok test_zero_timeout (cache.tests.FileBasedCacheTests.test_zero_timeout) Passing in zero into timeout results in a value that is not cached ... ok test_add (cache.tests.FileBasedCachePathLibTests.test_add) ... ok test_add_fail_on_pickleerror (cache.tests.FileBasedCachePathLibTests.test_add_fail_on_pickleerror) ... ok test_binary_string (cache.tests.FileBasedCachePathLibTests.test_binary_string) ... ok test_cache_dir_permissions (cache.tests.FileBasedCachePathLibTests.test_cache_dir_permissions) ... ok test_cache_read_for_model_instance (cache.tests.FileBasedCachePathLibTests.test_cache_read_for_model_instance) ... ok test_cache_read_for_model_instance_with_deferred (cache.tests.FileBasedCachePathLibTests.test_cache_read_for_model_instance_with_deferred) ... ok test_cache_versioning_add (cache.tests.FileBasedCachePathLibTests.test_cache_versioning_add) ... ok test_cache_versioning_delete (cache.tests.FileBasedCachePathLibTests.test_cache_versioning_delete) ... ok test_cache_versioning_get_set (cache.tests.FileBasedCachePathLibTests.test_cache_versioning_get_set) ... ok test_cache_versioning_get_set_many (cache.tests.FileBasedCachePathLibTests.test_cache_versioning_get_set_many) ... ok test_cache_versioning_has_key (cache.tests.FileBasedCachePathLibTests.test_cache_versioning_has_key) ... ok test_cache_versioning_incr_decr (cache.tests.FileBasedCachePathLibTests.test_cache_versioning_incr_decr) ... ok test_cache_write_for_model_instance_with_deferred (cache.tests.FileBasedCachePathLibTests.test_cache_write_for_model_instance_with_deferred) ... ok test_cache_write_unpicklable_object (cache.tests.FileBasedCachePathLibTests.test_cache_write_unpicklable_object) ... ok test_clear (cache.tests.FileBasedCachePathLibTests.test_clear) ... ok test_clear_does_not_remove_cache_dir (cache.tests.FileBasedCachePathLibTests.test_clear_does_not_remove_cache_dir) ... ok test_close (cache.tests.FileBasedCachePathLibTests.test_close) ... ok test_creates_cache_dir_if_nonexistent (cache.tests.FileBasedCachePathLibTests.test_creates_cache_dir_if_nonexistent) ... ok test_cull (cache.tests.FileBasedCachePathLibTests.test_cull) ... ok test_cull_delete_when_store_empty (cache.tests.FileBasedCachePathLibTests.test_cull_delete_when_store_empty) ... ok test_custom_key_func (cache.tests.FileBasedCachePathLibTests.test_custom_key_func) ... ok test_data_types (cache.tests.FileBasedCachePathLibTests.test_data_types) ... ok test_decr (cache.tests.FileBasedCachePathLibTests.test_decr) ... ok test_decr_version (cache.tests.FileBasedCachePathLibTests.test_decr_version) ... ok test_default_used_when_none_is_set (cache.tests.FileBasedCachePathLibTests.test_default_used_when_none_is_set) If None is cached, get() returns it instead of the default. ... ok test_delete (cache.tests.FileBasedCachePathLibTests.test_delete) ... ok test_delete_many (cache.tests.FileBasedCachePathLibTests.test_delete_many) ... ok test_delete_nonexistent (cache.tests.FileBasedCachePathLibTests.test_delete_nonexistent) ... ok test_empty_cache_file_considered_expired (cache.tests.FileBasedCachePathLibTests.test_empty_cache_file_considered_expired) ... ok test_expiration (cache.tests.FileBasedCachePathLibTests.test_expiration) ... ok test_float_timeout (cache.tests.FileBasedCachePathLibTests.test_float_timeout) ... ok test_forever_timeout (cache.tests.FileBasedCachePathLibTests.test_forever_timeout) Passing in None into timeout results in a value that is cached forever ... ok test_get_does_not_ignore_non_filenotfound_exceptions (cache.tests.FileBasedCachePathLibTests.test_get_does_not_ignore_non_filenotfound_exceptions) ... ok test_get_ignores_enoent (cache.tests.FileBasedCachePathLibTests.test_get_ignores_enoent) ... ok test_get_many (cache.tests.FileBasedCachePathLibTests.test_get_many) ... ok test_get_or_set (cache.tests.FileBasedCachePathLibTests.test_get_or_set) ... ok test_get_or_set_callable (cache.tests.FileBasedCachePathLibTests.test_get_or_set_callable) ... ok test_get_or_set_racing (cache.tests.FileBasedCachePathLibTests.test_get_or_set_racing) ... ok test_get_or_set_version (cache.tests.FileBasedCachePathLibTests.test_get_or_set_version) ... ok test_has_key (cache.tests.FileBasedCachePathLibTests.test_has_key) ... ok test_ignores_non_cache_files (cache.tests.FileBasedCachePathLibTests.test_ignores_non_cache_files) ... ok test_in (cache.tests.FileBasedCachePathLibTests.test_in) ... ok test_incr (cache.tests.FileBasedCachePathLibTests.test_incr) ... ok test_incr_version (cache.tests.FileBasedCachePathLibTests.test_incr_version) ... ok test_invalid_key_characters (cache.tests.FileBasedCachePathLibTests.test_invalid_key_characters) ... ok test_invalid_key_length (cache.tests.FileBasedCachePathLibTests.test_invalid_key_length) ... ok test_long_timeout (cache.tests.FileBasedCachePathLibTests.test_long_timeout) Follow memcached's convention where a timeout greater than 30 days is ... ok test_non_existent (cache.tests.FileBasedCachePathLibTests.test_non_existent) Nonexistent cache keys return as None/default. ... ok test_prefix (cache.tests.FileBasedCachePathLibTests.test_prefix) ... ok test_set_fail_on_pickleerror (cache.tests.FileBasedCachePathLibTests.test_set_fail_on_pickleerror) ... ok test_set_many (cache.tests.FileBasedCachePathLibTests.test_set_many) ... ok test_set_many_expiration (cache.tests.FileBasedCachePathLibTests.test_set_many_expiration) ... ok test_set_many_returns_empty_list_on_success (cache.tests.FileBasedCachePathLibTests.test_set_many_returns_empty_list_on_success) set_many() returns an empty list when all keys are inserted. ... ok test_simple (cache.tests.FileBasedCachePathLibTests.test_simple) ... ok test_touch (cache.tests.FileBasedCachePathLibTests.test_touch) ... ok test_unicode (cache.tests.FileBasedCachePathLibTests.test_unicode) ... ok test_zero_cull (cache.tests.FileBasedCachePathLibTests.test_zero_cull) ... ok test_zero_timeout (cache.tests.FileBasedCachePathLibTests.test_zero_timeout) Passing in zero into timeout results in a value that is not cached ... ok test_input_not_found (auth_tests.test_management.MockInputTests.test_input_not_found) ... ok test_that_changepassword_command_with_database_option_uses_given_db (auth_tests.test_management.MultiDBChangepasswordManagementCommandTestCase.test_that_changepassword_command_with_database_option_uses_given_db) changepassword --database should operate on the specified DB. ... ok test_actual_implementation (auth_tests.test_management.GetDefaultUsernameTestCase.test_actual_implementation) ... ok test_existing (auth_tests.test_management.GetDefaultUsernameTestCase.test_existing) ... ok test_i18n (auth_tests.test_management.GetDefaultUsernameTestCase.test_i18n) ... ok test_simple (auth_tests.test_management.GetDefaultUsernameTestCase.test_simple) ... ok test_with_database (auth_tests.test_management.GetDefaultUsernameTestCase.test_with_database) ... ok test_createsuperuser_command_suggested_username_with_database_option (auth_tests.test_management.MultiDBCreatesuperuserTestCase.test_createsuperuser_command_suggested_username_with_database_option) ... ok test_createsuperuser_command_with_database_option (auth_tests.test_management.MultiDBCreatesuperuserTestCase.test_createsuperuser_command_with_database_option) createsuperuser --database should operate on the specified DB. ... ok test_changed_password_invalidates_session (auth_tests.test_middleware.TestAuthenticationMiddleware.test_changed_password_invalidates_session) ... ok test_no_password_change_does_not_invalidate_legacy_session (auth_tests.test_middleware.TestAuthenticationMiddleware.test_no_password_change_does_not_invalidate_legacy_session) ... ok test_no_password_change_doesnt_invalidate_session (auth_tests.test_middleware.TestAuthenticationMiddleware.test_no_password_change_doesnt_invalidate_session) ... ok test_no_session (auth_tests.test_middleware.TestAuthenticationMiddleware.test_no_session) ... ok test_session_default_hashing_algorithm (auth_tests.test_middleware.TestAuthenticationMiddleware.test_session_default_hashing_algorithm) ... ok test_access_mixin_permission_denied_remote_login_url (auth_tests.test_mixins.AccessMixinTests.test_access_mixin_permission_denied_remote_login_url) ... ok test_access_mixin_permission_denied_response (auth_tests.test_mixins.AccessMixinTests.test_access_mixin_permission_denied_response) ... ok test_stacked_mixins_missing_permission (auth_tests.test_mixins.AccessMixinTests.test_stacked_mixins_missing_permission) ... ok test_stacked_mixins_not_logged_in (auth_tests.test_mixins.AccessMixinTests.test_stacked_mixins_not_logged_in) ... ok test_stacked_mixins_success (auth_tests.test_mixins.AccessMixinTests.test_stacked_mixins_success) ... ok test_add (cache.tests.LocMemCacheTests.test_add) ... ok test_add_fail_on_pickleerror (cache.tests.LocMemCacheTests.test_add_fail_on_pickleerror) ... ok test_binary_string (cache.tests.LocMemCacheTests.test_binary_string) ... ok test_cache_read_for_model_instance (cache.tests.LocMemCacheTests.test_cache_read_for_model_instance) ... ok test_cache_read_for_model_instance_with_deferred (cache.tests.LocMemCacheTests.test_cache_read_for_model_instance_with_deferred) ... ok test_cache_versioning_add (cache.tests.LocMemCacheTests.test_cache_versioning_add) ... ok test_cache_versioning_delete (cache.tests.LocMemCacheTests.test_cache_versioning_delete) ... ok test_cache_versioning_get_set (cache.tests.LocMemCacheTests.test_cache_versioning_get_set) ... ok test_cache_versioning_get_set_many (cache.tests.LocMemCacheTests.test_cache_versioning_get_set_many) ... ok test_cache_versioning_has_key (cache.tests.LocMemCacheTests.test_cache_versioning_has_key) ... ok test_cache_versioning_incr_decr (cache.tests.LocMemCacheTests.test_cache_versioning_incr_decr) ... ok test_cache_write_for_model_instance_with_deferred (cache.tests.LocMemCacheTests.test_cache_write_for_model_instance_with_deferred) ... ok test_cache_write_unpicklable_object (cache.tests.LocMemCacheTests.test_cache_write_unpicklable_object) ... ok test_clear (cache.tests.LocMemCacheTests.test_clear) ... ok test_close (cache.tests.LocMemCacheTests.test_close) ... ok test_cull (cache.tests.LocMemCacheTests.test_cull) ... ok test_cull_delete_when_store_empty (cache.tests.LocMemCacheTests.test_cull_delete_when_store_empty) ... ok test_custom_key_func (cache.tests.LocMemCacheTests.test_custom_key_func) ... ok test_data_types (cache.tests.LocMemCacheTests.test_data_types) ... ok test_decr (cache.tests.LocMemCacheTests.test_decr) ... ok test_decr_version (cache.tests.LocMemCacheTests.test_decr_version) ... ok test_default_used_when_none_is_set (cache.tests.LocMemCacheTests.test_default_used_when_none_is_set) If None is cached, get() returns it instead of the default. ... ok test_delete (cache.tests.LocMemCacheTests.test_delete) ... ok test_delete_many (cache.tests.LocMemCacheTests.test_delete_many) ... ok test_delete_nonexistent (cache.tests.LocMemCacheTests.test_delete_nonexistent) ... ok test_expiration (cache.tests.LocMemCacheTests.test_expiration) ... ok test_float_timeout (cache.tests.LocMemCacheTests.test_float_timeout) ... ok test_forever_timeout (cache.tests.LocMemCacheTests.test_forever_timeout) Passing in None into timeout results in a value that is cached forever ... ok test_get_many (cache.tests.LocMemCacheTests.test_get_many) ... ok test_get_or_set (cache.tests.LocMemCacheTests.test_get_or_set) ... ok test_get_or_set_callable (cache.tests.LocMemCacheTests.test_get_or_set_callable) ... ok test_get_or_set_racing (cache.tests.LocMemCacheTests.test_get_or_set_racing) ... ok test_get_or_set_version (cache.tests.LocMemCacheTests.test_get_or_set_version) ... ok test_has_key (cache.tests.LocMemCacheTests.test_has_key) ... ok test_in (cache.tests.LocMemCacheTests.test_in) ... ok test_incr (cache.tests.LocMemCacheTests.test_incr) ... ok test_incr_decr_timeout (cache.tests.LocMemCacheTests.test_incr_decr_timeout) incr/decr does not modify expiry time (matches memcached behavior) ... ok test_incr_version (cache.tests.LocMemCacheTests.test_incr_version) ... ok test_invalid_key_characters (cache.tests.LocMemCacheTests.test_invalid_key_characters) ... ok test_invalid_key_length (cache.tests.LocMemCacheTests.test_invalid_key_length) ... ok test_locking_on_pickle (cache.tests.LocMemCacheTests.test_locking_on_pickle) #20613/#18541 -- Ensures pickling is done outside of the lock. ... ok test_long_timeout (cache.tests.LocMemCacheTests.test_long_timeout) Follow memcached's convention where a timeout greater than 30 days is ... ok test_lru_get (cache.tests.LocMemCacheTests.test_lru_get) get() moves cache keys. ... ok test_lru_incr (cache.tests.LocMemCacheTests.test_lru_incr) incr() moves cache keys. ... ok test_lru_set (cache.tests.LocMemCacheTests.test_lru_set) set() moves cache keys. ... ok test_multiple_caches (cache.tests.LocMemCacheTests.test_multiple_caches) Multiple locmem caches are isolated ... ok test_non_existent (cache.tests.LocMemCacheTests.test_non_existent) Nonexistent cache keys return as None/default. ... ok test_prefix (cache.tests.LocMemCacheTests.test_prefix) ... ok test_set_fail_on_pickleerror (cache.tests.LocMemCacheTests.test_set_fail_on_pickleerror) ... ok test_set_many (cache.tests.LocMemCacheTests.test_set_many) ... ok test_set_many_expiration (cache.tests.LocMemCacheTests.test_set_many_expiration) ... ok test_set_many_returns_empty_list_on_success (cache.tests.LocMemCacheTests.test_set_many_returns_empty_list_on_success) set_many() returns an empty list when all keys are inserted. ... ok test_simple (cache.tests.LocMemCacheTests.test_simple) ... ok test_touch (cache.tests.LocMemCacheTests.test_touch) ... ok test_unicode (cache.tests.LocMemCacheTests.test_unicode) ... ok test_zero_cull (cache.tests.LocMemCacheTests.test_zero_cull) ... ok test_zero_timeout (cache.tests.LocMemCacheTests.test_zero_timeout) Passing in zero into timeout results in a value that is not cached ... ok test_login_required (auth_tests.test_mixins.LoginRequiredMixinTests.test_login_required) login_required works on a simple view wrapped in a login_required ... ok test_many_permissions_pass (auth_tests.test_mixins.PermissionsRequiredMixinTests.test_many_permissions_pass) ... ok test_permissioned_denied_exception_raised (auth_tests.test_mixins.PermissionsRequiredMixinTests.test_permissioned_denied_exception_raised) ... ok test_permissioned_denied_redirect (auth_tests.test_mixins.PermissionsRequiredMixinTests.test_permissioned_denied_redirect) ... ok test_single_permission_pass (auth_tests.test_mixins.PermissionsRequiredMixinTests.test_single_permission_pass) ... ok test_builtin_user_isactive (auth_tests.test_models.IsActiveTestCase.test_builtin_user_isactive) ... ok test_is_active_field_default (auth_tests.test_models.IsActiveTestCase.test_is_active_field_default) tests that the default value for is_active is provided ... ok test_load_data_with_user_permissions (auth_tests.test_models.LoadDataWithNaturalKeysAndMultipleDatabasesTestCase.test_load_data_with_user_permissions) ... ok test_user_is_created_and_added_to_group (auth_tests.test_models.LoadDataWithNaturalKeysTestCase.test_user_is_created_and_added_to_group) ... ok test_user_is_created_and_added_to_group (auth_tests.test_models.LoadDataWithoutNaturalKeysTestCase.test_user_is_created_and_added_to_group) ... ok test_str (auth_tests.test_models.PermissionTests.test_str) ... ok test_group_natural_key (auth_tests.test_models.NaturalKeysTestCase.test_group_natural_key) ... ok test_user_natural_key (auth_tests.test_models.NaturalKeysTestCase.test_user_natural_key) ... ok test_create_superuser (auth_tests.test_models.TestCreateSuperUserSignals.test_create_superuser) ... ok test_create_user (auth_tests.test_models.TestCreateSuperUserSignals.test_create_user) ... ok test_basic_usage (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_basic_usage) Check the operation of the createsuperuser management command ... ok test_blank_username (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_blank_username) Creation fails if --username is blank. ... ok test_blank_username_non_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_blank_username_non_interactive) ... ok test_default_username (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_default_username) createsuperuser uses a default username when one isn't provided. ... ok test_email_in_username (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_email_in_username) ... ok test_environment_variable_non_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_environment_variable_non_interactive) ... ok test_existing_username (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_existing_username) Creation fails if the username already exists. ... ok test_existing_username_non_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_existing_username_non_interactive) Creation fails if the username already exists. ... ok test_existing_username_provided_via_option_and_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_existing_username_provided_via_option_and_interactive) call_command() gets username='janet' and interactive=True. ... ok test_fields_with_fk (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_fields_with_fk) ... ok test_fields_with_fk_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_fields_with_fk_interactive) ... ok test_fields_with_m2m (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_fields_with_m2m) ... ok test_fields_with_m2m_and_through (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_fields_with_m2m_and_through) ... ok test_fields_with_m2m_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_fields_with_m2m_interactive) ... ok test_fields_with_m2m_interactive_blank (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_fields_with_m2m_interactive_blank) ... ok test_ignore_environment_variable_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_ignore_environment_variable_interactive) ... ok test_ignore_environment_variable_non_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_ignore_environment_variable_non_interactive) ... ok test_invalid_username (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_invalid_username) Creation fails if the username fails validation. ... ok test_keyboard_interrupt (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_keyboard_interrupt) ... ok test_no_email_argument (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_no_email_argument) ... ok test_non_ascii_verbose_name (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_non_ascii_verbose_name) ... ok test_passing_stdin (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_passing_stdin) You can pass a stdin object as an option and it should be ... ok test_password_validation (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_password_validation) Creation should fail if the password fails validation. ... ok test_password_validation_bypass (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_password_validation_bypass) Password validation can be bypassed by entering 'y' at the prompt. ... ok test_skip_if_not_in_TTY (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_skip_if_not_in_TTY) If the command is not called from a TTY, it should be skipped and a ... ok test_swappable_user (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_swappable_user) A superuser can be created when a custom user model is in use ... ok test_swappable_user_missing_required_field (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_swappable_user_missing_required_field) A Custom superuser won't be created when a required field isn't provided ... ok test_swappable_user_username_non_unique (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_swappable_user_username_non_unique) ... ok test_usermodel_without_password (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_usermodel_without_password) ... ok test_usermodel_without_password_interactive (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_usermodel_without_password_interactive) ... ok test_validate_password_against_required_fields (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_validate_password_against_required_fields) ... ok test_validate_password_against_username (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_validate_password_against_username) ... ok test_validation_blank_password_entered (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_validation_blank_password_entered) Creation should fail if the user enters blank passwords. ... ok test_validation_mismatched_passwords (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_validation_mismatched_passwords) Creation should fail if the user enters mismatched passwords. ... ok test_verbosity_zero (auth_tests.test_management.CreatesuperuserManagementCommandTestCase.test_verbosity_zero) ... ok test_access (auth_tests.test_password_reset_timeout_days.DeprecationTests.test_access) ... ok test_access_warning (auth_tests.test_password_reset_timeout_days.DeprecationTests.test_access_warning) ... ok test_override_settings_warning (auth_tests.test_password_reset_timeout_days.DeprecationTests.test_override_settings_warning) ... ok test_settings_init_warning (auth_tests.test_password_reset_timeout_days.DeprecationTests.test_settings_init_warning) ... ok test_timeout (auth_tests.test_password_reset_timeout_days.DeprecationTests.test_timeout) The token is valid after n days, but no greater. ... ok test_use_both_settings_init_error (auth_tests.test_password_reset_timeout_days.DeprecationTests.test_use_both_settings_init_error) ... ok test_backend_without_with_perm (auth_tests.test_models.UserWithPermTestCase.test_backend_without_with_perm) ... ok test_basic (auth_tests.test_models.UserWithPermTestCase.test_basic) ... ok test_custom_backend (auth_tests.test_models.UserWithPermTestCase.test_custom_backend) ... ok test_custom_backend_pass_obj (auth_tests.test_models.UserWithPermTestCase.test_custom_backend_pass_obj) ... ok test_invalid_backend_type (auth_tests.test_models.UserWithPermTestCase.test_invalid_backend_type) ... ok test_invalid_permission_name (auth_tests.test_models.UserWithPermTestCase.test_invalid_permission_name) ... ok test_invalid_permission_type (auth_tests.test_models.UserWithPermTestCase.test_invalid_permission_type) ... ok test_multiple_backends (auth_tests.test_models.UserWithPermTestCase.test_multiple_backends) ... ok test_nonexistent_backend (auth_tests.test_models.UserWithPermTestCase.test_nonexistent_backend) ... ok test_nonexistent_permission (auth_tests.test_models.UserWithPermTestCase.test_nonexistent_permission) ... ok test_check_password_upgrade (auth_tests.test_models.AbstractUserTestCase.test_check_password_upgrade) password_changed() shouldn't be called if User.check_password() ... ok test_email_user (auth_tests.test_models.AbstractUserTestCase.test_email_user) ... ok test_last_login_default (auth_tests.test_models.AbstractUserTestCase.test_last_login_default) ... ok test_user_clean_normalize_email (auth_tests.test_models.AbstractUserTestCase.test_user_clean_normalize_email) ... ok test_user_double_save (auth_tests.test_models.AbstractUserTestCase.test_user_double_save) Calling user.save() twice should trigger password_changed() once. ... ok test_csrf_validation_passes_after_process_request_login (auth_tests.test_remote_user.CustomHeaderRemoteUserTest.test_csrf_validation_passes_after_process_request_login) CSRF check must access the CSRF token from the session or cookie, ... ok test_header_disappears (auth_tests.test_remote_user.CustomHeaderRemoteUserTest.test_header_disappears) A logged in user is logged out automatically when ... ok test_inactive_user (auth_tests.test_remote_user.CustomHeaderRemoteUserTest.test_inactive_user) ... ok test_known_user (auth_tests.test_remote_user.CustomHeaderRemoteUserTest.test_known_user) Tests the case where the username passed in the header is a valid User. ... ok test_last_login (auth_tests.test_remote_user.CustomHeaderRemoteUserTest.test_last_login) A user's last_login is set the first time they make a ... ok test_no_remote_user (auth_tests.test_remote_user.CustomHeaderRemoteUserTest.test_no_remote_user) Tests requests where no remote user is specified and insures that no ... ok test_unknown_user (auth_tests.test_remote_user.CustomHeaderRemoteUserTest.test_unknown_user) Tests the case where the username passed in the header does not exist ... ok test_user_switch_forces_new_login (auth_tests.test_remote_user.CustomHeaderRemoteUserTest.test_user_switch_forces_new_login) If the username in the header changes between requests ... ok test_csrf_validation_passes_after_process_request_login (auth_tests.test_remote_user.AllowAllUsersRemoteUserBackendTest.test_csrf_validation_passes_after_process_request_login) CSRF check must access the CSRF token from the session or cookie, ... ok test_header_disappears (auth_tests.test_remote_user.AllowAllUsersRemoteUserBackendTest.test_header_disappears) A logged in user is logged out automatically when ... ok test_inactive_user (auth_tests.test_remote_user.AllowAllUsersRemoteUserBackendTest.test_inactive_user) ... ok test_known_user (auth_tests.test_remote_user.AllowAllUsersRemoteUserBackendTest.test_known_user) Tests the case where the username passed in the header is a valid User. ... ok test_last_login (auth_tests.test_remote_user.AllowAllUsersRemoteUserBackendTest.test_last_login) A user's last_login is set the first time they make a ... ok test_no_remote_user (auth_tests.test_remote_user.AllowAllUsersRemoteUserBackendTest.test_no_remote_user) Tests requests where no remote user is specified and insures that no ... ok test_unknown_user (auth_tests.test_remote_user.AllowAllUsersRemoteUserBackendTest.test_unknown_user) Tests the case where the username passed in the header does not exist ... ok test_user_switch_forces_new_login (auth_tests.test_remote_user.AllowAllUsersRemoteUserBackendTest.test_user_switch_forces_new_login) If the username in the header changes between requests ... ok test_csrf_validation_passes_after_process_request_login (auth_tests.test_remote_user.PersistentRemoteUserTest.test_csrf_validation_passes_after_process_request_login) CSRF check must access the CSRF token from the session or cookie, ... ok test_header_disappears (auth_tests.test_remote_user.PersistentRemoteUserTest.test_header_disappears) A logged in user is kept logged in even if the REMOTE_USER header ... ok test_inactive_user (auth_tests.test_remote_user.PersistentRemoteUserTest.test_inactive_user) ... ok test_known_user (auth_tests.test_remote_user.PersistentRemoteUserTest.test_known_user) Tests the case where the username passed in the header is a valid User. ... ok test_last_login (auth_tests.test_remote_user.PersistentRemoteUserTest.test_last_login) A user's last_login is set the first time they make a ... ok test_no_remote_user (auth_tests.test_remote_user.PersistentRemoteUserTest.test_no_remote_user) Tests requests where no remote user is specified and insures that no ... ok test_unknown_user (auth_tests.test_remote_user.PersistentRemoteUserTest.test_unknown_user) Tests the case where the username passed in the header does not exist ... ok test_user_switch_forces_new_login (auth_tests.test_remote_user.PersistentRemoteUserTest.test_user_switch_forces_new_login) If the username in the header changes between requests ... ok test_csrf_validation_passes_after_process_request_login (auth_tests.test_remote_user.RemoteUserNoCreateTest.test_csrf_validation_passes_after_process_request_login) CSRF check must access the CSRF token from the session or cookie, ... ok test_header_disappears (auth_tests.test_remote_user.RemoteUserNoCreateTest.test_header_disappears) A logged in user is logged out automatically when ... ok test_inactive_user (auth_tests.test_remote_user.RemoteUserNoCreateTest.test_inactive_user) ... ok test_known_user (auth_tests.test_remote_user.RemoteUserNoCreateTest.test_known_user) Tests the case where the username passed in the header is a valid User. ... ok test_last_login (auth_tests.test_remote_user.RemoteUserNoCreateTest.test_last_login) A user's last_login is set the first time they make a ... ok test_no_remote_user (auth_tests.test_remote_user.RemoteUserNoCreateTest.test_no_remote_user) Tests requests where no remote user is specified and insures that no ... ok test_unknown_user (auth_tests.test_remote_user.RemoteUserNoCreateTest.test_unknown_user) ... ok test_user_switch_forces_new_login (auth_tests.test_remote_user.RemoteUserNoCreateTest.test_user_switch_forces_new_login) If the username in the header changes between requests ... ok test_csrf_validation_passes_after_process_request_login (auth_tests.test_remote_user.RemoteUserCustomTest.test_csrf_validation_passes_after_process_request_login) CSRF check must access the CSRF token from the session or cookie, ... ok test_header_disappears (auth_tests.test_remote_user.RemoteUserCustomTest.test_header_disappears) A logged in user is logged out automatically when ... ok test_inactive_user (auth_tests.test_remote_user.RemoteUserCustomTest.test_inactive_user) ... ok test_known_user (auth_tests.test_remote_user.RemoteUserCustomTest.test_known_user) The strings passed in REMOTE_USER should be cleaned and the known users ... ok test_last_login (auth_tests.test_remote_user.RemoteUserCustomTest.test_last_login) A user's last_login is set the first time they make a ... ok test_no_remote_user (auth_tests.test_remote_user.RemoteUserCustomTest.test_no_remote_user) Tests requests where no remote user is specified and insures that no ... ok test_unknown_user (auth_tests.test_remote_user.RemoteUserCustomTest.test_unknown_user) The unknown user created should be configured with an email address ... ok test_user_switch_forces_new_login (auth_tests.test_remote_user.RemoteUserCustomTest.test_user_switch_forces_new_login) If the username in the header changes between requests ... ok test_csrf_validation_passes_after_process_request_login (auth_tests.test_remote_user.RemoteUserTest.test_csrf_validation_passes_after_process_request_login) CSRF check must access the CSRF token from the session or cookie, ... ok test_header_disappears (auth_tests.test_remote_user.RemoteUserTest.test_header_disappears) A logged in user is logged out automatically when ... ok test_inactive_user (auth_tests.test_remote_user.RemoteUserTest.test_inactive_user) ... ok test_known_user (auth_tests.test_remote_user.RemoteUserTest.test_known_user) Tests the case where the username passed in the header is a valid User. ... ok test_last_login (auth_tests.test_remote_user.RemoteUserTest.test_last_login) A user's last_login is set the first time they make a ... ok test_no_remote_user (auth_tests.test_remote_user.RemoteUserTest.test_no_remote_user) Tests requests where no remote user is specified and insures that no ... ok test_unknown_user (auth_tests.test_remote_user.RemoteUserTest.test_unknown_user) Tests the case where the username passed in the header does not exist ... ok test_user_switch_forces_new_login (auth_tests.test_remote_user.RemoteUserTest.test_user_switch_forces_new_login) If the username in the header changes between requests ... ok test_help_text (auth_tests.test_validators.UserAttributeSimilarityValidatorTest.test_help_text) ... ok test_validate (auth_tests.test_validators.UserAttributeSimilarityValidatorTest.test_validate) ... ok test_validate_property (auth_tests.test_validators.UserAttributeSimilarityValidatorTest.test_validate_property) ... ok test_failed_login_without_request (auth_tests.test_signals.SignalTestCase.test_failed_login_without_request) ... ok test_login (auth_tests.test_signals.SignalTestCase.test_login) ... ok test_login_with_custom_user_without_last_login_field (auth_tests.test_signals.SignalTestCase.test_login_with_custom_user_without_last_login_field) The user_logged_in signal is only registered if the user model has a ... ok test_logout (auth_tests.test_signals.SignalTestCase.test_logout) ... ok test_logout_anonymous (auth_tests.test_signals.SignalTestCase.test_logout_anonymous) ... ok test_update_last_login (auth_tests.test_signals.SignalTestCase.test_update_last_login) Only `last_login` is updated in `update_last_login` ... ok test_named_urls (auth_tests.test_views.AuthViewNamedURLTests.test_named_urls) Named URLs should be reversible ... ok test_password_change_done_view (auth_tests.test_templates.AuthTemplateTests.test_password_change_done_view) ... ok test_password_reset_change_view (auth_tests.test_templates.AuthTemplateTests.test_password_reset_change_view) ... ok test_password_reset_complete_view (auth_tests.test_templates.AuthTemplateTests.test_password_reset_complete_view) ... ok test_password_reset_confirm_view_custom_username_hint (auth_tests.test_templates.AuthTemplateTests.test_password_reset_confirm_view_custom_username_hint) ... ok test_password_reset_confirm_view_invalid_token (auth_tests.test_templates.AuthTemplateTests.test_password_reset_confirm_view_invalid_token) ... ok test_password_reset_confirm_view_valid_token (auth_tests.test_templates.AuthTemplateTests.test_password_reset_confirm_view_valid_token) ... ok test_password_reset_done_view (auth_tests.test_templates.AuthTemplateTests.test_password_reset_done_view) ... ok test_password_reset_view (auth_tests.test_templates.AuthTemplateTests.test_password_reset_view) ... ok test_10265 (auth_tests.test_tokens.TokenGeneratorTest.test_10265) The token generated for a user created in the same request ... ok test_check_token_with_nonexistent_token_and_user (auth_tests.test_tokens.TokenGeneratorTest.test_check_token_with_nonexistent_token_and_user) ... ok test_legacy_days_timeout (auth_tests.test_tokens.TokenGeneratorTest.test_legacy_days_timeout) ... ok test_legacy_token_validation (auth_tests.test_tokens.TokenGeneratorTest.test_legacy_token_validation) ... ok test_make_token (auth_tests.test_tokens.TokenGeneratorTest.test_make_token) ... ok test_timeout (auth_tests.test_tokens.TokenGeneratorTest.test_timeout) The token is valid after n seconds, but no greater. ... ok test_token_default_hashing_algorithm (auth_tests.test_tokens.TokenGeneratorTest.test_token_default_hashing_algorithm) ... ok test_token_with_different_email (auth_tests.test_tokens.TokenGeneratorTest.test_token_with_different_email) Updating the user email address invalidates the token. ... ok test_token_with_different_secret (auth_tests.test_tokens.TokenGeneratorTest.test_token_with_different_secret) A valid token can be created with a secret other than SECRET_KEY by ... ok test_confirm_valid_custom_user (auth_tests.test_views.CustomUserPasswordResetTest.test_confirm_valid_custom_user) ... ok test_custom (auth_tests.test_views.LoginRedirectUrlTest.test_custom) ... ok test_default (auth_tests.test_views.LoginRedirectUrlTest.test_default) ... ok test_named (auth_tests.test_views.LoginRedirectUrlTest.test_named) ... ok test_remote (auth_tests.test_views.LoginRedirectUrlTest.test_remote) ... ok test_password_change_done_fails (auth_tests.test_views.ChangePasswordTest.test_password_change_done_fails) ... ok test_password_change_done_succeeds (auth_tests.test_views.ChangePasswordTest.test_password_change_done_succeeds) ... ok test_password_change_fails_with_invalid_old_password (auth_tests.test_views.ChangePasswordTest.test_password_change_fails_with_invalid_old_password) ... ok test_password_change_fails_with_mismatched_passwords (auth_tests.test_views.ChangePasswordTest.test_password_change_fails_with_mismatched_passwords) ... ok test_password_change_redirect_custom (auth_tests.test_views.ChangePasswordTest.test_password_change_redirect_custom) ... ok test_password_change_redirect_custom_named (auth_tests.test_views.ChangePasswordTest.test_password_change_redirect_custom_named) ... ok test_password_change_redirect_default (auth_tests.test_views.ChangePasswordTest.test_password_change_redirect_default) ... ok test_password_change_succeeds (auth_tests.test_views.ChangePasswordTest.test_password_change_succeeds) ... ok test_success_url_allowed_hosts_safe_host (auth_tests.test_views.LoginSuccessURLAllowedHostsTest.test_success_url_allowed_hosts_safe_host) ... ok test_success_url_allowed_hosts_same_host (auth_tests.test_views.LoginSuccessURLAllowedHostsTest.test_success_url_allowed_hosts_same_host) ... ok test_success_url_allowed_hosts_unsafe_host (auth_tests.test_views.LoginSuccessURLAllowedHostsTest.test_success_url_allowed_hosts_unsafe_host) ... ok test_default (auth_tests.test_views.LoginRedirectAuthenticatedUser.test_default) Stay on the login page by default. ... ok test_guest (auth_tests.test_views.LoginRedirectAuthenticatedUser.test_guest) If not logged in, stay on the same page. ... ok test_permission_required_logged_in (auth_tests.test_views.LoginRedirectAuthenticatedUser.test_permission_required_logged_in) ... ok test_permission_required_not_logged_in (auth_tests.test_views.LoginRedirectAuthenticatedUser.test_permission_required_not_logged_in) ... ok test_redirect (auth_tests.test_views.LoginRedirectAuthenticatedUser.test_redirect) If logged in, go to default redirected URL. ... ok test_redirect_loop (auth_tests.test_views.LoginRedirectAuthenticatedUser.test_redirect_loop) Detect a redirect loop if LOGIN_REDIRECT_URL is not correctly set, ... ok test_redirect_param (auth_tests.test_views.LoginRedirectAuthenticatedUser.test_redirect_param) If next is specified as a GET parameter, go there. ... ok test_redirect_url (auth_tests.test_views.LoginRedirectAuthenticatedUser.test_redirect_url) If logged in, go to custom redirected URL. ... ok test_https_login_url (auth_tests.test_views.LoginURLSettings.test_https_login_url) ... ok test_lazy_login_url (auth_tests.test_views.LoginURLSettings.test_lazy_login_url) ... ok test_login_url_with_querystring (auth_tests.test_views.LoginURLSettings.test_login_url_with_querystring) ... ok test_named_login_url (auth_tests.test_views.LoginURLSettings.test_named_login_url) ... ok test_remote_login_url (auth_tests.test_views.LoginURLSettings.test_remote_login_url) ... ok test_remote_login_url_with_next_querystring (auth_tests.test_views.LoginURLSettings.test_remote_login_url_with_next_querystring) ... ok test_standard_login_url (auth_tests.test_views.LoginURLSettings.test_standard_login_url) ... ok test_default_logout_then_login (auth_tests.test_views.LogoutThenLoginTests.test_default_logout_then_login) ... ok test_logout_then_login_with_custom_login (auth_tests.test_views.LogoutThenLoginTests.test_logout_then_login_with_custom_login) ... ok test_current_site_in_context_after_login (auth_tests.test_views.LoginTest.test_current_site_in_context_after_login) ... ok test_legacy_session_key_flushed_on_login (auth_tests.test_views.LoginTest.test_legacy_session_key_flushed_on_login) ... ok test_login_csrf_rotate (auth_tests.test_views.LoginTest.test_login_csrf_rotate) Makes sure that a login rotates the currently-used CSRF token. ... ok test_login_form_contains_request (auth_tests.test_views.LoginTest.test_login_form_contains_request) ... ok test_login_session_without_hash_session_key (auth_tests.test_views.LoginTest.test_login_session_without_hash_session_key) Session without django.contrib.auth.HASH_SESSION_KEY should login ... ok test_security_check (auth_tests.test_views.LoginTest.test_security_check) ... ok test_security_check_https (auth_tests.test_views.LoginTest.test_security_check_https) ... ok test_session_key_flushed_on_login (auth_tests.test_views.LoginTest.test_session_key_flushed_on_login) To avoid reusing another user's session, ensure a new, empty session is ... ok test_session_key_flushed_on_login_after_password_change (auth_tests.test_views.LoginTest.test_session_key_flushed_on_login_after_password_change) As above, but same user logging in after a password change. ... ok test_redirect_to_login_with_lazy (auth_tests.test_views.RedirectToLoginTests.test_redirect_to_login_with_lazy) ... ok test_redirect_to_login_with_lazy_and_unicode (auth_tests.test_views.RedirectToLoginTests.test_redirect_to_login_with_lazy_and_unicode) ... ok test_user_password_change_updates_session (auth_tests.test_views.SessionAuthenticationTests.test_user_password_change_updates_session) #21649 - Ensure contrib.auth.views.password_change updates the user's ... ok test_confirm_invalid_uuid (auth_tests.test_views.UUIDUserPasswordResetTest.test_confirm_invalid_uuid) A uidb64 that decodes to a non-UUID doesn't crash. ... ok test_confirm_valid_custom_user (auth_tests.test_views.UUIDUserPasswordResetTest.test_confirm_valid_custom_user) ... ok test_14377 (auth_tests.test_views.LogoutTest.test_14377) ... ok test_logout_default (auth_tests.test_views.LogoutTest.test_logout_default) Logout without next_page option renders the default template ... ok test_logout_doesnt_cache (auth_tests.test_views.LogoutTest.test_logout_doesnt_cache) The logout() view should send "no-cache" headers for reasons described ... ok test_logout_preserve_language (auth_tests.test_views.LogoutTest.test_logout_preserve_language) Language is preserved after logout. ... ok test_logout_redirect_url_named_setting (auth_tests.test_views.LogoutTest.test_logout_redirect_url_named_setting) ... ok test_logout_redirect_url_setting (auth_tests.test_views.LogoutTest.test_logout_redirect_url_setting) ... ok test_logout_with_custom_redirect_argument (auth_tests.test_views.LogoutTest.test_logout_with_custom_redirect_argument) Logout with custom query string redirects to specified resource ... ok test_logout_with_named_redirect (auth_tests.test_views.LogoutTest.test_logout_with_named_redirect) Logout resolves names or URLs passed as next_page. ... ok test_logout_with_next_page_specified (auth_tests.test_views.LogoutTest.test_logout_with_next_page_specified) Logout with next_page option given redirects to specified resource ... ok test_logout_with_overridden_redirect_url (auth_tests.test_views.LogoutTest.test_logout_with_overridden_redirect_url) ... ok test_logout_with_post (auth_tests.test_views.LogoutTest.test_logout_with_post) ... ok test_logout_with_redirect_argument (auth_tests.test_views.LogoutTest.test_logout_with_redirect_argument) Logout with query string redirects to specified resource ... ok test_security_check (auth_tests.test_views.LogoutTest.test_security_check) ... ok test_security_check_https (auth_tests.test_views.LogoutTest.test_security_check_https) ... ok test_success_url_allowed_hosts_safe_host (auth_tests.test_views.LogoutTest.test_success_url_allowed_hosts_safe_host) ... ok test_success_url_allowed_hosts_same_host (auth_tests.test_views.LogoutTest.test_success_url_allowed_hosts_same_host) ... ok test_success_url_allowed_hosts_unsafe_host (auth_tests.test_views.LogoutTest.test_success_url_allowed_hosts_unsafe_host) ... ok test_basic (save_delete_hooks.tests.SaveDeleteHookTests.test_basic) ... ok test_access (deprecation.test_default_hashing_algorithm.DefaultHashingAlgorithmDeprecationTests.test_access) ... ok test_override_settings_warning (deprecation.test_default_hashing_algorithm.DefaultHashingAlgorithmDeprecationTests.test_override_settings_warning) ... ok test_settings_init_warning (deprecation.test_default_hashing_algorithm.DefaultHashingAlgorithmDeprecationTests.test_settings_init_warning) ... ok test_system_check_invalid_value (deprecation.test_default_hashing_algorithm.DefaultHashingAlgorithmDeprecationTests.test_system_check_invalid_value) ... ok test_system_check_valid_value (deprecation.test_default_hashing_algorithm.DefaultHashingAlgorithmDeprecationTests.test_system_check_valid_value) ... ok test_confirm_complete (auth_tests.test_views.PasswordResetTest.test_confirm_complete) ... ok test_confirm_custom_reset_url_token (auth_tests.test_views.PasswordResetTest.test_confirm_custom_reset_url_token) ... ok test_confirm_custom_reset_url_token_link_redirects_to_set_password_page (auth_tests.test_views.PasswordResetTest.test_confirm_custom_reset_url_token_link_redirects_to_set_password_page) ... ok test_confirm_different_passwords (auth_tests.test_views.PasswordResetTest.test_confirm_different_passwords) ... ok test_confirm_display_user_from_form (auth_tests.test_views.PasswordResetTest.test_confirm_display_user_from_form) ... ok test_confirm_invalid (auth_tests.test_views.PasswordResetTest.test_confirm_invalid) ... ok test_confirm_invalid_hash (auth_tests.test_views.PasswordResetTest.test_confirm_invalid_hash) A POST with an invalid token is rejected. ... ok test_confirm_invalid_post (auth_tests.test_views.PasswordResetTest.test_confirm_invalid_post) ... ok test_confirm_invalid_user (auth_tests.test_views.PasswordResetTest.test_confirm_invalid_user) ... ok test_confirm_link_redirects_to_set_password_page (auth_tests.test_views.PasswordResetTest.test_confirm_link_redirects_to_set_password_page) ... ok test_confirm_login_post_reset (auth_tests.test_views.PasswordResetTest.test_confirm_login_post_reset) ... ok test_confirm_login_post_reset_already_logged_in (auth_tests.test_views.PasswordResetTest.test_confirm_login_post_reset_already_logged_in) ... ok test_confirm_login_post_reset_custom_backend (auth_tests.test_views.PasswordResetTest.test_confirm_login_post_reset_custom_backend) ... ok test_confirm_overflow_user (auth_tests.test_views.PasswordResetTest.test_confirm_overflow_user) ... ok test_confirm_redirect_custom (auth_tests.test_views.PasswordResetTest.test_confirm_redirect_custom) ... ok test_confirm_redirect_custom_named (auth_tests.test_views.PasswordResetTest.test_confirm_redirect_custom_named) ... ok test_confirm_redirect_default (auth_tests.test_views.PasswordResetTest.test_confirm_redirect_default) ... ok test_confirm_valid (auth_tests.test_views.PasswordResetTest.test_confirm_valid) ... ok test_email_found (auth_tests.test_views.PasswordResetTest.test_email_found) Email is sent if a valid email address is provided for password reset ... ok test_email_found_custom_from (auth_tests.test_views.PasswordResetTest.test_email_found_custom_from) Email is sent if a valid email address is provided for password reset when a custom from_email is provided. ... ok test_email_not_found (auth_tests.test_views.PasswordResetTest.test_email_not_found) If the provided email is not registered, don't raise any error but ... ok test_extra_email_context (auth_tests.test_views.PasswordResetTest.test_extra_email_context) extra_email_context should be available in the email template context. ... ok test_html_mail_template (auth_tests.test_views.PasswordResetTest.test_html_mail_template) A multipart email with text/plain and text/html is sent ... ok test_invalid_link_if_going_directly_to_the_final_reset_password_url (auth_tests.test_views.PasswordResetTest.test_invalid_link_if_going_directly_to_the_final_reset_password_url) ... ok test_poisoned_http_host (auth_tests.test_views.PasswordResetTest.test_poisoned_http_host) Poisoned HTTP_HOST headers can't be used for reset emails ... ok test_poisoned_http_host_admin_site (auth_tests.test_views.PasswordResetTest.test_poisoned_http_host_admin_site) Poisoned HTTP_HOST headers can't be used for reset emails on admin views ... ok test_reset_custom_redirect (auth_tests.test_views.PasswordResetTest.test_reset_custom_redirect) ... ok test_reset_custom_redirect_named (auth_tests.test_views.PasswordResetTest.test_reset_custom_redirect_named) ... ok test_reset_redirect_default (auth_tests.test_views.PasswordResetTest.test_reset_redirect_default) ... ok test_inlineformset_factory_ignores_default_pks_on_submit (model_formsets.test_uuid.InlineFormsetTests.test_inlineformset_factory_ignores_default_pks_on_submit) #24377 - Inlines with a model field default should ignore that default ... ok test_inlineformset_factory_nulls_default_pks (model_formsets.test_uuid.InlineFormsetTests.test_inlineformset_factory_nulls_default_pks) #24377 - If we're adding a new object, a parent's auto-generated pk ... ok test_inlineformset_factory_nulls_default_pks_alternate_key_relation (model_formsets.test_uuid.InlineFormsetTests.test_inlineformset_factory_nulls_default_pks_alternate_key_relation) #24958 - Variant of test_inlineformset_factory_nulls_default_pks for ... ok test_inlineformset_factory_nulls_default_pks_auto_parent_uuid_child (model_formsets.test_uuid.InlineFormsetTests.test_inlineformset_factory_nulls_default_pks_auto_parent_uuid_child) #24958 - Variant of test_inlineformset_factory_nulls_default_pks for ... ok test_inlineformset_factory_nulls_default_pks_child_editable_pk (model_formsets.test_uuid.InlineFormsetTests.test_inlineformset_factory_nulls_default_pks_child_editable_pk) #24958 - Variant of test_inlineformset_factory_nulls_default_pks for ... ok test_inlineformset_factory_nulls_default_pks_uuid_parent_auto_child (model_formsets.test_uuid.InlineFormsetTests.test_inlineformset_factory_nulls_default_pks_uuid_parent_auto_child) #24958 - Variant of test_inlineformset_factory_nulls_default_pks for ... ok test_add_form_deletion_when_invalid (model_formsets.tests.DeletionTests.test_add_form_deletion_when_invalid) Make sure that an add form that is filled out, but marked for deletion ... ok test_change_form_deletion_when_invalid (model_formsets.tests.DeletionTests.test_change_form_deletion_when_invalid) Make sure that a change form that is filled out, but marked for deletion ... ok test_deletion (model_formsets.tests.DeletionTests.test_deletion) ... ok test_outdated_deletion (model_formsets.tests.DeletionTests.test_outdated_deletion) ... ok test_callable_defaults (model_formsets.tests.ModelFormsetTest.test_callable_defaults) ... ok test_commit_false (model_formsets.tests.ModelFormsetTest.test_commit_false) ... ok test_custom_form (model_formsets.tests.ModelFormsetTest.test_custom_form) model_formset_factory() respects fields and exclude parameters of a ... ok test_custom_pk (model_formsets.tests.ModelFormsetTest.test_custom_pk) ... ok test_custom_queryset_init (model_formsets.tests.ModelFormsetTest.test_custom_queryset_init) A queryset can be overridden in the formset's __init__() method. ... ok test_custom_save_method (model_formsets.tests.ModelFormsetTest.test_custom_save_method) ... ok test_foreign_keys_in_parents (model_formsets.tests.ModelFormsetTest.test_foreign_keys_in_parents) ... ok test_initial_form_count_empty_data (model_formsets.tests.ModelFormsetTest.test_initial_form_count_empty_data) ... ok test_inline_formsets (model_formsets.tests.ModelFormsetTest.test_inline_formsets) ... ok test_inline_formsets_save_as_new (model_formsets.tests.ModelFormsetTest.test_inline_formsets_save_as_new) ... ok test_inline_formsets_with_custom_pk (model_formsets.tests.ModelFormsetTest.test_inline_formsets_with_custom_pk) ... ok test_inline_formsets_with_custom_save_method (model_formsets.tests.ModelFormsetTest.test_inline_formsets_with_custom_save_method) ... ok test_inline_formsets_with_custom_save_method_related_instance (model_formsets.tests.ModelFormsetTest.test_inline_formsets_with_custom_save_method_related_instance) The ModelForm.save() method should be able to access the related object ... ok test_inline_formsets_with_multi_table_inheritance (model_formsets.tests.ModelFormsetTest.test_inline_formsets_with_multi_table_inheritance) ... ok test_inline_formsets_with_nullable_unique_together (model_formsets.tests.ModelFormsetTest.test_inline_formsets_with_nullable_unique_together) ... ok test_inline_formsets_with_wrong_fk_name (model_formsets.tests.ModelFormsetTest.test_inline_formsets_with_wrong_fk_name) Regression for #23451 ... ok test_inlineformset_factory_with_null_fk (model_formsets.tests.ModelFormsetTest.test_inlineformset_factory_with_null_fk) ... ok test_inlineformset_with_arrayfield (model_formsets.tests.ModelFormsetTest.test_inlineformset_with_arrayfield) ... ok test_max_num (model_formsets.tests.ModelFormsetTest.test_max_num) ... ok test_min_num (model_formsets.tests.ModelFormsetTest.test_min_num) ... ok test_min_num_with_existing (model_formsets.tests.ModelFormsetTest.test_min_num_with_existing) ... ok test_model_formset_with_custom_pk (model_formsets.tests.ModelFormsetTest.test_model_formset_with_custom_pk) ... ok test_model_formset_with_initial_model_instance (model_formsets.tests.ModelFormsetTest.test_model_formset_with_initial_model_instance) ... ok test_model_formset_with_initial_queryset (model_formsets.tests.ModelFormsetTest.test_model_formset_with_initial_queryset) ... ok test_model_inheritance (model_formsets.tests.ModelFormsetTest.test_model_inheritance) ... ok test_modelformset_factory_without_fields (model_formsets.tests.ModelFormsetTest.test_modelformset_factory_without_fields) Regression for #19733 ... ok test_modelformset_min_num_equals_max_num_less_than (model_formsets.tests.ModelFormsetTest.test_modelformset_min_num_equals_max_num_less_than) ... ok test_modelformset_min_num_equals_max_num_more_than (model_formsets.tests.ModelFormsetTest.test_modelformset_min_num_equals_max_num_more_than) ... ok test_modelformset_validate_max_flag (model_formsets.tests.ModelFormsetTest.test_modelformset_validate_max_flag) ... ok test_prevent_change_outer_model_and_create_invalid_data (model_formsets.tests.ModelFormsetTest.test_prevent_change_outer_model_and_create_invalid_data) ... ok test_prevent_duplicates_from_with_the_same_formset (model_formsets.tests.ModelFormsetTest.test_prevent_duplicates_from_with_the_same_formset) ... ok test_simple_save (model_formsets.tests.ModelFormsetTest.test_simple_save) ... ok test_unique_together_validation (model_formsets.tests.ModelFormsetTest.test_unique_together_validation) ... ok test_unique_together_with_inlineformset_factory (model_formsets.tests.ModelFormsetTest.test_unique_together_with_inlineformset_factory) ... ok test_unique_true_enforces_max_num_one (model_formsets.tests.ModelFormsetTest.test_unique_true_enforces_max_num_one) ... ok test_unique_validation (model_formsets.tests.ModelFormsetTest.test_unique_validation) ... ok test_validation_with_child_model_without_id (model_formsets.tests.ModelFormsetTest.test_validation_with_child_model_without_id) ... ok test_validation_with_invalid_id (model_formsets.tests.ModelFormsetTest.test_validation_with_invalid_id) ... ok test_validation_with_nonexistent_id (model_formsets.tests.ModelFormsetTest.test_validation_with_nonexistent_id) ... ok test_validation_without_id (model_formsets.tests.ModelFormsetTest.test_validation_without_id) ... ok test_inlineformset_factory_absolute_max (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_absolute_max) ... ok test_inlineformset_factory_absolute_max_with_max_num (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_absolute_max_with_max_num) ... ok test_inlineformset_factory_can_delete_extra (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_can_delete_extra) ... ok test_inlineformset_factory_can_not_delete_extra (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_can_not_delete_extra) ... ok test_inlineformset_factory_error_messages_overrides (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_error_messages_overrides) ... ok test_inlineformset_factory_field_class_overrides (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_field_class_overrides) ... ok test_inlineformset_factory_help_text_overrides (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_help_text_overrides) ... ok test_inlineformset_factory_labels_overrides (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_labels_overrides) ... ok test_inlineformset_factory_widgets (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_inlineformset_factory_widgets) ... ok test_modelformset_factory_absolute_max (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_absolute_max) ... ok test_modelformset_factory_absolute_max_with_max_num (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_absolute_max_with_max_num) ... ok test_modelformset_factory_can_delete_extra (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_can_delete_extra) ... ok test_modelformset_factory_disable_delete_extra (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_disable_delete_extra) ... ok test_modelformset_factory_error_messages_overrides (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_error_messages_overrides) ... ok test_modelformset_factory_field_class_overrides (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_field_class_overrides) ... ok test_modelformset_factory_help_text_overrides (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_help_text_overrides) ... ok test_modelformset_factory_labels_overrides (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_labels_overrides) ... ok test_modelformset_factory_widgets (model_formsets.tests.TestModelFormsetOverridesTroughFormMeta.test_modelformset_factory_widgets) ... ok test_auth_manager (multiple_database.tests.AuthTestCase.test_auth_manager) The methods on the auth manager obey database hints ... ok test_dumpdata (multiple_database.tests.AuthTestCase.test_dumpdata) dumpdata honors allow_migrate restrictions on the router ... ok test_fixture_loading (multiple_database.tests.FixtureTestCase.test_fixture_loading) Multi-db fixtures are loaded correctly ... ok test_pseudo_empty_fixtures (multiple_database.tests.FixtureTestCase.test_pseudo_empty_fixtures) A fixture can contain entries, but lead to nothing in the database; ... ok test_pickling (multiple_database.tests.PickleQuerySetTestCase.test_pickling) ... ok test_migrate_to_other_database (multiple_database.tests.MigrateTestCase.test_migrate_to_other_database) Regression test for #16039: migrate with --database option. ... ok test_migrate_to_other_database_with_router (multiple_database.tests.MigrateTestCase.test_migrate_to_other_database_with_router) Regression test for #16039: migrate with --database option. ... ok test_fk_delete (multiple_database.tests.RouteForWriteTestCase.test_fk_delete) ... ok test_m2m_add (multiple_database.tests.RouteForWriteTestCase.test_m2m_add) ... ok test_m2m_clear (multiple_database.tests.RouteForWriteTestCase.test_m2m_clear) ... ok test_m2m_delete (multiple_database.tests.RouteForWriteTestCase.test_m2m_delete) ... ok test_m2m_get_or_create (multiple_database.tests.RouteForWriteTestCase.test_m2m_get_or_create) ... ok test_m2m_remove (multiple_database.tests.RouteForWriteTestCase.test_m2m_remove) ... ok test_m2m_update (multiple_database.tests.RouteForWriteTestCase.test_m2m_update) ... ok test_reverse_fk_delete (multiple_database.tests.RouteForWriteTestCase.test_reverse_fk_delete) ... ok test_reverse_fk_get_or_create (multiple_database.tests.RouteForWriteTestCase.test_reverse_fk_get_or_create) ... ok test_reverse_fk_update (multiple_database.tests.RouteForWriteTestCase.test_reverse_fk_update) ... ok test_reverse_m2m_add (multiple_database.tests.RouteForWriteTestCase.test_reverse_m2m_add) ... ok test_reverse_m2m_clear (multiple_database.tests.RouteForWriteTestCase.test_reverse_m2m_clear) ... ok test_reverse_m2m_delete (multiple_database.tests.RouteForWriteTestCase.test_reverse_m2m_delete) ... ok test_reverse_m2m_get_or_create (multiple_database.tests.RouteForWriteTestCase.test_reverse_m2m_get_or_create) ... ok test_reverse_m2m_remove (multiple_database.tests.RouteForWriteTestCase.test_reverse_m2m_remove) ... ok test_reverse_m2m_update (multiple_database.tests.RouteForWriteTestCase.test_reverse_m2m_update) ... ok test_attribute_error_delete (multiple_database.tests.RouterAttributeErrorTestCase.test_attribute_error_delete) The AttributeError from AttributeErrorRouter bubbles up ... ok test_attribute_error_m2m (multiple_database.tests.RouterAttributeErrorTestCase.test_attribute_error_m2m) The AttributeError from AttributeErrorRouter bubbles up ... ok test_attribute_error_read (multiple_database.tests.RouterAttributeErrorTestCase.test_attribute_error_read) The AttributeError from AttributeErrorRouter bubbles up ... ok test_attribute_error_save (multiple_database.tests.RouterAttributeErrorTestCase.test_attribute_error_save) The AttributeError from AttributeErrorRouter bubbles up ... ok test_foreignkey_collection (multiple_database.tests.RouterModelArgumentTestCase.test_foreignkey_collection) ... ok test_m2m_collection (multiple_database.tests.RouterModelArgumentTestCase.test_m2m_collection) ... ok test_basic_queries (multiple_database.tests.QueryTestCase.test_basic_queries) Queries are constrained to a single database ... ok test_db_selection (multiple_database.tests.QueryTestCase.test_db_selection) Querysets will use the default database by default ... ok test_default_creation (multiple_database.tests.QueryTestCase.test_default_creation) Objects created on the default database don't leak onto other databases ... ok test_foreign_key_cross_database_protection (multiple_database.tests.QueryTestCase.test_foreign_key_cross_database_protection) Operations that involve sharing FK objects across databases raise an error ... ok test_foreign_key_deletion (multiple_database.tests.QueryTestCase.test_foreign_key_deletion) Cascaded deletions of Foreign Key relations issue queries on the right database ... ok test_foreign_key_reverse_operations (multiple_database.tests.QueryTestCase.test_foreign_key_reverse_operations) FK reverse manipulations are all constrained to a single DB ... ok test_foreign_key_separation (multiple_database.tests.QueryTestCase.test_foreign_key_separation) FK fields are constrained to a single database ... ok test_foreign_key_validation (multiple_database.tests.QueryTestCase.test_foreign_key_validation) ForeignKey.validate() uses the correct database ... ok test_foreign_key_validation_with_router (multiple_database.tests.QueryTestCase.test_foreign_key_validation_with_router) ForeignKey.validate() passes `model` to db_for_read() even if ... ok test_generic_key_cross_database_protection (multiple_database.tests.QueryTestCase.test_generic_key_cross_database_protection) Operations that involve sharing generic key objects across databases raise an error ... ok test_generic_key_deletion (multiple_database.tests.QueryTestCase.test_generic_key_deletion) Cascaded deletions of Generic Key relations issue queries on the right database ... ok test_generic_key_reverse_operations (multiple_database.tests.QueryTestCase.test_generic_key_reverse_operations) Generic reverse manipulations are all constrained to a single DB ... ok test_generic_key_separation (multiple_database.tests.QueryTestCase.test_generic_key_separation) Generic fields are constrained to a single database ... ok test_m2m_cross_database_protection (multiple_database.tests.QueryTestCase.test_m2m_cross_database_protection) Operations that involve sharing M2M objects across databases raise an error ... ok test_m2m_deletion (multiple_database.tests.QueryTestCase.test_m2m_deletion) Cascaded deletions of m2m relations issue queries on the right database ... ok test_m2m_forward_operations (multiple_database.tests.QueryTestCase.test_m2m_forward_operations) M2M forward manipulations are all constrained to a single DB ... ok test_m2m_reverse_operations (multiple_database.tests.QueryTestCase.test_m2m_reverse_operations) M2M reverse manipulations are all constrained to a single DB ... ok test_m2m_separation (multiple_database.tests.QueryTestCase.test_m2m_separation) M2M fields are constrained to a single database ... ok test_o2o_cross_database_protection (multiple_database.tests.QueryTestCase.test_o2o_cross_database_protection) Operations that involve sharing FK objects across databases raise an error ... ok test_o2o_separation (multiple_database.tests.QueryTestCase.test_o2o_separation) OneToOne fields are constrained to a single database ... ok test_ordering (multiple_database.tests.QueryTestCase.test_ordering) get_next_by_XXX commands stick to a single database ... ok test_other_creation (multiple_database.tests.QueryTestCase.test_other_creation) Objects created on another database don't leak onto the default database ... ok test_raw (multiple_database.tests.QueryTestCase.test_raw) test the raw() method across databases ... ok test_refresh (multiple_database.tests.QueryTestCase.test_refresh) ... ok test_refresh_router_instance_hint (multiple_database.tests.QueryTestCase.test_refresh_router_instance_hint) ... ok test_related_manager (multiple_database.tests.QueryTestCase.test_related_manager) Related managers return managers, not querysets ... ok test_select_related (multiple_database.tests.QueryTestCase.test_select_related) Database assignment is retained if an object is retrieved with select_related() ... ok test_subquery (multiple_database.tests.QueryTestCase.test_subquery) Make sure as_sql works with subqueries and primary/replica. ... ok test_database_arg_m2m (multiple_database.tests.SignalTests.test_database_arg_m2m) The m2m_changed signal has a correct database arg. ... ok test_database_arg_save_and_delete (multiple_database.tests.SignalTests.test_database_arg_save_and_delete) The pre/post_save signal contains the correct database. ... ok test_admin_password_change (auth_tests.test_views.UUIDUserTests.test_admin_password_change) ... ok test_custom_max_lengths (max_lengths.tests.MaxLengthORMTests.test_custom_max_lengths) ... ok test_abstract_manager (managers_regress.tests.ManagersRegressionTests.test_abstract_manager) ... ok test_custom_abstract_manager (managers_regress.tests.ManagersRegressionTests.test_custom_abstract_manager) ... ok test_custom_swappable_manager (managers_regress.tests.ManagersRegressionTests.test_custom_swappable_manager) ... ok test_explicit_abstract_manager (managers_regress.tests.ManagersRegressionTests.test_explicit_abstract_manager) ... ok test_explicit_swappable_manager (managers_regress.tests.ManagersRegressionTests.test_explicit_swappable_manager) ... ok test_field_can_be_called_exact (managers_regress.tests.ManagersRegressionTests.test_field_can_be_called_exact) ... ok test_managers (managers_regress.tests.ManagersRegressionTests.test_managers) ... ok test_regress_3871 (managers_regress.tests.ManagersRegressionTests.test_regress_3871) ... ok test_swappable_manager (managers_regress.tests.ManagersRegressionTests.test_swappable_manager) ... ok test_recursive_m2m_add_in_both_directions (m2m_recursive.tests.RecursiveM2MTests.test_recursive_m2m_add_in_both_directions) ... ok test_recursive_m2m_add_via_related_name (m2m_recursive.tests.RecursiveM2MTests.test_recursive_m2m_add_via_related_name) ... ok test_recursive_m2m_all (m2m_recursive.tests.RecursiveM2MTests.test_recursive_m2m_all) ... ok test_recursive_m2m_clear (m2m_recursive.tests.RecursiveM2MTests.test_recursive_m2m_clear) ... ok test_recursive_m2m_related_to_self (m2m_recursive.tests.RecursiveM2MTests.test_recursive_m2m_related_to_self) ... ok test_recursive_m2m_remove (m2m_recursive.tests.RecursiveM2MTests.test_recursive_m2m_remove) ... ok test_recursive_m2m_reverse_add (m2m_recursive.tests.RecursiveM2MTests.test_recursive_m2m_reverse_add) ... ok test_database_routing (multiple_database.tests.RouterTestCase.test_database_routing) ... ok test_db_selection (multiple_database.tests.RouterTestCase.test_db_selection) Querysets obey the router for db suggestions ... ok test_deferred_models (multiple_database.tests.RouterTestCase.test_deferred_models) ... ok test_foreign_key_cross_database_protection (multiple_database.tests.RouterTestCase.test_foreign_key_cross_database_protection) Foreign keys can cross databases if they two databases have a common source ... ok test_foreign_key_managers (multiple_database.tests.RouterTestCase.test_foreign_key_managers) FK reverse relations are represented by managers, and can be controlled like managers ... ok test_generic_key_cross_database_protection (multiple_database.tests.RouterTestCase.test_generic_key_cross_database_protection) Generic Key operations can span databases if they share a source ... ok test_generic_key_managers (multiple_database.tests.RouterTestCase.test_generic_key_managers) Generic key relations are represented by managers, and can be controlled like managers ... ok test_invalid_set_foreign_key_assignment (multiple_database.tests.RouterTestCase.test_invalid_set_foreign_key_assignment) ... ok test_m2m_cross_database_protection (multiple_database.tests.RouterTestCase.test_m2m_cross_database_protection) M2M relations can cross databases if the database share a source ... ok test_m2m_managers (multiple_database.tests.RouterTestCase.test_m2m_managers) M2M relations are represented by managers, and can be controlled like managers ... ok test_migrate_selection (multiple_database.tests.RouterTestCase.test_migrate_selection) Synchronization behavior is predictable ... ok test_o2o_cross_database_protection (multiple_database.tests.RouterTestCase.test_o2o_cross_database_protection) Operations that involve sharing FK objects across databases raise an error ... ok test_partial_router (multiple_database.tests.RouterTestCase.test_partial_router) A router can choose to implement a subset of methods ... ok test_subquery (multiple_database.tests.RouterTestCase.test_subquery) Make sure as_sql works with subqueries and primary/replica. ... ok test_sqlflush_no_tables (empty_models.test_commands.CoreCommandsNoOutputTests.test_sqlflush_no_tables) ... ok test_sqlsequencereset_no_sequences (empty_models.test_commands.CoreCommandsNoOutputTests.test_sqlsequencereset_no_sequences) ... ok test_recursive_m2m_all (m2m_recursive.tests.RecursiveSymmetricalM2MThroughTests.test_recursive_m2m_all) ... ok test_recursive_m2m_clear (m2m_recursive.tests.RecursiveSymmetricalM2MThroughTests.test_recursive_m2m_clear) ... ok test_recursive_m2m_remove (m2m_recursive.tests.RecursiveSymmetricalM2MThroughTests.test_recursive_m2m_remove) ... ok test_recursive_m2m_reverse_add (m2m_recursive.tests.RecursiveSymmetricalM2MThroughTests.test_recursive_m2m_reverse_add) ... ok test_recursive_m2m_set (m2m_recursive.tests.RecursiveSymmetricalM2MThroughTests.test_recursive_m2m_set) ... ok test_unique (model_inheritance.tests.InheritanceUniqueTests.test_unique) ... ok test_unique_together (model_inheritance.tests.InheritanceUniqueTests.test_unique_together) ... ok test_get (custom_pk.tests.BasicCustomPKTests.test_get) Get can accept pk or the real attribute name ... ok test_in_bulk (custom_pk.tests.BasicCustomPKTests.test_in_bulk) Custom pks work with in_bulk, both for integer and non-integer types ... ok test_pk_attributes (custom_pk.tests.BasicCustomPKTests.test_pk_attributes) pk and attribute name are available on the model ... ok test_querysets (custom_pk.tests.BasicCustomPKTests.test_querysets) Both pk and custom attribute_name can be used in filter and friends ... ok test_querysets_related_name (custom_pk.tests.BasicCustomPKTests.test_querysets_related_name) Custom pk doesn't affect related_name based lookups ... ok test_querysets_relational (custom_pk.tests.BasicCustomPKTests.test_querysets_relational) Queries across tables, involving primary key ... ok test_save (custom_pk.tests.BasicCustomPKTests.test_save) custom pks do not affect save ... ok test_changelist_disallows_password_lookups (auth_tests.test_views.ChangelistTests.test_changelist_disallows_password_lookups) ... ok test_password_change_bad_url (auth_tests.test_views.ChangelistTests.test_password_change_bad_url) ... ok test_user_change_different_user_password (auth_tests.test_views.ChangelistTests.test_user_change_different_user_password) ... ok test_user_change_email (auth_tests.test_views.ChangelistTests.test_user_change_email) ... ok test_user_change_password (auth_tests.test_views.ChangelistTests.test_user_change_password) ... ok test_user_change_password_passes_user_to_has_change_permission (auth_tests.test_views.ChangelistTests.test_user_change_password_passes_user_to_has_change_permission) ... ok test_user_not_change (auth_tests.test_views.ChangelistTests.test_user_not_change) ... ok test_view_user_password_is_readonly (auth_tests.test_views.ChangelistTests.test_view_user_password_is_readonly) ... ok test_custom_field_pk (custom_pk.tests.CustomPKTests.test_custom_field_pk) ... ok test_custom_pk_create (custom_pk.tests.CustomPKTests.test_custom_pk_create) New objects can be created both with pk and the custom name ... ok test_required_pk (custom_pk.tests.CustomPKTests.test_required_pk) ... skipped 'Database has feature(s) supports_unspecified_pk' test_unicode_pk (custom_pk.tests.CustomPKTests.test_unicode_pk) ... ok test_unique_pk (custom_pk.tests.CustomPKTests.test_unique_pk) ... ok test_zero_non_autoincrement_pk (custom_pk.tests.CustomPKTests.test_zero_non_autoincrement_pk) ... ok test_migration_warning_multiple_apps (admin_scripts.tests.ManageRunserverMigrationWarning.test_migration_warning_multiple_apps) ... ok test_migration_warning_one_app (admin_scripts.tests.ManageRunserverMigrationWarning.test_migration_warning_one_app) ... ok test_exclude_inherited_on_null (model_inheritance.tests.ModelInheritanceDataTests.test_exclude_inherited_on_null) ... ok test_filter_inherited_model (model_inheritance.tests.ModelInheritanceDataTests.test_filter_inherited_model) ... ok test_filter_inherited_on_null (model_inheritance.tests.ModelInheritanceDataTests.test_filter_inherited_on_null) ... ok test_filter_on_parent_returns_object_of_parent_type (model_inheritance.tests.ModelInheritanceDataTests.test_filter_on_parent_returns_object_of_parent_type) ... ok test_inherited_does_not_exist_exception (model_inheritance.tests.ModelInheritanceDataTests.test_inherited_does_not_exist_exception) ... ok test_inherited_multiple_objects_returned_exception (model_inheritance.tests.ModelInheritanceDataTests.test_inherited_multiple_objects_returned_exception) ... ok test_parent_cache_reuse (model_inheritance.tests.ModelInheritanceDataTests.test_parent_cache_reuse) ... ok test_parent_child_one_to_one_link (model_inheritance.tests.ModelInheritanceDataTests.test_parent_child_one_to_one_link) ... ok test_parent_child_one_to_one_link_on_nonrelated_objects (model_inheritance.tests.ModelInheritanceDataTests.test_parent_child_one_to_one_link_on_nonrelated_objects) ... ok test_parent_fields_available_for_filtering_in_child_model (model_inheritance.tests.ModelInheritanceDataTests.test_parent_fields_available_for_filtering_in_child_model) ... ok test_related_objects_for_inherited_models (model_inheritance.tests.ModelInheritanceDataTests.test_related_objects_for_inherited_models) ... ok test_select_related_defer (model_inheritance.tests.ModelInheritanceDataTests.test_select_related_defer) #23370 - Should be able to defer child fields when using ... ok test_select_related_works_on_parent_model_fields (model_inheritance.tests.ModelInheritanceDataTests.test_select_related_works_on_parent_model_fields) ... ok test_update_inherited_model (model_inheritance.tests.ModelInheritanceDataTests.test_update_inherited_model) ... ok test_update_query_counts (model_inheritance.tests.ModelInheritanceDataTests.test_update_query_counts) Update queries do not generate unnecessary queries (#18304). ... ok test_update_works_on_parent_and_child_models_at_once (model_inheritance.tests.ModelInheritanceDataTests.test_update_works_on_parent_and_child_models_at_once) ... ok test_values_works_on_parent_model_fields (model_inheritance.tests.ModelInheritanceDataTests.test_values_works_on_parent_model_fields) ... ok test_abstract (model_inheritance.tests.ModelInheritanceTests.test_abstract) ... ok test_abstract_parent_link (model_inheritance.tests.ModelInheritanceTests.test_abstract_parent_link) ... ok test_create_child_no_update (model_inheritance.tests.ModelInheritanceTests.test_create_child_no_update) Creating a child with non-abstract parents only issues INSERTs. ... ok test_custompk_m2m (model_inheritance.tests.ModelInheritanceTests.test_custompk_m2m) ... ok test_eq (model_inheritance.tests.ModelInheritanceTests.test_eq) ... ok test_inherited_ordering_pk_desc (model_inheritance.tests.ModelInheritanceTests.test_inherited_ordering_pk_desc) ... ok test_init_subclass (model_inheritance.tests.ModelInheritanceTests.test_init_subclass) ... ok test_meta_fields_and_ordering (model_inheritance.tests.ModelInheritanceTests.test_meta_fields_and_ordering) ... ok test_mixin_init (model_inheritance.tests.ModelInheritanceTests.test_mixin_init) ... ok test_model_with_distinct_accessors (model_inheritance.tests.ModelInheritanceTests.test_model_with_distinct_accessors) ... ok test_model_with_distinct_related_query_name (model_inheritance.tests.ModelInheritanceTests.test_model_with_distinct_related_query_name) ... ok test_queryset_class_getitem (model_inheritance.tests.ModelInheritanceTests.test_queryset_class_getitem) ... ok test_reverse_relation_for_different_hierarchy_tree (model_inheritance.tests.ModelInheritanceTests.test_reverse_relation_for_different_hierarchy_tree) ... ok test_set_name (model_inheritance.tests.ModelInheritanceTests.test_set_name) ... ok test_update_parent_filtering (model_inheritance.tests.ModelInheritanceTests.test_update_parent_filtering) Updating a field of a model subclass doesn't issue an UPDATE ... ok test_extra_args (schema.test_logging.SchemaLoggerTests.test_extra_args) ... ok test_build_absolute_uri (urlpatterns_reverse.tests.ReverseLazyTest.test_build_absolute_uri) ... ok test_inserting_reverse_lazy_into_string (urlpatterns_reverse.tests.ReverseLazyTest.test_inserting_reverse_lazy_into_string) ... ok test_redirect_with_lazy_reverse (urlpatterns_reverse.tests.ReverseLazyTest.test_redirect_with_lazy_reverse) ... ok test_user_permission_with_lazy_reverse (urlpatterns_reverse.tests.ReverseLazyTest.test_user_permission_with_lazy_reverse) ... ok test_many_to_many_between_unmanaged (unmanaged_models.tests.ManyToManyUnmanagedTests.test_many_to_many_between_unmanaged) The intermediary table between two unmanaged models should not be created. ... ok test_many_to_many_between_unmanaged_and_managed (unmanaged_models.tests.ManyToManyUnmanagedTests.test_many_to_many_between_unmanaged_and_managed) An intermediary table between a managed and an unmanaged model should be created. ... ok test_simple (unmanaged_models.tests.SimpleTests.test_simple) The main test here is that the all the models can be created without ... ok test_override_settings_inheritance (settings_tests.tests.ChildDecoratedTestCase.test_override_settings_inheritance) ... ok test_max_recursion_error (settings_tests.tests.ClassDecoratedTestCase.test_max_recursion_error) Overriding a method on a super class and then calling that method on ... ok test_method_override (settings_tests.tests.ClassDecoratedTestCase.test_method_override) ... ok test_override (settings_tests.tests.ClassDecoratedTestCase.test_override) ... ok test_setupclass_override (settings_tests.tests.ClassDecoratedTestCase.test_setupclass_override) Settings are overridden within setUpClass (#21281). ... ok test_max_recursion_error (settings_tests.tests.ClassDecoratedTestCaseSuper.test_max_recursion_error) ... ok test_method_override (settings_tests.tests.FullyDecoratedTestCase.test_method_override) ... ok test_override (settings_tests.tests.FullyDecoratedTestCase.test_override) ... ok test_add (messages_tests.test_session.SessionTests.test_add) ... ok test_add_lazy_translation (messages_tests.test_session.SessionTests.test_add_lazy_translation) ... ok test_add_update (messages_tests.test_session.SessionTests.test_add_update) ... ok test_context_processor_message_levels (messages_tests.test_session.SessionTests.test_context_processor_message_levels) ... ok test_custom_tags (messages_tests.test_session.SessionTests.test_custom_tags) ... ok test_default_level (messages_tests.test_session.SessionTests.test_default_level) ... ok test_existing_add (messages_tests.test_session.SessionTests.test_existing_add) ... ok test_existing_add_read_update (messages_tests.test_session.SessionTests.test_existing_add_read_update) ... ok test_existing_read (messages_tests.test_session.SessionTests.test_existing_read) Reading the existing storage doesn't cause the data to be lost. ... ok test_existing_read_add_update (messages_tests.test_session.SessionTests.test_existing_read_add_update) ... ok test_full_request_response_cycle (messages_tests.test_session.SessionTests.test_full_request_response_cycle) With the message middleware enabled, messages are properly stored and ... ok test_get (messages_tests.test_session.SessionTests.test_get) ... ok test_high_level (messages_tests.test_session.SessionTests.test_high_level) ... ok test_level_tag (messages_tests.test_session.SessionTests.test_level_tag) ... ok test_low_level (messages_tests.test_session.SessionTests.test_low_level) ... ok test_middleware_disabled (messages_tests.test_session.SessionTests.test_middleware_disabled) When the middleware is disabled, an exception is raised when one ... ok test_middleware_disabled_fail_silently (messages_tests.test_session.SessionTests.test_middleware_disabled_fail_silently) When the middleware is disabled, an exception is not raised ... ok test_multiple_posts (messages_tests.test_session.SessionTests.test_multiple_posts) Messages persist properly when multiple POSTs are made before a GET. ... ok test_no_session (messages_tests.test_session.SessionTests.test_no_session) ... ok test_no_update (messages_tests.test_session.SessionTests.test_no_update) ... ok test_safedata (messages_tests.test_session.SessionTests.test_safedata) A message containing SafeData keeps its safe status when retrieved from ... ok test_settings_level (messages_tests.test_session.SessionTests.test_settings_level) ... ok test_tags (messages_tests.test_session.SessionTests.test_tags) ... ok test_with_template_response (messages_tests.test_session.SessionTests.test_with_template_response) ... ok test_back_and_forward (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_back_and_forward) ... ok test_basic (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_basic) ... ok test_follow_from_child_class (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_follow_from_child_class) ... ok test_follow_inheritance (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_follow_inheritance) ... ok test_follow_next_level (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_follow_next_level) ... ok test_follow_two (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_follow_two) ... ok test_follow_two_next_level (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_follow_two_next_level) ... ok test_forward_and_back (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_forward_and_back) ... ok test_inheritance_deferred (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_inheritance_deferred) ... ok test_inheritance_deferred2 (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_inheritance_deferred2) ... ok test_missing_reverse (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_missing_reverse) Ticket #13839: select_related() should NOT cache None ... ok test_multiinheritance_two_subclasses (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_multiinheritance_two_subclasses) ... ok test_multiple_subclass (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_multiple_subclass) ... ok test_not_followed_by_default (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_not_followed_by_default) ... ok test_nullable_missing_reverse (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_nullable_missing_reverse) Ticket #13839: select_related() should NOT cache None ... ok test_nullable_relation (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_nullable_relation) ... ok test_onetoone_with_subclass (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_onetoone_with_subclass) ... ok test_onetoone_with_two_subclasses (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_onetoone_with_two_subclasses) ... ok test_parent_only (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_parent_only) ... ok test_self_relation (select_related_onetoone.tests.ReverseSelectRelatedTestCase.test_self_relation) ... ok test_immutable_content_type (admin_inlines.tests.TestInlineAdminForm.test_immutable_content_type) Regression for #9362 ... ok test_default_ordering (ordering.tests.OrderingTests.test_default_ordering) By default, Article.objects.all() orders by pub_date descending, then ... ok test_default_ordering_by_f_expression (ordering.tests.OrderingTests.test_default_ordering_by_f_expression) F expressions can be used in Meta.ordering. ... ok test_default_ordering_override (ordering.tests.OrderingTests.test_default_ordering_override) Override ordering with order_by, which is in the same format as the ... ok test_extra_ordering (ordering.tests.OrderingTests.test_extra_ordering) Ordering can be based on fields included from an 'extra' clause ... ok test_extra_ordering_quoting (ordering.tests.OrderingTests.test_extra_ordering_quoting) If the extra clause uses an SQL keyword for a name, it will be ... ok test_extra_ordering_with_table_name (ordering.tests.OrderingTests.test_extra_ordering_with_table_name) ... ok test_no_reordering_after_slicing (ordering.tests.OrderingTests.test_no_reordering_after_slicing) ... ok test_order_by_constant_value (ordering.tests.OrderingTests.test_order_by_constant_value) ... ok test_order_by_f_expression (ordering.tests.OrderingTests.test_order_by_f_expression) ... ok test_order_by_f_expression_duplicates (ordering.tests.OrderingTests.test_order_by_f_expression_duplicates) A column may only be included once (the first occurrence) so we check ... ok test_order_by_fk_attname (ordering.tests.OrderingTests.test_order_by_fk_attname) ordering by a foreign key by its attribute name prevents the query ... ok test_order_by_nulls_first (ordering.tests.OrderingTests.test_order_by_nulls_first) ... ok test_order_by_nulls_first_and_last (ordering.tests.OrderingTests.test_order_by_nulls_first_and_last) ... ok test_order_by_nulls_last (ordering.tests.OrderingTests.test_order_by_nulls_last) ... ok test_order_by_override (ordering.tests.OrderingTests.test_order_by_override) Only the last order_by has any effect (since they each override any ... ok test_order_by_pk (ordering.tests.OrderingTests.test_order_by_pk) 'pk' works as an ordering option in Meta. ... ok test_order_by_ptr_field_with_default_ordering_by_expression (ordering.tests.OrderingTests.test_order_by_ptr_field_with_default_ordering_by_expression) ... ok test_order_by_self_referential_fk (ordering.tests.OrderingTests.test_order_by_self_referential_fk) ... ok test_orders_nulls_first_on_filtered_subquery (ordering.tests.OrderingTests.test_orders_nulls_first_on_filtered_subquery) ... ok test_random_ordering (ordering.tests.OrderingTests.test_random_ordering) Use '?' to order randomly. ... ok test_related_ordering_duplicate_table_reference (ordering.tests.OrderingTests.test_related_ordering_duplicate_table_reference) An ordering referencing a model with an ordering referencing a model ... ok test_reverse_meta_ordering_pure (ordering.tests.OrderingTests.test_reverse_meta_ordering_pure) ... ok test_reverse_ordering_pure (ordering.tests.OrderingTests.test_reverse_ordering_pure) ... ok test_reversed_ordering (ordering.tests.OrderingTests.test_reversed_ordering) Ordering can be reversed using the reverse() method on a queryset. ... ok test_stop_slicing (ordering.tests.OrderingTests.test_stop_slicing) Use the 'stop' part of slicing notation to limit the results. ... ok test_stop_start_slicing (ordering.tests.OrderingTests.test_stop_start_slicing) Use the 'stop' and 'start' parts of slicing notation to offset the ... ok test_deleting_inline_with_protected_delete_does_not_validate (admin_inlines.tests.TestInlineProtectedOnDelete.test_deleting_inline_with_protected_delete_does_not_validate) ... ok test_all_inline_media (admin_inlines.tests.TestInlineMedia.test_all_inline_media) ... ok test_inline_media_only_base (admin_inlines.tests.TestInlineMedia.test_inline_media_only_base) ... ok test_inline_media_only_inline (admin_inlines.tests.TestInlineMedia.test_inline_media_only_inline) ... ok test_earliest (get_earliest_or_latest.tests.EarliestOrLatestTests.test_earliest) ... ok test_latest (get_earliest_or_latest.tests.EarliestOrLatestTests.test_latest) ... ok test_latest_manual (get_earliest_or_latest.tests.EarliestOrLatestTests.test_latest_manual) ... ok test_first (get_earliest_or_latest.tests.TestFirstLast.test_first) ... ok test_index_error_not_suppressed (get_earliest_or_latest.tests.TestFirstLast.test_index_error_not_suppressed) #23555 -- Unexpected IndexError exceptions in QuerySet iteration ... ok test_last (get_earliest_or_latest.tests.TestFirstLast.test_last) ... ok test_add_url_not_allowed (admin_inlines.tests.TestReadOnlyChangeViewInlinePermissions.test_add_url_not_allowed) ... ok test_extra_inlines_are_not_shown (admin_inlines.tests.TestReadOnlyChangeViewInlinePermissions.test_extra_inlines_are_not_shown) ... ok test_get_to_change_url_is_allowed (admin_inlines.tests.TestReadOnlyChangeViewInlinePermissions.test_get_to_change_url_is_allowed) ... ok test_inline_delete_buttons_are_not_shown (admin_inlines.tests.TestReadOnlyChangeViewInlinePermissions.test_inline_delete_buttons_are_not_shown) ... ok test_inlines_are_rendered_as_read_only (admin_inlines.tests.TestReadOnlyChangeViewInlinePermissions.test_inlines_are_rendered_as_read_only) ... ok test_main_model_is_rendered_as_read_only (admin_inlines.tests.TestReadOnlyChangeViewInlinePermissions.test_main_model_is_rendered_as_read_only) ... ok test_post_to_change_url_not_allowed (admin_inlines.tests.TestReadOnlyChangeViewInlinePermissions.test_post_to_change_url_not_allowed) ... ok test_submit_line_shows_only_close_button (admin_inlines.tests.TestReadOnlyChangeViewInlinePermissions.test_submit_line_shows_only_close_button) ... ok test_change_editable (timezones.tests.AdminTests.test_change_editable) ... ok test_change_editable_in_other_timezone (timezones.tests.AdminTests.test_change_editable_in_other_timezone) ... ok test_change_readonly (timezones.tests.AdminTests.test_change_readonly) ... ok test_change_readonly_in_other_timezone (timezones.tests.AdminTests.test_change_readonly_in_other_timezone) ... ok test_changelist (timezones.tests.AdminTests.test_changelist) ... ok test_changelist_in_other_timezone (timezones.tests.AdminTests.test_changelist_in_other_timezone) ... ok test_form (timezones.tests.LegacyFormsTests.test_form) ... ok test_form_with_ambiguous_time (timezones.tests.LegacyFormsTests.test_form_with_ambiguous_time) ... ok test_form_with_non_existent_time (timezones.tests.LegacyFormsTests.test_form_with_non_existent_time) ... ok test_model_form (timezones.tests.LegacyFormsTests.test_model_form) ... ok test_split_form (timezones.tests.LegacyFormsTests.test_split_form) ... ok test_inline_add_fk_add_perm (admin_inlines.tests.TestInlinePermissions.test_inline_add_fk_add_perm) ... ok test_inline_add_fk_noperm (admin_inlines.tests.TestInlinePermissions.test_inline_add_fk_noperm) ... ok test_inline_add_m2m_add_perm (admin_inlines.tests.TestInlinePermissions.test_inline_add_m2m_add_perm) ... ok test_inline_add_m2m_noperm (admin_inlines.tests.TestInlinePermissions.test_inline_add_m2m_noperm) ... ok test_inline_add_m2m_view_only_perm (admin_inlines.tests.TestInlinePermissions.test_inline_add_m2m_view_only_perm) ... ok test_inline_change_fk_add_change_perm (admin_inlines.tests.TestInlinePermissions.test_inline_change_fk_add_change_perm) ... ok test_inline_change_fk_add_perm (admin_inlines.tests.TestInlinePermissions.test_inline_change_fk_add_perm) ... ok test_inline_change_fk_all_perms (admin_inlines.tests.TestInlinePermissions.test_inline_change_fk_all_perms) ... ok test_inline_change_fk_change_del_perm (admin_inlines.tests.TestInlinePermissions.test_inline_change_fk_change_del_perm) ... ok test_inline_change_fk_change_perm (admin_inlines.tests.TestInlinePermissions.test_inline_change_fk_change_perm) ... ok test_inline_change_fk_noperm (admin_inlines.tests.TestInlinePermissions.test_inline_change_fk_noperm) ... ok test_inline_change_m2m_add_perm (admin_inlines.tests.TestInlinePermissions.test_inline_change_m2m_add_perm) ... ok test_inline_change_m2m_change_perm (admin_inlines.tests.TestInlinePermissions.test_inline_change_m2m_change_perm) ... ok test_inline_change_m2m_noperm (admin_inlines.tests.TestInlinePermissions.test_inline_change_m2m_noperm) ... ok test_inline_change_m2m_view_only_perm (admin_inlines.tests.TestInlinePermissions.test_inline_change_m2m_view_only_perm) ... ok test_auto_now_and_auto_now_add (timezones.tests.LegacyDatabaseTests.test_auto_now_and_auto_now_add) ... ok test_aware_datetime_in_local_timezone (timezones.tests.LegacyDatabaseTests.test_aware_datetime_in_local_timezone) ... skipped "Database doesn't support feature(s): supports_timezones" test_aware_datetime_in_local_timezone_with_microsecond (timezones.tests.LegacyDatabaseTests.test_aware_datetime_in_local_timezone_with_microsecond) ... skipped "Database doesn't support feature(s): supports_timezones" test_aware_datetime_in_other_timezone (timezones.tests.LegacyDatabaseTests.test_aware_datetime_in_other_timezone) ... skipped "Database doesn't support feature(s): supports_timezones" test_aware_datetime_in_utc (timezones.tests.LegacyDatabaseTests.test_aware_datetime_in_utc) ... skipped "Database doesn't support feature(s): supports_timezones" test_aware_datetime_unsupported (timezones.tests.LegacyDatabaseTests.test_aware_datetime_unsupported) ... ok test_cursor_execute_accepts_naive_datetime (timezones.tests.LegacyDatabaseTests.test_cursor_execute_accepts_naive_datetime) ... ok test_cursor_execute_returns_naive_datetime (timezones.tests.LegacyDatabaseTests.test_cursor_execute_returns_naive_datetime) ... ok test_filter_date_field_with_aware_datetime (timezones.tests.LegacyDatabaseTests.test_filter_date_field_with_aware_datetime) ... ok test_naive_datetime (timezones.tests.LegacyDatabaseTests.test_naive_datetime) ... ok test_naive_datetime_with_microsecond (timezones.tests.LegacyDatabaseTests.test_naive_datetime_with_microsecond) ... ok test_query_aggregation (timezones.tests.LegacyDatabaseTests.test_query_aggregation) ... ok test_query_annotation (timezones.tests.LegacyDatabaseTests.test_query_annotation) ... ok test_query_datetime_lookups (timezones.tests.LegacyDatabaseTests.test_query_datetime_lookups) ... ok test_query_datetimes (timezones.tests.LegacyDatabaseTests.test_query_datetimes) ... ok test_query_filter (timezones.tests.LegacyDatabaseTests.test_query_filter) ... ok test_raw_sql (timezones.tests.LegacyDatabaseTests.test_raw_sql) ... ok test_deletion_through_intermediate_proxy (proxy_model_inheritance.tests.MultiTableInheritanceProxyTest.test_deletion_through_intermediate_proxy) ... ok test_model_subclass_proxy (proxy_model_inheritance.tests.MultiTableInheritanceProxyTest.test_model_subclass_proxy) Deleting an instance of a model proxying a multi-table inherited ... ok test_database_checks_called (check_framework.test_database.DatabaseCheckTests.test_database_checks_called) ... ok test_mysql_strict_mode (check_framework.test_database.DatabaseCheckTests.test_mysql_strict_mode) ... skipped 'Test only for MySQL' test_form (timezones.tests.NewFormsTests.test_form) ... ok test_form_with_ambiguous_time (timezones.tests.NewFormsTests.test_form_with_ambiguous_time) ... ok test_form_with_non_existent_time (timezones.tests.NewFormsTests.test_form_with_non_existent_time) ... ok test_form_with_other_timezone (timezones.tests.NewFormsTests.test_form_with_other_timezone) ... ok test_localized_form (timezones.tests.NewFormsTests.test_localized_form) ... ok test_localized_model_form (timezones.tests.NewFormsTests.test_localized_model_form) ... ok test_model_form (timezones.tests.NewFormsTests.test_model_form) ... ok test_split_form (timezones.tests.NewFormsTests.test_split_form) ... ok test_collision_abstract_model (check_framework.test_model_checks.ConstraintNameTests.test_collision_abstract_model) ... ok test_collision_across_apps (check_framework.test_model_checks.ConstraintNameTests.test_collision_across_apps) ... ok test_collision_in_different_models (check_framework.test_model_checks.ConstraintNameTests.test_collision_in_different_models) ... ok test_collision_in_same_model (check_framework.test_model_checks.ConstraintNameTests.test_collision_in_same_model) ... ok test_no_collision_abstract_model_interpolation (check_framework.test_model_checks.ConstraintNameTests.test_no_collision_abstract_model_interpolation) ... ok test_no_collision_across_apps_interpolation (check_framework.test_model_checks.ConstraintNameTests.test_no_collision_across_apps_interpolation) ... ok test_follow_parameter_not_implemented (test_client.tests.AsyncClientTest.test_follow_parameter_not_implemented) ... ok test_response_resolver_match (test_client.tests.AsyncClientTest.test_response_resolver_match) ... ok test_auto_now_and_auto_now_add (timezones.tests.NewDatabaseTests.test_auto_now_and_auto_now_add) ... ok test_aware_datetime_in_local_timezone (timezones.tests.NewDatabaseTests.test_aware_datetime_in_local_timezone) ... ok test_aware_datetime_in_local_timezone_with_microsecond (timezones.tests.NewDatabaseTests.test_aware_datetime_in_local_timezone_with_microsecond) ... ok test_aware_datetime_in_other_timezone (timezones.tests.NewDatabaseTests.test_aware_datetime_in_other_timezone) ... ok test_aware_datetime_in_utc (timezones.tests.NewDatabaseTests.test_aware_datetime_in_utc) ... ok test_cursor_execute_accepts_aware_datetime (timezones.tests.NewDatabaseTests.test_cursor_execute_accepts_aware_datetime) ... skipped "Database doesn't support feature(s): supports_timezones" test_cursor_execute_accepts_naive_datetime (timezones.tests.NewDatabaseTests.test_cursor_execute_accepts_naive_datetime) ... ok test_cursor_execute_returns_aware_datetime (timezones.tests.NewDatabaseTests.test_cursor_execute_returns_aware_datetime) ... skipped "Database doesn't support feature(s): supports_timezones" test_cursor_execute_returns_naive_datetime (timezones.tests.NewDatabaseTests.test_cursor_execute_returns_naive_datetime) ... ok test_cursor_explicit_time_zone (timezones.tests.NewDatabaseTests.test_cursor_explicit_time_zone) ... skipped "Database doesn't support feature(s): supports_timezones" test_datetime_from_date (timezones.tests.NewDatabaseTests.test_datetime_from_date) ... ok test_filter_date_field_with_aware_datetime (timezones.tests.NewDatabaseTests.test_filter_date_field_with_aware_datetime) ... ok test_naive_datetime (timezones.tests.NewDatabaseTests.test_naive_datetime) ... ok test_naive_datetime_with_microsecond (timezones.tests.NewDatabaseTests.test_naive_datetime_with_microsecond) ... ok test_null_datetime (timezones.tests.NewDatabaseTests.test_null_datetime) ... ok test_query_aggregation (timezones.tests.NewDatabaseTests.test_query_aggregation) ... ok test_query_annotation (timezones.tests.NewDatabaseTests.test_query_annotation) ... ok test_query_convert_timezones (timezones.tests.NewDatabaseTests.test_query_convert_timezones) ... ok test_query_datetime_lookups (timezones.tests.NewDatabaseTests.test_query_datetime_lookups) ... ok test_query_datetime_lookups_in_other_timezone (timezones.tests.NewDatabaseTests.test_query_datetime_lookups_in_other_timezone) ... ok test_query_datetimes (timezones.tests.NewDatabaseTests.test_query_datetimes) ... ok test_query_datetimes_in_other_timezone (timezones.tests.NewDatabaseTests.test_query_datetimes_in_other_timezone) ... ok test_query_filter (timezones.tests.NewDatabaseTests.test_query_filter) ... ok test_query_filter_with_naive_datetime (timezones.tests.NewDatabaseTests.test_query_filter_with_naive_datetime) ... ok test_query_filter_with_pytz_timezones (timezones.tests.NewDatabaseTests.test_query_filter_with_pytz_timezones) ... ok test_raw_sql (timezones.tests.NewDatabaseTests.test_raw_sql) ... ok test_update_with_timedelta (timezones.tests.NewDatabaseTests.test_update_with_timedelta) ... ok test_annotate (generic_relations_regress.tests.GenericRelationTests.test_annotate) ... ok test_charlink_delete (generic_relations_regress.tests.GenericRelationTests.test_charlink_delete) ... ok test_coerce_object_id_remote_field_cache_persistence (generic_relations_regress.tests.GenericRelationTests.test_coerce_object_id_remote_field_cache_persistence) ... ok test_editable_generic_rel (generic_relations_regress.tests.GenericRelationTests.test_editable_generic_rel) ... ok test_extra_join_condition (generic_relations_regress.tests.GenericRelationTests.test_extra_join_condition) ... ok test_filter_on_related_proxy_model (generic_relations_regress.tests.GenericRelationTests.test_filter_on_related_proxy_model) ... ok test_filter_targets_related_pk (generic_relations_regress.tests.GenericRelationTests.test_filter_targets_related_pk) ... ok test_generic_relation_ordering (generic_relations_regress.tests.GenericRelationTests.test_generic_relation_ordering) Ordering over a generic relation does not include extraneous ... ok test_generic_reverse_relation_with_abc (generic_relations_regress.tests.GenericRelationTests.test_generic_reverse_relation_with_abc) The reverse generic relation accessor (targets) is created if the ... ok test_generic_reverse_relation_with_mti (generic_relations_regress.tests.GenericRelationTests.test_generic_reverse_relation_with_mti) Filtering with a reverse generic relation, where the GenericRelation ... ok test_gfk_to_model_with_empty_pk (generic_relations_regress.tests.GenericRelationTests.test_gfk_to_model_with_empty_pk) Test related to #13085 ... ok test_inherited_models_content_type (generic_relations_regress.tests.GenericRelationTests.test_inherited_models_content_type) GenericRelations on inherited classes use the correct content type. ... ok test_join_reuse (generic_relations_regress.tests.GenericRelationTests.test_join_reuse) ... ok test_q_object_or (generic_relations_regress.tests.GenericRelationTests.test_q_object_or) SQL query parameters for generic relations are properly ... ok test_reverse_relation_pk (generic_relations_regress.tests.GenericRelationTests.test_reverse_relation_pk) The correct column name is used for the primary key on the ... ok test_target_model_bool_false (generic_relations_regress.tests.GenericRelationTests.test_target_model_bool_false) Saving a model with a GenericForeignKey to a model instance whose ... ok test_target_model_is_unsaved (generic_relations_regress.tests.GenericRelationTests.test_target_model_is_unsaved) Test related to #13085 ... ok test_target_model_len_zero (generic_relations_regress.tests.GenericRelationTests.test_target_model_len_zero) Saving a model with a GenericForeignKey to a model instance whose ... ok test_textlink_delete (generic_relations_regress.tests.GenericRelationTests.test_textlink_delete) ... ok test_ticket_20378 (generic_relations_regress.tests.GenericRelationTests.test_ticket_20378) ... ok test_ticket_20564 (generic_relations_regress.tests.GenericRelationTests.test_ticket_20564) ... ok test_ticket_20564_nullable_fk (generic_relations_regress.tests.GenericRelationTests.test_ticket_20564_nullable_fk) ... ok test_ticket_22982 (generic_relations_regress.tests.GenericRelationTests.test_ticket_22982) ... ok test_ticket_22998 (generic_relations_regress.tests.GenericRelationTests.test_ticket_22998) ... ok test_check_constraint_pointing_to_fk (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_fk) ... ok test_check_constraint_pointing_to_joined_fields (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_joined_fields) ... ok test_check_constraint_pointing_to_joined_fields_complex_check (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_joined_fields_complex_check) ... ok test_check_constraint_pointing_to_m2m_field (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_m2m_field) ... ok test_check_constraint_pointing_to_missing_field (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_missing_field) ... ok test_check_constraint_pointing_to_non_local_field (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_non_local_field) ... ok test_check_constraint_pointing_to_pk (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_pk) ... ok test_check_constraint_pointing_to_reverse_fk (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_reverse_fk) ... ok test_check_constraint_pointing_to_reverse_o2o (invalid_models_tests.test_models.ConstraintsTests.test_check_constraint_pointing_to_reverse_o2o) ... ok test_check_constraints (invalid_models_tests.test_models.ConstraintsTests.test_check_constraints) ... ok test_check_constraints_required_db_features (invalid_models_tests.test_models.ConstraintsTests.test_check_constraints_required_db_features) ... ok test_deferrable_unique_constraint (invalid_models_tests.test_models.ConstraintsTests.test_deferrable_unique_constraint) ... ok test_deferrable_unique_constraint_required_db_features (invalid_models_tests.test_models.ConstraintsTests.test_deferrable_unique_constraint_required_db_features) ... ok test_unique_constraint_condition_pointing_to_joined_fields (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_condition_pointing_to_joined_fields) ... ok test_unique_constraint_condition_pointing_to_missing_field (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_condition_pointing_to_missing_field) ... ok test_unique_constraint_include_pointing_to_fk (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_include_pointing_to_fk) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_unique_constraint_include_pointing_to_m2m_field (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_include_pointing_to_m2m_field) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_unique_constraint_include_pointing_to_missing_field (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_include_pointing_to_missing_field) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_unique_constraint_include_pointing_to_non_local_field (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_include_pointing_to_non_local_field) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_unique_constraint_pointing_to_fk (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_pointing_to_fk) ... ok test_unique_constraint_pointing_to_m2m_field (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_pointing_to_m2m_field) ... ok test_unique_constraint_pointing_to_missing_field (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_pointing_to_missing_field) ... ok test_unique_constraint_pointing_to_non_local_field (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_pointing_to_non_local_field) ... ok test_unique_constraint_pointing_to_reverse_o2o (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_pointing_to_reverse_o2o) ... ok test_unique_constraint_with_condition (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_with_condition) ... ok test_unique_constraint_with_condition_required_db_features (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_with_condition_required_db_features) ... ok test_unique_constraint_with_include (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_with_include) ... ok test_unique_constraint_with_include_required_db_features (invalid_models_tests.test_models.ConstraintsTests.test_unique_constraint_with_include_required_db_features) ... ok test_M2M_long_column_name (invalid_models_tests.test_models.FieldNamesTests.test_M2M_long_column_name) #13711 -- Model check for long M2M column names when database has ... skipped "The database doesn't have a column name length limit." test_db_column_clash (invalid_models_tests.test_models.FieldNamesTests.test_db_column_clash) ... ok test_ending_with_underscore (invalid_models_tests.test_models.FieldNamesTests.test_ending_with_underscore) ... ok test_including_separator (invalid_models_tests.test_models.FieldNamesTests.test_including_separator) ... ok test_local_field_long_column_name (invalid_models_tests.test_models.FieldNamesTests.test_local_field_long_column_name) #13711 -- Model check for long column names ... skipped "The database doesn't have a column name length limit." test_pk (invalid_models_tests.test_models.FieldNamesTests.test_pk) ... ok test_base64_invalid_upload (file_uploads.tests.FileUploadTests.test_base64_invalid_upload) ... ok test_base64_upload (file_uploads.tests.FileUploadTests.test_base64_upload) ... ok test_big_base64_newlines_upload (file_uploads.tests.FileUploadTests.test_big_base64_newlines_upload) ... ok test_big_base64_upload (file_uploads.tests.FileUploadTests.test_big_base64_upload) ... ok test_blank_filenames (file_uploads.tests.FileUploadTests.test_blank_filenames) Receiving file upload when filename is blank (before and after ... ok test_broken_custom_upload_handler (file_uploads.tests.FileUploadTests.test_broken_custom_upload_handler) ... ok test_content_type_extra (file_uploads.tests.FileUploadTests.test_content_type_extra) Uploaded files may have content type parameters available. ... ok test_custom_upload_handler (file_uploads.tests.FileUploadTests.test_custom_upload_handler) ... ok test_dangerous_file_names (file_uploads.tests.FileUploadTests.test_dangerous_file_names) Uploaded file names should be sanitized before ever reaching the view. ... ok test_empty_multipart_handled_gracefully (file_uploads.tests.FileUploadTests.test_empty_multipart_handled_gracefully) If passed an empty multipart message, MultiPartParser will return ... ok test_file_content (file_uploads.tests.FileUploadTests.test_file_content) ... ok test_file_error_blocking (file_uploads.tests.FileUploadTests.test_file_error_blocking) The server should not block when there are upload errors (bug #8622). ... ok test_filename_case_preservation (file_uploads.tests.FileUploadTests.test_filename_case_preservation) The storage backend shouldn't mess with the case of the filenames ... ok test_filename_overflow (file_uploads.tests.FileUploadTests.test_filename_overflow) File names over 256 characters (dangerous on some platforms) get fixed up. ... ok test_filename_traversal_upload (file_uploads.tests.FileUploadTests.test_filename_traversal_upload) ... ok test_fileupload_getlist (file_uploads.tests.FileUploadTests.test_fileupload_getlist) ... ok test_fileuploads_closed_at_request_end (file_uploads.tests.FileUploadTests.test_fileuploads_closed_at_request_end) ... ok test_large_upload (file_uploads.tests.FileUploadTests.test_large_upload) ... ok test_no_parsing_triggered_by_fd_closing (file_uploads.tests.FileUploadTests.test_no_parsing_triggered_by_fd_closing) ... ok test_simple_upload (file_uploads.tests.FileUploadTests.test_simple_upload) ... ok test_stop_upload_temporary_file_handler (file_uploads.tests.FileUploadTests.test_stop_upload_temporary_file_handler) ... ok test_truncated_multipart_handled_gracefully (file_uploads.tests.FileUploadTests.test_truncated_multipart_handled_gracefully) If passed an incomplete multipart message, MultiPartParser does not ... ok test_unicode_file_name (file_uploads.tests.FileUploadTests.test_unicode_file_name) ... ok test_unicode_file_name_rfc2231 (file_uploads.tests.FileUploadTests.test_unicode_file_name_rfc2231) Test receiving file upload when filename is encoded with RFC2231 ... ok test_unicode_file_name_rfc2231_with_double_quotes (file_uploads.tests.FileUploadTests.test_unicode_file_name_rfc2231_with_double_quotes) ... ok test_unicode_name_rfc2231 (file_uploads.tests.FileUploadTests.test_unicode_name_rfc2231) Test receiving file upload when filename is encoded with RFC2231 ... ok test_unicode_name_rfc2231_with_double_quotes (file_uploads.tests.FileUploadTests.test_unicode_name_rfc2231_with_double_quotes) ... ok test_upload_interrupted_temporary_file_handler (file_uploads.tests.FileUploadTests.test_upload_interrupted_temporary_file_handler) ... ok test_upload_name_is_validated (file_uploads.tests.FileUploadTests.test_upload_name_is_validated) ... ok test_check_jsonfield (invalid_models_tests.test_models.JSONFieldTests.test_check_jsonfield) ... ok test_check_jsonfield_required_db_features (invalid_models_tests.test_models.JSONFieldTests.test_check_jsonfield_required_db_features) ... ok test_ordering_pointing_to_json_field_value (invalid_models_tests.test_models.JSONFieldTests.test_ordering_pointing_to_json_field_value) ... ok test_callable_lookup (admin_inlines.tests.TestInline.test_callable_lookup) Admin inline should invoke local callable when its name is listed in readonly_fields ... ok test_can_delete (admin_inlines.tests.TestInline.test_can_delete) can_delete should be passed to inlineformset factory. ... ok test_create_inlines_on_inherited_model (admin_inlines.tests.TestInline.test_create_inlines_on_inherited_model) An object can be created with inlines when it inherits another class. ... ok test_custom_form_tabular_inline_extra_field_label (admin_inlines.tests.TestInline.test_custom_form_tabular_inline_extra_field_label) ... ok test_custom_form_tabular_inline_label (admin_inlines.tests.TestInline.test_custom_form_tabular_inline_label) A model form with a form field specified (TitleForm.title1) should have ... ok test_custom_form_tabular_inline_overridden_label (admin_inlines.tests.TestInline.test_custom_form_tabular_inline_overridden_label) SomeChildModelForm.__init__() overrides the label of a form field. ... ok test_custom_get_extra_form (admin_inlines.tests.TestInline.test_custom_get_extra_form) ... ok test_custom_min_num (admin_inlines.tests.TestInline.test_custom_min_num) ... ok test_custom_pk_shortcut (admin_inlines.tests.TestInline.test_custom_pk_shortcut) The "View on Site" link is correct for models with a custom primary key ... ok test_help_text (admin_inlines.tests.TestInline.test_help_text) The inlines' model field help texts are displayed when using both the ... ok test_inline_editable_pk (admin_inlines.tests.TestInline.test_inline_editable_pk) ... ok test_inline_hidden_field_no_column (admin_inlines.tests.TestInline.test_inline_hidden_field_no_column) #18263 -- Make sure hidden fields don't get a column in tabular inlines ... ok test_inline_nonauto_noneditable_inherited_pk (admin_inlines.tests.TestInline.test_inline_nonauto_noneditable_inherited_pk) ... ok test_inline_nonauto_noneditable_pk (admin_inlines.tests.TestInline.test_inline_nonauto_noneditable_pk) ... ok test_inline_primary (admin_inlines.tests.TestInline.test_inline_primary) ... ok test_inlines_show_change_link_registered (admin_inlines.tests.TestInline.test_inlines_show_change_link_registered) Inlines `show_change_link` for registered models when enabled. ... ok test_inlines_show_change_link_unregistered (admin_inlines.tests.TestInline.test_inlines_show_change_link_unregistered) Inlines `show_change_link` disabled for unregistered models. ... ok test_inlines_singular_heading_one_to_one (admin_inlines.tests.TestInline.test_inlines_singular_heading_one_to_one) ... ok test_localize_pk_shortcut (admin_inlines.tests.TestInline.test_localize_pk_shortcut) The "View on Site" link is correct for locales that use thousand ... ok test_many_to_many_inlines (admin_inlines.tests.TestInline.test_many_to_many_inlines) Autogenerated many-to-many inlines are displayed correctly (#13407) ... ok test_min_num (admin_inlines.tests.TestInline.test_min_num) min_num and extra determine number of forms. ... ok test_no_parent_callable_lookup (admin_inlines.tests.TestInline.test_no_parent_callable_lookup) Admin inline `readonly_field` shouldn't invoke parent ModelAdmin callable ... ok test_non_editable_custom_form_tabular_inline_extra_field_label (admin_inlines.tests.TestInline.test_non_editable_custom_form_tabular_inline_extra_field_label) ... ok test_non_related_name_inline (admin_inlines.tests.TestInline.test_non_related_name_inline) Multiple inlines with related_name='+' have correct form prefixes. ... ok test_noneditable_inline_has_field_inputs (admin_inlines.tests.TestInline.test_noneditable_inline_has_field_inputs) Inlines without change permission shows field inputs on add form. ... ok test_readonly_stacked_inline_label (admin_inlines.tests.TestInline.test_readonly_stacked_inline_label) Bug #13174. ... ok test_stacked_inline_edit_form_contains_has_original_class (admin_inlines.tests.TestInline.test_stacked_inline_edit_form_contains_has_original_class) ... ok test_tabular_inline_column_css_class (admin_inlines.tests.TestInline.test_tabular_inline_column_css_class) Field names are included in the context to output a field-specific ... ok test_tabular_inline_show_change_link_false_registered (admin_inlines.tests.TestInline.test_tabular_inline_show_change_link_false_registered) Inlines `show_change_link` disabled by default. ... ok test_tabular_model_form_meta_readonly_field (admin_inlines.tests.TestInline.test_tabular_model_form_meta_readonly_field) Tabular inlines use ModelForm.Meta.help_texts and labels for read-only ... ok test_tabular_non_field_errors (admin_inlines.tests.TestInline.test_tabular_non_field_errors) non_field_errors are displayed correctly, including the correct value ... ok test_invalid_default (invalid_models_tests.test_ordinary_fields.JSONFieldTests.test_invalid_default) ... ok test_valid_callable_default (invalid_models_tests.test_ordinary_fields.JSONFieldTests.test_valid_callable_default) ... ok test_valid_default (invalid_models_tests.test_ordinary_fields.JSONFieldTests.test_valid_default) ... ok test_valid_default_none (invalid_models_tests.test_ordinary_fields.JSONFieldTests.test_valid_default_none) ... ok test_db_collation (invalid_models_tests.test_ordinary_fields.TextFieldTests.test_db_collation) ... ok test_db_collation_required_db_features (invalid_models_tests.test_ordinary_fields.TextFieldTests.test_db_collation_required_db_features) ... ok test_max_length_warning (invalid_models_tests.test_ordinary_fields.TextFieldTests.test_max_length_warning) ... skipped 'Database has feature(s) supports_index_on_text_field' test_choices_named_group (invalid_models_tests.test_ordinary_fields.UUIDFieldTests.test_choices_named_group) ... ok test_func_index (invalid_models_tests.test_models.IndexesTests.test_func_index) ... ok test_func_index_complex_expression_custom_lookup (invalid_models_tests.test_models.IndexesTests.test_func_index_complex_expression_custom_lookup) ... ok test_func_index_pointing_to_fk (invalid_models_tests.test_models.IndexesTests.test_func_index_pointing_to_fk) ... ok test_func_index_pointing_to_m2m_field (invalid_models_tests.test_models.IndexesTests.test_func_index_pointing_to_m2m_field) ... ok test_func_index_pointing_to_missing_field (invalid_models_tests.test_models.IndexesTests.test_func_index_pointing_to_missing_field) ... ok test_func_index_pointing_to_missing_field_nested (invalid_models_tests.test_models.IndexesTests.test_func_index_pointing_to_missing_field_nested) ... ok test_func_index_pointing_to_non_local_field (invalid_models_tests.test_models.IndexesTests.test_func_index_pointing_to_non_local_field) ... ok test_func_index_required_db_features (invalid_models_tests.test_models.IndexesTests.test_func_index_required_db_features) ... ok test_index_include_pointing_to_fk (invalid_models_tests.test_models.IndexesTests.test_index_include_pointing_to_fk) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_index_include_pointing_to_m2m_field (invalid_models_tests.test_models.IndexesTests.test_index_include_pointing_to_m2m_field) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_index_include_pointing_to_missing_field (invalid_models_tests.test_models.IndexesTests.test_index_include_pointing_to_missing_field) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_index_include_pointing_to_non_local_field (invalid_models_tests.test_models.IndexesTests.test_index_include_pointing_to_non_local_field) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_index_with_condition (invalid_models_tests.test_models.IndexesTests.test_index_with_condition) ... ok test_index_with_condition_required_db_features (invalid_models_tests.test_models.IndexesTests.test_index_with_condition_required_db_features) ... ok test_index_with_include (invalid_models_tests.test_models.IndexesTests.test_index_with_include) ... ok test_index_with_include_required_db_features (invalid_models_tests.test_models.IndexesTests.test_index_with_include_required_db_features) ... ok test_max_name_length (invalid_models_tests.test_models.IndexesTests.test_max_name_length) ... ok test_name_constraints (invalid_models_tests.test_models.IndexesTests.test_name_constraints) ... ok test_pointing_to_fk (invalid_models_tests.test_models.IndexesTests.test_pointing_to_fk) ... ok test_pointing_to_m2m_field (invalid_models_tests.test_models.IndexesTests.test_pointing_to_m2m_field) ... ok test_pointing_to_missing_field (invalid_models_tests.test_models.IndexesTests.test_pointing_to_missing_field) ... ok test_pointing_to_non_local_field (invalid_models_tests.test_models.IndexesTests.test_pointing_to_non_local_field) ... ok test_actions_inheritance (modeladmin.test_actions.AdminActionsTests.test_actions_inheritance) ... ok test_actions_replace_global_action (modeladmin.test_actions.AdminActionsTests.test_actions_replace_global_action) ... ok test_get_actions_respects_permissions (modeladmin.test_actions.AdminActionsTests.test_get_actions_respects_permissions) ... ok test_global_actions_description (modeladmin.test_actions.AdminActionsTests.test_global_actions_description) ... ok test_bad_db_index_value (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_bad_db_index_value) ... ok test_bad_max_length_value (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_bad_max_length_value) ... ok test_bad_validators (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_bad_validators) ... ok test_choices_containing_lazy (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_choices_containing_lazy) ... ok test_choices_containing_non_pairs (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_choices_containing_non_pairs) ... ok test_choices_in_max_length (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_choices_in_max_length) ... ok test_choices_named_group (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_choices_named_group) ... ok test_choices_named_group_bad_structure (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_choices_named_group_bad_structure) ... ok test_choices_named_group_lazy (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_choices_named_group_lazy) ... ok test_choices_named_group_non_pairs (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_choices_named_group_non_pairs) ... ok test_db_collation (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_db_collation) ... ok test_db_collation_required_db_features (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_db_collation_required_db_features) ... ok test_iterable_of_iterable_choices (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_iterable_of_iterable_choices) ... ok test_lazy_choices (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_lazy_choices) ... ok test_missing_max_length (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_missing_max_length) ... ok test_negative_max_length (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_negative_max_length) ... ok test_non_iterable_choices (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_non_iterable_choices) ... ok test_non_iterable_choices_two_letters (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_non_iterable_choices_two_letters) Two letters isn't a valid choice pair. ... ok test_str_max_length_type (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_str_max_length_type) ... ok test_str_max_length_value (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_str_max_length_value) ... ok test_too_long_char_field_under_mysql (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_too_long_char_field_under_mysql) ... skipped 'Test valid only for MySQL' test_valid_field (invalid_models_tests.test_ordinary_fields.CharFieldTests.test_valid_field) ... ok test_unsupported_backend (expressions_window.tests.WindowUnsupportedTests.test_unsupported_backend) ... ok test_cascade_delete_proxy_model_admin_warning (proxy_models.tests.ProxyModelAdminTests.test_cascade_delete_proxy_model_admin_warning) Test if admin gives warning about cascade deleting models referenced ... ok test_delete_str_in_model_admin (proxy_models.tests.ProxyModelAdminTests.test_delete_str_in_model_admin) Test if the admin delete page shows the correct string representation ... ok test_custom_form_meta_exclude (modeladmin.tests.ModelAdminTests.test_custom_form_meta_exclude) The custom ModelForm's `Meta.exclude` is overridden if ... ok test_custom_form_meta_exclude_with_readonly (modeladmin.tests.ModelAdminTests.test_custom_form_meta_exclude_with_readonly) The custom ModelForm's `Meta.exclude` is respected when used in ... ok test_custom_form_validation (modeladmin.tests.ModelAdminTests.test_custom_form_validation) ... ok test_custom_formfield_override_readonly (modeladmin.tests.ModelAdminTests.test_custom_formfield_override_readonly) ... ok test_default_fields (modeladmin.tests.ModelAdminTests.test_default_fields) ... ok test_default_fieldsets (modeladmin.tests.ModelAdminTests.test_default_fieldsets) ... ok test_default_foreign_key_widget (modeladmin.tests.ModelAdminTests.test_default_foreign_key_widget) ... ok test_field_arguments (modeladmin.tests.ModelAdminTests.test_field_arguments) ... ok test_field_arguments_restricted_on_form (modeladmin.tests.ModelAdminTests.test_field_arguments_restricted_on_form) ... ok test_foreign_key_as_radio_field (modeladmin.tests.ModelAdminTests.test_foreign_key_as_radio_field) ... ok test_form_exclude_kwarg_override (modeladmin.tests.ModelAdminTests.test_form_exclude_kwarg_override) The `exclude` kwarg passed to `ModelAdmin.get_form()` overrides all ... ok test_formset_exclude_kwarg_override (modeladmin.tests.ModelAdminTests.test_formset_exclude_kwarg_override) The `exclude` kwarg passed to `InlineModelAdmin.get_formset()` ... ok test_formset_overriding_get_exclude_with_form_exclude (modeladmin.tests.ModelAdminTests.test_formset_overriding_get_exclude_with_form_exclude) ... ok test_formset_overriding_get_exclude_with_form_fields (modeladmin.tests.ModelAdminTests.test_formset_overriding_get_exclude_with_form_fields) ... ok test_get_autocomplete_fields (modeladmin.tests.ModelAdminTests.test_get_autocomplete_fields) ... ok test_get_deleted_objects (modeladmin.tests.ModelAdminTests.test_get_deleted_objects) ... ok test_get_deleted_objects_with_custom_has_delete_permission (modeladmin.tests.ModelAdminTests.test_get_deleted_objects_with_custom_has_delete_permission) ModelAdmin.get_deleted_objects() uses ModelAdmin.has_delete_permission() ... ok test_get_exclude_overrides_exclude (modeladmin.tests.ModelAdminTests.test_get_exclude_overrides_exclude) ... ok test_get_exclude_takes_obj (modeladmin.tests.ModelAdminTests.test_get_exclude_takes_obj) ... ok test_get_fieldsets (modeladmin.tests.ModelAdminTests.test_get_fieldsets) ... ok test_log_actions (modeladmin.tests.ModelAdminTests.test_log_actions) ... ok test_lookup_allowed_allows_nonexistent_lookup (modeladmin.tests.ModelAdminTests.test_lookup_allowed_allows_nonexistent_lookup) A lookup_allowed allows a parameter whose field lookup doesn't exist. ... ok test_lookup_allowed_onetoone (modeladmin.tests.ModelAdminTests.test_lookup_allowed_onetoone) ... ok test_modeladmin_str (modeladmin.tests.ModelAdminTests.test_modeladmin_str) ... ok test_overriding_get_exclude (modeladmin.tests.ModelAdminTests.test_overriding_get_exclude) ... ok test_queryset_override (modeladmin.tests.ModelAdminTests.test_queryset_override) ... ok test_raw_id_fields_widget_override (modeladmin.tests.ModelAdminTests.test_raw_id_fields_widget_override) The autocomplete_fields, raw_id_fields, and radio_fields widgets may ... ok test_regression_for_ticket_15820 (modeladmin.tests.ModelAdminTests.test_regression_for_ticket_15820) `obj` is passed from `InlineModelAdmin.get_fieldsets()` to ... ok test_avg_salary_department (expressions_window.tests.WindowFunctionTests.test_avg_salary_department) ... ok test_cume_dist (expressions_window.tests.WindowFunctionTests.test_cume_dist) Compute the cumulative distribution for the employees based on the ... ok test_dense_rank (expressions_window.tests.WindowFunctionTests.test_dense_rank) ... ok test_department_salary (expressions_window.tests.WindowFunctionTests.test_department_salary) ... ok test_distinct_window_function (expressions_window.tests.WindowFunctionTests.test_distinct_window_function) Window functions are not aggregates, and hence a query to filter out ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_fail_insert (expressions_window.tests.WindowFunctionTests.test_fail_insert) Window expressions can't be used in an INSERT statement. ... ok test_fail_update (expressions_window.tests.WindowFunctionTests.test_fail_update) Window expressions can't be used in an UPDATE statement. ... ok test_first_value (expressions_window.tests.WindowFunctionTests.test_first_value) ... ok test_function_list_of_values (expressions_window.tests.WindowFunctionTests.test_function_list_of_values) ... ok test_invalid_end_value_range (expressions_window.tests.WindowFunctionTests.test_invalid_end_value_range) ... ok test_invalid_start_value_range (expressions_window.tests.WindowFunctionTests.test_invalid_start_value_range) ... ok test_invalid_type_end_row_range (expressions_window.tests.WindowFunctionTests.test_invalid_type_end_row_range) ... ok test_invalid_type_end_value_range (expressions_window.tests.WindowFunctionTests.test_invalid_type_end_value_range) ... ok test_invalid_type_start_row_range (expressions_window.tests.WindowFunctionTests.test_invalid_type_start_row_range) ... ok test_invalid_type_start_value_range (expressions_window.tests.WindowFunctionTests.test_invalid_type_start_value_range) ... ok test_key_transform (expressions_window.tests.WindowFunctionTests.test_key_transform) ... ok test_lag (expressions_window.tests.WindowFunctionTests.test_lag) Compute the difference between an employee's salary and the next ... ok test_lag_decimalfield (expressions_window.tests.WindowFunctionTests.test_lag_decimalfield) ... ok test_last_value (expressions_window.tests.WindowFunctionTests.test_last_value) ... ok test_lead (expressions_window.tests.WindowFunctionTests.test_lead) Determine what the next person hired in the same department makes. ... ok test_lead_default (expressions_window.tests.WindowFunctionTests.test_lead_default) ... ok test_lead_offset (expressions_window.tests.WindowFunctionTests.test_lead_offset) Determine what the person hired after someone makes. Due to ... ok test_max_per_year (expressions_window.tests.WindowFunctionTests.test_max_per_year) Find the maximum salary awarded in the same year as the ... ok test_min_department (expressions_window.tests.WindowFunctionTests.test_min_department) An alternative way to specify a query for FirstValue. ... ok test_multiple_ordering (expressions_window.tests.WindowFunctionTests.test_multiple_ordering) Accumulate the salaries over the departments based on hire_date. ... ok test_multiple_partitioning (expressions_window.tests.WindowFunctionTests.test_multiple_partitioning) Find the maximum salary for each department for people hired in the ... ok test_nth_returns_null (expressions_window.tests.WindowFunctionTests.test_nth_returns_null) Find the nth row of the data set. None is returned since there are ... ok test_nthvalue (expressions_window.tests.WindowFunctionTests.test_nthvalue) ... ok test_ntile (expressions_window.tests.WindowFunctionTests.test_ntile) Compute the group for each of the employees across the entire company, ... ok test_percent_rank (expressions_window.tests.WindowFunctionTests.test_percent_rank) Calculate the percentage rank of the employees across the entire ... ok test_range_n_preceding_and_following (expressions_window.tests.WindowFunctionTests.test_range_n_preceding_and_following) ... ok test_range_unbound (expressions_window.tests.WindowFunctionTests.test_range_unbound) A query with RANGE BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING. ... ok test_rank (expressions_window.tests.WindowFunctionTests.test_rank) Rank the employees based on the year they're were hired. Since there ... ok test_related_ordering_with_count (expressions_window.tests.WindowFunctionTests.test_related_ordering_with_count) ... ok test_row_number (expressions_window.tests.WindowFunctionTests.test_row_number) The row number window function computes the number based on the order ... ok test_row_number_no_ordering (expressions_window.tests.WindowFunctionTests.test_row_number_no_ordering) The row number window function computes the number based on the order ... ok test_row_range_rank (expressions_window.tests.WindowFunctionTests.test_row_range_rank) A query with ROWS BETWEEN UNBOUNDED PRECEDING AND 3 FOLLOWING. ... ok test_subquery_row_range_rank (expressions_window.tests.WindowFunctionTests.test_subquery_row_range_rank) ... ok test_unsupported_range_frame_end (expressions_window.tests.WindowFunctionTests.test_unsupported_range_frame_end) ... skipped "Database doesn't support feature(s): only_supports_unbounded_with_preceding_and_following" test_unsupported_range_frame_start (expressions_window.tests.WindowFunctionTests.test_unsupported_range_frame_start) ... skipped "Database doesn't support feature(s): only_supports_unbounded_with_preceding_and_following" test_window_expression_within_subquery (expressions_window.tests.WindowFunctionTests.test_window_expression_within_subquery) ... ok test_empty_post (test_client.tests.ClientTest.test_empty_post) POST an empty dictionary to a view ... ok test_exc_info (test_client.tests.ClientTest.test_exc_info) ... ok test_exc_info_none (test_client.tests.ClientTest.test_exc_info_none) ... ok test_exception_following_nested_client_request (test_client.tests.ClientTest.test_exception_following_nested_client_request) A nested test client request shouldn't clobber exception signals from ... ok test_external_redirect (test_client.tests.ClientTest.test_external_redirect) ... ok test_external_redirect_with_fetch_error_msg (test_client.tests.ClientTest.test_external_redirect_with_fetch_error_msg) assertRedirects without fetch_redirect_response=False raises ... ok test_follow_307_and_308_get_head_query_string (test_client.tests.ClientTest.test_follow_307_and_308_get_head_query_string) ... ok test_follow_307_and_308_preserves_get_params (test_client.tests.ClientTest.test_follow_307_and_308_preserves_get_params) ... ok test_follow_307_and_308_preserves_post_data (test_client.tests.ClientTest.test_follow_307_and_308_preserves_post_data) ... ok test_follow_307_and_308_preserves_put_body (test_client.tests.ClientTest.test_follow_307_and_308_preserves_put_body) ... ok test_follow_307_and_308_preserves_query_string (test_client.tests.ClientTest.test_follow_307_and_308_preserves_query_string) ... ok test_follow_307_and_308_redirect (test_client.tests.ClientTest.test_follow_307_and_308_redirect) A 307 or 308 redirect preserves the request method after the redirect. ... ok test_follow_redirect (test_client.tests.ClientTest.test_follow_redirect) A URL that redirects can be followed to termination. ... ok test_follow_relative_redirect (test_client.tests.ClientTest.test_follow_relative_redirect) A URL with a relative redirect can be followed. ... ok test_follow_relative_redirect_no_trailing_slash (test_client.tests.ClientTest.test_follow_relative_redirect_no_trailing_slash) A URL with a relative redirect with no trailing slash can be followed. ... ok test_force_login_with_backend (test_client.tests.ClientTest.test_force_login_with_backend) Request a page that is protected with @login_required when using ... ok test_force_login_with_backend_missing_get_user (test_client.tests.ClientTest.test_force_login_with_backend_missing_get_user) force_login() skips auth backends without a get_user() method. ... ok test_force_login_without_backend (test_client.tests.ClientTest.test_force_login_without_backend) force_login() without passing a backend and with multiple backends ... ok test_form_error (test_client.tests.ClientTest.test_form_error) POST erroneous data to a form ... ok test_form_error_with_template (test_client.tests.ClientTest.test_form_error_with_template) POST erroneous data to a form using multiple templates ... ok test_get_data_none (test_client.tests.ClientTest.test_get_data_none) ... ok test_get_post_view (test_client.tests.ClientTest.test_get_post_view) GET a view that normally expects POSTs ... ok test_get_view (test_client.tests.ClientTest.test_get_view) GET a view ... ok test_incomplete_data_form (test_client.tests.ClientTest.test_incomplete_data_form) POST incomplete data to a form ... ok test_incomplete_data_form_with_template (test_client.tests.ClientTest.test_incomplete_data_form_with_template) POST incomplete data to a form using multiple templates ... ok test_insecure (test_client.tests.ClientTest.test_insecure) GET a URL through http ... ok test_json_encoder_argument (test_client.tests.ClientTest.test_json_encoder_argument) The test Client accepts a json_encoder. ... ok test_json_serialization (test_client.tests.ClientTest.test_json_serialization) The test client serializes JSON data. ... ok test_logout (test_client.tests.ClientTest.test_logout) Request a logout after logging in ... ok test_logout_cookie_sessions (test_client.tests.ClientTest.test_logout_cookie_sessions) ... ok test_logout_with_force_login (test_client.tests.ClientTest.test_logout_with_force_login) Request a logout after logging in ... ok test_mail_sending (test_client.tests.ClientTest.test_mail_sending) Mail is redirected to a dummy outbox during test setup ... ok test_mass_mail_sending (test_client.tests.ClientTest.test_mass_mail_sending) Mass mail is redirected to a dummy outbox during test setup ... ok test_notfound_response (test_client.tests.ClientTest.test_notfound_response) GET a URL that responds as '404:Not Found' ... ok test_permanent_redirect (test_client.tests.ClientTest.test_permanent_redirect) GET a URL that redirects permanently elsewhere ... ok test_post (test_client.tests.ClientTest.test_post) POST some data to a view ... ok test_post_data_none (test_client.tests.ClientTest.test_post_data_none) ... ok test_put (test_client.tests.ClientTest.test_put) ... ok test_query_string_encoding (test_client.tests.ClientTest.test_query_string_encoding) ... ok test_raw_post (test_client.tests.ClientTest.test_raw_post) POST raw data (with a content type) to a view ... ok test_redirect (test_client.tests.ClientTest.test_redirect) GET a URL that redirects elsewhere ... ok test_redirect_http (test_client.tests.ClientTest.test_redirect_http) GET a URL that redirects to an http URI ... ok test_redirect_https (test_client.tests.ClientTest.test_redirect_https) GET a URL that redirects to an https URI ... ok test_redirect_to_strange_location (test_client.tests.ClientTest.test_redirect_to_strange_location) GET a URL that redirects to a non-200 page ... ok test_redirect_with_query (test_client.tests.ClientTest.test_redirect_with_query) GET a URL that redirects with given GET parameters ... ok test_redirect_with_query_ordering (test_client.tests.ClientTest.test_redirect_with_query_ordering) assertRedirects() ignores the order of query string parameters. ... ok test_relative_redirect (test_client.tests.ClientTest.test_relative_redirect) ... ok test_relative_redirect_no_trailing_slash (test_client.tests.ClientTest.test_relative_redirect_no_trailing_slash) ... ok test_response_attached_request (test_client.tests.ClientTest.test_response_attached_request) The returned response has a ``request`` attribute with the originating ... ok test_response_headers (test_client.tests.ClientTest.test_response_headers) Check the value of HTTP headers returned in a response ... ok test_response_raises_multi_arg_exception (test_client.tests.ClientTest.test_response_raises_multi_arg_exception) A request may raise an exception with more than one required arg. ... ok test_response_resolver_match (test_client.tests.ClientTest.test_response_resolver_match) The response contains a ResolverMatch instance. ... ok test_response_resolver_match_redirect_follow (test_client.tests.ClientTest.test_response_resolver_match_redirect_follow) The response ResolverMatch instance contains the correct ... ok test_response_resolver_match_regular_view (test_client.tests.ClientTest.test_response_resolver_match_regular_view) The response ResolverMatch instance contains the correct ... ok test_reverse_lazy_decodes (test_client.tests.ClientTest.test_reverse_lazy_decodes) reverse_lazy() works in the test client ... ok test_secure (test_client.tests.ClientTest.test_secure) GET a URL through https ... ok test_session_engine_is_invalid (test_client.tests.ClientTest.test_session_engine_is_invalid) ... ok test_session_modifying_view (test_client.tests.ClientTest.test_session_modifying_view) Request a page that modifies the session ... ok test_sessions_app_is_not_installed (test_client.tests.ClientTest.test_sessions_app_is_not_installed) ... ok test_temporary_redirect (test_client.tests.ClientTest.test_temporary_redirect) GET a URL that does a non-permanent redirect ... ok test_trace (test_client.tests.ClientTest.test_trace) TRACE a view ... ok test_unknown_page (test_client.tests.ClientTest.test_unknown_page) GET an invalid URL ... ok test_uploading_named_temp_file (test_client.tests.ClientTest.test_uploading_named_temp_file) ... ok test_uploading_temp_file (test_client.tests.ClientTest.test_uploading_temp_file) ... ok test_url_parameters (test_client.tests.ClientTest.test_url_parameters) Make sure that URL ;-parameters are not stripped. ... ok test_valid_form (test_client.tests.ClientTest.test_valid_form) POST valid data to a form ... ok test_valid_form_with_hints (test_client.tests.ClientTest.test_valid_form_with_hints) GET a form, providing hints in the GET data ... ok test_valid_form_with_template (test_client.tests.ClientTest.test_valid_form_with_template) POST valid data to a form using multiple templates ... ok test_view_with_bad_login (test_client.tests.ClientTest.test_view_with_bad_login) Request a page that is protected with @login, but use bad credentials ... ok test_view_with_exception (test_client.tests.ClientTest.test_view_with_exception) Request a page that is known to throw an error ... ok test_view_with_force_login (test_client.tests.ClientTest.test_view_with_force_login) Request a page that is protected with @login_required ... ok test_view_with_force_login_and_custom_redirect (test_client.tests.ClientTest.test_view_with_force_login_and_custom_redirect) Request a page that is protected with ... ok test_view_with_inactive_force_login (test_client.tests.ClientTest.test_view_with_inactive_force_login) Request a page that is protected with @login, but use an inactive login ... ok test_view_with_inactive_login (test_client.tests.ClientTest.test_view_with_inactive_login) An inactive user may login if the authenticate backend allows it. ... ok test_view_with_login (test_client.tests.ClientTest.test_view_with_login) Request a page that is protected with @login_required ... ok test_view_with_login_and_custom_redirect (test_client.tests.ClientTest.test_view_with_login_and_custom_redirect) Request a page that is protected with @login_required(redirect_field_name='redirect_to') ... ok test_view_with_login_when_sessions_app_is_not_installed (test_client.tests.ClientTest.test_view_with_login_when_sessions_app_is_not_installed) ... ok test_view_with_method_force_login (test_client.tests.ClientTest.test_view_with_method_force_login) Request a page that is protected with a @login_required method ... ok test_view_with_method_login (test_client.tests.ClientTest.test_view_with_method_login) Request a page that is protected with a @login_required method ... ok test_view_with_method_permissions (test_client.tests.ClientTest.test_view_with_method_permissions) Request a page that is protected with a @permission_required method ... ok test_view_with_permissions (test_client.tests.ClientTest.test_view_with_permissions) Request a page that is protected with @permission_required ... ok test_view_with_permissions_exception (test_client.tests.ClientTest.test_view_with_permissions_exception) Request a page that is protected with @permission_required but raises an exception ... ok test_bad_class (get_object_or_404.tests.GetObjectOr404Tests.test_bad_class) ... ok test_get_list_or_404_queryset_attribute_error (get_object_or_404.tests.GetObjectOr404Tests.test_get_list_or_404_queryset_attribute_error) AttributeError raised by QuerySet.filter() isn't hidden. ... ok test_get_object_or_404 (get_object_or_404.tests.GetObjectOr404Tests.test_get_object_or_404) ... ok test_get_object_or_404_queryset_attribute_error (get_object_or_404.tests.GetObjectOr404Tests.test_get_object_or_404_queryset_attribute_error) AttributeError raised by QuerySet.get() isn't hidden. ... ok test_abstract_base_with_model_fields (proxy_models.tests.ProxyModelTests.test_abstract_base_with_model_fields) ... ok test_basic_proxy (proxy_models.tests.ProxyModelTests.test_basic_proxy) Creating a Person makes them accessible through the MyPerson proxy. ... ok test_basic_proxy_reverse (proxy_models.tests.ProxyModelTests.test_basic_proxy_reverse) A new MyPerson also shows up as a standard Person. ... ok test_concrete_model (proxy_models.tests.ProxyModelTests.test_concrete_model) ... ok test_content_type (proxy_models.tests.ProxyModelTests.test_content_type) ... ok test_correct_type_proxy_of_proxy (proxy_models.tests.ProxyModelTests.test_correct_type_proxy_of_proxy) Correct type when querying a proxy of proxy ... ok test_eq (proxy_models.tests.ProxyModelTests.test_eq) ... ok test_filter_proxy_relation_reverse (proxy_models.tests.ProxyModelTests.test_filter_proxy_relation_reverse) ... ok test_inheritance_new_table (proxy_models.tests.ProxyModelTests.test_inheritance_new_table) The StatusPerson models should have its own table (it's using ORM-level ... ok test_myperson_manager (proxy_models.tests.ProxyModelTests.test_myperson_manager) ... ok test_new_fields (proxy_models.tests.ProxyModelTests.test_new_fields) ... ok test_no_base_classes (proxy_models.tests.ProxyModelTests.test_no_base_classes) ... ok test_no_proxy (proxy_models.tests.ProxyModelTests.test_no_proxy) Person is not proxied by StatusPerson subclass. ... ok test_otherperson_manager (proxy_models.tests.ProxyModelTests.test_otherperson_manager) ... ok test_permissions_created (proxy_models.tests.ProxyModelTests.test_permissions_created) ... ok test_proxy_bug (proxy_models.tests.ProxyModelTests.test_proxy_bug) ... ok test_proxy_delete (proxy_models.tests.ProxyModelTests.test_proxy_delete) Proxy objects can be deleted ... ok test_proxy_for_model (proxy_models.tests.ProxyModelTests.test_proxy_for_model) ... ok test_proxy_included_in_ancestors (proxy_models.tests.ProxyModelTests.test_proxy_included_in_ancestors) Proxy models are included in the ancestors for a model's DoesNotExist ... ok test_proxy_load_from_fixture (proxy_models.tests.ProxyModelTests.test_proxy_load_from_fixture) ... ok test_proxy_model_signals (proxy_models.tests.ProxyModelTests.test_proxy_model_signals) Test save signals for proxy models ... ok test_proxy_update (proxy_models.tests.ProxyModelTests.test_proxy_update) ... ok test_same_manager_queries (proxy_models.tests.ProxyModelTests.test_same_manager_queries) The MyPerson model should be generating the same database queries as ... ok test_select_related (proxy_models.tests.ProxyModelTests.test_select_related) We can still use `select_related()` to include related models in our ... ok test_swappable (proxy_models.tests.ProxyModelTests.test_swappable) ... ok test_too_many_concrete_classes (proxy_models.tests.ProxyModelTests.test_too_many_concrete_classes) ... ok test_user_proxy_models (proxy_models.tests.ProxyModelTests.test_user_proxy_models) ... ok test_aware_datetime_date_detail (generic_views.test_dates.DateDetailViewTests.test_aware_datetime_date_detail) ... ok test_date_detail_allow_future (generic_views.test_dates.DateDetailViewTests.test_date_detail_allow_future) ... ok test_date_detail_by_pk (generic_views.test_dates.DateDetailViewTests.test_date_detail_by_pk) ... ok test_date_detail_by_slug (generic_views.test_dates.DateDetailViewTests.test_date_detail_by_slug) ... ok test_date_detail_custom_month_format (generic_views.test_dates.DateDetailViewTests.test_date_detail_custom_month_format) ... ok test_datetime_date_detail (generic_views.test_dates.DateDetailViewTests.test_datetime_date_detail) ... ok test_get_object_custom_queryset (generic_views.test_dates.DateDetailViewTests.test_get_object_custom_queryset) Custom querysets are used when provided to ... ok test_get_object_custom_queryset_numqueries (generic_views.test_dates.DateDetailViewTests.test_get_object_custom_queryset_numqueries) ... ok test_invalid_url (generic_views.test_dates.DateDetailViewTests.test_invalid_url) ... ok test_year_out_of_range (generic_views.test_dates.DateDetailViewTests.test_year_out_of_range) ... ok test_abstract_base_class_m2m_relation_inheritance (model_inheritance_regress.tests.ModelInheritanceTest.test_abstract_base_class_m2m_relation_inheritance) ... ok test_abstract_verbose_name_plural_inheritance (model_inheritance_regress.tests.ModelInheritanceTest.test_abstract_verbose_name_plural_inheritance) verbose_name_plural correctly inherited from ABC if inheritance chain ... ok test_all_fields_from_abstract_base_class (model_inheritance_regress.tests.ModelInheritanceTest.test_all_fields_from_abstract_base_class) Regression tests for #7588 ... ok test_concrete_abstract_concrete_pk (model_inheritance_regress.tests.ModelInheritanceTest.test_concrete_abstract_concrete_pk) Primary key set correctly with concrete->abstract->concrete inheritance. ... ok test_create_new_instance_with_pk_equals_none (model_inheritance_regress.tests.ModelInheritanceTest.test_create_new_instance_with_pk_equals_none) ... ok test_create_new_instance_with_pk_equals_none_multi_inheritance (model_inheritance_regress.tests.ModelInheritanceTest.test_create_new_instance_with_pk_equals_none_multi_inheritance) ... ok test_filter_with_parent_fk (model_inheritance_regress.tests.ModelInheritanceTest.test_filter_with_parent_fk) ... ok test_get_next_previous_by_date (model_inheritance_regress.tests.ModelInheritanceTest.test_get_next_previous_by_date) Regression tests for #8076 ... ok test_id_field_update_on_ancestor_change (model_inheritance_regress.tests.ModelInheritanceTest.test_id_field_update_on_ancestor_change) ... ok test_inheritance_joins (model_inheritance_regress.tests.ModelInheritanceTest.test_inheritance_joins) ... ok test_inheritance_resolve_columns (model_inheritance_regress.tests.ModelInheritanceTest.test_inheritance_resolve_columns) ... ok test_inheritance_select_related (model_inheritance_regress.tests.ModelInheritanceTest.test_inheritance_select_related) ... ok test_inheritance_values_joins (model_inheritance_regress.tests.ModelInheritanceTest.test_inheritance_values_joins) ... expected failure test_inherited_fields (model_inheritance_regress.tests.ModelInheritanceTest.test_inherited_fields) Regression test for #8825 and #9390 ... ok test_inherited_nullable_exclude (model_inheritance_regress.tests.ModelInheritanceTest.test_inherited_nullable_exclude) ... ok test_inherited_unique_field_with_form (model_inheritance_regress.tests.ModelInheritanceTest.test_inherited_unique_field_with_form) A model which has different primary key for the parent model passes ... ok test_issue_11764 (model_inheritance_regress.tests.ModelInheritanceTest.test_issue_11764) Regression test for #11764 ... ok test_issue_21554 (model_inheritance_regress.tests.ModelInheritanceTest.test_issue_21554) ... ok test_issue_6755 (model_inheritance_regress.tests.ModelInheritanceTest.test_issue_6755) Regression test for #6755 ... ok test_issue_7105 (model_inheritance_regress.tests.ModelInheritanceTest.test_issue_7105) ... ok test_issue_7276 (model_inheritance_regress.tests.ModelInheritanceTest.test_issue_7276) ... ok test_issue_7488 (model_inheritance_regress.tests.ModelInheritanceTest.test_issue_7488) ... ok test_issue_7853 (model_inheritance_regress.tests.ModelInheritanceTest.test_issue_7853) Regression test for #7853 ... ok test_model_inheritance (model_inheritance_regress.tests.ModelInheritanceTest.test_model_inheritance) ... ok test_ptr_accessor_assigns_state (model_inheritance_regress.tests.ModelInheritanceTest.test_ptr_accessor_assigns_state) ... ok test_queries_on_parent_access (model_inheritance_regress.tests.ModelInheritanceTest.test_queries_on_parent_access) ... ok test_queryset_update_on_parent_model (model_inheritance_regress.tests.ModelInheritanceTest.test_queryset_update_on_parent_model) Regression test for #10362 ... ok test_related_filtering_query_efficiency_ticket_15844 (model_inheritance_regress.tests.ModelInheritanceTest.test_related_filtering_query_efficiency_ticket_15844) ... ok test_use_explicit_o2o_to_parent_as_pk (model_inheritance_regress.tests.ModelInheritanceTest.test_use_explicit_o2o_to_parent_as_pk) The connector from child to parent need not be the pk on the child. ... ok test_use_explicit_o2o_to_parent_from_abstract_model (model_inheritance_regress.tests.ModelInheritanceTest.test_use_explicit_o2o_to_parent_from_abstract_model) ... ok test_aware_datetime_day_view (generic_views.test_dates.DayArchiveViewTests.test_aware_datetime_day_view) ... ok test_custom_month_format (generic_views.test_dates.DayArchiveViewTests.test_custom_month_format) ... ok test_datetime_day_view (generic_views.test_dates.DayArchiveViewTests.test_datetime_day_view) ... ok test_day_view (generic_views.test_dates.DayArchiveViewTests.test_day_view) ... ok test_day_view_allow_empty (generic_views.test_dates.DayArchiveViewTests.test_day_view_allow_empty) ... ok test_day_view_allow_future (generic_views.test_dates.DayArchiveViewTests.test_day_view_allow_future) ... ok test_day_view_invalid_pattern (generic_views.test_dates.DayArchiveViewTests.test_day_view_invalid_pattern) ... ok test_day_view_paginated (generic_views.test_dates.DayArchiveViewTests.test_day_view_paginated) ... ok test_next_prev_context (generic_views.test_dates.DayArchiveViewTests.test_next_prev_context) ... ok test_today_view (generic_views.test_dates.DayArchiveViewTests.test_today_view) ... ok test_allow_empty_archive_view (generic_views.test_dates.ArchiveIndexViewTests.test_allow_empty_archive_view) ... ok test_archive_view (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view) ... ok test_archive_view_by_month (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view_by_month) ... ok test_archive_view_context_object_name (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view_context_object_name) ... ok test_archive_view_custom_sorting (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view_custom_sorting) ... ok test_archive_view_custom_sorting_dec (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view_custom_sorting_dec) ... ok test_archive_view_invalid (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view_invalid) ... ok test_archive_view_template (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view_template) ... ok test_archive_view_template_suffix (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view_template_suffix) ... ok test_archive_view_without_date_field (generic_views.test_dates.ArchiveIndexViewTests.test_archive_view_without_date_field) ... ok test_aware_datetime_archive_view (generic_views.test_dates.ArchiveIndexViewTests.test_aware_datetime_archive_view) ... ok test_date_list_order (generic_views.test_dates.ArchiveIndexViewTests.test_date_list_order) date_list should be sorted descending in index ... ok test_datetime_archive_view (generic_views.test_dates.ArchiveIndexViewTests.test_datetime_archive_view) ... ok test_empty_archive_view (generic_views.test_dates.ArchiveIndexViewTests.test_empty_archive_view) ... ok test_no_duplicate_query (generic_views.test_dates.ArchiveIndexViewTests.test_no_duplicate_query) ... ok test_paginated_archive_view (generic_views.test_dates.ArchiveIndexViewTests.test_paginated_archive_view) ... ok test_paginated_archive_view_does_not_load_entire_table (generic_views.test_dates.ArchiveIndexViewTests.test_paginated_archive_view_does_not_load_entire_table) ... ok test_aware_datetime_month_view (generic_views.test_dates.MonthArchiveViewTests.test_aware_datetime_month_view) ... ok test_custom_month_format (generic_views.test_dates.MonthArchiveViewTests.test_custom_month_format) ... ok test_date_list_order (generic_views.test_dates.MonthArchiveViewTests.test_date_list_order) date_list should be sorted ascending in month view ... ok test_datetime_month_view (generic_views.test_dates.MonthArchiveViewTests.test_datetime_month_view) ... ok test_month_view (generic_views.test_dates.MonthArchiveViewTests.test_month_view) ... ok test_month_view_allow_empty (generic_views.test_dates.MonthArchiveViewTests.test_month_view_allow_empty) ... ok test_month_view_allow_future (generic_views.test_dates.MonthArchiveViewTests.test_month_view_allow_future) ... ok test_month_view_get_month_from_request (generic_views.test_dates.MonthArchiveViewTests.test_month_view_get_month_from_request) ... ok test_month_view_invalid_pattern (generic_views.test_dates.MonthArchiveViewTests.test_month_view_invalid_pattern) ... ok test_month_view_paginated (generic_views.test_dates.MonthArchiveViewTests.test_month_view_paginated) ... ok test_month_view_without_month_in_url (generic_views.test_dates.MonthArchiveViewTests.test_month_view_without_month_in_url) ... ok test_previous_month_without_content (generic_views.test_dates.MonthArchiveViewTests.test_previous_month_without_content) Content can exist on any day of the previous month. Refs #14711 ... ok test_late_form_validation (generic_views.test_edit.BasicFormTests.test_late_form_validation) A form can be marked invalid in the form_valid() method (#25548). ... ok test_post_data (generic_views.test_edit.BasicFormTests.test_post_data) ... ok test_aware_datetime_week_view (generic_views.test_dates.WeekArchiveViewTests.test_aware_datetime_week_view) ... ok test_datetime_week_view (generic_views.test_dates.WeekArchiveViewTests.test_datetime_week_view) ... ok test_incompatible_iso_week_format_view (generic_views.test_dates.WeekArchiveViewTests.test_incompatible_iso_week_format_view) ... ok test_unknown_week_format (generic_views.test_dates.WeekArchiveViewTests.test_unknown_week_format) ... ok test_week_iso_format (generic_views.test_dates.WeekArchiveViewTests.test_week_iso_format) ... ok test_week_start_Monday (generic_views.test_dates.WeekArchiveViewTests.test_week_start_Monday) ... ok test_week_view (generic_views.test_dates.WeekArchiveViewTests.test_week_view) ... ok test_week_view_allow_empty (generic_views.test_dates.WeekArchiveViewTests.test_week_view_allow_empty) ... ok test_week_view_allow_future (generic_views.test_dates.WeekArchiveViewTests.test_week_view_allow_future) ... ok test_week_view_invalid_pattern (generic_views.test_dates.WeekArchiveViewTests.test_week_view_invalid_pattern) ... ok test_week_view_paginated (generic_views.test_dates.WeekArchiveViewTests.test_week_view_paginated) ... ok test_aware_datetime_year_view (generic_views.test_dates.YearArchiveViewTests.test_aware_datetime_year_view) ... ok test_date_list_order (generic_views.test_dates.YearArchiveViewTests.test_date_list_order) date_list should be sorted ascending in year view ... ok test_datetime_year_view (generic_views.test_dates.YearArchiveViewTests.test_datetime_year_view) ... ok test_get_context_data_receives_extra_context (generic_views.test_dates.YearArchiveViewTests.test_get_context_data_receives_extra_context) MultipleObjectMixin.get_context_data() receives the context set by ... ok test_get_dated_items_not_implemented (generic_views.test_dates.YearArchiveViewTests.test_get_dated_items_not_implemented) ... ok test_no_duplicate_query (generic_views.test_dates.YearArchiveViewTests.test_no_duplicate_query) ... ok test_year_view (generic_views.test_dates.YearArchiveViewTests.test_year_view) ... ok test_year_view_allow_future (generic_views.test_dates.YearArchiveViewTests.test_year_view_allow_future) ... ok test_year_view_custom_sort_order (generic_views.test_dates.YearArchiveViewTests.test_year_view_custom_sort_order) ... ok test_year_view_empty (generic_views.test_dates.YearArchiveViewTests.test_year_view_empty) ... ok test_year_view_invalid_pattern (generic_views.test_dates.YearArchiveViewTests.test_year_view_invalid_pattern) ... ok test_year_view_make_object_list (generic_views.test_dates.YearArchiveViewTests.test_year_view_make_object_list) ... ok test_year_view_paginated (generic_views.test_dates.YearArchiveViewTests.test_year_view_paginated) ... ok test_year_view_two_custom_sort_orders (generic_views.test_dates.YearArchiveViewTests.test_year_view_two_custom_sort_orders) ... ok test_delete_by_delete (generic_views.test_edit.DeleteViewTests.test_delete_by_delete) ... ok test_delete_by_post (generic_views.test_edit.DeleteViewTests.test_delete_by_post) ... ok test_delete_with_interpolated_redirect (generic_views.test_edit.DeleteViewTests.test_delete_with_interpolated_redirect) ... ok test_delete_with_redirect (generic_views.test_edit.DeleteViewTests.test_delete_with_redirect) ... ok test_delete_with_special_properties (generic_views.test_edit.DeleteViewTests.test_delete_with_special_properties) ... ok test_delete_without_redirect (generic_views.test_edit.DeleteViewTests.test_delete_without_redirect) ... ok test_create (generic_views.test_edit.CreateViewTests.test_create) ... ok test_create_invalid (generic_views.test_edit.CreateViewTests.test_create_invalid) ... ok test_create_restricted (generic_views.test_edit.CreateViewTests.test_create_restricted) ... ok test_create_view_all_fields (generic_views.test_edit.CreateViewTests.test_create_view_all_fields) ... ok test_create_view_with_restricted_fields (generic_views.test_edit.CreateViewTests.test_create_view_with_restricted_fields) ... ok test_create_view_without_explicit_fields (generic_views.test_edit.CreateViewTests.test_create_view_without_explicit_fields) ... ok test_create_with_interpolated_redirect (generic_views.test_edit.CreateViewTests.test_create_with_interpolated_redirect) ... ok test_create_with_object_url (generic_views.test_edit.CreateViewTests.test_create_with_object_url) ... ok test_create_with_redirect (generic_views.test_edit.CreateViewTests.test_create_with_redirect) ... ok test_create_with_special_properties (generic_views.test_edit.CreateViewTests.test_create_with_special_properties) ... ok test_create_without_redirect (generic_views.test_edit.CreateViewTests.test_create_without_redirect) ... ok test_define_both_fields_and_form_class (generic_views.test_edit.CreateViewTests.test_define_both_fields_and_form_class) ... ok test_array_agg_distinct_false (postgres_tests.test_aggregates.TestAggregateDistinct.test_array_agg_distinct_false) ... skipped 'PostgreSQL specific tests' test_array_agg_distinct_true (postgres_tests.test_aggregates.TestAggregateDistinct.test_array_agg_distinct_true) ... skipped 'PostgreSQL specific tests' test_json_agg_distinct_false (postgres_tests.test_aggregates.TestAggregateDistinct.test_json_agg_distinct_false) ... skipped 'PostgreSQL specific tests' test_json_agg_distinct_true (postgres_tests.test_aggregates.TestAggregateDistinct.test_json_agg_distinct_true) ... skipped 'PostgreSQL specific tests' test_string_agg_distinct_false (postgres_tests.test_aggregates.TestAggregateDistinct.test_string_agg_distinct_false) ... skipped 'PostgreSQL specific tests' test_string_agg_distinct_true (postgres_tests.test_aggregates.TestAggregateDistinct.test_string_agg_distinct_true) ... skipped 'PostgreSQL specific tests' test_array_agg_booleanfield (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_booleanfield) ... skipped 'PostgreSQL specific tests' test_array_agg_booleanfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_booleanfield_ordering) ... skipped 'PostgreSQL specific tests' test_array_agg_charfield (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_charfield) ... skipped 'PostgreSQL specific tests' test_array_agg_charfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_charfield_ordering) ... skipped 'PostgreSQL specific tests' test_array_agg_empty_result (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_empty_result) ... skipped 'PostgreSQL specific tests' test_array_agg_filter (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_filter) ... skipped 'PostgreSQL specific tests' test_array_agg_integerfield (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_integerfield) ... skipped 'PostgreSQL specific tests' test_array_agg_integerfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_integerfield_ordering) ... skipped 'PostgreSQL specific tests' test_array_agg_jsonfield (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_jsonfield) ... skipped 'PostgreSQL specific tests' test_array_agg_jsonfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_jsonfield_ordering) ... skipped 'PostgreSQL specific tests' test_array_agg_lookups (postgres_tests.test_aggregates.TestGeneralAggregate.test_array_agg_lookups) ... skipped 'PostgreSQL specific tests' test_bit_and_empty_result (postgres_tests.test_aggregates.TestGeneralAggregate.test_bit_and_empty_result) ... skipped 'PostgreSQL specific tests' test_bit_and_general (postgres_tests.test_aggregates.TestGeneralAggregate.test_bit_and_general) ... skipped 'PostgreSQL specific tests' test_bit_and_on_only_false_values (postgres_tests.test_aggregates.TestGeneralAggregate.test_bit_and_on_only_false_values) ... skipped 'PostgreSQL specific tests' test_bit_and_on_only_true_values (postgres_tests.test_aggregates.TestGeneralAggregate.test_bit_and_on_only_true_values) ... skipped 'PostgreSQL specific tests' test_bit_or_empty_result (postgres_tests.test_aggregates.TestGeneralAggregate.test_bit_or_empty_result) ... skipped 'PostgreSQL specific tests' test_bit_or_general (postgres_tests.test_aggregates.TestGeneralAggregate.test_bit_or_general) ... skipped 'PostgreSQL specific tests' test_bit_or_on_only_false_values (postgres_tests.test_aggregates.TestGeneralAggregate.test_bit_or_on_only_false_values) ... skipped 'PostgreSQL specific tests' test_bit_or_on_only_true_values (postgres_tests.test_aggregates.TestGeneralAggregate.test_bit_or_on_only_true_values) ... skipped 'PostgreSQL specific tests' test_bool_and_empty_result (postgres_tests.test_aggregates.TestGeneralAggregate.test_bool_and_empty_result) ... skipped 'PostgreSQL specific tests' test_bool_and_general (postgres_tests.test_aggregates.TestGeneralAggregate.test_bool_and_general) ... skipped 'PostgreSQL specific tests' test_bool_and_q_object (postgres_tests.test_aggregates.TestGeneralAggregate.test_bool_and_q_object) ... skipped 'PostgreSQL specific tests' test_bool_or_empty_result (postgres_tests.test_aggregates.TestGeneralAggregate.test_bool_or_empty_result) ... skipped 'PostgreSQL specific tests' test_bool_or_general (postgres_tests.test_aggregates.TestGeneralAggregate.test_bool_or_general) ... skipped 'PostgreSQL specific tests' test_bool_or_q_object (postgres_tests.test_aggregates.TestGeneralAggregate.test_bool_or_q_object) ... skipped 'PostgreSQL specific tests' test_json_agg (postgres_tests.test_aggregates.TestGeneralAggregate.test_json_agg) ... skipped 'PostgreSQL specific tests' test_json_agg_booleanfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_json_agg_booleanfield_ordering) ... skipped 'PostgreSQL specific tests' test_json_agg_charfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_json_agg_charfield_ordering) ... skipped 'PostgreSQL specific tests' test_json_agg_empty (postgres_tests.test_aggregates.TestGeneralAggregate.test_json_agg_empty) ... skipped 'PostgreSQL specific tests' test_json_agg_integerfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_json_agg_integerfield_ordering) ... skipped 'PostgreSQL specific tests' test_json_agg_jsonfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_json_agg_jsonfield_ordering) ... skipped 'PostgreSQL specific tests' test_orderable_agg_alternative_fields (postgres_tests.test_aggregates.TestGeneralAggregate.test_orderable_agg_alternative_fields) ... skipped 'PostgreSQL specific tests' test_string_agg_array_agg_filter_in_subquery (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_array_agg_filter_in_subquery) ... skipped 'PostgreSQL specific tests' test_string_agg_array_agg_ordering_in_subquery (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_array_agg_ordering_in_subquery) ... skipped 'PostgreSQL specific tests' test_string_agg_charfield (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_charfield) ... skipped 'PostgreSQL specific tests' test_string_agg_charfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_charfield_ordering) ... skipped 'PostgreSQL specific tests' test_string_agg_delimiter_escaping (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_delimiter_escaping) ... skipped 'PostgreSQL specific tests' test_string_agg_empty_result (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_empty_result) ... skipped 'PostgreSQL specific tests' test_string_agg_filter (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_filter) ... skipped 'PostgreSQL specific tests' test_string_agg_filter_in_subquery_with_exclude (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_filter_in_subquery_with_exclude) ... skipped 'PostgreSQL specific tests' test_string_agg_jsonfield_ordering (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_jsonfield_ordering) ... skipped 'PostgreSQL specific tests' test_string_agg_requires_delimiter (postgres_tests.test_aggregates.TestGeneralAggregate.test_string_agg_requires_delimiter) ... skipped 'PostgreSQL specific tests' test_alias_is_required (postgres_tests.test_aggregates.TestStatisticsAggregate.test_alias_is_required) ... skipped 'PostgreSQL specific tests' test_corr_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_corr_empty_result) ... skipped 'PostgreSQL specific tests' test_corr_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_corr_general) ... skipped 'PostgreSQL specific tests' test_correct_source_expressions (postgres_tests.test_aggregates.TestStatisticsAggregate.test_correct_source_expressions) ... skipped 'PostgreSQL specific tests' test_covar_pop_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_covar_pop_empty_result) ... skipped 'PostgreSQL specific tests' test_covar_pop_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_covar_pop_general) ... skipped 'PostgreSQL specific tests' test_covar_pop_sample (postgres_tests.test_aggregates.TestStatisticsAggregate.test_covar_pop_sample) ... skipped 'PostgreSQL specific tests' test_covar_pop_sample_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_covar_pop_sample_empty_result) ... skipped 'PostgreSQL specific tests' test_missing_arguments_raises_exception (postgres_tests.test_aggregates.TestStatisticsAggregate.test_missing_arguments_raises_exception) ... skipped 'PostgreSQL specific tests' test_regr_avgx_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_avgx_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_avgx_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_avgx_general) ... skipped 'PostgreSQL specific tests' test_regr_avgx_with_related_obj_and_number_as_argument (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_avgx_with_related_obj_and_number_as_argument) This is more complex test to check if JOIN on field and ... skipped 'PostgreSQL specific tests' test_regr_avgy_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_avgy_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_avgy_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_avgy_general) ... skipped 'PostgreSQL specific tests' test_regr_count_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_count_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_count_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_count_general) ... skipped 'PostgreSQL specific tests' test_regr_intercept_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_intercept_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_intercept_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_intercept_general) ... skipped 'PostgreSQL specific tests' test_regr_r2_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_r2_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_r2_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_r2_general) ... skipped 'PostgreSQL specific tests' test_regr_slope_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_slope_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_slope_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_slope_general) ... skipped 'PostgreSQL specific tests' test_regr_sxx_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_sxx_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_sxx_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_sxx_general) ... skipped 'PostgreSQL specific tests' test_regr_sxy_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_sxy_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_sxy_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_sxy_general) ... skipped 'PostgreSQL specific tests' test_regr_syy_empty_result (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_syy_empty_result) ... skipped 'PostgreSQL specific tests' test_regr_syy_general (postgres_tests.test_aggregates.TestStatisticsAggregate.test_regr_syy_general) ... skipped 'PostgreSQL specific tests' test_register_serializer_for_migrations (postgres_tests.test_apps.PostgresConfigTests.test_register_serializer_for_migrations) ... skipped 'PostgreSQL specific tests' test_register_type_handlers_connection (postgres_tests.test_apps.PostgresConfigTests.test_register_type_handlers_connection) ... skipped 'PostgreSQL specific tests' test_exact_dates (postgres_tests.test_array.TestDateTimeExactQuerying.test_exact_dates) ... skipped 'PostgreSQL specific tests' test_exact_datetimes (postgres_tests.test_array.TestDateTimeExactQuerying.test_exact_datetimes) ... skipped 'PostgreSQL specific tests' test_exact_times (postgres_tests.test_array.TestDateTimeExactQuerying.test_exact_times) ... skipped 'PostgreSQL specific tests' test_exact_decimals (postgres_tests.test_array.TestOtherTypesExactQuerying.test_exact_decimals) ... skipped 'PostgreSQL specific tests' test_exact_ip_addresses (postgres_tests.test_array.TestOtherTypesExactQuerying.test_exact_ip_addresses) ... skipped 'PostgreSQL specific tests' test_exact_tags (postgres_tests.test_array.TestOtherTypesExactQuerying.test_exact_tags) ... skipped 'PostgreSQL specific tests' test_exact_uuids (postgres_tests.test_array.TestOtherTypesExactQuerying.test_exact_uuids) ... skipped 'PostgreSQL specific tests' test_contained_by (postgres_tests.test_array.TestQuerying.test_contained_by) ... skipped 'PostgreSQL specific tests' test_contained_by_charfield (postgres_tests.test_array.TestQuerying.test_contained_by_charfield) ... skipped 'PostgreSQL specific tests' test_contained_by_including_F_object (postgres_tests.test_array.TestQuerying.test_contained_by_including_F_object) ... skipped 'PostgreSQL specific tests' test_contains (postgres_tests.test_array.TestQuerying.test_contains) ... skipped 'PostgreSQL specific tests' test_contains_charfield (postgres_tests.test_array.TestQuerying.test_contains_charfield) ... skipped 'PostgreSQL specific tests' test_contains_including_expression (postgres_tests.test_array.TestQuerying.test_contains_including_expression) ... skipped 'PostgreSQL specific tests' test_contains_subquery (postgres_tests.test_array.TestQuerying.test_contains_subquery) ... skipped 'PostgreSQL specific tests' test_empty_list (postgres_tests.test_array.TestQuerying.test_empty_list) ... skipped 'PostgreSQL specific tests' test_enum_lookup (postgres_tests.test_array.TestQuerying.test_enum_lookup) ... skipped 'PostgreSQL specific tests' test_exact (postgres_tests.test_array.TestQuerying.test_exact) ... skipped 'PostgreSQL specific tests' test_exact_charfield (postgres_tests.test_array.TestQuerying.test_exact_charfield) ... skipped 'PostgreSQL specific tests' test_exact_nested (postgres_tests.test_array.TestQuerying.test_exact_nested) ... skipped 'PostgreSQL specific tests' test_exact_with_expression (postgres_tests.test_array.TestQuerying.test_exact_with_expression) ... skipped 'PostgreSQL specific tests' test_grouping_by_annotations_with_array_field_param (postgres_tests.test_array.TestQuerying.test_grouping_by_annotations_with_array_field_param) ... skipped 'PostgreSQL specific tests' test_gt (postgres_tests.test_array.TestQuerying.test_gt) ... skipped 'PostgreSQL specific tests' test_icontains (postgres_tests.test_array.TestQuerying.test_icontains) ... skipped 'PostgreSQL specific tests' test_in (postgres_tests.test_array.TestQuerying.test_in) ... skipped 'PostgreSQL specific tests' test_in_as_F_object (postgres_tests.test_array.TestQuerying.test_in_as_F_object) ... skipped 'PostgreSQL specific tests' test_in_including_F_object (postgres_tests.test_array.TestQuerying.test_in_including_F_object) ... skipped 'PostgreSQL specific tests' test_in_subquery (postgres_tests.test_array.TestQuerying.test_in_subquery) ... skipped 'PostgreSQL specific tests' test_index (postgres_tests.test_array.TestQuerying.test_index) ... skipped 'PostgreSQL specific tests' test_index_annotation (postgres_tests.test_array.TestQuerying.test_index_annotation) ... skipped 'PostgreSQL specific tests' test_index_chained (postgres_tests.test_array.TestQuerying.test_index_chained) ... skipped 'PostgreSQL specific tests' test_index_nested (postgres_tests.test_array.TestQuerying.test_index_nested) ... skipped 'PostgreSQL specific tests' test_index_transform_expression (postgres_tests.test_array.TestQuerying.test_index_transform_expression) ... skipped 'PostgreSQL specific tests' test_index_used_on_nested_data (postgres_tests.test_array.TestQuerying.test_index_used_on_nested_data) ... skipped 'PostgreSQL specific tests' test_isnull (postgres_tests.test_array.TestQuerying.test_isnull) ... skipped 'PostgreSQL specific tests' test_len (postgres_tests.test_array.TestQuerying.test_len) ... skipped 'PostgreSQL specific tests' test_len_empty_array (postgres_tests.test_array.TestQuerying.test_len_empty_array) ... skipped 'PostgreSQL specific tests' test_lookups_autofield_array (postgres_tests.test_array.TestQuerying.test_lookups_autofield_array) ... skipped 'PostgreSQL specific tests' test_lt (postgres_tests.test_array.TestQuerying.test_lt) ... skipped 'PostgreSQL specific tests' test_order_by_slice (postgres_tests.test_array.TestQuerying.test_order_by_slice) ... skipped 'PostgreSQL specific tests' test_overlap (postgres_tests.test_array.TestQuerying.test_overlap) ... skipped 'PostgreSQL specific tests' test_overlap_charfield (postgres_tests.test_array.TestQuerying.test_overlap_charfield) ... skipped 'PostgreSQL specific tests' test_overlap_charfield_including_expression (postgres_tests.test_array.TestQuerying.test_overlap_charfield_including_expression) ... skipped 'PostgreSQL specific tests' test_slice (postgres_tests.test_array.TestQuerying.test_slice) ... skipped 'PostgreSQL specific tests' test_slice_annotation (postgres_tests.test_array.TestQuerying.test_slice_annotation) ... skipped 'PostgreSQL specific tests' test_slice_nested (postgres_tests.test_array.TestQuerying.test_slice_nested) ... skipped 'PostgreSQL specific tests' test_slice_transform_expression (postgres_tests.test_array.TestQuerying.test_slice_transform_expression) ... skipped 'PostgreSQL specific tests' test_unsupported_lookup (postgres_tests.test_array.TestQuerying.test_unsupported_lookup) ... skipped 'PostgreSQL specific tests' test_usage_in_subquery (postgres_tests.test_array.TestQuerying.test_usage_in_subquery) ... skipped 'PostgreSQL specific tests' test_char (postgres_tests.test_array.TestSaveLoad.test_char) ... skipped 'PostgreSQL specific tests' test_dates (postgres_tests.test_array.TestSaveLoad.test_dates) ... skipped 'PostgreSQL specific tests' test_default_null (postgres_tests.test_array.TestSaveLoad.test_default_null) ... skipped 'PostgreSQL specific tests' test_integer (postgres_tests.test_array.TestSaveLoad.test_integer) ... skipped 'PostgreSQL specific tests' test_integers_passed_as_strings (postgres_tests.test_array.TestSaveLoad.test_integers_passed_as_strings) ... skipped 'PostgreSQL specific tests' test_model_set_on_base_field (postgres_tests.test_array.TestSaveLoad.test_model_set_on_base_field) ... skipped 'PostgreSQL specific tests' test_nested (postgres_tests.test_array.TestSaveLoad.test_nested) ... skipped 'PostgreSQL specific tests' test_nested_nullable_base_field (postgres_tests.test_array.TestSaveLoad.test_nested_nullable_base_field) ... skipped 'PostgreSQL specific tests' test_null_from_db_value_handling (postgres_tests.test_array.TestSaveLoad.test_null_from_db_value_handling) ... skipped 'PostgreSQL specific tests' test_null_handling (postgres_tests.test_array.TestSaveLoad.test_null_handling) ... skipped 'PostgreSQL specific tests' test_other_array_types (postgres_tests.test_array.TestSaveLoad.test_other_array_types) ... skipped 'PostgreSQL specific tests' test_tuples (postgres_tests.test_array.TestSaveLoad.test_tuples) ... skipped 'PostgreSQL specific tests' test_context_object_name (generic_views.test_detail.DetailViewTest.test_context_object_name) ... ok test_custom_detail (generic_views.test_detail.DetailViewTest.test_custom_detail) AuthorCustomDetail overrides get() and ensures that ... ok test_deferred_queryset_context_object_name (generic_views.test_detail.DetailViewTest.test_deferred_queryset_context_object_name) ... ok test_deferred_queryset_template_name (generic_views.test_detail.DetailViewTest.test_deferred_queryset_template_name) ... ok test_detail_by_custom_pk (generic_views.test_detail.DetailViewTest.test_detail_by_custom_pk) ... ok test_detail_by_custom_slug (generic_views.test_detail.DetailViewTest.test_detail_by_custom_slug) ... ok test_detail_by_pk (generic_views.test_detail.DetailViewTest.test_detail_by_pk) ... ok test_detail_by_pk_and_slug (generic_views.test_detail.DetailViewTest.test_detail_by_pk_and_slug) ... ok test_detail_by_pk_and_slug_mismatch_404 (generic_views.test_detail.DetailViewTest.test_detail_by_pk_and_slug_mismatch_404) ... ok test_detail_by_pk_ignore_slug (generic_views.test_detail.DetailViewTest.test_detail_by_pk_ignore_slug) ... ok test_detail_by_pk_ignore_slug_mismatch (generic_views.test_detail.DetailViewTest.test_detail_by_pk_ignore_slug_mismatch) ... ok test_detail_by_slug (generic_views.test_detail.DetailViewTest.test_detail_by_slug) ... ok test_detail_missing_object (generic_views.test_detail.DetailViewTest.test_detail_missing_object) ... ok test_detail_object_does_not_exist (generic_views.test_detail.DetailViewTest.test_detail_object_does_not_exist) ... ok test_duplicated_context_object_name (generic_views.test_detail.DetailViewTest.test_duplicated_context_object_name) ... ok test_invalid_queryset (generic_views.test_detail.DetailViewTest.test_invalid_queryset) ... ok test_invalid_url (generic_views.test_detail.DetailViewTest.test_invalid_url) ... ok test_non_model_object_with_meta (generic_views.test_detail.DetailViewTest.test_non_model_object_with_meta) ... ok test_simple_object (generic_views.test_detail.DetailViewTest.test_simple_object) ... ok test_template_name (generic_views.test_detail.DetailViewTest.test_template_name) ... ok test_template_name_field (generic_views.test_detail.DetailViewTest.test_template_name_field) ... ok test_template_name_suffix (generic_views.test_detail.DetailViewTest.test_template_name_suffix) ... ok test_verbose_name (generic_views.test_detail.DetailViewTest.test_verbose_name) ... ok test_bulk_update (postgres_tests.test_bulk_update.BulkSaveTests.test_bulk_update) ... skipped 'PostgreSQL specific tests' test_array_field (postgres_tests.test_citext.CITextTestCase.test_array_field) ... skipped 'PostgreSQL specific tests' test_equal_lowercase (postgres_tests.test_citext.CITextTestCase.test_equal_lowercase) citext removes the need for iexact as the index is case-insensitive. ... skipped 'PostgreSQL specific tests' test_fail_citext_primary_key (postgres_tests.test_citext.CITextTestCase.test_fail_citext_primary_key) Creating an entry for a citext field used as a primary key which ... skipped 'PostgreSQL specific tests' test_lookups_description_text (postgres_tests.test_citext.CITextTestCase.test_lookups_description_text) ... skipped 'PostgreSQL specific tests' test_lookups_email (postgres_tests.test_citext.CITextTestCase.test_lookups_email) ... skipped 'PostgreSQL specific tests' test_lookups_name_char (postgres_tests.test_citext.CITextTestCase.test_lookups_name_char) ... skipped 'PostgreSQL specific tests' test_update_get_object (generic_views.test_edit.UpdateViewTests.test_update_get_object) ... ok test_update_invalid (generic_views.test_edit.UpdateViewTests.test_update_invalid) ... ok test_update_post (generic_views.test_edit.UpdateViewTests.test_update_post) ... ok test_update_with_interpolated_redirect (generic_views.test_edit.UpdateViewTests.test_update_with_interpolated_redirect) ... ok test_update_with_object_url (generic_views.test_edit.UpdateViewTests.test_update_with_object_url) ... ok test_update_with_redirect (generic_views.test_edit.UpdateViewTests.test_update_with_redirect) ... ok test_update_with_special_properties (generic_views.test_edit.UpdateViewTests.test_update_with_special_properties) ... ok test_update_without_redirect (generic_views.test_edit.UpdateViewTests.test_update_without_redirect) ... ok test_deconstruct (postgres_tests.test_constraints.ExclusionConstraintTests.test_deconstruct) ... skipped 'PostgreSQL specific tests' test_deconstruct_condition (postgres_tests.test_constraints.ExclusionConstraintTests.test_deconstruct_condition) ... skipped 'PostgreSQL specific tests' test_deconstruct_deferrable (postgres_tests.test_constraints.ExclusionConstraintTests.test_deconstruct_deferrable) ... skipped 'PostgreSQL specific tests' test_deconstruct_include (postgres_tests.test_constraints.ExclusionConstraintTests.test_deconstruct_include) ... skipped 'PostgreSQL specific tests' test_deconstruct_index_type (postgres_tests.test_constraints.ExclusionConstraintTests.test_deconstruct_index_type) ... skipped 'PostgreSQL specific tests' test_deconstruct_opclasses (postgres_tests.test_constraints.ExclusionConstraintTests.test_deconstruct_opclasses) ... skipped 'PostgreSQL specific tests' test_deferrable_with_condition (postgres_tests.test_constraints.ExclusionConstraintTests.test_deferrable_with_condition) ... skipped 'PostgreSQL specific tests' test_empty_expressions (postgres_tests.test_constraints.ExclusionConstraintTests.test_empty_expressions) ... skipped 'PostgreSQL specific tests' test_eq (postgres_tests.test_constraints.ExclusionConstraintTests.test_eq) ... skipped 'PostgreSQL specific tests' test_expressions_with_key_transform (postgres_tests.test_constraints.ExclusionConstraintTests.test_expressions_with_key_transform) ... skipped 'PostgreSQL specific tests' test_expressions_with_params (postgres_tests.test_constraints.ExclusionConstraintTests.test_expressions_with_params) ... skipped 'PostgreSQL specific tests' test_include_not_supported (postgres_tests.test_constraints.ExclusionConstraintTests.test_include_not_supported) ... skipped 'PostgreSQL specific tests' test_invalid_condition (postgres_tests.test_constraints.ExclusionConstraintTests.test_invalid_condition) ... skipped 'PostgreSQL specific tests' test_invalid_deferrable (postgres_tests.test_constraints.ExclusionConstraintTests.test_invalid_deferrable) ... skipped 'PostgreSQL specific tests' test_invalid_expressions (postgres_tests.test_constraints.ExclusionConstraintTests.test_invalid_expressions) ... skipped 'PostgreSQL specific tests' test_invalid_include_index_type (postgres_tests.test_constraints.ExclusionConstraintTests.test_invalid_include_index_type) ... skipped 'PostgreSQL specific tests' test_invalid_include_type (postgres_tests.test_constraints.ExclusionConstraintTests.test_invalid_include_type) ... skipped 'PostgreSQL specific tests' test_invalid_index_type (postgres_tests.test_constraints.ExclusionConstraintTests.test_invalid_index_type) ... skipped 'PostgreSQL specific tests' test_invalid_opclasses_type (postgres_tests.test_constraints.ExclusionConstraintTests.test_invalid_opclasses_type) ... skipped 'PostgreSQL specific tests' test_opclasses_and_expressions_same_length (postgres_tests.test_constraints.ExclusionConstraintTests.test_opclasses_and_expressions_same_length) ... skipped 'PostgreSQL specific tests' test_range_adjacent (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent) ... skipped 'PostgreSQL specific tests' test_range_adjacent_include (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent_include) ... skipped 'PostgreSQL specific tests' test_range_adjacent_include_condition (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent_include_condition) ... skipped 'PostgreSQL specific tests' test_range_adjacent_include_deferrable (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent_include_deferrable) ... skipped 'PostgreSQL specific tests' test_range_adjacent_initially_deferred (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent_initially_deferred) ... skipped 'PostgreSQL specific tests' test_range_adjacent_opclasses (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent_opclasses) ... skipped 'PostgreSQL specific tests' test_range_adjacent_opclasses_condition (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent_opclasses_condition) ... skipped 'PostgreSQL specific tests' test_range_adjacent_opclasses_deferrable (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent_opclasses_deferrable) ... skipped 'PostgreSQL specific tests' test_range_adjacent_opclasses_include (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_adjacent_opclasses_include) ... skipped 'PostgreSQL specific tests' test_range_equal_cast (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_equal_cast) ... skipped 'PostgreSQL specific tests' test_range_overlaps (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_overlaps) ... skipped 'PostgreSQL specific tests' test_range_overlaps_custom (postgres_tests.test_constraints.ExclusionConstraintTests.test_range_overlaps_custom) ... skipped 'PostgreSQL specific tests' test_repr (postgres_tests.test_constraints.ExclusionConstraintTests.test_repr) ... skipped 'PostgreSQL specific tests' test_check_constraint_daterange_contains (postgres_tests.test_constraints.SchemaTests.test_check_constraint_daterange_contains) ... skipped 'PostgreSQL specific tests' test_check_constraint_datetimerange_contains (postgres_tests.test_constraints.SchemaTests.test_check_constraint_datetimerange_contains) ... skipped 'PostgreSQL specific tests' test_check_constraint_range_value (postgres_tests.test_constraints.SchemaTests.test_check_constraint_range_value) ... skipped 'PostgreSQL specific tests' test_opclass (postgres_tests.test_constraints.SchemaTests.test_opclass) ... skipped 'PostgreSQL specific tests' test_opclass_include (postgres_tests.test_constraints.SchemaTests.test_opclass_include) ... skipped 'PostgreSQL specific tests' test_opclass_multiple_columns (postgres_tests.test_constraints.SchemaTests.test_opclass_multiple_columns) ... skipped 'PostgreSQL specific tests' test_opclass_partial (postgres_tests.test_constraints.SchemaTests.test_opclass_partial) ... skipped 'PostgreSQL specific tests' test_random_uuid (postgres_tests.test_functions.TestRandomUUID.test_random_uuid) ... skipped 'PostgreSQL specific tests' test_transaction_now (postgres_tests.test_functions.TestTransactionNow.test_transaction_now) The test case puts everything under a transaction, so two models ... skipped 'PostgreSQL specific tests' test_array_field (postgres_tests.test_hstore.SimpleTests.test_array_field) ... skipped 'PostgreSQL specific tests' test_key_val_cast_to_string (postgres_tests.test_hstore.SimpleTests.test_key_val_cast_to_string) ... skipped 'PostgreSQL specific tests' test_null (postgres_tests.test_hstore.SimpleTests.test_null) ... skipped 'PostgreSQL specific tests' test_save_load_success (postgres_tests.test_hstore.SimpleTests.test_save_load_success) ... skipped 'PostgreSQL specific tests' test_value_null (postgres_tests.test_hstore.SimpleTests.test_value_null) ... skipped 'PostgreSQL specific tests' test_contained_by (postgres_tests.test_hstore.TestQuerying.test_contained_by) ... skipped 'PostgreSQL specific tests' test_contains (postgres_tests.test_hstore.TestQuerying.test_contains) ... skipped 'PostgreSQL specific tests' test_exact (postgres_tests.test_hstore.TestQuerying.test_exact) ... skipped 'PostgreSQL specific tests' test_field_chaining (postgres_tests.test_hstore.TestQuerying.test_field_chaining) ... skipped 'PostgreSQL specific tests' test_has_any_keys (postgres_tests.test_hstore.TestQuerying.test_has_any_keys) ... skipped 'PostgreSQL specific tests' test_has_key (postgres_tests.test_hstore.TestQuerying.test_has_key) ... skipped 'PostgreSQL specific tests' test_has_keys (postgres_tests.test_hstore.TestQuerying.test_has_keys) ... skipped 'PostgreSQL specific tests' test_in_generator (postgres_tests.test_hstore.TestQuerying.test_in_generator) ... skipped 'PostgreSQL specific tests' test_key_isnull (postgres_tests.test_hstore.TestQuerying.test_key_isnull) ... skipped 'PostgreSQL specific tests' test_key_sql_injection (postgres_tests.test_hstore.TestQuerying.test_key_sql_injection) ... skipped 'PostgreSQL specific tests' test_key_transform (postgres_tests.test_hstore.TestQuerying.test_key_transform) ... skipped 'PostgreSQL specific tests' test_key_transform_annotation (postgres_tests.test_hstore.TestQuerying.test_key_transform_annotation) ... skipped 'PostgreSQL specific tests' test_key_transform_raw_expression (postgres_tests.test_hstore.TestQuerying.test_key_transform_raw_expression) ... skipped 'PostgreSQL specific tests' test_keys (postgres_tests.test_hstore.TestQuerying.test_keys) ... skipped 'PostgreSQL specific tests' test_keys_contains (postgres_tests.test_hstore.TestQuerying.test_keys_contains) ... skipped 'PostgreSQL specific tests' test_obj_subquery_lookup (postgres_tests.test_hstore.TestQuerying.test_obj_subquery_lookup) ... skipped 'PostgreSQL specific tests' test_order_by_field (postgres_tests.test_hstore.TestQuerying.test_order_by_field) ... skipped 'PostgreSQL specific tests' test_usage_in_subquery (postgres_tests.test_hstore.TestQuerying.test_usage_in_subquery) ... skipped 'PostgreSQL specific tests' test_values (postgres_tests.test_hstore.TestQuerying.test_values) ... skipped 'PostgreSQL specific tests' test_values_overlap (postgres_tests.test_hstore.TestQuerying.test_values_overlap) ... skipped 'PostgreSQL specific tests' test_bloom_index (postgres_tests.test_indexes.SchemaTests.test_bloom_index) ... skipped 'PostgreSQL specific tests' test_bloom_parameters (postgres_tests.test_indexes.SchemaTests.test_bloom_parameters) ... skipped 'PostgreSQL specific tests' test_brin_autosummarize_not_supported (postgres_tests.test_indexes.SchemaTests.test_brin_autosummarize_not_supported) ... skipped 'PostgreSQL specific tests' test_brin_index (postgres_tests.test_indexes.SchemaTests.test_brin_index) ... skipped 'PostgreSQL specific tests' test_brin_parameters (postgres_tests.test_indexes.SchemaTests.test_brin_parameters) ... skipped 'PostgreSQL specific tests' test_btree_index (postgres_tests.test_indexes.SchemaTests.test_btree_index) ... skipped 'PostgreSQL specific tests' test_btree_parameters (postgres_tests.test_indexes.SchemaTests.test_btree_parameters) ... skipped 'PostgreSQL specific tests' test_cast_search_vector_gin_index (postgres_tests.test_indexes.SchemaTests.test_cast_search_vector_gin_index) ... skipped 'PostgreSQL specific tests' test_gin_fastupdate (postgres_tests.test_indexes.SchemaTests.test_gin_fastupdate) ... skipped 'PostgreSQL specific tests' test_gin_index (postgres_tests.test_indexes.SchemaTests.test_gin_index) ... skipped 'PostgreSQL specific tests' test_gin_parameters (postgres_tests.test_indexes.SchemaTests.test_gin_parameters) ... skipped 'PostgreSQL specific tests' test_gist_include (postgres_tests.test_indexes.SchemaTests.test_gist_include) ... skipped 'PostgreSQL specific tests' test_gist_include_not_supported (postgres_tests.test_indexes.SchemaTests.test_gist_include_not_supported) ... skipped 'PostgreSQL specific tests' test_gist_index (postgres_tests.test_indexes.SchemaTests.test_gist_index) ... skipped 'PostgreSQL specific tests' test_gist_parameters (postgres_tests.test_indexes.SchemaTests.test_gist_parameters) ... skipped 'PostgreSQL specific tests' test_hash_index (postgres_tests.test_indexes.SchemaTests.test_hash_index) ... skipped 'PostgreSQL specific tests' test_hash_parameters (postgres_tests.test_indexes.SchemaTests.test_hash_parameters) ... skipped 'PostgreSQL specific tests' test_op_class (postgres_tests.test_indexes.SchemaTests.test_op_class) ... skipped 'PostgreSQL specific tests' test_op_class_descending_collation (postgres_tests.test_indexes.SchemaTests.test_op_class_descending_collation) ... skipped 'PostgreSQL specific tests' test_op_class_descending_partial (postgres_tests.test_indexes.SchemaTests.test_op_class_descending_partial) ... skipped 'PostgreSQL specific tests' test_op_class_descending_partial_tablespace (postgres_tests.test_indexes.SchemaTests.test_op_class_descending_partial_tablespace) ... skipped 'PostgreSQL specific tests' test_partial_gin_index (postgres_tests.test_indexes.SchemaTests.test_partial_gin_index) ... skipped 'PostgreSQL specific tests' test_partial_gin_index_with_tablespace (postgres_tests.test_indexes.SchemaTests.test_partial_gin_index_with_tablespace) ... skipped 'PostgreSQL specific tests' test_spgist_index (postgres_tests.test_indexes.SchemaTests.test_spgist_index) ... skipped 'PostgreSQL specific tests' test_spgist_parameters (postgres_tests.test_indexes.SchemaTests.test_spgist_parameters) ... skipped 'PostgreSQL specific tests' test_trigram_op_class_gin_index (postgres_tests.test_indexes.SchemaTests.test_trigram_op_class_gin_index) ... skipped 'PostgreSQL specific tests' test_tsvector_op_class_gist_index (postgres_tests.test_indexes.SchemaTests.test_tsvector_op_class_gist_index) ... skipped 'PostgreSQL specific tests' test_range_fields (postgres_tests.test_introspection.InspectDBTests.test_range_fields) ... skipped 'PostgreSQL specific tests' test_collation_with_icu_provider_raises_error (postgres_tests.test_operations.CreateCollationTests.test_collation_with_icu_provider_raises_error) ... skipped 'PostgreSQL specific tests.' test_create (postgres_tests.test_operations.CreateCollationTests.test_create) ... skipped 'PostgreSQL specific tests.' test_create_collation_alternate_provider (postgres_tests.test_operations.CreateCollationTests.test_create_collation_alternate_provider) ... skipped 'PostgreSQL specific tests.' test_create_non_deterministic_collation (postgres_tests.test_operations.CreateCollationTests.test_create_non_deterministic_collation) ... skipped 'PostgreSQL specific tests.' test_no_allow_migrate (postgres_tests.test_operations.CreateCollationTests.test_no_allow_migrate) ... skipped 'PostgreSQL specific tests.' test_nondeterministic_collation_not_supported (postgres_tests.test_operations.CreateCollationTests.test_nondeterministic_collation_not_supported) ... skipped 'PostgreSQL specific tests.' test_allow_migrate (postgres_tests.test_operations.CreateExtensionTests.test_allow_migrate) ... skipped 'PostgreSQL specific tests.' test_create_existing_extension (postgres_tests.test_operations.CreateExtensionTests.test_create_existing_extension) ... skipped 'PostgreSQL specific tests.' test_drop_nonexistent_extension (postgres_tests.test_operations.CreateExtensionTests.test_drop_nonexistent_extension) ... skipped 'PostgreSQL specific tests.' test_no_allow_migrate (postgres_tests.test_operations.CreateExtensionTests.test_no_allow_migrate) ... skipped 'PostgreSQL specific tests.' test_no_allow_migrate (postgres_tests.test_operations.RemoveCollationTests.test_no_allow_migrate) ... skipped 'PostgreSQL specific tests.' test_remove (postgres_tests.test_operations.RemoveCollationTests.test_remove) ... skipped 'PostgreSQL specific tests.' test_adjacent_to (postgres_tests.test_ranges.TestQuerying.test_adjacent_to) ... skipped 'PostgreSQL specific tests' test_bound_type (postgres_tests.test_ranges.TestQuerying.test_bound_type) ... skipped 'PostgreSQL specific tests' test_contained_by (postgres_tests.test_ranges.TestQuerying.test_contained_by) ... skipped 'PostgreSQL specific tests' test_contains (postgres_tests.test_ranges.TestQuerying.test_contains) ... skipped 'PostgreSQL specific tests' test_contains_range (postgres_tests.test_ranges.TestQuerying.test_contains_range) ... skipped 'PostgreSQL specific tests' test_endswith (postgres_tests.test_ranges.TestQuerying.test_endswith) ... skipped 'PostgreSQL specific tests' test_exact (postgres_tests.test_ranges.TestQuerying.test_exact) ... skipped 'PostgreSQL specific tests' test_fully_gt (postgres_tests.test_ranges.TestQuerying.test_fully_gt) ... skipped 'PostgreSQL specific tests' test_fully_lt (postgres_tests.test_ranges.TestQuerying.test_fully_lt) ... skipped 'PostgreSQL specific tests' test_isempty (postgres_tests.test_ranges.TestQuerying.test_isempty) ... skipped 'PostgreSQL specific tests' test_isnull (postgres_tests.test_ranges.TestQuerying.test_isnull) ... skipped 'PostgreSQL specific tests' test_not_gt (postgres_tests.test_ranges.TestQuerying.test_not_gt) ... skipped 'PostgreSQL specific tests' test_not_lt (postgres_tests.test_ranges.TestQuerying.test_not_lt) ... skipped 'PostgreSQL specific tests' test_overlap (postgres_tests.test_ranges.TestQuerying.test_overlap) ... skipped 'PostgreSQL specific tests' test_startswith (postgres_tests.test_ranges.TestQuerying.test_startswith) ... skipped 'PostgreSQL specific tests' test_startswith_chaining (postgres_tests.test_ranges.TestQuerying.test_startswith_chaining) ... skipped 'PostgreSQL specific tests' test_date_range_contains (postgres_tests.test_ranges.TestRangeContainsLookup.test_date_range_contains) ... skipped 'PostgreSQL specific tests' test_datetime_range_contains (postgres_tests.test_ranges.TestRangeContainsLookup.test_datetime_range_contains) ... skipped 'PostgreSQL specific tests' test_auto_field_contained_by (postgres_tests.test_ranges.TestQueryingWithRanges.test_auto_field_contained_by) ... skipped 'PostgreSQL specific tests' test_big_auto_field_contained_by (postgres_tests.test_ranges.TestQueryingWithRanges.test_big_auto_field_contained_by) ... skipped 'PostgreSQL specific tests' test_biginteger_range (postgres_tests.test_ranges.TestQueryingWithRanges.test_biginteger_range) ... skipped 'PostgreSQL specific tests' test_date_range (postgres_tests.test_ranges.TestQueryingWithRanges.test_date_range) ... skipped 'PostgreSQL specific tests' test_date_range_datetime_field (postgres_tests.test_ranges.TestQueryingWithRanges.test_date_range_datetime_field) ... skipped 'PostgreSQL specific tests' test_datetime_range (postgres_tests.test_ranges.TestQueryingWithRanges.test_datetime_range) ... skipped 'PostgreSQL specific tests' test_decimal_field_contained_by (postgres_tests.test_ranges.TestQueryingWithRanges.test_decimal_field_contained_by) ... skipped 'PostgreSQL specific tests' test_exclude (postgres_tests.test_ranges.TestQueryingWithRanges.test_exclude) ... skipped 'PostgreSQL specific tests' test_f_ranges (postgres_tests.test_ranges.TestQueryingWithRanges.test_f_ranges) ... skipped 'PostgreSQL specific tests' test_float_range (postgres_tests.test_ranges.TestQueryingWithRanges.test_float_range) ... skipped 'PostgreSQL specific tests' test_integer_range (postgres_tests.test_ranges.TestQueryingWithRanges.test_integer_range) ... skipped 'PostgreSQL specific tests' test_small_auto_field_contained_by (postgres_tests.test_ranges.TestQueryingWithRanges.test_small_auto_field_contained_by) ... skipped 'PostgreSQL specific tests' test_small_integer_field_contained_by (postgres_tests.test_ranges.TestQueryingWithRanges.test_small_integer_field_contained_by) ... skipped 'PostgreSQL specific tests' test_all_fields (postgres_tests.test_ranges.TestSaveLoad.test_all_fields) ... skipped 'PostgreSQL specific tests' test_empty (postgres_tests.test_ranges.TestSaveLoad.test_empty) ... skipped 'PostgreSQL specific tests' test_model_set_on_base_field (postgres_tests.test_ranges.TestSaveLoad.test_model_set_on_base_field) ... skipped 'PostgreSQL specific tests' test_null (postgres_tests.test_ranges.TestSaveLoad.test_null) ... skipped 'PostgreSQL specific tests' test_range_object (postgres_tests.test_ranges.TestSaveLoad.test_range_object) ... skipped 'PostgreSQL specific tests' test_range_object_boundaries (postgres_tests.test_ranges.TestSaveLoad.test_range_object_boundaries) ... skipped 'PostgreSQL specific tests' test_tuple (postgres_tests.test_ranges.TestSaveLoad.test_tuple) ... skipped 'PostgreSQL specific tests' test_unbounded (postgres_tests.test_ranges.TestSaveLoad.test_unbounded) ... skipped 'PostgreSQL specific tests' test_bad_search_type (postgres_tests.test_search.MultipleFieldsTest.test_bad_search_type) ... skipped 'PostgreSQL specific tests' test_config_from_field_explicit (postgres_tests.test_search.MultipleFieldsTest.test_config_from_field_explicit) ... skipped 'PostgreSQL specific tests' test_config_from_field_implicit (postgres_tests.test_search.MultipleFieldsTest.test_config_from_field_implicit) ... skipped 'PostgreSQL specific tests' test_config_query_explicit (postgres_tests.test_search.MultipleFieldsTest.test_config_query_explicit) ... skipped 'PostgreSQL specific tests' test_config_query_implicit (postgres_tests.test_search.MultipleFieldsTest.test_config_query_implicit) ... skipped 'PostgreSQL specific tests' test_non_exact_match (postgres_tests.test_search.MultipleFieldsTest.test_non_exact_match) ... skipped 'PostgreSQL specific tests' test_phrase_search (postgres_tests.test_search.MultipleFieldsTest.test_phrase_search) ... skipped 'PostgreSQL specific tests' test_phrase_search_with_config (postgres_tests.test_search.MultipleFieldsTest.test_phrase_search_with_config) ... skipped 'PostgreSQL specific tests' test_raw_search (postgres_tests.test_search.MultipleFieldsTest.test_raw_search) ... skipped 'PostgreSQL specific tests' test_raw_search_with_config (postgres_tests.test_search.MultipleFieldsTest.test_raw_search_with_config) ... skipped 'PostgreSQL specific tests' test_search_two_terms (postgres_tests.test_search.MultipleFieldsTest.test_search_two_terms) ... skipped 'PostgreSQL specific tests' test_search_with_non_text (postgres_tests.test_search.MultipleFieldsTest.test_search_with_non_text) ... skipped 'PostgreSQL specific tests' test_search_with_null (postgres_tests.test_search.MultipleFieldsTest.test_search_with_null) ... skipped 'PostgreSQL specific tests' test_simple_on_dialogue (postgres_tests.test_search.MultipleFieldsTest.test_simple_on_dialogue) ... skipped 'PostgreSQL specific tests' test_simple_on_scene (postgres_tests.test_search.MultipleFieldsTest.test_simple_on_scene) ... skipped 'PostgreSQL specific tests' test_terms_adjacent (postgres_tests.test_search.MultipleFieldsTest.test_terms_adjacent) ... skipped 'PostgreSQL specific tests' test_web_search (postgres_tests.test_search.MultipleFieldsTest.test_web_search) ... skipped 'PostgreSQL specific tests' test_web_search_with_config (postgres_tests.test_search.MultipleFieldsTest.test_web_search_with_config) ... skipped 'PostgreSQL specific tests' test_headline (postgres_tests.test_search.SearchHeadlineTests.test_headline) ... skipped 'PostgreSQL specific tests' test_headline_fragments_words_options (postgres_tests.test_search.SearchHeadlineTests.test_headline_fragments_words_options) ... skipped 'PostgreSQL specific tests' test_headline_highlight_all_option (postgres_tests.test_search.SearchHeadlineTests.test_headline_highlight_all_option) ... skipped 'PostgreSQL specific tests' test_headline_separator_options (postgres_tests.test_search.SearchHeadlineTests.test_headline_separator_options) ... skipped 'PostgreSQL specific tests' test_headline_short_word_option (postgres_tests.test_search.SearchHeadlineTests.test_headline_short_word_option) ... skipped 'PostgreSQL specific tests' test_headline_untyped_args (postgres_tests.test_search.SearchHeadlineTests.test_headline_untyped_args) ... skipped 'PostgreSQL specific tests' test_headline_with_config (postgres_tests.test_search.SearchHeadlineTests.test_headline_with_config) ... skipped 'PostgreSQL specific tests' test_headline_with_config_from_field (postgres_tests.test_search.SearchHeadlineTests.test_headline_with_config_from_field) ... skipped 'PostgreSQL specific tests' test_search_vector_index (postgres_tests.test_search.SearchVectorIndexTests.test_search_vector_index) SearchVector generates IMMUTABLE SQL in order to be indexable. ... skipped 'PostgreSQL specific tests' test_non_exact_match (postgres_tests.test_search.SimpleSearchTest.test_non_exact_match) ... skipped 'PostgreSQL specific tests' test_search_query_config (postgres_tests.test_search.SimpleSearchTest.test_search_query_config) ... skipped 'PostgreSQL specific tests' test_search_two_terms (postgres_tests.test_search.SimpleSearchTest.test_search_two_terms) ... skipped 'PostgreSQL specific tests' test_search_two_terms_with_partial_match (postgres_tests.test_search.SimpleSearchTest.test_search_two_terms_with_partial_match) ... skipped 'PostgreSQL specific tests' test_search_with_F_expression (postgres_tests.test_search.SimpleSearchTest.test_search_with_F_expression) ... skipped 'PostgreSQL specific tests' test_simple (postgres_tests.test_search.SimpleSearchTest.test_simple) ... skipped 'PostgreSQL specific tests' test_existing_vector (postgres_tests.test_search.SearchVectorFieldTest.test_existing_vector) ... skipped 'PostgreSQL specific tests' test_existing_vector_config_explicit (postgres_tests.test_search.SearchVectorFieldTest.test_existing_vector_config_explicit) ... skipped 'PostgreSQL specific tests' test_single_coalesce_expression (postgres_tests.test_search.SearchVectorFieldTest.test_single_coalesce_expression) ... skipped 'PostgreSQL specific tests' test_cover_density_ranking (postgres_tests.test_search.TestRankingAndWeights.test_cover_density_ranking) ... skipped 'PostgreSQL specific tests' test_rank_passing_untyped_args (postgres_tests.test_search.TestRankingAndWeights.test_rank_passing_untyped_args) ... skipped 'PostgreSQL specific tests' test_ranked_custom_weights (postgres_tests.test_search.TestRankingAndWeights.test_ranked_custom_weights) ... skipped 'PostgreSQL specific tests' test_ranking (postgres_tests.test_search.TestRankingAndWeights.test_ranking) ... skipped 'PostgreSQL specific tests' test_ranking_chaining (postgres_tests.test_search.TestRankingAndWeights.test_ranking_chaining) ... skipped 'PostgreSQL specific tests' test_ranking_with_masked_normalization (postgres_tests.test_search.TestRankingAndWeights.test_ranking_with_masked_normalization) ... skipped 'PostgreSQL specific tests' test_ranking_with_normalization (postgres_tests.test_search.TestRankingAndWeights.test_ranking_with_normalization) ... skipped 'PostgreSQL specific tests' test_weights_in_vector (postgres_tests.test_search.TestRankingAndWeights.test_weights_in_vector) ... skipped 'PostgreSQL specific tests' test_combine_different_configs (postgres_tests.test_search.TestCombinations.test_combine_different_configs) ... skipped 'PostgreSQL specific tests' test_combine_different_vector_configs (postgres_tests.test_search.TestCombinations.test_combine_different_vector_configs) ... skipped 'PostgreSQL specific tests' test_combine_raw_phrase (postgres_tests.test_search.TestCombinations.test_combine_raw_phrase) ... skipped 'PostgreSQL specific tests' test_combined_configs (postgres_tests.test_search.TestCombinations.test_combined_configs) ... skipped 'PostgreSQL specific tests' test_query_and (postgres_tests.test_search.TestCombinations.test_query_and) ... skipped 'PostgreSQL specific tests' test_query_combined_mismatch (postgres_tests.test_search.TestCombinations.test_query_combined_mismatch) ... skipped 'PostgreSQL specific tests' test_query_invert (postgres_tests.test_search.TestCombinations.test_query_invert) ... skipped 'PostgreSQL specific tests' test_query_multiple_and (postgres_tests.test_search.TestCombinations.test_query_multiple_and) ... skipped 'PostgreSQL specific tests' test_query_multiple_or (postgres_tests.test_search.TestCombinations.test_query_multiple_or) ... skipped 'PostgreSQL specific tests' test_query_or (postgres_tests.test_search.TestCombinations.test_query_or) ... skipped 'PostgreSQL specific tests' test_vector_add (postgres_tests.test_search.TestCombinations.test_vector_add) ... skipped 'PostgreSQL specific tests' test_vector_add_multi (postgres_tests.test_search.TestCombinations.test_vector_add_multi) ... skipped 'PostgreSQL specific tests' test_vector_combined_mismatch (postgres_tests.test_search.TestCombinations.test_vector_combined_mismatch) ... skipped 'PostgreSQL specific tests' test_citext_cache (postgres_tests.test_signals.OIDTests.test_citext_cache) ... skipped 'PostgreSQL specific tests' test_citext_values (postgres_tests.test_signals.OIDTests.test_citext_values) ... skipped 'PostgreSQL specific tests' test_hstore_cache (postgres_tests.test_signals.OIDTests.test_hstore_cache) ... skipped 'PostgreSQL specific tests' test_hstore_values (postgres_tests.test_signals.OIDTests.test_hstore_values) ... skipped 'PostgreSQL specific tests' test_register_type_handlers_no_db (postgres_tests.test_signals.OIDTests.test_register_type_handlers_no_db) Registering type handlers for the nodb connection does nothing. ... skipped 'PostgreSQL specific tests' test_trigram_search (postgres_tests.test_trigram.TrigramTextFieldTest.test_trigram_search) ... skipped 'PostgreSQL specific tests' test_trigram_similarity (postgres_tests.test_trigram.TrigramTextFieldTest.test_trigram_similarity) ... skipped 'PostgreSQL specific tests' test_trigram_similarity_alternate (postgres_tests.test_trigram.TrigramTextFieldTest.test_trigram_similarity_alternate) ... skipped 'PostgreSQL specific tests' test_trigram_search (postgres_tests.test_trigram.TrigramTest.test_trigram_search) ... skipped 'PostgreSQL specific tests' test_trigram_similarity (postgres_tests.test_trigram.TrigramTest.test_trigram_similarity) ... skipped 'PostgreSQL specific tests' test_trigram_similarity_alternate (postgres_tests.test_trigram.TrigramTest.test_trigram_similarity_alternate) ... skipped 'PostgreSQL specific tests' test_unaccent (postgres_tests.test_unaccent.UnaccentTest.test_unaccent) ... skipped 'PostgreSQL specific tests' test_unaccent_accentuated_needle (postgres_tests.test_unaccent.UnaccentTest.test_unaccent_accentuated_needle) ... skipped 'PostgreSQL specific tests' test_unaccent_chained (postgres_tests.test_unaccent.UnaccentTest.test_unaccent_chained) Unaccent can be used chained with a lookup (which should be the case ... skipped 'PostgreSQL specific tests' test_unaccent_with_conforming_strings_off (postgres_tests.test_unaccent.UnaccentTest.test_unaccent_with_conforming_strings_off) SQL is valid when standard_conforming_strings is off. ... skipped 'PostgreSQL specific tests' test_unaccent (postgres_tests.test_unaccent.UnaccentTextFieldTest.test_unaccent) ... skipped 'PostgreSQL specific tests' test_unaccent_accentuated_needle (postgres_tests.test_unaccent.UnaccentTextFieldTest.test_unaccent_accentuated_needle) ... skipped 'PostgreSQL specific tests' test_unaccent_chained (postgres_tests.test_unaccent.UnaccentTextFieldTest.test_unaccent_chained) Unaccent can be used chained with a lookup (which should be the case ... skipped 'PostgreSQL specific tests' test_unaccent_with_conforming_strings_off (postgres_tests.test_unaccent.UnaccentTextFieldTest.test_unaccent_with_conforming_strings_off) SQL is valid when standard_conforming_strings is off. ... skipped 'PostgreSQL specific tests' test_value_to_string (contenttypes_tests.test_fields.GenericRelationTests.test_value_to_string) ... ok test_multidb (contenttypes_tests.test_models.ContentTypesMultidbTests.test_multidb) When using multiple databases, ContentType.objects.get_for_model() uses ... ok test_change_ordering (contenttypes_tests.test_order_with_respect_to.OrderWithRespectToGFKTests.test_change_ordering) ... ok test_default_to_insertion_order (contenttypes_tests.test_order_with_respect_to.OrderWithRespectToGFKTests.test_default_to_insertion_order) ... ok test_delete_and_insert (contenttypes_tests.test_order_with_respect_to.OrderWithRespectToGFKTests.test_delete_and_insert) ... ok test_item_ordering (contenttypes_tests.test_order_with_respect_to.OrderWithRespectToGFKTests.test_item_ordering) ... ok test_previous_and_next_in_order (contenttypes_tests.test_order_with_respect_to.OrderWithRespectToGFKTests.test_previous_and_next_in_order) ... ok test_recursive_ordering (contenttypes_tests.test_order_with_respect_to.OrderWithRespectToGFKTests.test_recursive_ordering) ... ok test_set_order_unrelated_object (contenttypes_tests.test_order_with_respect_to.OrderWithRespectToGFKTests.test_set_order_unrelated_object) An answer that's not related isn't updated. ... ok test_allow_empty_false (generic_views.test_list.ListViewTests.test_allow_empty_false) ... ok test_context_object_name (generic_views.test_list.ListViewTests.test_context_object_name) ... ok test_duplicate_context_object_name (generic_views.test_list.ListViewTests.test_duplicate_context_object_name) ... ok test_explicitly_ordered_list_view (generic_views.test_list.ListViewTests.test_explicitly_ordered_list_view) ... ok test_invalid_get_queryset (generic_views.test_list.ListViewTests.test_invalid_get_queryset) ... ok test_items (generic_views.test_list.ListViewTests.test_items) ... ok test_missing_items (generic_views.test_list.ListViewTests.test_missing_items) ... ok test_paginated_custom_page_kwarg (generic_views.test_list.ListViewTests.test_paginated_custom_page_kwarg) ... ok test_paginated_custom_paginator_class (generic_views.test_list.ListViewTests.test_paginated_custom_paginator_class) ... ok test_paginated_custom_paginator_constructor (generic_views.test_list.ListViewTests.test_paginated_custom_paginator_constructor) ... ok test_paginated_get_last_page_by_query_string (generic_views.test_list.ListViewTests.test_paginated_get_last_page_by_query_string) ... ok test_paginated_get_page_by_query_string (generic_views.test_list.ListViewTests.test_paginated_get_page_by_query_string) ... ok test_paginated_get_page_by_urlvar (generic_views.test_list.ListViewTests.test_paginated_get_page_by_urlvar) ... ok test_paginated_invalid_page (generic_views.test_list.ListViewTests.test_paginated_invalid_page) ... ok test_paginated_list_view_does_not_load_entire_table (generic_views.test_list.ListViewTests.test_paginated_list_view_does_not_load_entire_table) ... ok test_paginated_list_view_returns_useful_message_on_invalid_page (generic_views.test_list.ListViewTests.test_paginated_list_view_returns_useful_message_on_invalid_page) ... ok test_paginated_non_queryset (generic_views.test_list.ListViewTests.test_paginated_non_queryset) ... ok test_paginated_orphaned_queryset (generic_views.test_list.ListViewTests.test_paginated_orphaned_queryset) ... ok test_paginated_page_out_of_range (generic_views.test_list.ListViewTests.test_paginated_page_out_of_range) ... ok test_paginated_queryset (generic_views.test_list.ListViewTests.test_paginated_queryset) ... ok test_paginated_queryset_shortdata (generic_views.test_list.ListViewTests.test_paginated_queryset_shortdata) ... ok test_queryset (generic_views.test_list.ListViewTests.test_queryset) ... ok test_template_name (generic_views.test_list.ListViewTests.test_template_name) ... ok test_template_name_suffix (generic_views.test_list.ListViewTests.test_template_name_suffix) ... ok test_verbose_name (generic_views.test_list.ListViewTests.test_verbose_name) ... ok test_shortcut_view_with_null_site_fk (contenttypes_tests.test_views.ContentTypesViewsSiteRelTests.test_shortcut_view_with_null_site_fk) The shortcut view works if a model's ForeignKey to site is None. ... ok test_shortcut_view_with_site_m2m (contenttypes_tests.test_views.ContentTypesViewsSiteRelTests.test_shortcut_view_with_site_m2m) When the object has a ManyToManyField to Site, redirect to the current ... ok test_model_with_broken_get_absolute_url (contenttypes_tests.test_views.ShortcutViewTests.test_model_with_broken_get_absolute_url) The view doesn't catch an AttributeError raised by ... ok test_model_without_get_absolute_url (contenttypes_tests.test_views.ShortcutViewTests.test_model_without_get_absolute_url) The view returns 404 when Model.get_absolute_url() isn't defined. ... ok test_not_dependent_on_sites_app (contenttypes_tests.test_views.ShortcutViewTests.test_not_dependent_on_sites_app) The view returns a complete URL regardless of whether the sites ... ok test_contenttypes_removed_for_apps_not_in_installed_apps (contenttypes_tests.test_management.RemoveStaleContentTypesTests.test_contenttypes_removed_for_apps_not_in_installed_apps) ... ok test_contenttypes_removed_in_installed_apps_without_models (contenttypes_tests.test_management.RemoveStaleContentTypesTests.test_contenttypes_removed_in_installed_apps_without_models) ... ok test_interactive_false (contenttypes_tests.test_management.RemoveStaleContentTypesTests.test_interactive_false) non-interactive mode deletes stale content types. ... ok test_interactive_true_with_dependent_objects (contenttypes_tests.test_management.RemoveStaleContentTypesTests.test_interactive_true_with_dependent_objects) interactive mode (the default) deletes stale content types and warns of ... ok test_interactive_true_without_dependent_objects (contenttypes_tests.test_management.RemoveStaleContentTypesTests.test_interactive_true_without_dependent_objects) interactive mode deletes stale content types even if there aren't any ... ok test_unavailable_content_type_model (contenttypes_tests.test_management.RemoveStaleContentTypesTests.test_unavailable_content_type_model) A ContentType isn't created if the model isn't available. ... ok test_bad_content_type (contenttypes_tests.test_views.ContentTypesViewsTests.test_bad_content_type) ... ok test_nonint_content_type (contenttypes_tests.test_views.ContentTypesViewsTests.test_nonint_content_type) ... ok test_shortcut_bad_pk (contenttypes_tests.test_views.ContentTypesViewsTests.test_shortcut_bad_pk) ... ok test_shortcut_no_absolute_url (contenttypes_tests.test_views.ContentTypesViewsTests.test_shortcut_no_absolute_url) Shortcuts for an object that has no get_absolute_url() method raise ... ok test_shortcut_with_absolute_url (contenttypes_tests.test_views.ContentTypesViewsTests.test_shortcut_with_absolute_url) Can view a shortcut for an Author object that has a get_absolute_url method ... ok test_shortcut_with_absolute_url_including_scheme (contenttypes_tests.test_views.ContentTypesViewsTests.test_shortcut_with_absolute_url_including_scheme) Can view a shortcut when object's get_absolute_url returns a full URL ... ok test_wrong_type_pk (contenttypes_tests.test_views.ContentTypesViewsTests.test_wrong_type_pk) ... ok test_decorators (signals.tests.SignalTests.test_decorators) ... ok test_delete_signals (signals.tests.SignalTests.test_delete_signals) ... ok test_disconnect_in_dispatch (signals.tests.SignalTests.test_disconnect_in_dispatch) Signals that disconnect when being called don't mess future ... ok test_lazy_model_signal (signals.tests.SignalTests.test_lazy_model_signal) ... ok test_model_pre_init_and_post_init (signals.tests.SignalTests.test_model_pre_init_and_post_init) ... ok test_save_and_delete_signals_with_m2m (signals.tests.SignalTests.test_save_and_delete_signals_with_m2m) ... ok test_save_signals (signals.tests.SignalTests.test_save_signals) ... ok test_multi_table_inheritance (select_related_regress.tests.SelectRelatedRegressTests.test_multi_table_inheritance) Exercising select_related() with multi-table model inheritance. ... ok test_null_join_promotion (select_related_regress.tests.SelectRelatedRegressTests.test_null_join_promotion) ... ok test_regression_10733 (select_related_regress.tests.SelectRelatedRegressTests.test_regression_10733) ... ok test_regression_12851 (select_related_regress.tests.SelectRelatedRegressTests.test_regression_12851) Regression for #12851 ... ok test_regression_19870 (select_related_regress.tests.SelectRelatedRegressTests.test_regression_19870) ... ok test_regression_22508 (select_related_regress.tests.SelectRelatedRegressTests.test_regression_22508) ... ok test_regression_7110 (select_related_regress.tests.SelectRelatedRegressTests.test_regression_7110) Regression test for bug #7110. ... ok test_regression_8036 (select_related_regress.tests.SelectRelatedRegressTests.test_regression_8036) Regression test for bug #8036 ... ok test_regression_8106 (select_related_regress.tests.SelectRelatedRegressTests.test_regression_8106) Regression test for bug #8106. ... ok test_custom_valid_name_callable_upload_to (file_storage.tests.FileFieldStorageTests.test_custom_valid_name_callable_upload_to) Storage.get_valid_name() should be called when upload_to is a callable. ... ok test_duplicate_filename (file_storage.tests.FileFieldStorageTests.test_duplicate_filename) ... ok test_empty_upload_to (file_storage.tests.FileFieldStorageTests.test_empty_upload_to) ... ok test_extended_length_storage (file_storage.tests.FileFieldStorageTests.test_extended_length_storage) ... ok test_file_object (file_storage.tests.FileFieldStorageTests.test_file_object) ... ok test_file_truncation (file_storage.tests.FileFieldStorageTests.test_file_truncation) ... ok test_filefield_default (file_storage.tests.FileFieldStorageTests.test_filefield_default) ... ok test_filefield_pickling (file_storage.tests.FileFieldStorageTests.test_filefield_pickling) ... ok test_filefield_read (file_storage.tests.FileFieldStorageTests.test_filefield_read) ... ok test_filefield_reopen (file_storage.tests.FileFieldStorageTests.test_filefield_reopen) ... ok test_filefield_write (file_storage.tests.FileFieldStorageTests.test_filefield_write) ... ok test_files (file_storage.tests.FileFieldStorageTests.test_files) ... ok test_pathlib_upload_to (file_storage.tests.FileFieldStorageTests.test_pathlib_upload_to) ... ok test_random_upload_to (file_storage.tests.FileFieldStorageTests.test_random_upload_to) ... ok test_stringio (file_storage.tests.FileFieldStorageTests.test_stringio) ... ok test_fallback_flatpage (flatpages_tests.test_csrf.FlatpageCSRFTests.test_fallback_flatpage) A flatpage can be served by the fallback middleware ... ok test_fallback_non_existent_flatpage (flatpages_tests.test_csrf.FlatpageCSRFTests.test_fallback_non_existent_flatpage) A nonexistent flatpage raises a 404 when served by the fallback ... ok test_post_fallback_flatpage (flatpages_tests.test_csrf.FlatpageCSRFTests.test_post_fallback_flatpage) POSTing to a flatpage served by the middleware will raise a CSRF error if no token is provided (Refs #14156) ... ok test_post_unknown_page (flatpages_tests.test_csrf.FlatpageCSRFTests.test_post_unknown_page) POSTing to an unknown page isn't caught as a 403 CSRF error ... ok test_post_view_flatpage (flatpages_tests.test_csrf.FlatpageCSRFTests.test_post_view_flatpage) POSTing to a flatpage served through a view will raise a CSRF error if no token is provided (Refs #14156) ... ok test_view_authenticated_flatpage (flatpages_tests.test_csrf.FlatpageCSRFTests.test_view_authenticated_flatpage) A flatpage served through a view can require authentication ... ok test_view_flatpage (flatpages_tests.test_csrf.FlatpageCSRFTests.test_view_flatpage) A flatpage can be served through a view, even when the middleware is in use ... ok test_view_non_existent_flatpage (flatpages_tests.test_csrf.FlatpageCSRFTests.test_view_non_existent_flatpage) A nonexistent flatpage raises 404 when served through a view, even when ... ok test_flatpage_admin_form_edit (flatpages_tests.test_forms.FlatpageAdminFormTests.test_flatpage_admin_form_edit) Existing flatpages can be edited in the admin form without triggering ... ok test_flatpage_admin_form_url_uniqueness_validation (flatpages_tests.test_forms.FlatpageAdminFormTests.test_flatpage_admin_form_url_uniqueness_validation) The flatpage admin form correctly enforces url uniqueness among flatpages of the same site ... ok test_flatpage_admin_form_url_validation (flatpages_tests.test_forms.FlatpageAdminFormTests.test_flatpage_admin_form_url_validation) The flatpage admin form correctly validates urls ... ok test_flatpage_doesnt_requires_trailing_slash_without_append_slash (flatpages_tests.test_forms.FlatpageAdminFormTests.test_flatpage_doesnt_requires_trailing_slash_without_append_slash) ... ok test_flatpage_nosites (flatpages_tests.test_forms.FlatpageAdminFormTests.test_flatpage_nosites) ... ok test_flatpage_requires_leading_slash (flatpages_tests.test_forms.FlatpageAdminFormTests.test_flatpage_requires_leading_slash) ... ok test_flatpage_requires_trailing_slash_with_append_slash (flatpages_tests.test_forms.FlatpageAdminFormTests.test_flatpage_requires_trailing_slash_with_append_slash) ... ok test_redirect_fallback_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareAppendSlashTests.test_redirect_fallback_flatpage) A flatpage can be served by the fallback middleware and should add a slash ... ok test_redirect_fallback_flatpage_root (flatpages_tests.test_middleware.FlatpageMiddlewareAppendSlashTests.test_redirect_fallback_flatpage_root) A flatpage at / should not cause a redirect loop when APPEND_SLASH is set ... ok test_redirect_fallback_flatpage_special_chars (flatpages_tests.test_middleware.FlatpageMiddlewareAppendSlashTests.test_redirect_fallback_flatpage_special_chars) A flatpage with special chars in the URL can be served by the fallback middleware and should add a slash ... ok test_redirect_fallback_non_existent_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareAppendSlashTests.test_redirect_fallback_non_existent_flatpage) A nonexistent flatpage raises a 404 when served by the fallback ... ok test_redirect_view_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareAppendSlashTests.test_redirect_view_flatpage) A flatpage can be served through a view and should add a slash ... ok test_redirect_view_non_existent_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareAppendSlashTests.test_redirect_view_non_existent_flatpage) A nonexistent flatpage raises 404 when served through a view and ... ok test_flatpage_sitemap (flatpages_tests.test_sitemaps.FlatpagesSitemapTests.test_flatpage_sitemap) ... ok test_fallback_authenticated_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareTests.test_fallback_authenticated_flatpage) A flatpage served by the middleware can require authentication ... ok test_fallback_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareTests.test_fallback_flatpage) A flatpage can be served by the fallback middleware ... ok test_fallback_flatpage_special_chars (flatpages_tests.test_middleware.FlatpageMiddlewareTests.test_fallback_flatpage_special_chars) A flatpage with special chars in the URL can be served by the fallback middleware ... ok test_fallback_non_existent_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareTests.test_fallback_non_existent_flatpage) A nonexistent flatpage raises a 404 when served by the fallback ... ok test_view_authenticated_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareTests.test_view_authenticated_flatpage) A flatpage served through a view can require authentication ... ok test_view_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareTests.test_view_flatpage) A flatpage can be served through a view, even when the middleware is in use ... ok test_view_non_existent_flatpage (flatpages_tests.test_middleware.FlatpageMiddlewareTests.test_view_non_existent_flatpage) A nonexistent flatpage raises 404 when served through a view, even when ... ok test_get_flatpages_tag (flatpages_tests.test_templatetags.FlatpageTemplateTagTests.test_get_flatpages_tag) The flatpage template tag retrieves unregistered prefixed flatpages by default ... ok test_get_flatpages_tag_for_anon_user (flatpages_tests.test_templatetags.FlatpageTemplateTagTests.test_get_flatpages_tag_for_anon_user) The flatpage template tag retrieves unregistered flatpages for an anonymous user ... ok test_get_flatpages_tag_for_user (flatpages_tests.test_templatetags.FlatpageTemplateTagTests.test_get_flatpages_tag_for_user) The flatpage template tag retrieves all flatpages for an authenticated user ... ok test_get_flatpages_with_prefix (flatpages_tests.test_templatetags.FlatpageTemplateTagTests.test_get_flatpages_with_prefix) The flatpage template tag retrieves unregistered prefixed flatpages by default ... ok test_get_flatpages_with_prefix_for_anon_user (flatpages_tests.test_templatetags.FlatpageTemplateTagTests.test_get_flatpages_with_prefix_for_anon_user) The flatpage template tag retrieves unregistered prefixed flatpages for an anonymous user ... ok test_get_flatpages_with_prefix_for_user (flatpages_tests.test_templatetags.FlatpageTemplateTagTests.test_get_flatpages_with_prefix_for_user) The flatpage template tag retrieve prefixed flatpages for an authenticated user ... ok test_get_flatpages_with_variable_prefix (flatpages_tests.test_templatetags.FlatpageTemplateTagTests.test_get_flatpages_with_variable_prefix) The prefix for the flatpage template tag can be a template variable ... ok test_parsing_errors (flatpages_tests.test_templatetags.FlatpageTemplateTagTests.test_parsing_errors) There are various ways that the flatpages template tag won't parse ... ok test_app_labeled_name (contenttypes_tests.test_models.ContentTypesTests.test_app_labeled_name) ... ok test_app_labeled_name_unknown_model (contenttypes_tests.test_models.ContentTypesTests.test_app_labeled_name_unknown_model) ... ok test_cache_not_shared_between_managers (contenttypes_tests.test_models.ContentTypesTests.test_cache_not_shared_between_managers) ... ok test_get_for_concrete_model (contenttypes_tests.test_models.ContentTypesTests.test_get_for_concrete_model) Make sure the `for_concrete_model` kwarg correctly works ... ok test_get_for_concrete_models (contenttypes_tests.test_models.ContentTypesTests.test_get_for_concrete_models) Make sure the `for_concrete_models` kwarg correctly works ... ok test_get_for_model_create_contenttype (contenttypes_tests.test_models.ContentTypesTests.test_get_for_model_create_contenttype) ContentTypeManager.get_for_model() creates the corresponding content ... ok test_get_for_models_creation (contenttypes_tests.test_models.ContentTypesTests.test_get_for_models_creation) ... ok test_get_for_models_empty_cache (contenttypes_tests.test_models.ContentTypesTests.test_get_for_models_empty_cache) ... ok test_get_for_models_full_cache (contenttypes_tests.test_models.ContentTypesTests.test_get_for_models_full_cache) ... ok test_get_for_models_partial_cache (contenttypes_tests.test_models.ContentTypesTests.test_get_for_models_partial_cache) ... ok test_lookup_cache (contenttypes_tests.test_models.ContentTypesTests.test_lookup_cache) The content type cache (see ContentTypeManager) works correctly. ... ok test_missing_model (contenttypes_tests.test_models.ContentTypesTests.test_missing_model) Displaying content types in admin (or anywhere) doesn't break on ... ok test_str (contenttypes_tests.test_models.ContentTypesTests.test_str) ... ok test_redirect_fallback_flatpage (flatpages_tests.test_views.FlatpageViewAppendSlashTests.test_redirect_fallback_flatpage) A fallback flatpage won't be served if the middleware is disabled and should not add a slash ... ok test_redirect_fallback_non_existent_flatpage (flatpages_tests.test_views.FlatpageViewAppendSlashTests.test_redirect_fallback_non_existent_flatpage) A nonexistent flatpage won't be served if the fallback middleware is ... ok test_redirect_view_flatpage (flatpages_tests.test_views.FlatpageViewAppendSlashTests.test_redirect_view_flatpage) A flatpage can be served through a view and should add a slash ... ok test_redirect_view_flatpage_special_chars (flatpages_tests.test_views.FlatpageViewAppendSlashTests.test_redirect_view_flatpage_special_chars) A flatpage with special chars in the URL can be served through a view and should add a slash ... ok test_redirect_view_non_existent_flatpage (flatpages_tests.test_views.FlatpageViewAppendSlashTests.test_redirect_view_non_existent_flatpage) A nonexistent flatpage raises 404 when served through a view and ... ok test_dependency_sorting_m2m_complex (fixtures_regress.tests.M2MNaturalKeyFixtureTests.test_dependency_sorting_m2m_complex) M2M relations with explicit through models should NOT count as ... ok test_dependency_sorting_m2m_complex_circular_1 (fixtures_regress.tests.M2MNaturalKeyFixtureTests.test_dependency_sorting_m2m_complex_circular_1) Circular M2M relations with explicit through models should be serializable ... ok test_dependency_sorting_m2m_complex_circular_2 (fixtures_regress.tests.M2MNaturalKeyFixtureTests.test_dependency_sorting_m2m_complex_circular_2) Circular M2M relations with explicit through models should be serializable ... ok test_dependency_sorting_m2m_simple (fixtures_regress.tests.M2MNaturalKeyFixtureTests.test_dependency_sorting_m2m_simple) M2M relations without explicit through models SHOULD count as dependencies ... ok test_dependency_sorting_m2m_simple_circular (fixtures_regress.tests.M2MNaturalKeyFixtureTests.test_dependency_sorting_m2m_simple_circular) Resolving circular M2M relations without explicit through models should ... ok test_dump_and_load_m2m_simple (fixtures_regress.tests.M2MNaturalKeyFixtureTests.test_dump_and_load_m2m_simple) Test serializing and deserializing back models with simple M2M relations ... ok test_fallback_flatpage (flatpages_tests.test_views.FlatpageViewTests.test_fallback_flatpage) A fallback flatpage won't be served if the middleware is disabled ... ok test_fallback_non_existent_flatpage (flatpages_tests.test_views.FlatpageViewTests.test_fallback_non_existent_flatpage) A nonexistent flatpage won't be served if the fallback middleware is ... ok test_view_authenticated_flatpage (flatpages_tests.test_views.FlatpageViewTests.test_view_authenticated_flatpage) A flatpage served through a view can require authentication ... ok test_view_flatpage (flatpages_tests.test_views.FlatpageViewTests.test_view_flatpage) A flatpage can be served through a view ... ok test_view_flatpage_special_chars (flatpages_tests.test_views.FlatpageViewTests.test_view_flatpage_special_chars) A flatpage with special chars in the URL can be served through a view ... ok test_view_non_existent_flatpage (flatpages_tests.test_views.FlatpageViewTests.test_view_non_existent_flatpage) A nonexistent flatpage raises 404 when served through a view. ... ok test_fixtures_loaded (fixtures_regress.tests.TestLoadFixtureFromOtherAppDirectory.test_fixtures_loaded) ... ok test_ipaddress_on_postgresql (string_lookup.tests.StringLookupTests.test_ipaddress_on_postgresql) Regression test for #708 ... ok test_queries_on_textfields (string_lookup.tests.StringLookupTests.test_queries_on_textfields) Regression tests for #5087 ... ok test_string_form_referencing (string_lookup.tests.StringLookupTests.test_string_form_referencing) Regression test for #1661 and #1662 ... ok test_unicode_chars_in_queries (string_lookup.tests.StringLookupTests.test_unicode_chars_in_queries) Regression tests for #3937 ... ok test_15776 (delete_regress.tests.DeleteCascadeTests.test_15776) ... ok test_fk_to_m2m_through (delete_regress.tests.DeleteCascadeTests.test_fk_to_m2m_through) If an M2M relationship has an explicitly-specified through model, and ... ok test_generic_relation_cascade (delete_regress.tests.DeleteCascadeTests.test_generic_relation_cascade) Django cascades deletes through generic-related objects to their ... ok test_foreign_key_delete_nullifies_correct_columns (delete_regress.tests.DeleteTests.test_foreign_key_delete_nullifies_correct_columns) With a model (Researcher) that has two foreign keys pointing to the ... ok test_meta_ordered_delete (delete_regress.tests.DeleteTests.test_meta_ordered_delete) ... ok test_self_reference_with_through_m2m_at_second_level (delete_regress.tests.DeleteTests.test_self_reference_with_through_m2m_at_second_level) ... ok test_large_deletes (delete_regress.tests.LargeDeleteTests.test_large_deletes) Regression for #13309 -- if the number of objects > chunk size, deletion still occurs ... ok test_dependency_self_referential (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_self_referential) ... ok test_dependency_sorting (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting) It doesn't matter what order you mention the models, Store *must* be ... ok test_dependency_sorting_2 (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_2) ... ok test_dependency_sorting_3 (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_3) ... ok test_dependency_sorting_4 (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_4) ... ok test_dependency_sorting_5 (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_5) ... ok test_dependency_sorting_6 (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_6) ... ok test_dependency_sorting_dangling (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_dangling) ... ok test_dependency_sorting_long (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_long) ... ok test_dependency_sorting_normal (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_normal) ... ok test_dependency_sorting_tight_circular (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_tight_circular) ... ok test_dependency_sorting_tight_circular_2 (fixtures_regress.tests.NaturalKeyFixtureTests.test_dependency_sorting_tight_circular_2) ... ok test_nk_deserialize (fixtures_regress.tests.NaturalKeyFixtureTests.test_nk_deserialize) Test for ticket #13030 - Python based parser version ... ok test_nk_deserialize_xml (fixtures_regress.tests.NaturalKeyFixtureTests.test_nk_deserialize_xml) Test for ticket #13030 - XML version ... ok test_nk_on_serialize (fixtures_regress.tests.NaturalKeyFixtureTests.test_nk_on_serialize) Natural key requirements are taken into account when serializing models. ... ok test_normal_pk (fixtures_regress.tests.NaturalKeyFixtureTests.test_normal_pk) Normal primary keys work on a model with natural key capabilities. ... ok test_ticket_19102_annotate (delete_regress.tests.Ticket19102Tests.test_ticket_19102_annotate) ... ok test_ticket_19102_defer (delete_regress.tests.Ticket19102Tests.test_ticket_19102_defer) ... ok test_ticket_19102_extra (delete_regress.tests.Ticket19102Tests.test_ticket_19102_extra) ... ok test_ticket_19102_select_related (delete_regress.tests.Ticket19102Tests.test_ticket_19102_select_related) ... ok test_19187_values (delete_regress.tests.ProxyDeleteTest.test_19187_values) ... ok test_delete_concrete_parent (delete_regress.tests.ProxyDeleteTest.test_delete_concrete_parent) Deleting an instance of a concrete model should also delete objects ... ok test_delete_proxy (delete_regress.tests.ProxyDeleteTest.test_delete_proxy) Deleting the *proxy* instance bubbles through to its non-proxy and ... ok test_delete_proxy_of_proxy (delete_regress.tests.ProxyDeleteTest.test_delete_proxy_of_proxy) Deleting a proxy-of-proxy instance should bubble through to its proxy ... ok test_delete_proxy_pair (delete_regress.tests.ProxyDeleteTest.test_delete_proxy_pair) If a pair of proxy models are linked by an FK from one concrete parent ... ok test_absolute_path (fixtures_regress.tests.TestFixtures.test_absolute_path) Regression test for ticket #6436 -- ... ok test_close_connection_after_loaddata (fixtures_regress.tests.TestFixtures.test_close_connection_after_loaddata) Test for ticket #7572 -- MySQL has a problem if the same connection is ... ok test_dumpdata_uses_default_manager (fixtures_regress.tests.TestFixtures.test_dumpdata_uses_default_manager) Regression for #11286 ... ok test_duplicate_pk (fixtures_regress.tests.TestFixtures.test_duplicate_pk) This is a regression test for ticket #3790. ... ok test_empty (fixtures_regress.tests.TestFixtures.test_empty) Test for ticket #18213 -- Loading a fixture file with no data output a warning. ... ok test_error_message (fixtures_regress.tests.TestFixtures.test_error_message) Regression for #9011 - error message is correct. ... ok test_field_value_coerce (fixtures_regress.tests.TestFixtures.test_field_value_coerce) Test for tickets #8298, #9942 - Field values should be coerced into the ... ok test_fixture_dirs_with_default_fixture_path (fixtures_regress.tests.TestFixtures.test_fixture_dirs_with_default_fixture_path) settings.FIXTURE_DIRS cannot contain a default fixtures directory ... ok test_fixture_dirs_with_duplicates (fixtures_regress.tests.TestFixtures.test_fixture_dirs_with_duplicates) settings.FIXTURE_DIRS cannot contain duplicates in order to avoid ... ok test_fixtures_dir_pathlib (fixtures_regress.tests.TestFixtures.test_fixtures_dir_pathlib) ... ok test_invalid_data (fixtures_regress.tests.TestFixtures.test_invalid_data) Test for ticket #4371 -- Loading a fixture file with invalid data ... ok test_invalid_data_no_ext (fixtures_regress.tests.TestFixtures.test_invalid_data_no_ext) Test for ticket #4371 -- Loading a fixture file with invalid data ... ok test_loaddata_forward_refs_split_fixtures (fixtures_regress.tests.TestFixtures.test_loaddata_forward_refs_split_fixtures) Regression for #17530 - should be able to cope with forward references ... ok test_loaddata_no_fixture_specified (fixtures_regress.tests.TestFixtures.test_loaddata_no_fixture_specified) Regression for #7043 - Error is quickly reported when no fixtures is provided in the command line. ... ok test_loaddata_not_found_fields_ignore (fixtures_regress.tests.TestFixtures.test_loaddata_not_found_fields_ignore) Test for ticket #9279 -- Ignores entries in ... ok test_loaddata_not_found_fields_ignore_xml (fixtures_regress.tests.TestFixtures.test_loaddata_not_found_fields_ignore_xml) Test for ticket #19998 -- Ignore entries in the XML serialized data ... ok test_loaddata_not_found_fields_not_ignore (fixtures_regress.tests.TestFixtures.test_loaddata_not_found_fields_not_ignore) Test for ticket #9279 -- Error is raised for entries in ... ok test_loaddata_raises_error_when_fixture_has_invalid_foreign_key (fixtures_regress.tests.TestFixtures.test_loaddata_raises_error_when_fixture_has_invalid_foreign_key) Regression for #3615 - Ensure data with nonexistent child key references raises error ... ok test_loaddata_with_m2m_to_self (fixtures_regress.tests.TestFixtures.test_loaddata_with_m2m_to_self) Regression test for ticket #17946. ... ok test_loaddata_with_valid_fixture_dirs (fixtures_regress.tests.TestFixtures.test_loaddata_with_valid_fixture_dirs) ... ok test_loaddata_works_when_fixture_has_forward_refs (fixtures_regress.tests.TestFixtures.test_loaddata_works_when_fixture_has_forward_refs) Regression for #3615 - Forward references cause fixtures not to load in MySQL (InnoDB) ... ok test_path_containing_dots (fixtures_regress.tests.TestFixtures.test_path_containing_dots) ... ok test_pg_sequence_resetting_checks (fixtures_regress.tests.TestFixtures.test_pg_sequence_resetting_checks) Test for ticket #7565 -- PostgreSQL sequence resetting checks shouldn't ... ok test_pretty_print_xml (fixtures_regress.tests.TestFixtures.test_pretty_print_xml) Regression test for ticket #4558 -- pretty printing of XML fixtures ... ok test_pretty_print_xml_empty_strings (fixtures_regress.tests.TestFixtures.test_pretty_print_xml_empty_strings) Regression test for ticket #4558 -- pretty printing of XML fixtures ... skipped "Database doesn't support feature(s): interprets_empty_strings_as_nulls" test_proxy_model_included (fixtures_regress.tests.TestFixtures.test_proxy_model_included) Regression for #11428 - Proxy models aren't included when you dumpdata ... ok test_relative_path (fixtures_regress.tests.TestFixtures.test_relative_path) ... ok test_relative_path_in_fixture_dirs (fixtures_regress.tests.TestFixtures.test_relative_path_in_fixture_dirs) ... ok test_ticket_20820 (fixtures_regress.tests.TestFixtures.test_ticket_20820) Regression for ticket #20820 -- loaddata on a model that inherits ... ok test_ticket_22421 (fixtures_regress.tests.TestFixtures.test_ticket_22421) Regression for ticket #22421 -- loaddata on a model that inherits from ... ok test_unimportable_serializer (fixtures_regress.tests.TestFixtures.test_unimportable_serializer) Failing serializer import raises the proper error ... ok test_unknown_format (fixtures_regress.tests.TestFixtures.test_unknown_format) Test for ticket #4371 -- Loading data of an unknown format should fail ... ok test_actual_expiry (sessions_tests.tests.CacheDBSessionTests.test_actual_expiry) ... ok test_clear (sessions_tests.tests.CacheDBSessionTests.test_clear) ... ok test_custom_expiry_datetime (sessions_tests.tests.CacheDBSessionTests.test_custom_expiry_datetime) ... ok test_custom_expiry_reset (sessions_tests.tests.CacheDBSessionTests.test_custom_expiry_reset) ... ok test_custom_expiry_seconds (sessions_tests.tests.CacheDBSessionTests.test_custom_expiry_seconds) ... ok test_custom_expiry_timedelta (sessions_tests.tests.CacheDBSessionTests.test_custom_expiry_timedelta) ... ok test_cycle (sessions_tests.tests.CacheDBSessionTests.test_cycle) ... ok test_cycle_with_no_session_cache (sessions_tests.tests.CacheDBSessionTests.test_cycle_with_no_session_cache) ... ok test_decode (sessions_tests.tests.CacheDBSessionTests.test_decode) ... ok test_decode_failure_logged_to_security (sessions_tests.tests.CacheDBSessionTests.test_decode_failure_logged_to_security) ... ok test_decode_legacy (sessions_tests.tests.CacheDBSessionTests.test_decode_legacy) ... ok test_default_expiry (sessions_tests.tests.CacheDBSessionTests.test_default_expiry) ... ok test_default_hashing_algorith_legacy_decode (sessions_tests.tests.CacheDBSessionTests.test_default_hashing_algorith_legacy_decode) ... ok test_delete (sessions_tests.tests.CacheDBSessionTests.test_delete) ... ok test_exists_searches_cache_first (sessions_tests.tests.CacheDBSessionTests.test_exists_searches_cache_first) ... ok test_flush (sessions_tests.tests.CacheDBSessionTests.test_flush) ... ok test_get_empty (sessions_tests.tests.CacheDBSessionTests.test_get_empty) ... ok test_get_expire_at_browser_close (sessions_tests.tests.CacheDBSessionTests.test_get_expire_at_browser_close) ... ok test_has_key (sessions_tests.tests.CacheDBSessionTests.test_has_key) ... ok test_invalid_key (sessions_tests.tests.CacheDBSessionTests.test_invalid_key) ... ok test_items (sessions_tests.tests.CacheDBSessionTests.test_items) ... ok test_keys (sessions_tests.tests.CacheDBSessionTests.test_keys) ... ok test_load_overlong_key (sessions_tests.tests.CacheDBSessionTests.test_load_overlong_key) ... ok test_new_session (sessions_tests.tests.CacheDBSessionTests.test_new_session) ... ok test_non_default_cache (sessions_tests.tests.CacheDBSessionTests.test_non_default_cache) ... ok test_pop (sessions_tests.tests.CacheDBSessionTests.test_pop) ... ok test_pop_default (sessions_tests.tests.CacheDBSessionTests.test_pop_default) ... ok test_pop_default_named_argument (sessions_tests.tests.CacheDBSessionTests.test_pop_default_named_argument) ... ok test_pop_no_default_keyerror_raised (sessions_tests.tests.CacheDBSessionTests.test_pop_no_default_keyerror_raised) ... ok test_save (sessions_tests.tests.CacheDBSessionTests.test_save) ... ok test_save_doesnt_clear_data (sessions_tests.tests.CacheDBSessionTests.test_save_doesnt_clear_data) ... ok test_session_key_empty_string_invalid (sessions_tests.tests.CacheDBSessionTests.test_session_key_empty_string_invalid) Falsey values (Such as an empty string) are rejected. ... ok test_session_key_is_read_only (sessions_tests.tests.CacheDBSessionTests.test_session_key_is_read_only) ... ok test_session_key_too_short_invalid (sessions_tests.tests.CacheDBSessionTests.test_session_key_too_short_invalid) Strings shorter than 8 characters are rejected. ... ok test_session_key_valid_string_saved (sessions_tests.tests.CacheDBSessionTests.test_session_key_valid_string_saved) Strings of length 8 and up are accepted and stored. ... ok test_session_load_does_not_create_record (sessions_tests.tests.CacheDBSessionTests.test_session_load_does_not_create_record) Loading an unknown session key does not create a session record. ... ok test_session_save_does_not_resurrect_session_logged_out_in_other_context (sessions_tests.tests.CacheDBSessionTests.test_session_save_does_not_resurrect_session_logged_out_in_other_context) Sessions shouldn't be resurrected by a concurrent request. ... ok test_setdefault (sessions_tests.tests.CacheDBSessionTests.test_setdefault) ... ok test_store (sessions_tests.tests.CacheDBSessionTests.test_store) ... ok test_update (sessions_tests.tests.CacheDBSessionTests.test_update) ... ok test_values (sessions_tests.tests.CacheDBSessionTests.test_values) ... ok test_actual_expiry (sessions_tests.tests.CustomDatabaseSessionTests.test_actual_expiry) ... ok test_clear (sessions_tests.tests.CustomDatabaseSessionTests.test_clear) ... ok test_clearsessions_command (sessions_tests.tests.CustomDatabaseSessionTests.test_clearsessions_command) Test clearsessions command for clearing expired sessions. ... ok test_custom_expiry_datetime (sessions_tests.tests.CustomDatabaseSessionTests.test_custom_expiry_datetime) ... ok test_custom_expiry_reset (sessions_tests.tests.CustomDatabaseSessionTests.test_custom_expiry_reset) ... ok test_custom_expiry_seconds (sessions_tests.tests.CustomDatabaseSessionTests.test_custom_expiry_seconds) ... ok test_custom_expiry_timedelta (sessions_tests.tests.CustomDatabaseSessionTests.test_custom_expiry_timedelta) ... ok test_cycle (sessions_tests.tests.CustomDatabaseSessionTests.test_cycle) ... ok test_cycle_with_no_session_cache (sessions_tests.tests.CustomDatabaseSessionTests.test_cycle_with_no_session_cache) ... ok test_decode (sessions_tests.tests.CustomDatabaseSessionTests.test_decode) ... ok test_decode_failure_logged_to_security (sessions_tests.tests.CustomDatabaseSessionTests.test_decode_failure_logged_to_security) ... ok test_decode_legacy (sessions_tests.tests.CustomDatabaseSessionTests.test_decode_legacy) ... ok test_default_expiry (sessions_tests.tests.CustomDatabaseSessionTests.test_default_expiry) ... ok test_default_hashing_algorith_legacy_decode (sessions_tests.tests.CustomDatabaseSessionTests.test_default_hashing_algorith_legacy_decode) ... ok test_delete (sessions_tests.tests.CustomDatabaseSessionTests.test_delete) ... ok test_extra_session_field (sessions_tests.tests.CustomDatabaseSessionTests.test_extra_session_field) ... ok test_flush (sessions_tests.tests.CustomDatabaseSessionTests.test_flush) ... ok test_get_empty (sessions_tests.tests.CustomDatabaseSessionTests.test_get_empty) ... ok test_get_expire_at_browser_close (sessions_tests.tests.CustomDatabaseSessionTests.test_get_expire_at_browser_close) ... ok test_has_key (sessions_tests.tests.CustomDatabaseSessionTests.test_has_key) ... ok test_invalid_key (sessions_tests.tests.CustomDatabaseSessionTests.test_invalid_key) ... ok test_items (sessions_tests.tests.CustomDatabaseSessionTests.test_items) ... ok test_keys (sessions_tests.tests.CustomDatabaseSessionTests.test_keys) ... ok test_new_session (sessions_tests.tests.CustomDatabaseSessionTests.test_new_session) ... ok test_pop (sessions_tests.tests.CustomDatabaseSessionTests.test_pop) ... ok test_pop_default (sessions_tests.tests.CustomDatabaseSessionTests.test_pop_default) ... ok test_pop_default_named_argument (sessions_tests.tests.CustomDatabaseSessionTests.test_pop_default_named_argument) ... ok test_pop_no_default_keyerror_raised (sessions_tests.tests.CustomDatabaseSessionTests.test_pop_no_default_keyerror_raised) ... ok test_save (sessions_tests.tests.CustomDatabaseSessionTests.test_save) ... ok test_save_doesnt_clear_data (sessions_tests.tests.CustomDatabaseSessionTests.test_save_doesnt_clear_data) ... ok test_session_get_decoded (sessions_tests.tests.CustomDatabaseSessionTests.test_session_get_decoded) Test we can use Session.get_decoded to retrieve data stored ... ok test_session_key_empty_string_invalid (sessions_tests.tests.CustomDatabaseSessionTests.test_session_key_empty_string_invalid) Falsey values (Such as an empty string) are rejected. ... ok test_session_key_is_read_only (sessions_tests.tests.CustomDatabaseSessionTests.test_session_key_is_read_only) ... ok test_session_key_too_short_invalid (sessions_tests.tests.CustomDatabaseSessionTests.test_session_key_too_short_invalid) Strings shorter than 8 characters are rejected. ... ok test_session_key_valid_string_saved (sessions_tests.tests.CustomDatabaseSessionTests.test_session_key_valid_string_saved) Strings of length 8 and up are accepted and stored. ... ok test_session_load_does_not_create_record (sessions_tests.tests.CustomDatabaseSessionTests.test_session_load_does_not_create_record) Loading an unknown session key does not create a session record. ... ok test_session_save_does_not_resurrect_session_logged_out_in_other_context (sessions_tests.tests.CustomDatabaseSessionTests.test_session_save_does_not_resurrect_session_logged_out_in_other_context) Sessions shouldn't be resurrected by a concurrent request. ... ok test_session_str (sessions_tests.tests.CustomDatabaseSessionTests.test_session_str) Session repr should be the session key. ... ok test_sessionmanager_save (sessions_tests.tests.CustomDatabaseSessionTests.test_sessionmanager_save) Test SessionManager.save method ... ok test_setdefault (sessions_tests.tests.CustomDatabaseSessionTests.test_setdefault) ... ok test_store (sessions_tests.tests.CustomDatabaseSessionTests.test_store) ... ok test_update (sessions_tests.tests.CustomDatabaseSessionTests.test_update) ... ok test_values (sessions_tests.tests.CustomDatabaseSessionTests.test_values) ... ok test_actual_expiry (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_actual_expiry) ... ok test_clear (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_clear) ... ok test_custom_expiry_datetime (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_custom_expiry_datetime) ... ok test_custom_expiry_reset (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_custom_expiry_reset) ... ok test_custom_expiry_seconds (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_custom_expiry_seconds) ... ok test_custom_expiry_timedelta (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_custom_expiry_timedelta) ... ok test_cycle (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_cycle) ... ok test_cycle_with_no_session_cache (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_cycle_with_no_session_cache) ... ok test_decode (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_decode) ... ok test_decode_failure_logged_to_security (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_decode_failure_logged_to_security) ... ok test_decode_legacy (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_decode_legacy) ... ok test_default_expiry (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_default_expiry) ... ok test_default_hashing_algorith_legacy_decode (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_default_hashing_algorith_legacy_decode) ... ok test_delete (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_delete) ... ok test_exists_searches_cache_first (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_exists_searches_cache_first) ... ok test_flush (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_flush) ... ok test_get_empty (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_get_empty) ... ok test_get_expire_at_browser_close (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_get_expire_at_browser_close) ... ok test_has_key (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_has_key) ... ok test_invalid_key (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_invalid_key) ... ok test_items (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_items) ... ok test_keys (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_keys) ... ok test_load_overlong_key (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_load_overlong_key) ... ok test_new_session (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_new_session) ... ok test_non_default_cache (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_non_default_cache) ... ok test_pop (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_pop) ... ok test_pop_default (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_pop_default) ... ok test_pop_default_named_argument (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_pop_default_named_argument) ... ok test_pop_no_default_keyerror_raised (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_pop_no_default_keyerror_raised) ... ok test_save (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_save) ... ok test_save_doesnt_clear_data (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_save_doesnt_clear_data) ... ok test_session_key_empty_string_invalid (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_session_key_empty_string_invalid) Falsey values (Such as an empty string) are rejected. ... ok test_session_key_is_read_only (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_session_key_is_read_only) ... ok test_session_key_too_short_invalid (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_session_key_too_short_invalid) Strings shorter than 8 characters are rejected. ... ok test_session_key_valid_string_saved (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_session_key_valid_string_saved) Strings of length 8 and up are accepted and stored. ... ok test_session_load_does_not_create_record (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_session_load_does_not_create_record) Loading an unknown session key does not create a session record. ... ok test_session_save_does_not_resurrect_session_logged_out_in_other_context (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_session_save_does_not_resurrect_session_logged_out_in_other_context) Sessions shouldn't be resurrected by a concurrent request. ... ok test_setdefault (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_setdefault) ... ok test_store (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_store) ... ok test_update (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_update) ... ok test_values (sessions_tests.tests.CacheDBSessionWithTimeZoneTests.test_values) ... ok test_first_page (pagination.tests.ModelPaginationTests.test_first_page) ... ok test_last_page (pagination.tests.ModelPaginationTests.test_last_page) ... ok test_page_getitem (pagination.tests.ModelPaginationTests.test_page_getitem) Tests proper behavior of a paginator page __getitem__ (queryset ... ok test_paginating_empty_queryset_does_not_warn (pagination.tests.ModelPaginationTests.test_paginating_empty_queryset_does_not_warn) ... ok test_paginating_unordered_object_list_raises_warning (pagination.tests.ModelPaginationTests.test_paginating_unordered_object_list_raises_warning) Unordered object list warning with an object that has an ordered ... ok test_paginating_unordered_queryset_raises_warning (pagination.tests.ModelPaginationTests.test_paginating_unordered_queryset_raises_warning) ... ok test_empty_session_saved (sessions_tests.tests.SessionMiddlewareTests.test_empty_session_saved) If a session is emptied of data but still has a key, it should still ... ok test_flush_empty_without_session_cookie_doesnt_set_cookie (sessions_tests.tests.SessionMiddlewareTests.test_flush_empty_without_session_cookie_doesnt_set_cookie) ... ok test_httponly_session_cookie (sessions_tests.tests.SessionMiddlewareTests.test_httponly_session_cookie) ... ok test_no_httponly_session_cookie (sessions_tests.tests.SessionMiddlewareTests.test_no_httponly_session_cookie) ... ok test_samesite_session_cookie (sessions_tests.tests.SessionMiddlewareTests.test_samesite_session_cookie) ... ok test_secure_session_cookie (sessions_tests.tests.SessionMiddlewareTests.test_secure_session_cookie) ... ok test_session_delete_on_end (sessions_tests.tests.SessionMiddlewareTests.test_session_delete_on_end) ... ok test_session_delete_on_end_with_custom_domain_and_path (sessions_tests.tests.SessionMiddlewareTests.test_session_delete_on_end_with_custom_domain_and_path) ... ok test_session_save_on_500 (sessions_tests.tests.SessionMiddlewareTests.test_session_save_on_500) ... ok test_session_update_error_redirect (sessions_tests.tests.SessionMiddlewareTests.test_session_update_error_redirect) ... ok test_custom_methods (custom_methods.tests.MethodsTests.test_custom_methods) ... ok test_dates (reserved_names.tests.ReservedNameTests.test_dates) ... ok test_fields (reserved_names.tests.ReservedNameTests.test_fields) ... ok test_month_filter (reserved_names.tests.ReservedNameTests.test_month_filter) ... ok test_order_by (reserved_names.tests.ReservedNameTests.test_order_by) ... ok test_simple (reserved_names.tests.ReservedNameTests.test_simple) ... ok test_explicit_ForeignKey (nested_foreign_keys.tests.DeeplyNestedForeignKeysTests.test_explicit_ForeignKey) ... ok test_inheritance (nested_foreign_keys.tests.DeeplyNestedForeignKeysTests.test_inheritance) ... ok test_explicit_ForeignKey (nested_foreign_keys.tests.NestedForeignKeysTests.test_explicit_ForeignKey) ... ok test_explicit_ForeignKey_NullFK (nested_foreign_keys.tests.NestedForeignKeysTests.test_explicit_ForeignKey_NullFK) ... ok test_inheritance (nested_foreign_keys.tests.NestedForeignKeysTests.test_inheritance) ... ok test_inheritance_null_FK (nested_foreign_keys.tests.NestedForeignKeysTests.test_inheritance_null_FK) ... ok test_null_exclude (nested_foreign_keys.tests.NestedForeignKeysTests.test_null_exclude) ... ok test_actual_expiry (sessions_tests.tests.DatabaseSessionTests.test_actual_expiry) ... ok test_clear (sessions_tests.tests.DatabaseSessionTests.test_clear) ... ok test_clearsessions_command (sessions_tests.tests.DatabaseSessionTests.test_clearsessions_command) Test clearsessions command for clearing expired sessions. ... ok test_custom_expiry_datetime (sessions_tests.tests.DatabaseSessionTests.test_custom_expiry_datetime) ... ok test_custom_expiry_reset (sessions_tests.tests.DatabaseSessionTests.test_custom_expiry_reset) ... ok test_custom_expiry_seconds (sessions_tests.tests.DatabaseSessionTests.test_custom_expiry_seconds) ... ok test_custom_expiry_timedelta (sessions_tests.tests.DatabaseSessionTests.test_custom_expiry_timedelta) ... ok test_cycle (sessions_tests.tests.DatabaseSessionTests.test_cycle) ... ok test_cycle_with_no_session_cache (sessions_tests.tests.DatabaseSessionTests.test_cycle_with_no_session_cache) ... ok test_decode (sessions_tests.tests.DatabaseSessionTests.test_decode) ... ok test_decode_failure_logged_to_security (sessions_tests.tests.DatabaseSessionTests.test_decode_failure_logged_to_security) ... ok test_decode_legacy (sessions_tests.tests.DatabaseSessionTests.test_decode_legacy) ... ok test_default_expiry (sessions_tests.tests.DatabaseSessionTests.test_default_expiry) ... ok test_default_hashing_algorith_legacy_decode (sessions_tests.tests.DatabaseSessionTests.test_default_hashing_algorith_legacy_decode) ... ok test_delete (sessions_tests.tests.DatabaseSessionTests.test_delete) ... ok test_flush (sessions_tests.tests.DatabaseSessionTests.test_flush) ... ok test_get_empty (sessions_tests.tests.DatabaseSessionTests.test_get_empty) ... ok test_get_expire_at_browser_close (sessions_tests.tests.DatabaseSessionTests.test_get_expire_at_browser_close) ... ok test_has_key (sessions_tests.tests.DatabaseSessionTests.test_has_key) ... ok test_invalid_key (sessions_tests.tests.DatabaseSessionTests.test_invalid_key) ... ok test_items (sessions_tests.tests.DatabaseSessionTests.test_items) ... ok test_keys (sessions_tests.tests.DatabaseSessionTests.test_keys) ... ok test_new_session (sessions_tests.tests.DatabaseSessionTests.test_new_session) ... ok test_pop (sessions_tests.tests.DatabaseSessionTests.test_pop) ... ok test_pop_default (sessions_tests.tests.DatabaseSessionTests.test_pop_default) ... ok test_pop_default_named_argument (sessions_tests.tests.DatabaseSessionTests.test_pop_default_named_argument) ... ok test_pop_no_default_keyerror_raised (sessions_tests.tests.DatabaseSessionTests.test_pop_no_default_keyerror_raised) ... ok test_save (sessions_tests.tests.DatabaseSessionTests.test_save) ... ok test_save_doesnt_clear_data (sessions_tests.tests.DatabaseSessionTests.test_save_doesnt_clear_data) ... ok test_session_get_decoded (sessions_tests.tests.DatabaseSessionTests.test_session_get_decoded) Test we can use Session.get_decoded to retrieve data stored ... ok test_session_key_empty_string_invalid (sessions_tests.tests.DatabaseSessionTests.test_session_key_empty_string_invalid) Falsey values (Such as an empty string) are rejected. ... ok test_session_key_is_read_only (sessions_tests.tests.DatabaseSessionTests.test_session_key_is_read_only) ... ok test_session_key_too_short_invalid (sessions_tests.tests.DatabaseSessionTests.test_session_key_too_short_invalid) Strings shorter than 8 characters are rejected. ... ok test_session_key_valid_string_saved (sessions_tests.tests.DatabaseSessionTests.test_session_key_valid_string_saved) Strings of length 8 and up are accepted and stored. ... ok test_session_load_does_not_create_record (sessions_tests.tests.DatabaseSessionTests.test_session_load_does_not_create_record) Loading an unknown session key does not create a session record. ... ok test_session_save_does_not_resurrect_session_logged_out_in_other_context (sessions_tests.tests.DatabaseSessionTests.test_session_save_does_not_resurrect_session_logged_out_in_other_context) Sessions shouldn't be resurrected by a concurrent request. ... ok test_session_str (sessions_tests.tests.DatabaseSessionTests.test_session_str) Session repr should be the session key. ... ok test_sessionmanager_save (sessions_tests.tests.DatabaseSessionTests.test_sessionmanager_save) Test SessionManager.save method ... ok test_setdefault (sessions_tests.tests.DatabaseSessionTests.test_setdefault) ... ok test_store (sessions_tests.tests.DatabaseSessionTests.test_store) ... ok test_update (sessions_tests.tests.DatabaseSessionTests.test_update) ... ok test_values (sessions_tests.tests.DatabaseSessionTests.test_values) ... ok test_order_by_update_on_parent_unique_constraint (update.tests.MySQLUpdateOrderByTest.test_order_by_update_on_parent_unique_constraint) ... skipped 'UPDATE...ORDER BY syntax is supported on MySQL/MariaDB' test_order_by_update_on_related_field (update.tests.MySQLUpdateOrderByTest.test_order_by_update_on_related_field) ... skipped 'UPDATE...ORDER BY syntax is supported on MySQL/MariaDB' test_order_by_update_on_unique_constraint (update.tests.MySQLUpdateOrderByTest.test_order_by_update_on_unique_constraint) ... skipped 'UPDATE...ORDER BY syntax is supported on MySQL/MariaDB' test_order_by_update_on_unique_constraint_annotation (update.tests.MySQLUpdateOrderByTest.test_order_by_update_on_unique_constraint_annotation) ... skipped 'UPDATE...ORDER BY syntax is supported on MySQL/MariaDB' test_add_efficiency (many_to_one_null.tests.ManyToOneNullTests.test_add_efficiency) ... ok test_assign_clear_related_set (many_to_one_null.tests.ManyToOneNullTests.test_assign_clear_related_set) ... ok test_assign_with_queryset (many_to_one_null.tests.ManyToOneNullTests.test_assign_with_queryset) ... ok test_clear_efficiency (many_to_one_null.tests.ManyToOneNullTests.test_clear_efficiency) ... ok test_created_via_related_set (many_to_one_null.tests.ManyToOneNullTests.test_created_via_related_set) ... ok test_created_without_related (many_to_one_null.tests.ManyToOneNullTests.test_created_without_related) ... ok test_get_related (many_to_one_null.tests.ManyToOneNullTests.test_get_related) ... ok test_related_null_to_field (many_to_one_null.tests.ManyToOneNullTests.test_related_null_to_field) ... ok test_related_set (many_to_one_null.tests.ManyToOneNullTests.test_related_set) ... ok test_remove_from_wrong_set (many_to_one_null.tests.ManyToOneNullTests.test_remove_from_wrong_set) ... ok test_set (many_to_one_null.tests.ManyToOneNullTests.test_set) ... ok test_set_clear_non_bulk (many_to_one_null.tests.ManyToOneNullTests.test_set_clear_non_bulk) ... ok test_force_update (force_insert_update.tests.ForceTests.test_force_update) ... ok test_empty_update (update.tests.SimpleTest.test_empty_update) Update changes the right number of rows for an empty queryset ... ok test_empty_update_with_inheritance (update.tests.SimpleTest.test_empty_update_with_inheritance) Update changes the right number of rows for an empty queryset ... ok test_foreign_key_update_with_id (update.tests.SimpleTest.test_foreign_key_update_with_id) Update works using _id for foreign keys ... ok test_nonempty_update (update.tests.SimpleTest.test_nonempty_update) Update changes the right number of rows for a nonempty queryset ... ok test_nonempty_update_with_inheritance (update.tests.SimpleTest.test_nonempty_update_with_inheritance) Update changes the right number of rows for an empty queryset ... ok test_force_update_on_inherited_model (force_insert_update.tests.InheritanceTests.test_force_update_on_inherited_model) ... ok test_force_update_on_inherited_model_without_fields (force_insert_update.tests.InheritanceTests.test_force_update_on_inherited_model_without_fields) Issue 13864: force_update fails on subclassed models, if they don't ... ok test_force_update_on_proxy_model (force_insert_update.tests.InheritanceTests.test_force_update_on_proxy_model) ... ok test_update (update.tests.AdvancedTests.test_update) Objects are updated by first filtering the candidates into a queryset ... ok test_update_all (update.tests.AdvancedTests.test_update_all) In the rare case you want to update every instance of a model, update() ... ok test_update_annotated_multi_table_queryset (update.tests.AdvancedTests.test_update_annotated_multi_table_queryset) Update of a queryset that's been annotated and involves multiple tables. ... ok test_update_annotated_queryset (update.tests.AdvancedTests.test_update_annotated_queryset) Update of a queryset that's been annotated. ... ok test_update_fk (update.tests.AdvancedTests.test_update_fk) Foreign key fields can also be updated, although you can only update ... ok test_update_m2m_field (update.tests.AdvancedTests.test_update_m2m_field) ... ok test_update_multiple_fields (update.tests.AdvancedTests.test_update_multiple_fields) Multiple fields can be updated at once ... ok test_update_multiple_objects (update.tests.AdvancedTests.test_update_multiple_objects) We can update multiple objects at once. ... ok test_update_respects_to_field (update.tests.AdvancedTests.test_update_respects_to_field) Update of an FK field which specifies a to_field works. ... ok test_update_slice_fail (update.tests.AdvancedTests.test_update_slice_fail) We do not support update on already sliced query sets. ... ok test_update_transformed_field (update.tests.AdvancedTests.test_update_transformed_field) ... ok test_update_with_joined_field_annotation (update.tests.AdvancedTests.test_update_with_joined_field_annotation) ... ok test_multiple (m2m_multiple.tests.M2MMultipleTests.test_multiple) ... ok test_commit (transactions.tests.DisableDurabiltityCheckTests.test_commit) ... ok test_nested_both_durable (transactions.tests.DisableDurabiltityCheckTests.test_nested_both_durable) ... ok test_nested_inner_durable (transactions.tests.DisableDurabiltityCheckTests.test_nested_inner_durable) ... ok test_nested_outer_durable (transactions.tests.DisableDurabiltityCheckTests.test_nested_outer_durable) ... ok test_mutually_referential (mutually_referential.tests.MutuallyReferentialTests.test_mutually_referential) ... ok test_actual_expiry (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_actual_expiry) ... ok test_clear (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_clear) ... ok test_clearsessions_command (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_clearsessions_command) Test clearsessions command for clearing expired sessions. ... ok test_custom_expiry_datetime (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_custom_expiry_datetime) ... ok test_custom_expiry_reset (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_custom_expiry_reset) ... ok test_custom_expiry_seconds (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_custom_expiry_seconds) ... ok test_custom_expiry_timedelta (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_custom_expiry_timedelta) ... ok test_cycle (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_cycle) ... ok test_cycle_with_no_session_cache (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_cycle_with_no_session_cache) ... ok test_decode (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_decode) ... ok test_decode_failure_logged_to_security (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_decode_failure_logged_to_security) ... ok test_decode_legacy (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_decode_legacy) ... ok test_default_expiry (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_default_expiry) ... ok test_default_hashing_algorith_legacy_decode (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_default_hashing_algorith_legacy_decode) ... ok test_delete (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_delete) ... ok test_flush (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_flush) ... ok test_get_empty (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_get_empty) ... ok test_get_expire_at_browser_close (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_get_expire_at_browser_close) ... ok test_has_key (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_has_key) ... ok test_invalid_key (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_invalid_key) ... ok test_items (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_items) ... ok test_keys (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_keys) ... ok test_new_session (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_new_session) ... ok test_pop (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_pop) ... ok test_pop_default (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_pop_default) ... ok test_pop_default_named_argument (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_pop_default_named_argument) ... ok test_pop_no_default_keyerror_raised (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_pop_no_default_keyerror_raised) ... ok test_save (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_save) ... ok test_save_doesnt_clear_data (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_save_doesnt_clear_data) ... ok test_session_get_decoded (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_session_get_decoded) Test we can use Session.get_decoded to retrieve data stored ... ok test_session_key_empty_string_invalid (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_session_key_empty_string_invalid) Falsey values (Such as an empty string) are rejected. ... ok test_session_key_is_read_only (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_session_key_is_read_only) ... ok test_session_key_too_short_invalid (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_session_key_too_short_invalid) Strings shorter than 8 characters are rejected. ... ok test_session_key_valid_string_saved (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_session_key_valid_string_saved) Strings of length 8 and up are accepted and stored. ... ok test_session_load_does_not_create_record (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_session_load_does_not_create_record) Loading an unknown session key does not create a session record. ... ok test_session_save_does_not_resurrect_session_logged_out_in_other_context (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_session_save_does_not_resurrect_session_logged_out_in_other_context) Sessions shouldn't be resurrected by a concurrent request. ... ok test_session_str (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_session_str) Session repr should be the session key. ... ok test_sessionmanager_save (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_sessionmanager_save) Test SessionManager.save method ... ok test_setdefault (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_setdefault) ... ok test_store (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_store) ... ok test_update (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_update) ... ok test_values (sessions_tests.tests.DatabaseSessionWithTimeZoneTests.test_values) ... ok test_add_m2m_with_base_class (m2m_regress.tests.M2MRegressionTests.test_add_m2m_with_base_class) ... ok test_assigning_invalid_data_to_m2m_doesnt_clear_existing_relations (m2m_regress.tests.M2MRegressionTests.test_assigning_invalid_data_to_m2m_doesnt_clear_existing_relations) ... ok test_internal_related_name_not_in_error_msg (m2m_regress.tests.M2MRegressionTests.test_internal_related_name_not_in_error_msg) ... ok test_m2m_abstract_split (m2m_regress.tests.M2MRegressionTests.test_m2m_abstract_split) ... ok test_m2m_inheritance_symmetry (m2m_regress.tests.M2MRegressionTests.test_m2m_inheritance_symmetry) ... ok test_m2m_pk_field_type (m2m_regress.tests.M2MRegressionTests.test_m2m_pk_field_type) ... ok test_manager_class_caching (m2m_regress.tests.M2MRegressionTests.test_manager_class_caching) ... ok test_multiple_forwards_only_m2m (m2m_regress.tests.M2MRegressionTests.test_multiple_forwards_only_m2m) ... ok test_multiple_m2m (m2m_regress.tests.M2MRegressionTests.test_multiple_m2m) ... ok test_gt (lookup.test_decimalfield.DecimalFieldLookupTests.test_gt) ... ok test_gte (lookup.test_decimalfield.DecimalFieldLookupTests.test_gte) ... ok test_lt (lookup.test_decimalfield.DecimalFieldLookupTests.test_lt) ... ok test_lte (lookup.test_decimalfield.DecimalFieldLookupTests.test_lte) ... ok test_hour_lookups (lookup.test_timefield.TimeFieldLookupTests.test_hour_lookups) ... ok test_minute_lookups (lookup.test_timefield.TimeFieldLookupTests.test_minute_lookups) ... ok test_second_lookups (lookup.test_timefield.TimeFieldLookupTests.test_second_lookups) ... ok test_boolean_type (datatypes.tests.DataTypesTestCase.test_boolean_type) ... ok test_date_type (datatypes.tests.DataTypesTestCase.test_date_type) ... ok test_datefield_auto_now_add (datatypes.tests.DataTypesTestCase.test_datefield_auto_now_add) Regression test for #10970, auto_now_add for DateField should store ... ok test_error_on_timezone (datatypes.tests.DataTypesTestCase.test_error_on_timezone) Regression test for #8354: the MySQL and Oracle backends should raise ... ok test_textfields_str (datatypes.tests.DataTypesTestCase.test_textfields_str) TextField values returned from the database should be str. ... ok test_time_field (datatypes.tests.DataTypesTestCase.test_time_field) ... ok test_year_boundaries (datatypes.tests.DataTypesTestCase.test_year_boundaries) Year boundary tests (ticket #3689) ... ok test_bulk_insert (queries.test_db_returning.ReturningValuesTests.test_bulk_insert) ... skipped "Database doesn't support feature(s): can_return_columns_from_insert" test_insert_returning (queries.test_db_returning.ReturningValuesTests.test_insert_returning) ... skipped "Database doesn't support feature(s): can_return_columns_from_insert" test_insert_returning_multiple (queries.test_db_returning.ReturningValuesTests.test_insert_returning_multiple) ... skipped "Database doesn't support feature(s): can_return_columns_from_insert" test_insert_returning_non_integer (queries.test_db_returning.ReturningValuesTests.test_insert_returning_non_integer) ... skipped "Database doesn't support feature(s): can_return_columns_from_insert" test_batch_size (queries.test_bulk_update.BulkUpdateNoteTests.test_batch_size) ... ok test_foreign_keys_do_not_lookup (queries.test_bulk_update.BulkUpdateNoteTests.test_foreign_keys_do_not_lookup) ... ok test_functions (queries.test_bulk_update.BulkUpdateNoteTests.test_functions) ... ok test_multiple_fields (queries.test_bulk_update.BulkUpdateNoteTests.test_multiple_fields) ... ok test_set_field_to_null (queries.test_bulk_update.BulkUpdateNoteTests.test_set_field_to_null) ... ok test_set_mixed_fields_to_null (queries.test_bulk_update.BulkUpdateNoteTests.test_set_mixed_fields_to_null) ... ok test_simple (queries.test_bulk_update.BulkUpdateNoteTests.test_simple) ... ok test_unsaved_models (queries.test_bulk_update.BulkUpdateNoteTests.test_unsaved_models) ... ok test_message (queries.test_explain.ExplainUnsupportedTests.test_message) ... skipped 'Database has feature(s) supports_explaining_query_execution' test_basic (queries.test_explain.ExplainTests.test_basic) ... ok test_invalid_option_names (queries.test_explain.ExplainTests.test_invalid_option_names) ... ok test_mysql_analyze (queries.test_explain.ExplainTests.test_mysql_analyze) ... skipped 'MariaDB and MySQL >= 8.0.18 specific.' test_mysql_text_to_traditional (queries.test_explain.ExplainTests.test_mysql_text_to_traditional) ... skipped 'MySQL specific' test_option_sql_injection (queries.test_explain.ExplainTests.test_option_sql_injection) ... ok test_postgres_options (queries.test_explain.ExplainTests.test_postgres_options) ... skipped 'PostgreSQL specific' test_unknown_format (queries.test_explain.ExplainTests.test_unknown_format) ... ok test_unknown_options (queries.test_explain.ExplainTests.test_unknown_options) ... ok test_default_iterator_chunk_size (queries.test_iterator.QuerySetIteratorTests.test_default_iterator_chunk_size) ... ok test_iterator_chunk_size (queries.test_iterator.QuerySetIteratorTests.test_iterator_chunk_size) ... ok test_iterator_invalid_chunk_size (queries.test_iterator.QuerySetIteratorTests.test_iterator_invalid_chunk_size) ... ok test_no_chunked_reads (queries.test_iterator.QuerySetIteratorTests.test_no_chunked_reads) If the database backend doesn't support chunked reads, then the ... ok test_evaluated_queryset_as_argument (queries.tests.CloneTests.test_evaluated_queryset_as_argument) #13227 -- If a queryset is already evaluated, it can still be used as a query arg ... ok test_no_fields_cloning (queries.tests.CloneTests.test_no_fields_cloning) Cloning a queryset does not get out of hand. While complete ... ok test_no_model_options_cloning (queries.tests.CloneTests.test_no_model_options_cloning) Cloning a queryset does not get out of hand. While complete ... ok test_ticket8597 (queries.tests.ComparisonTests.test_ticket8597) ... ok test_in_list_limit (queries.tests.ConditionalTests.test_in_list_limit) ... ok test_infinite_loop (queries.tests.ConditionalTests.test_infinite_loop) ... ok test_null_ordering_added (queries.tests.ConditionalTests.test_null_ordering_added) ... skipped "Database doesn't support feature(s): requires_explicit_null_ordering_when_grouping" test_ticket7371 (queries.tests.CustomPkTests.test_ticket7371) ... ok test_no_extra_params (queries.tests.DefaultValuesInsertTest.test_no_extra_params) Can create an instance of a model with only the PK field (#17056)." ... ok test_booleanfield (queries.test_bulk_update.BulkUpdateTests.test_booleanfield) ... ok test_custom_db_columns (queries.test_bulk_update.BulkUpdateTests.test_custom_db_columns) ... ok test_custom_pk (queries.test_bulk_update.BulkUpdateTests.test_custom_pk) ... ok test_datetime_field (queries.test_bulk_update.BulkUpdateTests.test_datetime_field) ... ok test_empty_objects (queries.test_bulk_update.BulkUpdateTests.test_empty_objects) ... ok test_falsey_pk_value (queries.test_bulk_update.BulkUpdateTests.test_falsey_pk_value) ... ok test_field_references (queries.test_bulk_update.BulkUpdateTests.test_field_references) ... ok test_inherited_fields (queries.test_bulk_update.BulkUpdateTests.test_inherited_fields) ... ok test_invalid_batch_size (queries.test_bulk_update.BulkUpdateTests.test_invalid_batch_size) ... ok test_ipaddressfield (queries.test_bulk_update.BulkUpdateTests.test_ipaddressfield) ... ok test_json_field (queries.test_bulk_update.BulkUpdateTests.test_json_field) ... ok test_large_batch (queries.test_bulk_update.BulkUpdateTests.test_large_batch) ... ok test_no_fields (queries.test_bulk_update.BulkUpdateTests.test_no_fields) ... ok test_nonexistent_field (queries.test_bulk_update.BulkUpdateTests.test_nonexistent_field) ... ok test_only_concrete_fields_allowed (queries.test_bulk_update.BulkUpdateTests.test_only_concrete_fields_allowed) ... ok test_update_custom_primary_key (queries.test_bulk_update.BulkUpdateTests.test_update_custom_primary_key) ... ok test_update_primary_key (queries.test_bulk_update.BulkUpdateTests.test_update_primary_key) ... ok test_ticket7872 (queries.tests.DisjunctiveFilterTests.test_ticket7872) ... ok test_ticket8283 (queries.tests.DisjunctiveFilterTests.test_ticket8283) ... ok test_double_subquery_in (queries.tests.DoubleInSubqueryTests.test_double_subquery_in) ... ok test_disjunction_promotion1 (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion1) ... ok test_disjunction_promotion2 (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion2) ... ok test_disjunction_promotion3 (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion3) ... ok test_disjunction_promotion3_demote (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion3_demote) ... ok test_disjunction_promotion4 (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion4) ... ok test_disjunction_promotion4_demote (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion4_demote) ... ok test_disjunction_promotion5_demote (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion5_demote) ... ok test_disjunction_promotion6 (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion6) ... ok test_disjunction_promotion7 (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion7) ... ok test_disjunction_promotion_fexpression (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion_fexpression) ... ok test_disjunction_promotion_select_related (queries.tests.DisjunctionPromotionTests.test_disjunction_promotion_select_related) ... ok test_ticket_7302 (queries.tests.EscapingTests.test_ticket_7302) ... ok test_21001 (queries.tests.EmptyStringsAsNullTest.test_21001) ... ok test_direct_exclude (queries.tests.EmptyStringsAsNullTest.test_direct_exclude) ... ok test_joined_exclude (queries.tests.EmptyStringsAsNullTest.test_joined_exclude) ... ok test_ticket15786 (queries.tests.Exclude15786.test_ticket15786) ... ok test_chain_date_time_lookups (lookup.tests.LookupTests.test_chain_date_time_lookups) ... ok test_count (lookup.tests.LookupTests.test_count) ... ok test_custom_field_none_rhs (lookup.tests.LookupTests.test_custom_field_none_rhs) __exact=value is transformed to __isnull=True if Field.get_prep_value() ... ok test_custom_lookup_none_rhs (lookup.tests.LookupTests.test_custom_lookup_none_rhs) Lookup.can_use_none_as_rhs=True allows None as a lookup value. ... ok test_error_messages (lookup.tests.LookupTests.test_error_messages) ... ok test_escaping (lookup.tests.LookupTests.test_escaping) ... ok test_exact_exists (lookup.tests.LookupTests.test_exact_exists) ... ok test_exact_none_transform (lookup.tests.LookupTests.test_exact_none_transform) Transforms are used for __exact=None. ... ok test_exact_query_rhs_with_selected_columns (lookup.tests.LookupTests.test_exact_query_rhs_with_selected_columns) ... ok test_exact_sliced_queryset_limit_one (lookup.tests.LookupTests.test_exact_sliced_queryset_limit_one) ... ok test_exact_sliced_queryset_limit_one_offset (lookup.tests.LookupTests.test_exact_sliced_queryset_limit_one_offset) ... ok test_exact_sliced_queryset_not_limited_to_one (lookup.tests.LookupTests.test_exact_sliced_queryset_not_limited_to_one) ... ok test_exclude (lookup.tests.LookupTests.test_exclude) ... ok test_exists (lookup.tests.LookupTests.test_exists) ... ok test_get_next_previous_by (lookup.tests.LookupTests.test_get_next_previous_by) ... ok test_in (lookup.tests.LookupTests.test_in) ... ok test_in_bulk (lookup.tests.LookupTests.test_in_bulk) ... ok test_in_bulk_distinct_field (lookup.tests.LookupTests.test_in_bulk_distinct_field) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_in_bulk_lots_of_ids (lookup.tests.LookupTests.test_in_bulk_lots_of_ids) ... ok test_in_bulk_meta_constraint (lookup.tests.LookupTests.test_in_bulk_meta_constraint) ... ok test_in_bulk_multiple_distinct_field (lookup.tests.LookupTests.test_in_bulk_multiple_distinct_field) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_in_bulk_non_unique_field (lookup.tests.LookupTests.test_in_bulk_non_unique_field) ... ok test_in_bulk_non_unique_meta_constaint (lookup.tests.LookupTests.test_in_bulk_non_unique_meta_constaint) ... ok test_in_bulk_with_field (lookup.tests.LookupTests.test_in_bulk_with_field) ... ok test_in_different_database (lookup.tests.LookupTests.test_in_different_database) ... ok test_in_empty_list (lookup.tests.LookupTests.test_in_empty_list) ... ok test_in_ignore_none (lookup.tests.LookupTests.test_in_ignore_none) ... ok test_in_ignore_none_with_unhashable_items (lookup.tests.LookupTests.test_in_ignore_none_with_unhashable_items) ... ok test_in_ignore_solo_none (lookup.tests.LookupTests.test_in_ignore_solo_none) ... ok test_in_keeps_value_ordering (lookup.tests.LookupTests.test_in_keeps_value_ordering) ... ok test_isnull_non_boolean_value (lookup.tests.LookupTests.test_isnull_non_boolean_value) ... ok test_iterator (lookup.tests.LookupTests.test_iterator) ... ok test_lookup_collision (lookup.tests.LookupTests.test_lookup_collision) Genuine field names don't collide with built-in lookup types ... ok test_lookup_date_as_str (lookup.tests.LookupTests.test_lookup_date_as_str) ... ok test_lookup_int_as_str (lookup.tests.LookupTests.test_lookup_int_as_str) ... ok test_nested_outerref_lhs (lookup.tests.LookupTests.test_nested_outerref_lhs) ... ok test_none (lookup.tests.LookupTests.test_none) ... ok test_nonfield_lookups (lookup.tests.LookupTests.test_nonfield_lookups) A lookup query containing non-fields raises the proper exception. ... ok test_pattern_lookups_with_substr (lookup.tests.LookupTests.test_pattern_lookups_with_substr) ... ok test_regex (lookup.tests.LookupTests.test_regex) ... ok test_regex_backreferencing (lookup.tests.LookupTests.test_regex_backreferencing) ... ok test_regex_non_ascii (lookup.tests.LookupTests.test_regex_non_ascii) A regex lookup does not trip on non-ASCII characters. ... ok test_regex_non_string (lookup.tests.LookupTests.test_regex_non_string) A regex lookup does not fail on non-string fields ... ok test_regex_null (lookup.tests.LookupTests.test_regex_null) A regex lookup does not fail on null/None values ... ok test_relation_nested_lookup_error (lookup.tests.LookupTests.test_relation_nested_lookup_error) ... ok test_unsupported_lookups (lookup.tests.LookupTests.test_unsupported_lookups) ... ok test_values (lookup.tests.LookupTests.test_values) ... ok test_values_list (lookup.tests.LookupTests.test_values_list) ... ok test_exclude_plain (queries.tests.ExcludeTest17600.test_exclude_plain) This should exclude Orders which have some items with status 1 ... ok test_exclude_plain_distinct (queries.tests.ExcludeTest17600.test_exclude_plain_distinct) This should exclude Orders which have some items with status 1 ... ok test_exclude_with_q_is_equal_to_plain_exclude (queries.tests.ExcludeTest17600.test_exclude_with_q_is_equal_to_plain_exclude) Using exclude(condition) and exclude(Q(condition)) should ... ok test_exclude_with_q_is_equal_to_plain_exclude_variation (queries.tests.ExcludeTest17600.test_exclude_with_q_is_equal_to_plain_exclude_variation) Using exclude(condition) and exclude(Q(condition)) should ... ok test_exclude_with_q_object_distinct (queries.tests.ExcludeTest17600.test_exclude_with_q_object_distinct) This should exclude Orders which have some items with status 1 ... ok test_exclude_with_q_object_no_distinct (queries.tests.ExcludeTest17600.test_exclude_with_q_object_no_distinct) This should exclude Orders which have some items with status 1 ... ok test_only_orders_with_all_items_having_status_1 (queries.tests.ExcludeTest17600.test_only_orders_with_all_items_having_status_1) This should only return orders having ALL items set to status 1, or ... expected failure test_ticket_21787 (queries.tests.ForeignKeyToBaseExcludeTests.test_ticket_21787) ... ok test_exclude_multivalued_exists (queries.tests.ExcludeTests.test_exclude_multivalued_exists) ... ok test_exclude_nullable_fields (queries.tests.ExcludeTests.test_exclude_nullable_fields) ... ok test_exclude_reverse_fk_field_ref (queries.tests.ExcludeTests.test_exclude_reverse_fk_field_ref) ... ok test_exclude_subquery (queries.tests.ExcludeTests.test_exclude_subquery) ... ok test_exclude_with_circular_fk_relation (queries.tests.ExcludeTests.test_exclude_with_circular_fk_relation) ... ok test_subquery_exclude_outerref (queries.tests.ExcludeTests.test_subquery_exclude_outerref) ... ok test_ticket14511 (queries.tests.ExcludeTests.test_ticket14511) ... ok test_to_field (queries.tests.ExcludeTests.test_to_field) ... ok test_exists (queries.tests.ExistsSql.test_exists) ... ok test_ticket_18414 (queries.tests.ExistsSql.test_ticket_18414) ... ok test_ticket_18414_distinct_on (queries.tests.ExistsSql.test_ticket_18414_distinct_on) ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_primary_key (queries.tests.IsNullTests.test_primary_key) ... ok test_to_field (queries.tests.IsNullTests.test_to_field) ... ok test_exclude_many_to_many (queries.tests.ManyToManyExcludeTest.test_exclude_many_to_many) ... ok test_ticket_12823 (queries.tests.ManyToManyExcludeTest.test_ticket_12823) ... ok test_col_not_in_list_containing_null (queries.tests.NullInExcludeTest.test_col_not_in_list_containing_null) The following case is not handled properly because ... expected failure test_double_exclude (queries.tests.NullInExcludeTest.test_double_exclude) ... ok test_null_in_exclude_qs (queries.tests.NullInExcludeTest.test_null_in_exclude_qs) ... ok test_fk_reuse (queries.tests.JoinReuseTest.test_fk_reuse) ... ok test_fk_reuse_annotation (queries.tests.JoinReuseTest.test_fk_reuse_annotation) ... ok test_fk_reuse_disjunction (queries.tests.JoinReuseTest.test_fk_reuse_disjunction) ... ok test_fk_reuse_order_by (queries.tests.JoinReuseTest.test_fk_reuse_order_by) ... ok test_fk_reuse_select_related (queries.tests.JoinReuseTest.test_fk_reuse_select_related) ... ok test_inverted_q_across_relations (queries.tests.JoinReuseTest.test_inverted_q_across_relations) When a trimmable join is specified in the query (here school__), the ... ok test_revfk_noreuse (queries.tests.JoinReuseTest.test_revfk_noreuse) ... ok test_revo2o_reuse (queries.tests.JoinReuseTest.test_revo2o_reuse) ... ok test_join_already_in_query (queries.tests.NullableRelOrderingTests.test_join_already_in_query) ... ok test_ticket10028 (queries.tests.NullableRelOrderingTests.test_ticket10028) ... ok test_evaluated_proxy_count (queries.tests.ProxyQueryCleanupTest.test_evaluated_proxy_count) Generating the query string doesn't alter the query's state ... ok test_isnull_filter_promotion (queries.tests.NullJoinPromotionOrTest.test_isnull_filter_promotion) ... ok test_null_join_demotion (queries.tests.NullJoinPromotionOrTest.test_null_join_demotion) ... ok test_ticket_17886 (queries.tests.NullJoinPromotionOrTest.test_ticket_17886) ... ok test_ticket_21366 (queries.tests.NullJoinPromotionOrTest.test_ticket_21366) ... ok test_ticket_21748 (queries.tests.NullJoinPromotionOrTest.test_ticket_21748) ... ok test_ticket_21748_complex_filter (queries.tests.NullJoinPromotionOrTest.test_ticket_21748_complex_filter) ... ok test_ticket_21748_double_negated_and (queries.tests.NullJoinPromotionOrTest.test_ticket_21748_double_negated_and) ... ok test_ticket_21748_double_negated_or (queries.tests.NullJoinPromotionOrTest.test_ticket_21748_double_negated_or) ... ok test_combining_multiple_models (queries.test_qs_combinators.QuerySetSetOperationTests.test_combining_multiple_models) ... ok test_count_difference (queries.test_qs_combinators.QuerySetSetOperationTests.test_count_difference) ... ok test_count_intersection (queries.test_qs_combinators.QuerySetSetOperationTests.test_count_intersection) ... ok test_count_union (queries.test_qs_combinators.QuerySetSetOperationTests.test_count_union) ... ok test_count_union_empty_result (queries.test_qs_combinators.QuerySetSetOperationTests.test_count_union_empty_result) ... ok test_difference_with_empty_qs (queries.test_qs_combinators.QuerySetSetOperationTests.test_difference_with_empty_qs) ... ok test_difference_with_values (queries.test_qs_combinators.QuerySetSetOperationTests.test_difference_with_values) ... ok test_empty_qs_union_with_ordered_qs (queries.test_qs_combinators.QuerySetSetOperationTests.test_empty_qs_union_with_ordered_qs) ... ok test_exists_difference (queries.test_qs_combinators.QuerySetSetOperationTests.test_exists_difference) ... ok test_exists_intersection (queries.test_qs_combinators.QuerySetSetOperationTests.test_exists_intersection) ... ok test_exists_union (queries.test_qs_combinators.QuerySetSetOperationTests.test_exists_union) ... ok test_exists_union_empty_result (queries.test_qs_combinators.QuerySetSetOperationTests.test_exists_union_empty_result) ... ok test_get_difference (queries.test_qs_combinators.QuerySetSetOperationTests.test_get_difference) ... ok test_get_intersection (queries.test_qs_combinators.QuerySetSetOperationTests.test_get_intersection) ... ok test_get_union (queries.test_qs_combinators.QuerySetSetOperationTests.test_get_union) ... ok test_get_with_filters_unsupported_on_combined_qs (queries.test_qs_combinators.QuerySetSetOperationTests.test_get_with_filters_unsupported_on_combined_qs) ... ok test_intersection_with_empty_qs (queries.test_qs_combinators.QuerySetSetOperationTests.test_intersection_with_empty_qs) ... ok test_intersection_with_values (queries.test_qs_combinators.QuerySetSetOperationTests.test_intersection_with_values) ... ok test_limits (queries.test_qs_combinators.QuerySetSetOperationTests.test_limits) ... ok test_order_by_same_type (queries.test_qs_combinators.QuerySetSetOperationTests.test_order_by_same_type) ... ok test_order_raises_on_non_selected_column (queries.test_qs_combinators.QuerySetSetOperationTests.test_order_raises_on_non_selected_column) ... ok test_ordering (queries.test_qs_combinators.QuerySetSetOperationTests.test_ordering) ... ok test_ordering_by_alias (queries.test_qs_combinators.QuerySetSetOperationTests.test_ordering_by_alias) ... ok test_ordering_by_f_expression (queries.test_qs_combinators.QuerySetSetOperationTests.test_ordering_by_f_expression) ... ok test_ordering_by_f_expression_and_alias (queries.test_qs_combinators.QuerySetSetOperationTests.test_ordering_by_f_expression_and_alias) ... ok test_ordering_subqueries (queries.test_qs_combinators.QuerySetSetOperationTests.test_ordering_subqueries) ... skipped "Database doesn't support feature(s): supports_slicing_ordering_in_compound" test_qs_with_subcompound_qs (queries.test_qs_combinators.QuerySetSetOperationTests.test_qs_with_subcompound_qs) ... ok test_simple_difference (queries.test_qs_combinators.QuerySetSetOperationTests.test_simple_difference) ... ok test_simple_intersection (queries.test_qs_combinators.QuerySetSetOperationTests.test_simple_intersection) ... ok test_simple_union (queries.test_qs_combinators.QuerySetSetOperationTests.test_simple_union) ... ok test_union_distinct (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_distinct) ... ok test_union_multiple_models_with_values_list_and_order (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_multiple_models_with_values_list_and_order) ... ok test_union_multiple_models_with_values_list_and_order_by_extra_select (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_multiple_models_with_values_list_and_order_by_extra_select) ... ok test_union_none (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_none) ... ok test_union_with_empty_qs (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_with_empty_qs) ... ok test_union_with_extra_and_values_list (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_with_extra_and_values_list) ... ok test_union_with_two_annotated_values_list (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_with_two_annotated_values_list) ... ok test_union_with_values (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_with_values) ... ok test_union_with_values_list_and_order (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_with_values_list_and_order) ... ok test_union_with_values_list_and_order_on_annotation (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_with_values_list_and_order_on_annotation) ... ok test_union_with_values_list_on_annotated_and_unannotated (queries.test_qs_combinators.QuerySetSetOperationTests.test_union_with_values_list_on_annotated_and_unannotated) ... ok test_unsupported_intersection_raises_db_error (queries.test_qs_combinators.QuerySetSetOperationTests.test_unsupported_intersection_raises_db_error) ... skipped 'Database has feature(s) supports_select_intersection' test_unsupported_operations_on_combined_qs (queries.test_qs_combinators.QuerySetSetOperationTests.test_unsupported_operations_on_combined_qs) ... ok test_unsupported_ordering_slicing_raises_db_error (queries.test_qs_combinators.QuerySetSetOperationTests.test_unsupported_ordering_slicing_raises_db_error) ... ok test_ticket12239 (queries.tests.Queries2Tests.test_ticket12239) ... ok test_ticket4289 (queries.tests.Queries2Tests.test_ticket4289) ... ok test_ticket7759 (queries.tests.Queries2Tests.test_ticket7759) ... ok test_ticket22023 (queries.tests.Queries3Tests.test_ticket22023) ... ok test_ticket7107 (queries.tests.Queries3Tests.test_ticket7107) ... ok test_ticket8683 (queries.tests.Queries3Tests.test_ticket8683) ... ok test_extra_select_alias_sql_injection (queries.tests.Queries5Tests.test_extra_select_alias_sql_injection) ... ok test_extra_select_literal_percent_s (queries.tests.Queries5Tests.test_extra_select_literal_percent_s) ... ok test_ordering (queries.tests.Queries5Tests.test_ordering) ... ok test_ticket5261 (queries.tests.Queries5Tests.test_ticket5261) ... ok test_ticket7045 (queries.tests.Queries5Tests.test_ticket7045) ... ok test_ticket7256 (queries.tests.Queries5Tests.test_ticket7256) ... ok test_ticket9848 (queries.tests.Queries5Tests.test_ticket9848) ... ok test_distinct_ordered_sliced_subquery_aggregation (queries.tests.Queries6Tests.test_distinct_ordered_sliced_subquery_aggregation) ... ok test_multiple_columns_with_the_same_name_slice (queries.tests.Queries6Tests.test_multiple_columns_with_the_same_name_slice) ... ok test_nested_queries_sql (queries.tests.Queries6Tests.test_nested_queries_sql) ... ok test_parallel_iterators (queries.tests.Queries6Tests.test_parallel_iterators) ... ok test_ticket3739 (queries.tests.Queries6Tests.test_ticket3739) ... ok test_ticket_11320 (queries.tests.Queries6Tests.test_ticket_11320) ... ok test_tickets_8921_9188 (queries.tests.Queries6Tests.test_tickets_8921_9188) ... ok test_or_with_both_slice (queries.tests.QuerySetBitwiseOperationTests.test_or_with_both_slice) ... ok test_or_with_both_slice_and_ordering (queries.tests.QuerySetBitwiseOperationTests.test_or_with_both_slice_and_ordering) ... ok test_or_with_lhs_slice (queries.tests.QuerySetBitwiseOperationTests.test_or_with_lhs_slice) ... ok test_or_with_rhs_slice (queries.tests.QuerySetBitwiseOperationTests.test_or_with_rhs_slice) ... ok test_subquery_aliases (queries.tests.QuerySetBitwiseOperationTests.test_subquery_aliases) ... ok test_ticket14729 (queries.tests.RawQueriesTests.test_ticket14729) ... ok test_combine_join_reuse (queries.tests.Queries4Tests.test_combine_join_reuse) ... ok test_combine_or_filter_reuse (queries.tests.Queries4Tests.test_combine_or_filter_reuse) ... ok test_filter_reverse_non_integer_pk (queries.tests.Queries4Tests.test_filter_reverse_non_integer_pk) ... ok test_join_reuse_order (queries.tests.Queries4Tests.test_join_reuse_order) ... ok test_order_by_resetting (queries.tests.Queries4Tests.test_order_by_resetting) ... ok test_order_by_reverse_fk (queries.tests.Queries4Tests.test_order_by_reverse_fk) ... ok test_ticket10181 (queries.tests.Queries4Tests.test_ticket10181) ... ok test_ticket11811 (queries.tests.Queries4Tests.test_ticket11811) ... ok test_ticket14876 (queries.tests.Queries4Tests.test_ticket14876) ... ok test_ticket15316_exclude_false (queries.tests.Queries4Tests.test_ticket15316_exclude_false) ... ok test_ticket15316_exclude_true (queries.tests.Queries4Tests.test_ticket15316_exclude_true) ... ok test_ticket15316_filter_false (queries.tests.Queries4Tests.test_ticket15316_filter_false) ... ok test_ticket15316_filter_true (queries.tests.Queries4Tests.test_ticket15316_filter_true) ... ok test_ticket15316_one2one_exclude_false (queries.tests.Queries4Tests.test_ticket15316_one2one_exclude_false) ... ok test_ticket15316_one2one_exclude_true (queries.tests.Queries4Tests.test_ticket15316_one2one_exclude_true) ... ok test_ticket15316_one2one_filter_false (queries.tests.Queries4Tests.test_ticket15316_one2one_filter_false) ... ok test_ticket15316_one2one_filter_true (queries.tests.Queries4Tests.test_ticket15316_one2one_filter_true) ... ok test_ticket24525 (queries.tests.Queries4Tests.test_ticket24525) ... ok test_ticket7095 (queries.tests.Queries4Tests.test_ticket7095) ... ok test_ticket_19964 (queries.tests.RelabelCloneTest.test_ticket_19964) ... ok test_reverse_trimming (queries.tests.ReverseJoinTrimmingTest.test_reverse_trimming) ... ok test_can_combine_queries_using_and_and_or_operators (queries.tests.QuerySetSupportsPythonIdioms.test_can_combine_queries_using_and_and_or_operators) ... ok test_can_get_items_using_index_and_slice_notation (queries.tests.QuerySetSupportsPythonIdioms.test_can_get_items_using_index_and_slice_notation) ... ok test_can_get_number_of_items_in_queryset_using_standard_len (queries.tests.QuerySetSupportsPythonIdioms.test_can_get_number_of_items_in_queryset_using_standard_len) ... ok test_invalid_index (queries.tests.QuerySetSupportsPythonIdioms.test_invalid_index) ... ok test_slicing_can_slice_again_after_slicing (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_can_slice_again_after_slicing) ... ok test_slicing_cannot_combine_queries_once_sliced (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_cannot_combine_queries_once_sliced) ... ok test_slicing_cannot_filter_queryset_once_sliced (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_cannot_filter_queryset_once_sliced) ... ok test_slicing_cannot_reorder_queryset_once_sliced (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_cannot_reorder_queryset_once_sliced) ... ok test_slicing_negative_indexing_not_supported_for_range (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_negative_indexing_not_supported_for_range) hint: inverting your ordering might do what you need ... ok test_slicing_negative_indexing_not_supported_for_single_element (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_negative_indexing_not_supported_for_single_element) hint: inverting your ordering might do what you need ... ok test_slicing_with_steps_can_be_used (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_with_steps_can_be_used) ... ok test_slicing_with_tests_is_not_lazy (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_with_tests_is_not_lazy) ... ok test_slicing_without_step_is_lazy (queries.tests.QuerySetSupportsPythonIdioms.test_slicing_without_step_is_lazy) ... ok test_ticket_21879 (queries.tests.ReverseM2MCustomPkTests.test_ticket_21879) ... ok test_correct_lookup (queries.tests.RelatedLookupTypeTests.test_correct_lookup) When passing proxy model objects, child objects, or parent objects, ... ok test_values_queryset_lookup (queries.tests.RelatedLookupTypeTests.test_values_queryset_lookup) #23396 - Ensure ValueQuerySets are not checked for compatibility with the lookup field ... ok test_wrong_backward_lookup (queries.tests.RelatedLookupTypeTests.test_wrong_backward_lookup) A ValueError is raised when the incorrect object type is passed to a ... ok test_wrong_type_lookup (queries.tests.RelatedLookupTypeTests.test_wrong_type_lookup) A ValueError is raised when the incorrect object type is passed to a ... ok test_tickets_3045_3288 (queries.tests.SelectRelatedTests.test_tickets_3045_3288) ... ok test_ticket7778 (queries.tests.SubclassFKTests.test_ticket7778) ... ok test_ticket_24278 (queries.tests.TestTicket24279.test_ticket_24278) ... ok test_ticket_24605 (queries.tests.TestTicket24605.test_ticket_24605) Subquery table names should be quoted. ... ok test_ticket_12807 (queries.tests.Ticket12807Tests.test_ticket_12807) ... ok test_ticket_14056 (queries.tests.Ticket14056Tests.test_ticket_14056) ... ok test_distinct_ordered_sliced_subquery (queries.tests.SubqueryTests.test_distinct_ordered_sliced_subquery) ... ok test_ordered_subselect (queries.tests.SubqueryTests.test_ordered_subselect) Subselects honor any manual ordering ... ok test_related_sliced_subquery (queries.tests.SubqueryTests.test_related_sliced_subquery) Related objects constraints can safely contain sliced subqueries. ... ok test_slice_subquery_and_query (queries.tests.SubqueryTests.test_slice_subquery_and_query) Slice a query that has a sliced subquery ... ok test_sliced_delete (queries.tests.SubqueryTests.test_sliced_delete) Delete queries can safely contain sliced subqueries ... ok test_ticket_20101 (queries.tests.Ticket20101Tests.test_ticket_20101) Tests QuerySet ORed combining in exclude subquery case. ... ok test_ticket_20788 (queries.tests.Ticket20788Tests.test_ticket_20788) ... ok test_ticket_20955 (queries.tests.Ticket20955Tests.test_ticket_20955) ... ok test_ticket_21203 (queries.tests.Ticket21203Tests.test_ticket_21203) ... ok test_ticket_22429 (queries.tests.Ticket22429Tests.test_ticket_22429) ... ok test_ticket_23622 (queries.tests.Ticket23622Tests.test_ticket_23622) Make sure __pk__in and __in work the same for related fields when ... skipped "Database doesn't support feature(s): can_distinct_on_fields" test_ticket_23605 (queries.tests.Ticket23605Tests.test_ticket_23605) ... ok test_non_nullable_fk_not_promoted (queries.tests.ValuesJoinPromotionTests.test_non_nullable_fk_not_promoted) ... ok test_ticket_21376 (queries.tests.ValuesJoinPromotionTests.test_ticket_21376) ... ok test_values_no_promotion_for_existing (queries.tests.ValuesJoinPromotionTests.test_values_no_promotion_for_existing) ... ok test_values_in_subquery (queries.tests.ValuesSubqueryTests.test_values_in_subquery) ... ok test_in_query (queries.tests.ToFieldTests.test_in_query) ... ok test_in_subquery (queries.tests.ToFieldTests.test_in_subquery) ... ok test_nested_in_subquery (queries.tests.ToFieldTests.test_nested_in_subquery) ... ok test_recursive_fk (queries.tests.ToFieldTests.test_recursive_fk) ... ok test_recursive_fk_reverse (queries.tests.ToFieldTests.test_recursive_fk_reverse) ... ok test_reverse_in (queries.tests.ToFieldTests.test_reverse_in) ... ok test_single_object (queries.tests.ToFieldTests.test_single_object) ... ok test_single_object_reverse (queries.tests.ToFieldTests.test_single_object_reverse) ... ok test_empty_resultset_sql (queries.tests.WeirdQuerysetSlicingTests.test_empty_resultset_sql) ... ok test_empty_sliced_subquery (queries.tests.WeirdQuerysetSlicingTests.test_empty_sliced_subquery) ... ok test_empty_sliced_subquery_exclude (queries.tests.WeirdQuerysetSlicingTests.test_empty_sliced_subquery_exclude) ... ok test_tickets_7698_10202 (queries.tests.WeirdQuerysetSlicingTests.test_tickets_7698_10202) ... ok test_zero_length_values_slicing (queries.tests.WeirdQuerysetSlicingTests.test_zero_length_values_slicing) ... ok test_render (shortcuts.tests.RenderTests.test_render) ... ok test_render_with_content_type (shortcuts.tests.RenderTests.test_render_with_content_type) ... ok test_render_with_multiple_templates (shortcuts.tests.RenderTests.test_render_with_multiple_templates) ... ok test_render_with_status (shortcuts.tests.RenderTests.test_render_with_status) ... ok test_render_with_using (shortcuts.tests.RenderTests.test_render_with_using) ... ok test_auto (migrations.test_autodetector.MigrationSuggestNameTests.test_auto) ... ok test_none_name (migrations.test_autodetector.MigrationSuggestNameTests.test_none_name) ... ok test_none_name_with_initial_true (migrations.test_autodetector.MigrationSuggestNameTests.test_none_name_with_initial_true) ... ok test_single_operation (migrations.test_autodetector.MigrationSuggestNameTests.test_single_operation) ... ok test_two_create_models (migrations.test_autodetector.MigrationSuggestNameTests.test_two_create_models) ... ok test_two_create_models_with_initial_true (migrations.test_autodetector.MigrationSuggestNameTests.test_two_create_models_with_initial_true) ... ok test_extra_multiple_select_params_values_order_by (queries.tests.ValuesQuerysetTests.test_extra_multiple_select_params_values_order_by) ... ok test_extra_select_params_values_order_in_extra (queries.tests.ValuesQuerysetTests.test_extra_select_params_values_order_in_extra) ... ok test_extra_values (queries.tests.ValuesQuerysetTests.test_extra_values) ... ok test_extra_values_list (queries.tests.ValuesQuerysetTests.test_extra_values_list) ... ok test_extra_values_order_in_extra (queries.tests.ValuesQuerysetTests.test_extra_values_order_in_extra) ... ok test_extra_values_order_multiple (queries.tests.ValuesQuerysetTests.test_extra_values_order_multiple) ... ok test_extra_values_order_twice (queries.tests.ValuesQuerysetTests.test_extra_values_order_twice) ... ok test_field_error_values_list (queries.tests.ValuesQuerysetTests.test_field_error_values_list) ... ok test_flat_extra_values_list (queries.tests.ValuesQuerysetTests.test_flat_extra_values_list) ... ok test_flat_values_list (queries.tests.ValuesQuerysetTests.test_flat_values_list) ... ok test_named_values_list_bad_field_name (queries.tests.ValuesQuerysetTests.test_named_values_list_bad_field_name) ... ok test_named_values_list_expression (queries.tests.ValuesQuerysetTests.test_named_values_list_expression) ... ok test_named_values_list_expression_with_default_alias (queries.tests.ValuesQuerysetTests.test_named_values_list_expression_with_default_alias) ... ok test_named_values_list_flat (queries.tests.ValuesQuerysetTests.test_named_values_list_flat) ... ok test_named_values_list_with_fields (queries.tests.ValuesQuerysetTests.test_named_values_list_with_fields) ... ok test_named_values_list_without_fields (queries.tests.ValuesQuerysetTests.test_named_values_list_without_fields) ... ok test_named_values_pickle (queries.tests.ValuesQuerysetTests.test_named_values_pickle) ... ok test_add_domain (syndication_tests.tests.SyndicationFeedTest.test_add_domain) add_domain() prefixes domains onto the correct URLs. ... ok test_atom_feed (syndication_tests.tests.SyndicationFeedTest.test_atom_feed) Test the structure and content of feeds generated by Atom1Feed. ... ok test_atom_feed_published_and_updated_elements (syndication_tests.tests.SyndicationFeedTest.test_atom_feed_published_and_updated_elements) The published and updated elements are not ... ok test_atom_multiple_enclosures (syndication_tests.tests.SyndicationFeedTest.test_atom_multiple_enclosures) ... ok test_atom_single_enclosure (syndication_tests.tests.SyndicationFeedTest.test_atom_single_enclosure) ... ok test_aware_datetime_conversion (syndication_tests.tests.SyndicationFeedTest.test_aware_datetime_conversion) Datetimes with timezones don't get trodden on. ... ok test_custom_feed_generator (syndication_tests.tests.SyndicationFeedTest.test_custom_feed_generator) ... ok test_feed_generator_language_attribute (syndication_tests.tests.SyndicationFeedTest.test_feed_generator_language_attribute) ... ok test_feed_last_modified_time (syndication_tests.tests.SyndicationFeedTest.test_feed_last_modified_time) Tests the Last-Modified header with aware publication dates. ... ok test_feed_last_modified_time_naive_date (syndication_tests.tests.SyndicationFeedTest.test_feed_last_modified_time_naive_date) Tests the Last-Modified header with naive publication dates. ... ok test_feed_url (syndication_tests.tests.SyndicationFeedTest.test_feed_url) The feed_url can be overridden. ... ok test_get_non_existent_object (syndication_tests.tests.SyndicationFeedTest.test_get_non_existent_object) ... ok test_get_object (syndication_tests.tests.SyndicationFeedTest.test_get_object) ... ok test_item_link_error (syndication_tests.tests.SyndicationFeedTest.test_item_link_error) An ImproperlyConfigured is raised if no link could be found for the ... ok test_latest_post_date (syndication_tests.tests.SyndicationFeedTest.test_latest_post_date) Both the published and updated dates are ... ok test_naive_datetime_conversion (syndication_tests.tests.SyndicationFeedTest.test_naive_datetime_conversion) Datetimes are correctly converted to the local time zone. ... ok test_rss091_feed (syndication_tests.tests.SyndicationFeedTest.test_rss091_feed) Test the structure and content of feeds generated by RssUserland091Feed. ... ok test_rss2_feed (syndication_tests.tests.SyndicationFeedTest.test_rss2_feed) Test the structure and content of feeds generated by Rss201rev2Feed. ... ok test_rss2_feed_guid_permalink_false (syndication_tests.tests.SyndicationFeedTest.test_rss2_feed_guid_permalink_false) Test if the 'isPermaLink' attribute of element of an item ... ok test_rss2_feed_guid_permalink_true (syndication_tests.tests.SyndicationFeedTest.test_rss2_feed_guid_permalink_true) Test if the 'isPermaLink' attribute of element of an item ... ok test_rss2_multiple_enclosures (syndication_tests.tests.SyndicationFeedTest.test_rss2_multiple_enclosures) ... ok test_rss2_single_enclosure (syndication_tests.tests.SyndicationFeedTest.test_rss2_single_enclosure) ... ok test_secure_urls (syndication_tests.tests.SyndicationFeedTest.test_secure_urls) Test URLs are prefixed with https:// when feed is requested over HTTPS. ... ok test_template_context_feed (syndication_tests.tests.SyndicationFeedTest.test_template_context_feed) Custom context data can be passed to templates for title ... ok test_template_feed (syndication_tests.tests.SyndicationFeedTest.test_template_feed) The item title and description can be overridden with templates. ... ok test_title_escaping (syndication_tests.tests.SyndicationFeedTest.test_title_escaping) Titles are escaped correctly in RSS feeds. ... ok test_avoid_infinite_loop_on_too_many_subqueries (queries.tests.Queries1Tests.test_avoid_infinite_loop_on_too_many_subqueries) ... ok test_common_mixed_case_foreign_keys (queries.tests.Queries1Tests.test_common_mixed_case_foreign_keys) Valid query should be generated when fields fetched from joined tables ... ok test_deferred_load_qs_pickling (queries.tests.Queries1Tests.test_deferred_load_qs_pickling) ... ok test_double_exclude (queries.tests.Queries1Tests.test_double_exclude) ... ok test_error_raised_on_filter_with_dictionary (queries.tests.Queries1Tests.test_error_raised_on_filter_with_dictionary) ... ok test_exclude (queries.tests.Queries1Tests.test_exclude) ... ok test_exclude_in (queries.tests.Queries1Tests.test_exclude_in) ... ok test_excluded_intermediary_m2m_table_joined (queries.tests.Queries1Tests.test_excluded_intermediary_m2m_table_joined) ... ok test_field_with_filterable (queries.tests.Queries1Tests.test_field_with_filterable) ... ok test_get_clears_ordering (queries.tests.Queries1Tests.test_get_clears_ordering) get() should clear ordering for optimization purposes. ... ok test_heterogeneous_qs_combination (queries.tests.Queries1Tests.test_heterogeneous_qs_combination) ... ok test_lookup_constraint_fielderror (queries.tests.Queries1Tests.test_lookup_constraint_fielderror) ... ok test_negate_field (queries.tests.Queries1Tests.test_negate_field) ... ok test_nested_exclude (queries.tests.Queries1Tests.test_nested_exclude) ... ok test_order_by_join_unref (queries.tests.Queries1Tests.test_order_by_join_unref) This test is related to the above one, testing that there aren't ... ok test_order_by_raw_column_alias_warning (queries.tests.Queries1Tests.test_order_by_raw_column_alias_warning) ... ok test_order_by_rawsql (queries.tests.Queries1Tests.test_order_by_rawsql) ... ok test_order_by_tables (queries.tests.Queries1Tests.test_order_by_tables) ... ok test_reasonable_number_of_subq_aliases (queries.tests.Queries1Tests.test_reasonable_number_of_subq_aliases) ... ok test_subquery_condition (queries.tests.Queries1Tests.test_subquery_condition) ... ok test_ticket10205 (queries.tests.Queries1Tests.test_ticket10205) ... ok test_ticket10432 (queries.tests.Queries1Tests.test_ticket10432) ... ok test_ticket1050 (queries.tests.Queries1Tests.test_ticket1050) ... ok test_ticket10742 (queries.tests.Queries1Tests.test_ticket10742) ... ok test_ticket17429 (queries.tests.Queries1Tests.test_ticket17429) Meta.ordering=None works the same as Meta.ordering=[] ... ok test_ticket1801 (queries.tests.Queries1Tests.test_ticket1801) ... ok test_ticket19672 (queries.tests.Queries1Tests.test_ticket19672) ... ok test_ticket2091 (queries.tests.Queries1Tests.test_ticket2091) ... ok test_ticket2253 (queries.tests.Queries1Tests.test_ticket2253) ... ok test_ticket2306 (queries.tests.Queries1Tests.test_ticket2306) ... ok test_ticket2400 (queries.tests.Queries1Tests.test_ticket2400) ... ok test_ticket2496 (queries.tests.Queries1Tests.test_ticket2496) ... ok test_ticket3037 (queries.tests.Queries1Tests.test_ticket3037) ... ok test_ticket3141 (queries.tests.Queries1Tests.test_ticket3141) ... ok test_ticket4358 (queries.tests.Queries1Tests.test_ticket4358) ... ok test_ticket4464 (queries.tests.Queries1Tests.test_ticket4464) ... ok test_ticket4510 (queries.tests.Queries1Tests.test_ticket4510) ... ok test_ticket6074 (queries.tests.Queries1Tests.test_ticket6074) ... ok test_ticket6154 (queries.tests.Queries1Tests.test_ticket6154) ... ok test_ticket6981 (queries.tests.Queries1Tests.test_ticket6981) ... ok test_ticket7076 (queries.tests.Queries1Tests.test_ticket7076) ... ok test_ticket7096 (queries.tests.Queries1Tests.test_ticket7096) ... ok test_ticket7098 (queries.tests.Queries1Tests.test_ticket7098) ... ok test_ticket7155 (queries.tests.Queries1Tests.test_ticket7155) ... ok test_ticket7181 (queries.tests.Queries1Tests.test_ticket7181) ... ok test_ticket7235 (queries.tests.Queries1Tests.test_ticket7235) ... ok test_ticket7277 (queries.tests.Queries1Tests.test_ticket7277) ... ok test_ticket7323 (queries.tests.Queries1Tests.test_ticket7323) ... ok test_ticket7378 (queries.tests.Queries1Tests.test_ticket7378) ... ok test_ticket7791 (queries.tests.Queries1Tests.test_ticket7791) ... ok test_ticket7813 (queries.tests.Queries1Tests.test_ticket7813) ... ok test_ticket8439 (queries.tests.Queries1Tests.test_ticket8439) ... ok test_ticket9926 (queries.tests.Queries1Tests.test_ticket9926) ... ok test_ticket9985 (queries.tests.Queries1Tests.test_ticket9985) ... ok test_ticket9997 (queries.tests.Queries1Tests.test_ticket9997) ... ok test_ticket_10790_1 (queries.tests.Queries1Tests.test_ticket_10790_1) ... ok test_ticket_10790_2 (queries.tests.Queries1Tests.test_ticket_10790_2) ... ok test_ticket_10790_3 (queries.tests.Queries1Tests.test_ticket_10790_3) ... ok test_ticket_10790_4 (queries.tests.Queries1Tests.test_ticket_10790_4) ... ok test_ticket_10790_5 (queries.tests.Queries1Tests.test_ticket_10790_5) ... ok test_ticket_10790_6 (queries.tests.Queries1Tests.test_ticket_10790_6) ... ok test_ticket_10790_7 (queries.tests.Queries1Tests.test_ticket_10790_7) ... ok test_ticket_10790_8 (queries.tests.Queries1Tests.test_ticket_10790_8) ... ok test_ticket_10790_combine (queries.tests.Queries1Tests.test_ticket_10790_combine) ... ok test_ticket_20250 (queries.tests.Queries1Tests.test_ticket_20250) ... ok test_tickets_1878_2939 (queries.tests.Queries1Tests.test_tickets_1878_2939) ... ok test_tickets_2076_7256 (queries.tests.Queries1Tests.test_tickets_2076_7256) ... ok test_tickets_2080_3592 (queries.tests.Queries1Tests.test_tickets_2080_3592) ... ok test_tickets_2874_3002 (queries.tests.Queries1Tests.test_tickets_2874_3002) ... ok test_tickets_4088_4306 (queries.tests.Queries1Tests.test_tickets_4088_4306) ... ok test_tickets_5321_7070 (queries.tests.Queries1Tests.test_tickets_5321_7070) ... ok test_tickets_5324_6704 (queries.tests.Queries1Tests.test_tickets_5324_6704) ... ok test_tickets_6180_6203 (queries.tests.Queries1Tests.test_tickets_6180_6203) ... ok test_tickets_7087_12242 (queries.tests.Queries1Tests.test_tickets_7087_12242) ... ok test_tickets_7204_7506 (queries.tests.Queries1Tests.test_tickets_7204_7506) ... ok test_tickets_7448_7707 (queries.tests.Queries1Tests.test_tickets_7448_7707) ... ok test_squashed_name_with_start_migration_name (migrations.test_commands.SquashMigrationsTests.test_squashed_name_with_start_migration_name) --squashed-name specifies the new migration's name. ... ok test_squashed_name_without_start_migration_name (migrations.test_commands.SquashMigrationsTests.test_squashed_name_without_start_migration_name) --squashed-name also works if a start migration is omitted. ... ok test_squashmigrations_initial_attribute (migrations.test_commands.SquashMigrationsTests.test_squashmigrations_initial_attribute) ... ok test_squashmigrations_invalid_start (migrations.test_commands.SquashMigrationsTests.test_squashmigrations_invalid_start) squashmigrations doesn't accept a starting migration after the ending migration. ... ok test_squashmigrations_optimizes (migrations.test_commands.SquashMigrationsTests.test_squashmigrations_optimizes) squashmigrations optimizes operations. ... ok test_squashmigrations_squashes (migrations.test_commands.SquashMigrationsTests.test_squashmigrations_squashes) squashmigrations squashes migrations. ... ok test_squashmigrations_valid_start (migrations.test_commands.SquashMigrationsTests.test_squashmigrations_valid_start) squashmigrations accepts a starting migration. ... ok test_ticket_23799_squashmigrations_no_optimize (migrations.test_commands.SquashMigrationsTests.test_ticket_23799_squashmigrations_no_optimize) squashmigrations --no-optimize doesn't optimize operations. ... ok test_node_not_found_error_repr (migrations.test_exceptions.ExceptionTests.test_node_not_found_error_repr) ... ok test_migrate (migrations.test_deprecated_fields.Tests.test_migrate) ... ok test_backwards_nothing_to_do (migrations.test_executor.ExecutorUnitTests.test_backwards_nothing_to_do) If the current state satisfies the given target, do nothing. ... ok test_minimize_rollbacks (migrations.test_executor.ExecutorUnitTests.test_minimize_rollbacks) Minimize unnecessary rollbacks in connected apps. ... ok test_minimize_rollbacks_branchy (migrations.test_executor.ExecutorUnitTests.test_minimize_rollbacks_branchy) Minimize rollbacks when target has multiple in-app children. ... ok test_circular_graph (migrations.test_graph.GraphTests.test_circular_graph) Tests a circular dependency graph. ... ok test_circular_graph_2 (migrations.test_graph.GraphTests.test_circular_graph_2) ... ok test_complex_graph (migrations.test_graph.GraphTests.test_complex_graph) Tests a complex dependency graph: ... ok test_infinite_loop (migrations.test_graph.GraphTests.test_infinite_loop) Tests a complex dependency graph: ... ok test_iterative_dfs (migrations.test_graph.GraphTests.test_iterative_dfs) ... ok test_iterative_dfs_complexity (migrations.test_graph.GraphTests.test_iterative_dfs_complexity) In a graph with merge migrations, iterative_dfs() traverses each node ... ok test_missing_child_nodes (migrations.test_graph.GraphTests.test_missing_child_nodes) Tests for missing child nodes. ... ok test_missing_parent_nodes (migrations.test_graph.GraphTests.test_missing_parent_nodes) Tests for missing parent nodes. ... ok test_plan_invalid_node (migrations.test_graph.GraphTests.test_plan_invalid_node) Tests for forwards/backwards_plan of nonexistent node. ... ok test_remove_replaced_nodes (migrations.test_graph.GraphTests.test_remove_replaced_nodes) Replaced nodes are properly removed and dependencies remapped. ... ok test_remove_replacement_node (migrations.test_graph.GraphTests.test_remove_replacement_node) A replacement node is properly removed and child dependencies remapped. ... ok test_simple_graph (migrations.test_graph.GraphTests.test_simple_graph) Tests a basic dependency graph: ... ok test_stringify (migrations.test_graph.GraphTests.test_stringify) ... ok test_validate_consistency_dummy (migrations.test_graph.GraphTests.test_validate_consistency_dummy) validate_consistency() raises an error if there's an isolated dummy ... ok test_validate_consistency_missing_child (migrations.test_graph.GraphTests.test_validate_consistency_missing_child) ... ok test_validate_consistency_missing_parent (migrations.test_graph.GraphTests.test_validate_consistency_missing_parent) ... ok test_validate_consistency_no_error (migrations.test_graph.GraphTests.test_validate_consistency_no_error) ... ok test_dummynode_repr (migrations.test_graph.NodeTests.test_dummynode_repr) ... ok test_node_repr (migrations.test_graph.NodeTests.test_node_repr) ... ok test_failing_migration (migrations.test_commands.MakeMigrationsTests.test_failing_migration) ... ok test_files_content (migrations.test_commands.MakeMigrationsTests.test_files_content) ... ok test_makemigration_merge_dry_run (migrations.test_commands.MakeMigrationsTests.test_makemigration_merge_dry_run) makemigrations respects --dry-run option when fixing migration ... ok test_makemigration_merge_dry_run_verbosity_3 (migrations.test_commands.MakeMigrationsTests.test_makemigration_merge_dry_run_verbosity_3) `makemigrations --merge --dry-run` writes the merge migration file to ... ok test_makemigrations_auto_merge_name (migrations.test_commands.MakeMigrationsTests.test_makemigrations_auto_merge_name) ... ok test_makemigrations_auto_now_add_interactive (migrations.test_commands.MakeMigrationsTests.test_makemigrations_auto_now_add_interactive) makemigrations prompts the user when adding auto_now_add to an existing ... ok test_makemigrations_check (migrations.test_commands.MakeMigrationsTests.test_makemigrations_check) makemigrations --check should exit with a non-zero status when ... ok test_makemigrations_conflict_exit (migrations.test_commands.MakeMigrationsTests.test_makemigrations_conflict_exit) makemigrations exits if it detects a conflict. ... ok test_makemigrations_consistency_checks_respect_routers (migrations.test_commands.MakeMigrationsTests.test_makemigrations_consistency_checks_respect_routers) The history consistency checks in makemigrations respect ... ok test_makemigrations_default_merge_name (migrations.test_commands.MakeMigrationsTests.test_makemigrations_default_merge_name) ... ok test_makemigrations_disabled_migrations_for_app (migrations.test_commands.MakeMigrationsTests.test_makemigrations_disabled_migrations_for_app) makemigrations raises a nice error when migrations are disabled for an ... ok test_makemigrations_dry_run (migrations.test_commands.MakeMigrationsTests.test_makemigrations_dry_run) `makemigrations --dry-run` should not ask for defaults. ... ok test_makemigrations_dry_run_verbosity_3 (migrations.test_commands.MakeMigrationsTests.test_makemigrations_dry_run_verbosity_3) Allow `makemigrations --dry-run` to output the migrations file to ... ok test_makemigrations_empty_connections (migrations.test_commands.MakeMigrationsTests.test_makemigrations_empty_connections) ... ok test_makemigrations_empty_migration (migrations.test_commands.MakeMigrationsTests.test_makemigrations_empty_migration) makemigrations properly constructs an empty migration. ... ok test_makemigrations_empty_no_app_specified (migrations.test_commands.MakeMigrationsTests.test_makemigrations_empty_no_app_specified) makemigrations exits if no app is specified with 'empty' mode. ... ok test_makemigrations_handle_merge (migrations.test_commands.MakeMigrationsTests.test_makemigrations_handle_merge) makemigrations properly merges the conflicting migrations with --noinput. ... ok test_makemigrations_inconsistent_history (migrations.test_commands.MakeMigrationsTests.test_makemigrations_inconsistent_history) makemigrations should raise InconsistentMigrationHistory exception if ... ok test_makemigrations_inconsistent_history_db_failure (migrations.test_commands.MakeMigrationsTests.test_makemigrations_inconsistent_history_db_failure) ... ok test_makemigrations_interactive_accept (migrations.test_commands.MakeMigrationsTests.test_makemigrations_interactive_accept) makemigrations enters interactive mode and merges properly. ... ok test_makemigrations_interactive_by_default (migrations.test_commands.MakeMigrationsTests.test_makemigrations_interactive_by_default) The user is prompted to merge by default if there are conflicts and ... ok test_makemigrations_interactive_reject (migrations.test_commands.MakeMigrationsTests.test_makemigrations_interactive_reject) makemigrations enters and exits interactive mode properly. ... ok test_makemigrations_merge_dont_output_dependency_operations (migrations.test_commands.MakeMigrationsTests.test_makemigrations_merge_dont_output_dependency_operations) makemigrations --merge does not output any operations from apps that ... ok test_makemigrations_merge_no_conflict (migrations.test_commands.MakeMigrationsTests.test_makemigrations_merge_no_conflict) makemigrations exits if in merge mode with no conflicts. ... ok test_makemigrations_migration_path_output (migrations.test_commands.MakeMigrationsTests.test_makemigrations_migration_path_output) makemigrations should print the relative paths to the migrations unless ... ok test_makemigrations_migration_path_output_valueerror (migrations.test_commands.MakeMigrationsTests.test_makemigrations_migration_path_output_valueerror) makemigrations prints the absolute path if os.path.relpath() raises a ... ok test_makemigrations_migrations_announce (migrations.test_commands.MakeMigrationsTests.test_makemigrations_migrations_announce) makemigrations announces the migration at the default verbosity level. ... ok test_makemigrations_migrations_modules_nonexistent_toplevel_package (migrations.test_commands.MakeMigrationsTests.test_makemigrations_migrations_modules_nonexistent_toplevel_package) ... ok test_makemigrations_migrations_modules_path_not_exist (migrations.test_commands.MakeMigrationsTests.test_makemigrations_migrations_modules_path_not_exist) makemigrations creates migrations when specifying a custom location ... ok test_makemigrations_no_apps_initial (migrations.test_commands.MakeMigrationsTests.test_makemigrations_no_apps_initial) makemigrations should detect initial is needed on empty migration ... ok test_makemigrations_no_changes (migrations.test_commands.MakeMigrationsTests.test_makemigrations_no_changes) makemigrations exits when there are no changes to an app. ... ok test_makemigrations_no_changes_no_apps (migrations.test_commands.MakeMigrationsTests.test_makemigrations_no_changes_no_apps) makemigrations exits when there are no changes and no apps are specified. ... ok test_makemigrations_no_common_ancestor (migrations.test_commands.MakeMigrationsTests.test_makemigrations_no_common_ancestor) makemigrations fails to merge migrations with no common ancestor. ... ok test_makemigrations_no_init (migrations.test_commands.MakeMigrationsTests.test_makemigrations_no_init) Migration directories without an __init__.py file are allowed. ... ok test_makemigrations_non_interactive_no_field_rename (migrations.test_commands.MakeMigrationsTests.test_makemigrations_non_interactive_no_field_rename) makemigrations adds and removes a possible field rename in ... ok test_makemigrations_non_interactive_no_model_rename (migrations.test_commands.MakeMigrationsTests.test_makemigrations_non_interactive_no_model_rename) makemigrations adds and removes a possible model rename in ... ok test_makemigrations_non_interactive_not_null_addition (migrations.test_commands.MakeMigrationsTests.test_makemigrations_non_interactive_not_null_addition) Non-interactive makemigrations fails when a default is missing on a ... ok test_makemigrations_non_interactive_not_null_alteration (migrations.test_commands.MakeMigrationsTests.test_makemigrations_non_interactive_not_null_alteration) Non-interactive makemigrations fails when a default is missing on a ... ok test_makemigrations_order (migrations.test_commands.MakeMigrationsTests.test_makemigrations_order) makemigrations should recognize number-only migrations (0001.py). ... ok test_makemigrations_unspecified_app_with_conflict_merge (migrations.test_commands.MakeMigrationsTests.test_makemigrations_unspecified_app_with_conflict_merge) makemigrations does not create a merge for an unspecified app even if ... ok test_makemigrations_unspecified_app_with_conflict_no_merge (migrations.test_commands.MakeMigrationsTests.test_makemigrations_unspecified_app_with_conflict_no_merge) makemigrations does not raise a CommandError when an unspecified app ... ok test_makemigrations_with_custom_name (migrations.test_commands.MakeMigrationsTests.test_makemigrations_with_custom_name) makemigrations --name generate a custom migration name. ... ok test_makemigrations_with_invalid_custom_name (migrations.test_commands.MakeMigrationsTests.test_makemigrations_with_invalid_custom_name) ... ok test_invalid (migrations.test_loader.PycLoaderTests.test_invalid) MigrationLoader reraises ImportErrors caused by "bad magic number" pyc ... ok test_valid (migrations.test_loader.PycLoaderTests.test_valid) To support frozen environments, MigrationLoader loads .pyc migrations. ... ok test_reference_field_by_through_fields (migrations.test_operations.FieldOperationTests.test_reference_field_by_through_fields) ... ok test_references_field_by_from_fields (migrations.test_operations.FieldOperationTests.test_references_field_by_from_fields) ... ok test_references_field_by_name (migrations.test_operations.FieldOperationTests.test_references_field_by_name) ... ok test_references_field_by_remote_field_model (migrations.test_operations.FieldOperationTests.test_references_field_by_remote_field_model) ... ok test_references_field_by_through (migrations.test_operations.FieldOperationTests.test_references_field_by_through) ... ok test_references_field_by_to_fields (migrations.test_operations.FieldOperationTests.test_references_field_by_to_fields) ... ok test_references_model (migrations.test_operations.FieldOperationTests.test_references_model) ... ok test_create_model (migrations.test_multidb.MultiDBOperationTests.test_create_model) Test when router doesn't have an opinion (i.e. CreateModel should run). ... ok test_create_model2 (migrations.test_multidb.MultiDBOperationTests.test_create_model2) Test when router returns False (i.e. CreateModel shouldn't run). ... ok test_create_model3 (migrations.test_multidb.MultiDBOperationTests.test_create_model3) Test when router returns True (i.e. CreateModel should run). ... ok test_create_model4 (migrations.test_multidb.MultiDBOperationTests.test_create_model4) Test multiple routers. ... ok test_run_python_migrate_foo_router_with_hints (migrations.test_multidb.MultiDBOperationTests.test_run_python_migrate_foo_router_with_hints) ... ok test_run_python_migrate_foo_router_without_hints (migrations.test_multidb.MultiDBOperationTests.test_run_python_migrate_foo_router_without_hints) ... ok test_run_python_migrate_nothing_router (migrations.test_multidb.MultiDBOperationTests.test_run_python_migrate_nothing_router) ... ok test_run_sql_migrate_foo_router_with_hints (migrations.test_multidb.MultiDBOperationTests.test_run_sql_migrate_foo_router_with_hints) ... ok test_run_sql_migrate_foo_router_without_hints (migrations.test_multidb.MultiDBOperationTests.test_run_sql_migrate_foo_router_without_hints) ... ok test_run_sql_migrate_nothing_router (migrations.test_multidb.MultiDBOperationTests.test_run_sql_migrate_nothing_router) ... ok test_add_field_ignore_swapped (migrations.test_operations.SwappableOperationTests.test_add_field_ignore_swapped) Tests the AddField operation. ... ok test_create_ignore_swapped (migrations.test_operations.SwappableOperationTests.test_create_ignore_swapped) The CreateTable operation ignores swapped models. ... ok test_delete_ignore_swapped (migrations.test_operations.SwappableOperationTests.test_delete_ignore_swapped) Tests the DeleteModel operation ignores swapped models. ... ok test_indexes_ignore_swapped (migrations.test_operations.SwappableOperationTests.test_indexes_ignore_swapped) Add/RemoveIndex operations ignore swapped models. ... ok test_references_model_mixin (migrations.test_operations.TestCreateModel.test_references_model_mixin) ... ok test_add_field_alter_field (migrations.test_optimizer.OptimizerTests.test_add_field_alter_field) AlterField should optimize into AddField. ... ok test_add_field_delete_field (migrations.test_optimizer.OptimizerTests.test_add_field_delete_field) RemoveField should cancel AddField ... ok test_add_field_rename_field (migrations.test_optimizer.OptimizerTests.test_add_field_rename_field) RenameField should optimize into AddField ... ok test_alter_alter_index_model (migrations.test_optimizer.OptimizerTests.test_alter_alter_index_model) ... ok test_alter_alter_owrt_model (migrations.test_optimizer.OptimizerTests.test_alter_alter_owrt_model) ... ok test_alter_alter_table_model (migrations.test_optimizer.OptimizerTests.test_alter_alter_table_model) ... ok test_alter_alter_unique_model (migrations.test_optimizer.OptimizerTests.test_alter_alter_unique_model) ... ok test_alter_field_delete_field (migrations.test_optimizer.OptimizerTests.test_alter_field_delete_field) RemoveField should absorb AlterField ... ok test_alter_field_rename_field (migrations.test_optimizer.OptimizerTests.test_alter_field_rename_field) RenameField should optimize to the other side of AlterField, ... ok test_create_alter_index_delete_model (migrations.test_optimizer.OptimizerTests.test_create_alter_index_delete_model) ... ok test_create_alter_index_field (migrations.test_optimizer.OptimizerTests.test_create_alter_index_field) ... ok test_create_alter_model_options (migrations.test_optimizer.OptimizerTests.test_create_alter_model_options) ... ok test_create_alter_owrt_delete_model (migrations.test_optimizer.OptimizerTests.test_create_alter_owrt_delete_model) ... ok test_create_alter_owrt_field (migrations.test_optimizer.OptimizerTests.test_create_alter_owrt_field) ... ok test_create_alter_unique_delete_model (migrations.test_optimizer.OptimizerTests.test_create_alter_unique_delete_model) ... ok test_create_alter_unique_field (migrations.test_optimizer.OptimizerTests.test_create_alter_unique_field) ... ok test_create_delete_model (migrations.test_optimizer.OptimizerTests.test_create_delete_model) CreateModel and DeleteModel should collapse into nothing. ... ok test_create_model_add_field (migrations.test_optimizer.OptimizerTests.test_create_model_add_field) AddField should optimize into CreateModel. ... ok test_create_model_add_field_not_through_m2m_through (migrations.test_optimizer.OptimizerTests.test_create_model_add_field_not_through_m2m_through) AddField should NOT optimize into CreateModel if it's an M2M using a ... ok test_create_model_alter_field (migrations.test_optimizer.OptimizerTests.test_create_model_alter_field) AlterField should optimize into CreateModel. ... ok test_create_model_and_remove_model_options (migrations.test_optimizer.OptimizerTests.test_create_model_and_remove_model_options) ... ok test_create_model_no_reordering_for_unrelated_fk (migrations.test_optimizer.OptimizerTests.test_create_model_no_reordering_for_unrelated_fk) CreateModel order remains unchanged if the later AddField operation ... ok test_create_model_no_reordering_of_inherited_model (migrations.test_optimizer.OptimizerTests.test_create_model_no_reordering_of_inherited_model) A CreateModel that inherits from another isn't reordered to avoid ... ok test_create_model_remove_field (migrations.test_optimizer.OptimizerTests.test_create_model_remove_field) RemoveField should optimize into CreateModel. ... ok test_create_model_rename_field (migrations.test_optimizer.OptimizerTests.test_create_model_rename_field) RenameField should optimize into CreateModel. ... ok test_create_model_reordering (migrations.test_optimizer.OptimizerTests.test_create_model_reordering) AddField optimizes into CreateModel if it's a FK to a model that's ... ok test_create_model_reordering_circular_fk (migrations.test_optimizer.OptimizerTests.test_create_model_reordering_circular_fk) CreateModel reordering behavior doesn't result in an infinite loop if ... ok test_create_rename_model (migrations.test_optimizer.OptimizerTests.test_create_rename_model) CreateModel should absorb RenameModels. ... ok test_none_app_label (migrations.test_optimizer.OptimizerTests.test_none_app_label) ... ok test_optimize_elidable_operation (migrations.test_optimizer.OptimizerTests.test_optimize_elidable_operation) ... ok test_optimize_through_create (migrations.test_optimizer.OptimizerTests.test_optimize_through_create) We should be able to optimize away create/delete through a create or delete ... ok test_optimize_through_fields (migrations.test_optimizer.OptimizerTests.test_optimize_through_fields) field-level through checking is working. This should manage to collapse ... ok test_rename_model_self (migrations.test_optimizer.OptimizerTests.test_rename_model_self) RenameModels should absorb themselves. ... ok test_single (migrations.test_optimizer.OptimizerTests.test_single) The optimizer does nothing on a single operation, ... ok test_ask_initial_with_disabled_migrations (migrations.test_questioner.QuestionerTests.test_ask_initial_with_disabled_migrations) ... ok test_timedelta_default (migrations.test_questioner.QuestionerTests.test_timedelta_default) ... ok test_abstract_model_children_inherit_indexes (migrations.test_state.ModelStateTests.test_abstract_model_children_inherit_indexes) ... ok test_bound_field_sanity_check (migrations.test_state.ModelStateTests.test_bound_field_sanity_check) ... ok test_create_swappable (migrations.test_state.ModelStateTests.test_create_swappable) Tests making a ProjectState from an Apps with a swappable model ... ok test_create_swappable_from_abstract (migrations.test_state.ModelStateTests.test_create_swappable_from_abstract) A swappable model inheriting from a hierarchy: ... ok test_custom_manager_swappable (migrations.test_state.ModelStateTests.test_custom_manager_swappable) Tests making a ProjectState from unused models with custom managers ... ok test_custom_model_base (migrations.test_state.ModelStateTests.test_custom_model_base) ... ok test_explicit_index_name (migrations.test_state.ModelStateTests.test_explicit_index_name) ... ok test_fields_immutability (migrations.test_state.ModelStateTests.test_fields_immutability) Rendering a model state doesn't alter its internal fields. ... ok test_fields_ordering_equality (migrations.test_state.ModelStateTests.test_fields_ordering_equality) ... ok test_from_model_constraints (migrations.test_state.ModelStateTests.test_from_model_constraints) ... ok test_order_with_respect_to_private_field (migrations.test_state.ModelStateTests.test_order_with_respect_to_private_field) ... ok test_repr (migrations.test_state.ModelStateTests.test_repr) ... ok test_sanity_check_through (migrations.test_state.ModelStateTests.test_sanity_check_through) ... ok test_sanity_check_to (migrations.test_state.ModelStateTests.test_sanity_check_to) ... ok test_sanity_index_name (migrations.test_state.ModelStateTests.test_sanity_index_name) ... ok test_abstract_base (migrations.test_state.RelatedModelsTests.test_abstract_base) ... ok test_base (migrations.test_state.RelatedModelsTests.test_base) ... ok test_base_to_base_fk (migrations.test_state.RelatedModelsTests.test_base_to_base_fk) ... ok test_base_to_subclass_fk (migrations.test_state.RelatedModelsTests.test_base_to_subclass_fk) ... ok test_circle (migrations.test_state.RelatedModelsTests.test_circle) ... ok test_direct_fk (migrations.test_state.RelatedModelsTests.test_direct_fk) ... ok test_direct_hidden_fk (migrations.test_state.RelatedModelsTests.test_direct_hidden_fk) ... ok test_direct_m2m (migrations.test_state.RelatedModelsTests.test_direct_m2m) ... ok test_direct_m2m_self (migrations.test_state.RelatedModelsTests.test_direct_m2m_self) ... ok test_fk_through_proxy (migrations.test_state.RelatedModelsTests.test_fk_through_proxy) ... ok test_generic_fk (migrations.test_state.RelatedModelsTests.test_generic_fk) ... ok test_intermediate_m2m (migrations.test_state.RelatedModelsTests.test_intermediate_m2m) ... ok test_intermediate_m2m_base (migrations.test_state.RelatedModelsTests.test_intermediate_m2m_base) ... ok test_intermediate_m2m_extern_fk (migrations.test_state.RelatedModelsTests.test_intermediate_m2m_extern_fk) ... ok test_intermediate_m2m_self (migrations.test_state.RelatedModelsTests.test_intermediate_m2m_self) ... ok test_multiple_bases (migrations.test_state.RelatedModelsTests.test_multiple_bases) ... ok test_multiple_mixed_bases (migrations.test_state.RelatedModelsTests.test_multiple_mixed_bases) ... ok test_multiple_nested_bases (migrations.test_state.RelatedModelsTests.test_multiple_nested_bases) ... ok test_nested_abstract_base (migrations.test_state.RelatedModelsTests.test_nested_abstract_base) ... ok test_nested_base (migrations.test_state.RelatedModelsTests.test_nested_base) ... ok test_nested_fk (migrations.test_state.RelatedModelsTests.test_nested_fk) ... ok test_nested_proxy_base (migrations.test_state.RelatedModelsTests.test_nested_proxy_base) ... ok test_proxy_base (migrations.test_state.RelatedModelsTests.test_proxy_base) ... ok test_two_sided (migrations.test_state.RelatedModelsTests.test_two_sided) ... ok test_unrelated (migrations.test_state.RelatedModelsTests.test_unrelated) ... ok test_add_relations (migrations.test_state.StateTests.test_add_relations) #24573 - Adding relations to existing models should reload the ... ok test_apps_bulk_update (migrations.test_state.StateTests.test_apps_bulk_update) StateApps.bulk_update() should update apps.ready to False and reset ... ok test_choices_iterator (migrations.test_state.StateTests.test_choices_iterator) #24483 - ProjectState.from_apps should not destructively consume ... ok test_create (migrations.test_state.StateTests.test_create) Tests making a ProjectState from an Apps ... ok test_custom_base_manager (migrations.test_state.StateTests.test_custom_base_manager) ... ok test_custom_default_manager (migrations.test_state.StateTests.test_custom_default_manager) ... ok test_custom_default_manager_added_to_the_model_state (migrations.test_state.StateTests.test_custom_default_manager_added_to_the_model_state) When the default manager of the model is a custom manager, ... ok test_custom_default_manager_named_objects_with_false_migration_flag (migrations.test_state.StateTests.test_custom_default_manager_named_objects_with_false_migration_flag) When a manager is added with a name of 'objects' but it does not ... ok test_dangling_references_throw_error (migrations.test_state.StateTests.test_dangling_references_throw_error) ... ok test_equality (migrations.test_state.StateTests.test_equality) == and != are implemented correctly. ... ok test_ignore_order_wrt (migrations.test_state.StateTests.test_ignore_order_wrt) Makes sure ProjectState doesn't include OrderWrt fields when ... ok test_manager_refer_correct_model_version (migrations.test_state.StateTests.test_manager_refer_correct_model_version) #24147 - Managers refer to the correct version of a ... ok test_no_duplicate_managers (migrations.test_state.StateTests.test_no_duplicate_managers) When a manager is added with `use_in_migrations = True` and a parent ... ok test_real_apps (migrations.test_state.StateTests.test_real_apps) Including real apps can resolve dangling FK errors. ... ok test_reference_mixed_case_app_label (migrations.test_state.StateTests.test_reference_mixed_case_app_label) ... ok test_reload_model_relationship_consistency (migrations.test_state.StateTests.test_reload_model_relationship_consistency) ... ok test_reload_related_model_on_non_relational_fields (migrations.test_state.StateTests.test_reload_related_model_on_non_relational_fields) The model is reloaded even on changes that are not involved in ... ok test_remove_relations (migrations.test_state.StateTests.test_remove_relations) #24225 - Relations between models are updated while ... ok test_render (migrations.test_state.StateTests.test_render) Tests rendering a ProjectState into an Apps. ... ok test_render_model_inheritance (migrations.test_state.StateTests.test_render_model_inheritance) ... ok test_render_model_with_multiple_inheritance (migrations.test_state.StateTests.test_render_model_with_multiple_inheritance) ... ok test_render_project_dependencies (migrations.test_state.StateTests.test_render_project_dependencies) The ProjectState render method correctly renders models ... ok test_render_unique_app_labels (migrations.test_state.StateTests.test_render_unique_app_labels) The ProjectState render method doesn't raise an ... ok test_self_relation (migrations.test_state.StateTests.test_self_relation) #24513 - Modifying an object pointing to itself would cause it to be ... ok test_args_kwargs_signature (migrations.test_writer.OperationWriterTests.test_args_kwargs_signature) ... ok test_args_signature (migrations.test_writer.OperationWriterTests.test_args_signature) ... ok test_empty_signature (migrations.test_writer.OperationWriterTests.test_empty_signature) ... ok test_expand_args_signature (migrations.test_writer.OperationWriterTests.test_expand_args_signature) ... ok test_kwargs_signature (migrations.test_writer.OperationWriterTests.test_kwargs_signature) ... ok test_multiline_args_signature (migrations.test_writer.OperationWriterTests.test_multiline_args_signature) ... ok test_nested_args_signature (migrations.test_writer.OperationWriterTests.test_nested_args_signature) ... ok test_nested_operation_expand_args_signature (migrations.test_writer.OperationWriterTests.test_nested_operation_expand_args_signature) ... ok test_custom_operation (migrations.test_writer.WriterTests.test_custom_operation) ... ok test_deconstruct_class_arguments (migrations.test_writer.WriterTests.test_deconstruct_class_arguments) ... ok test_migration_file_header_comments (migrations.test_writer.WriterTests.test_migration_file_header_comments) Test comments at top of file. ... ok test_migration_path (migrations.test_writer.WriterTests.test_migration_path) ... ok test_models_import_omitted (migrations.test_writer.WriterTests.test_models_import_omitted) django.db.models shouldn't be imported if unused. ... ok test_register_non_serializer (migrations.test_writer.WriterTests.test_register_non_serializer) ... ok test_register_serializer (migrations.test_writer.WriterTests.test_register_serializer) ... ok test_serialize_builtin_types (migrations.test_writer.WriterTests.test_serialize_builtin_types) ... ok test_serialize_builtins (migrations.test_writer.WriterTests.test_serialize_builtins) ... ok test_serialize_choices (migrations.test_writer.WriterTests.test_serialize_choices) ... ok test_serialize_class_based_validators (migrations.test_writer.WriterTests.test_serialize_class_based_validators) Ticket #22943: Test serialization of class-based validators, including ... ok test_serialize_collections (migrations.test_writer.WriterTests.test_serialize_collections) ... ok test_serialize_compiled_regex (migrations.test_writer.WriterTests.test_serialize_compiled_regex) Make sure compiled regex can be serialized. ... ok test_serialize_constants (migrations.test_writer.WriterTests.test_serialize_constants) ... ok test_serialize_datetime (migrations.test_writer.WriterTests.test_serialize_datetime) ... ok test_serialize_empty_nonempty_tuple (migrations.test_writer.WriterTests.test_serialize_empty_nonempty_tuple) Ticket #22679: makemigrations generates invalid code for (an empty ... ok test_serialize_enums (migrations.test_writer.WriterTests.test_serialize_enums) ... ok test_serialize_fields (migrations.test_writer.WriterTests.test_serialize_fields) ... ok test_serialize_frozensets (migrations.test_writer.WriterTests.test_serialize_frozensets) ... ok test_serialize_functions (migrations.test_writer.WriterTests.test_serialize_functions) ... ok test_serialize_functools_partial (migrations.test_writer.WriterTests.test_serialize_functools_partial) ... ok test_serialize_functools_partialmethod (migrations.test_writer.WriterTests.test_serialize_functools_partialmethod) ... ok test_serialize_iterators (migrations.test_writer.WriterTests.test_serialize_iterators) ... ok test_serialize_lazy_objects (migrations.test_writer.WriterTests.test_serialize_lazy_objects) ... ok test_serialize_local_function_reference (migrations.test_writer.WriterTests.test_serialize_local_function_reference) A reference in a local scope can't be serialized. ... ok test_serialize_managers (migrations.test_writer.WriterTests.test_serialize_managers) ... ok test_serialize_multiline_strings (migrations.test_writer.WriterTests.test_serialize_multiline_strings) ... ok test_serialize_nested_class (migrations.test_writer.WriterTests.test_serialize_nested_class) ... ok test_serialize_numbers (migrations.test_writer.WriterTests.test_serialize_numbers) ... ok test_serialize_path_like (migrations.test_writer.WriterTests.test_serialize_path_like) ... ok test_serialize_pathlib (migrations.test_writer.WriterTests.test_serialize_pathlib) ... ok test_serialize_range (migrations.test_writer.WriterTests.test_serialize_range) ... ok test_serialize_set (migrations.test_writer.WriterTests.test_serialize_set) ... ok test_serialize_settings (migrations.test_writer.WriterTests.test_serialize_settings) ... ok test_serialize_strings (migrations.test_writer.WriterTests.test_serialize_strings) ... ok test_serialize_timedelta (migrations.test_writer.WriterTests.test_serialize_timedelta) ... ok test_serialize_type_none (migrations.test_writer.WriterTests.test_serialize_type_none) ... ok test_serialize_unbound_method_reference (migrations.test_writer.WriterTests.test_serialize_unbound_method_reference) An unbound method used within a class body can be serialized. ... ok test_serialize_uuid (migrations.test_writer.WriterTests.test_serialize_uuid) ... ok test_simple_migration (migrations.test_writer.WriterTests.test_simple_migration) Tests serializing a simple migration. ... ok test_sorted_imports (migrations.test_writer.WriterTests.test_sorted_imports) #24155 - Tests ordering of imports. ... ok test_extract_function_traversal (utils_tests.test_archive.TestArchiveInvalid.test_extract_function_traversal) ... ok test_run_loop_catches_stopiteration (utils_tests.test_autoreload.BaseReloaderTests.test_run_loop_catches_stopiteration) ... ok test_run_loop_stop_and_return (utils_tests.test_autoreload.BaseReloaderTests.test_run_loop_stop_and_return) ... ok test_wait_for_apps_ready_checks_for_exception (utils_tests.test_autoreload.BaseReloaderTests.test_wait_for_apps_ready_checks_for_exception) ... ok test_wait_for_apps_ready_without_exception (utils_tests.test_autoreload.BaseReloaderTests.test_wait_for_apps_ready_without_exception) ... ok test_watch_dir_with_unresolvable_path (utils_tests.test_autoreload.BaseReloaderTests.test_watch_dir_with_unresolvable_path) ... ok test_watch_files_with_recursive_glob (utils_tests.test_autoreload.BaseReloaderTests.test_watch_files_with_recursive_glob) ... ok test_watch_with_glob (utils_tests.test_autoreload.BaseReloaderTests.test_watch_with_glob) ... ok test_watchman_available (utils_tests.test_autoreload.GetReloaderTests.test_watchman_available) ... ok test_watchman_unavailable (utils_tests.test_autoreload.GetReloaderTests.test_watchman_unavailable) ... ok test_manage_py (utils_tests.test_autoreload.RestartWithReloaderTests.test_manage_py) ... ok test_python_m_django (utils_tests.test_autoreload.RestartWithReloaderTests.test_python_m_django) ... ok test_calls_start_django (utils_tests.test_autoreload.RunWithReloaderTests.test_calls_start_django) ... ok test_calls_sys_exit (utils_tests.test_autoreload.RunWithReloaderTests.test_calls_sys_exit) ... ok test_swallows_keyboard_interrupt (utils_tests.test_autoreload.RunWithReloaderTests.test_swallows_keyboard_interrupt) ... ok test_check_errors_called (utils_tests.test_autoreload.StartDjangoTests.test_check_errors_called) ... ok test_echo_on_called (utils_tests.test_autoreload.StartDjangoTests.test_echo_on_called) ... ok test_starts_thread_with_args (utils_tests.test_autoreload.StartDjangoTests.test_starts_thread_with_args) ... ok test_watchman_becomes_unavailable (utils_tests.test_autoreload.StartDjangoTests.test_watchman_becomes_unavailable) ... ok test_glob (utils_tests.test_autoreload.StatReloaderTests.test_glob) ... ok test_glob_recursive (utils_tests.test_autoreload.StatReloaderTests.test_glob_recursive) ... ok test_multiple_globs (utils_tests.test_autoreload.StatReloaderTests.test_multiple_globs) ... ok test_multiple_recursive_globs (utils_tests.test_autoreload.StatReloaderTests.test_multiple_recursive_globs) ... ok test_nested_glob_recursive (utils_tests.test_autoreload.StatReloaderTests.test_nested_glob_recursive) ... ok test_overlapping_glob_recursive (utils_tests.test_autoreload.StatReloaderTests.test_overlapping_glob_recursive) ... ok test_overlapping_globs (utils_tests.test_autoreload.StatReloaderTests.test_overlapping_globs) ... ok test_snapshot_files_ignores_missing_files (utils_tests.test_autoreload.StatReloaderTests.test_snapshot_files_ignores_missing_files) ... ok test_snapshot_files_updates (utils_tests.test_autoreload.StatReloaderTests.test_snapshot_files_updates) ... ok test_snapshot_files_with_duplicates (utils_tests.test_autoreload.StatReloaderTests.test_snapshot_files_with_duplicates) ... ok test_tick_does_not_trigger_twice (utils_tests.test_autoreload.StatReloaderTests.test_tick_does_not_trigger_twice) ... ok test_mutates_error_files (utils_tests.test_autoreload.TestCheckErrors.test_mutates_error_files) ... ok test_entrypoint_fallback (utils_tests.test_autoreload.TestChildArguments.test_entrypoint_fallback) ... ok test_exe_fallback (utils_tests.test_autoreload.TestChildArguments.test_exe_fallback) ... ok test_module_no_spec (utils_tests.test_autoreload.TestChildArguments.test_module_no_spec) ... ok test_raises_runtimeerror (utils_tests.test_autoreload.TestChildArguments.test_raises_runtimeerror) ... ok test_run_as_module (utils_tests.test_autoreload.TestChildArguments.test_run_as_module) ... ok test_run_as_non_django_module (utils_tests.test_autoreload.TestChildArguments.test_run_as_non_django_module) ... ok test_warnoptions (utils_tests.test_autoreload.TestChildArguments.test_warnoptions) ... ok test_common_roots (utils_tests.test_autoreload.TestCommonRoots.test_common_roots) ... ok test_bytecode_conversion_to_source (utils_tests.test_autoreload.TestIterModulesAndFiles.test_bytecode_conversion_to_source) .pyc and .pyo files are included in the files list. ... ok test_check_errors (utils_tests.test_autoreload.TestIterModulesAndFiles.test_check_errors) When a file containing an error is imported in a function wrapped by ... ok test_check_errors_catches_all_exceptions (utils_tests.test_autoreload.TestIterModulesAndFiles.test_check_errors_catches_all_exceptions) Since Python may raise arbitrary exceptions when importing code, ... ok test_file_added (utils_tests.test_autoreload.TestIterModulesAndFiles.test_file_added) When a file is added, it's returned by iter_all_python_module_files(). ... ok test_main_module_is_resolved (utils_tests.test_autoreload.TestIterModulesAndFiles.test_main_module_is_resolved) ... ok test_main_module_without_file_is_not_resolved (utils_tests.test_autoreload.TestIterModulesAndFiles.test_main_module_without_file_is_not_resolved) ... ok test_module_without_spec (utils_tests.test_autoreload.TestIterModulesAndFiles.test_module_without_spec) ... ok test_path_with_embedded_null_bytes (utils_tests.test_autoreload.TestIterModulesAndFiles.test_path_with_embedded_null_bytes) ... ok test_paths_are_pathlib_instances (utils_tests.test_autoreload.TestIterModulesAndFiles.test_paths_are_pathlib_instances) ... ok test_weakref_in_sys_module (utils_tests.test_autoreload.TestIterModulesAndFiles.test_weakref_in_sys_module) iter_all_python_module_file() ignores weakref modules. ... ok test_zip_reload (utils_tests.test_autoreload.TestIterModulesAndFiles.test_zip_reload) Modules imported from zipped files have their archive location included ... ok test_no_exception (utils_tests.test_autoreload.TestRaiseLastException.test_no_exception) ... ok test_raises_custom_exception (utils_tests.test_autoreload.TestRaiseLastException.test_raises_custom_exception) ... ok test_raises_exception (utils_tests.test_autoreload.TestRaiseLastException.test_raises_exception) ... ok test_raises_exception_with_context (utils_tests.test_autoreload.TestRaiseLastException.test_raises_exception_with_context) ... ok test_sys_paths_absolute (utils_tests.test_autoreload.TestSysPathDirectories.test_sys_paths_absolute) ... ok test_sys_paths_directories (utils_tests.test_autoreload.TestSysPathDirectories.test_sys_paths_directories) ... ok test_sys_paths_non_existing (utils_tests.test_autoreload.TestSysPathDirectories.test_sys_paths_non_existing) ... ok test_sys_paths_with_directories (utils_tests.test_autoreload.TestSysPathDirectories.test_sys_paths_with_directories) ... ok test_is_django_module (utils_tests.test_autoreload.TestUtilities.test_is_django_module) ... ok test_is_django_path (utils_tests.test_autoreload.TestUtilities.test_is_django_path) ... ok test_check_availability (utils_tests.test_autoreload.WatchmanReloaderTests.test_check_availability) ... skipped 'Watchman unavailable: pywatchman not installed.' test_check_availability_lower_version (utils_tests.test_autoreload.WatchmanReloaderTests.test_check_availability_lower_version) ... skipped 'Watchman unavailable: pywatchman not installed.' test_check_server_status (utils_tests.test_autoreload.WatchmanReloaderTests.test_check_server_status) ... skipped 'Watchman unavailable: pywatchman not installed.' test_check_server_status_raises_error (utils_tests.test_autoreload.WatchmanReloaderTests.test_check_server_status_raises_error) ... skipped 'Watchman unavailable: pywatchman not installed.' test_glob (utils_tests.test_autoreload.WatchmanReloaderTests.test_glob) ... skipped 'Watchman unavailable: pywatchman not installed.' test_glob_recursive (utils_tests.test_autoreload.WatchmanReloaderTests.test_glob_recursive) ... skipped 'Watchman unavailable: pywatchman not installed.' test_multiple_globs (utils_tests.test_autoreload.WatchmanReloaderTests.test_multiple_globs) ... skipped 'Watchman unavailable: pywatchman not installed.' test_multiple_recursive_globs (utils_tests.test_autoreload.WatchmanReloaderTests.test_multiple_recursive_globs) ... skipped 'Watchman unavailable: pywatchman not installed.' test_nested_glob_recursive (utils_tests.test_autoreload.WatchmanReloaderTests.test_nested_glob_recursive) ... skipped 'Watchman unavailable: pywatchman not installed.' test_overlapping_glob_recursive (utils_tests.test_autoreload.WatchmanReloaderTests.test_overlapping_glob_recursive) ... skipped 'Watchman unavailable: pywatchman not installed.' test_overlapping_globs (utils_tests.test_autoreload.WatchmanReloaderTests.test_overlapping_globs) ... skipped 'Watchman unavailable: pywatchman not installed.' test_pywatchman_not_available (utils_tests.test_autoreload.WatchmanReloaderTests.test_pywatchman_not_available) ... skipped 'Watchman unavailable: pywatchman not installed.' test_setting_timeout_from_environment_variable (utils_tests.test_autoreload.WatchmanReloaderTests.test_setting_timeout_from_environment_variable) ... skipped 'Watchman unavailable: pywatchman not installed.' test_update_watches_raises_exceptions (utils_tests.test_autoreload.WatchmanReloaderTests.test_update_watches_raises_exceptions) ... skipped 'Watchman unavailable: pywatchman not installed.' test_watch_glob_ignores_non_existing_directories_two_levels (utils_tests.test_autoreload.WatchmanReloaderTests.test_watch_glob_ignores_non_existing_directories_two_levels) ... skipped 'Watchman unavailable: pywatchman not installed.' test_watch_glob_multiple_patterns (utils_tests.test_autoreload.WatchmanReloaderTests.test_watch_glob_multiple_patterns) ... skipped 'Watchman unavailable: pywatchman not installed.' test_watch_glob_uses_existing_parent_directories (utils_tests.test_autoreload.WatchmanReloaderTests.test_watch_glob_uses_existing_parent_directories) ... skipped 'Watchman unavailable: pywatchman not installed.' test_watched_roots_contains_directory_globs (utils_tests.test_autoreload.WatchmanReloaderTests.test_watched_roots_contains_directory_globs) ... skipped 'Watchman unavailable: pywatchman not installed.' test_watched_roots_contains_files (utils_tests.test_autoreload.WatchmanReloaderTests.test_watched_roots_contains_files) ... skipped 'Watchman unavailable: pywatchman not installed.' test_watched_roots_contains_sys_path (utils_tests.test_autoreload.WatchmanReloaderTests.test_watched_roots_contains_sys_path) ... skipped 'Watchman unavailable: pywatchman not installed.' test_create_connection (utils_tests.test_connection.BaseConnectionHandlerTests.test_create_connection) ... ok test_get_random_string (utils_tests.test_crypto.DeprecationTests.test_get_random_string) ... ok test_get_random_string_warning (utils_tests.test_crypto.DeprecationTests.test_get_random_string_warning) ... ok test_constant_time_compare (utils_tests.test_crypto.TestUtilsCryptoMisc.test_constant_time_compare) ... ok test_invalid_algorithm (utils_tests.test_crypto.TestUtilsCryptoMisc.test_invalid_algorithm) ... ok test_salted_hmac (utils_tests.test_crypto.TestUtilsCryptoMisc.test_salted_hmac) ... ok test_copy (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_copy) ... ok test_create_with_invalid_key (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_create_with_invalid_key) ... ok test_create_with_invalid_values (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_create_with_invalid_values) ... ok test_del (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_del) ... ok test_dict (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_dict) ... ok test_equal (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_equal) ... ok test_getitem (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_getitem) ... ok test_in (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_in) ... ok test_items (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_items) ... ok test_list (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_list) ... ok test_repr (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_repr) ... ok test_set (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_set) ... ok test_str (utils_tests.test_datastructures.CaseInsensitiveMappingTests.test_str) ... ok test_dictwrapper (utils_tests.test_datastructures.DictWrapperTests.test_dictwrapper) ... ok test_custom_warning (utils_tests.test_datastructures.ImmutableListTests.test_custom_warning) ... ok test_sort (utils_tests.test_datastructures.ImmutableListTests.test_sort) ... ok test_appendlist (utils_tests.test_datastructures.MultiValueDictTests.test_appendlist) ... ok test_copy (utils_tests.test_datastructures.MultiValueDictTests.test_copy) ... ok test_deepcopy (utils_tests.test_datastructures.MultiValueDictTests.test_deepcopy) ... ok test_dict_translation (utils_tests.test_datastructures.MultiValueDictTests.test_dict_translation) ... ok test_getlist_default (utils_tests.test_datastructures.MultiValueDictTests.test_getlist_default) ... ok test_getlist_doesnt_mutate (utils_tests.test_datastructures.MultiValueDictTests.test_getlist_doesnt_mutate) ... ok test_getlist_none_empty_values (utils_tests.test_datastructures.MultiValueDictTests.test_getlist_none_empty_values) ... ok test_internal_getlist_does_mutate (utils_tests.test_datastructures.MultiValueDictTests.test_internal_getlist_does_mutate) ... ok test_multivaluedict (utils_tests.test_datastructures.MultiValueDictTests.test_multivaluedict) ... ok test_pickle (utils_tests.test_datastructures.MultiValueDictTests.test_pickle) ... ok test_repr (utils_tests.test_datastructures.MultiValueDictTests.test_repr) ... ok test_setdefault (utils_tests.test_datastructures.MultiValueDictTests.test_setdefault) ... ok test_setitem (utils_tests.test_datastructures.MultiValueDictTests.test_setitem) ... ok test_update_dict_arg (utils_tests.test_datastructures.MultiValueDictTests.test_update_dict_arg) ... ok test_update_kwargs (utils_tests.test_datastructures.MultiValueDictTests.test_update_kwargs) ... ok test_update_multivaluedict_arg (utils_tests.test_datastructures.MultiValueDictTests.test_update_multivaluedict_arg) ... ok test_update_no_args (utils_tests.test_datastructures.MultiValueDictTests.test_update_no_args) ... ok test_update_raises_correct_exceptions (utils_tests.test_datastructures.MultiValueDictTests.test_update_raises_correct_exceptions) ... ok test_update_too_many_args (utils_tests.test_datastructures.MultiValueDictTests.test_update_too_many_args) ... ok test_update_with_empty_iterable (utils_tests.test_datastructures.MultiValueDictTests.test_update_with_empty_iterable) ... ok test_update_with_iterable_of_pairs (utils_tests.test_datastructures.MultiValueDictTests.test_update_with_iterable_of_pairs) ... ok test_bool (utils_tests.test_datastructures.OrderedSetTests.test_bool) ... ok test_contains (utils_tests.test_datastructures.OrderedSetTests.test_contains) ... ok test_discard (utils_tests.test_datastructures.OrderedSetTests.test_discard) ... ok test_init_with_iterable (utils_tests.test_datastructures.OrderedSetTests.test_init_with_iterable) ... ok test_len (utils_tests.test_datastructures.OrderedSetTests.test_len) ... ok test_remove (utils_tests.test_datastructures.OrderedSetTests.test_remove) ... ok test_am_pm (utils_tests.test_dateformat.DateFormatTests.test_am_pm) ... ok test_date (utils_tests.test_dateformat.DateFormatTests.test_date) ... ok test_date_formats (utils_tests.test_dateformat.DateFormatTests.test_date_formats) ... ok test_dateformat (utils_tests.test_dateformat.DateFormatTests.test_dateformat) ... ok test_datetime_with_local_tzinfo (utils_tests.test_dateformat.DateFormatTests.test_datetime_with_local_tzinfo) ... ok test_datetime_with_tzinfo (utils_tests.test_dateformat.DateFormatTests.test_datetime_with_tzinfo) ... ok test_day_of_year_leap (utils_tests.test_dateformat.DateFormatTests.test_day_of_year_leap) ... ok test_empty_format (utils_tests.test_dateformat.DateFormatTests.test_empty_format) ... ok test_epoch (utils_tests.test_dateformat.DateFormatTests.test_epoch) ... ok test_futuredates (utils_tests.test_dateformat.DateFormatTests.test_futuredates) ... ok test_invalid_time_format_specifiers (utils_tests.test_dateformat.DateFormatTests.test_invalid_time_format_specifiers) ... ok test_microsecond (utils_tests.test_dateformat.DateFormatTests.test_microsecond) ... ok test_naive_ambiguous_datetime (utils_tests.test_dateformat.DateFormatTests.test_naive_ambiguous_datetime) ... ok test_naive_datetime (utils_tests.test_dateformat.DateFormatTests.test_naive_datetime) ... ok test_r_format_with_non_en_locale (utils_tests.test_dateformat.DateFormatTests.test_r_format_with_non_en_locale) ... ok test_time_formats (utils_tests.test_dateformat.DateFormatTests.test_time_formats) ... ok test_timezones (utils_tests.test_dateformat.DateFormatTests.test_timezones) ... ok test_twelve_hour_format (utils_tests.test_dateformat.DateFormatTests.test_twelve_hour_format) ... ok test_year_before_1000 (utils_tests.test_dateformat.DateFormatTests.test_year_before_1000) ... ok test_compare_datetimes (utils_tests.test_datetime_safe.DatetimeTests.test_compare_datetimes) ... ok test_safe_strftime (utils_tests.test_datetime_safe.DatetimeTests.test_safe_strftime) ... ok test_zero_padding (utils_tests.test_datetime_safe.DatetimeTests.test_zero_padding) Regression for #12524 ... ok test_callable_process_view_middleware (utils_tests.test_decorators.DecoratorFromMiddlewareTests.test_callable_process_view_middleware) Test a middleware that implements process_view, operating on a callable class. ... ok test_full_dec_normal (utils_tests.test_decorators.DecoratorFromMiddlewareTests.test_full_dec_normal) All methods of middleware are called for normal HttpResponses ... ok test_full_dec_templateresponse (utils_tests.test_decorators.DecoratorFromMiddlewareTests.test_full_dec_templateresponse) All methods of middleware are called for TemplateResponses in ... ok test_process_view_middleware (utils_tests.test_decorators.DecoratorFromMiddlewareTests.test_process_view_middleware) Test a middleware that implements process_view. ... ok test_force_bytes_encoding (utils_tests.test_encoding.TestEncodingUtils.test_force_bytes_encoding) ... ok test_force_bytes_exception (utils_tests.test_encoding.TestEncodingUtils.test_force_bytes_exception) force_bytes knows how to convert to bytes an exception ... ok test_force_bytes_memory_view (utils_tests.test_encoding.TestEncodingUtils.test_force_bytes_memory_view) ... ok test_force_bytes_strings_only (utils_tests.test_encoding.TestEncodingUtils.test_force_bytes_strings_only) ... ok test_force_str_DjangoUnicodeDecodeError (utils_tests.test_encoding.TestEncodingUtils.test_force_str_DjangoUnicodeDecodeError) ... ok test_force_str_exception (utils_tests.test_encoding.TestEncodingUtils.test_force_str_exception) Broken __str__ actually raises an error. ... ok test_force_str_lazy (utils_tests.test_encoding.TestEncodingUtils.test_force_str_lazy) ... ok test_get_default_encoding (utils_tests.test_encoding.TestEncodingUtils.test_get_default_encoding) ... ok test_repercent_broken_unicode_recursion_error (utils_tests.test_encoding.TestEncodingUtils.test_repercent_broken_unicode_recursion_error) ... ok test_smart_bytes (utils_tests.test_encoding.TestEncodingUtils.test_smart_bytes) ... ok test_smart_str (utils_tests.test_encoding.TestEncodingUtils.test_smart_str) ... ok test_force_text (utils_tests.test_encoding_deprecations.TestDeprecatedEncodingUtils.test_force_text) ... ok test_smart_text (utils_tests.test_encoding_deprecations.TestDeprecatedEncodingUtils.test_smart_text) ... ok test_atom1_mime_type (utils_tests.test_feedgenerator.FeedgeneratorTests.test_atom1_mime_type) Atom MIME type has UTF8 Charset parameter set ... ok test_atom_add_item (utils_tests.test_feedgenerator.FeedgeneratorTests.test_atom_add_item) ... ok test_deterministic_attribute_order (utils_tests.test_feedgenerator.FeedgeneratorTests.test_deterministic_attribute_order) ... ok test_feed_with_feed_url_gets_rendered_with_atom_link (utils_tests.test_feedgenerator.FeedgeneratorTests.test_feed_with_feed_url_gets_rendered_with_atom_link) ... ok test_feed_without_feed_url_gets_rendered_without_atom_link (utils_tests.test_feedgenerator.FeedgeneratorTests.test_feed_without_feed_url_gets_rendered_without_atom_link) ... ok test_get_tag_uri (utils_tests.test_feedgenerator.FeedgeneratorTests.test_get_tag_uri) get_tag_uri() correctly generates TagURIs. ... ok test_get_tag_uri_with_port (utils_tests.test_feedgenerator.FeedgeneratorTests.test_get_tag_uri_with_port) get_tag_uri() correctly generates TagURIs from URLs with port numbers. ... ok test_latest_post_date_returns_utc_time (utils_tests.test_feedgenerator.FeedgeneratorTests.test_latest_post_date_returns_utc_time) ... ok test_rfc2822_date (utils_tests.test_feedgenerator.FeedgeneratorTests.test_rfc2822_date) rfc2822_date() correctly formats datetime objects. ... ok test_rfc2822_date_with_timezone (utils_tests.test_feedgenerator.FeedgeneratorTests.test_rfc2822_date_with_timezone) rfc2822_date() correctly formats datetime objects with tzinfo. ... ok test_rfc2822_date_without_time (utils_tests.test_feedgenerator.FeedgeneratorTests.test_rfc2822_date_without_time) rfc2822_date() correctly formats date objects. ... ok test_rfc3339_date (utils_tests.test_feedgenerator.FeedgeneratorTests.test_rfc3339_date) rfc3339_date() correctly formats datetime objects. ... ok test_rfc3339_date_with_timezone (utils_tests.test_feedgenerator.FeedgeneratorTests.test_rfc3339_date_with_timezone) rfc3339_date() correctly formats datetime objects with tzinfo. ... ok test_rfc3339_date_without_time (utils_tests.test_feedgenerator.FeedgeneratorTests.test_rfc3339_date_without_time) rfc3339_date() correctly formats date objects. ... ok test_rss_mime_type (utils_tests.test_feedgenerator.FeedgeneratorTests.test_rss_mime_type) RSS MIME type has UTF8 Charset parameter set ... ok test_cached_property (utils_tests.test_functional.FunctionalTests.test_cached_property) cached_property caches its value and behaves like a property. ... ok test_cached_property_auto_name (utils_tests.test_functional.FunctionalTests.test_cached_property_auto_name) cached_property caches its value and behaves like a property ... ok test_cached_property_reuse_different_names (utils_tests.test_functional.FunctionalTests.test_cached_property_reuse_different_names) Disallow this case because the decorated function wouldn't be cached. ... ok test_cached_property_reuse_same_name (utils_tests.test_functional.FunctionalTests.test_cached_property_reuse_same_name) Reusing a cached_property on different classes under the same name is ... ok test_cached_property_set_name_not_called (utils_tests.test_functional.FunctionalTests.test_cached_property_set_name_not_called) ... ok test_classproperty_getter (utils_tests.test_functional.FunctionalTests.test_classproperty_getter) ... ok test_classproperty_override_getter (utils_tests.test_functional.FunctionalTests.test_classproperty_override_getter) ... ok test_lazy (utils_tests.test_functional.FunctionalTests.test_lazy) ... ok test_lazy_add (utils_tests.test_functional.FunctionalTests.test_lazy_add) ... ok test_lazy_base_class (utils_tests.test_functional.FunctionalTests.test_lazy_base_class) lazy also finds base class methods in the proxy object ... ok test_lazy_base_class_override (utils_tests.test_functional.FunctionalTests.test_lazy_base_class_override) lazy finds the correct (overridden) method implementation ... ok test_lazy_class_preparation_caching (utils_tests.test_functional.FunctionalTests.test_lazy_class_preparation_caching) ... ok test_lazy_equality (utils_tests.test_functional.FunctionalTests.test_lazy_equality) == and != work correctly for Promises. ... ok test_lazy_object_to_string (utils_tests.test_functional.FunctionalTests.test_lazy_object_to_string) ... ok test_lazy_repr_bytes (utils_tests.test_functional.FunctionalTests.test_lazy_repr_bytes) ... ok test_lazy_repr_int (utils_tests.test_functional.FunctionalTests.test_lazy_repr_int) ... ok test_lazy_repr_text (utils_tests.test_functional.FunctionalTests.test_lazy_repr_text) ... ok test_count_equal (utils_tests.test_hashable.TestHashable.test_count_equal) ... ok test_equal (utils_tests.test_hashable.TestHashable.test_equal) ... ok test_unhashable (utils_tests.test_hashable.TestHashable.test_unhashable) ... ok test_conditional_escape (utils_tests.test_html.TestUtilsHtml.test_conditional_escape) ... ok test_escape (utils_tests.test_html.TestUtilsHtml.test_escape) ... ok test_escapejs (utils_tests.test_html.TestUtilsHtml.test_escapejs) ... ok test_format_html (utils_tests.test_html.TestUtilsHtml.test_format_html) ... ok test_html_safe (utils_tests.test_html.TestUtilsHtml.test_html_safe) ... ok test_html_safe_defines_html_error (utils_tests.test_html.TestUtilsHtml.test_html_safe_defines_html_error) ... ok test_html_safe_doesnt_define_str (utils_tests.test_html.TestUtilsHtml.test_html_safe_doesnt_define_str) ... ok test_html_safe_subclass (utils_tests.test_html.TestUtilsHtml.test_html_safe_subclass) ... ok test_json_script (utils_tests.test_html.TestUtilsHtml.test_json_script) ... ok test_linebreaks (utils_tests.test_html.TestUtilsHtml.test_linebreaks) ... ok test_smart_urlquote (utils_tests.test_html.TestUtilsHtml.test_smart_urlquote) ... ok test_strip_spaces_between_tags (utils_tests.test_html.TestUtilsHtml.test_strip_spaces_between_tags) ... ok test_strip_tags (utils_tests.test_html.TestUtilsHtml.test_strip_tags) ... ok test_strip_tags_files (utils_tests.test_html.TestUtilsHtml.test_strip_tags_files) ... ok test_urlize (utils_tests.test_html.TestUtilsHtml.test_urlize) ... ok test_urlize_unchanged_inputs (utils_tests.test_html.TestUtilsHtml.test_urlize_unchanged_inputs) ... ok test_input_too_large (utils_tests.test_http.Base36IntTests.test_input_too_large) ... ok test_invalid_literal (utils_tests.test_http.Base36IntTests.test_invalid_literal) ... ok test_negative_input (utils_tests.test_http.Base36IntTests.test_negative_input) ... ok test_roundtrip (utils_tests.test_http.Base36IntTests.test_roundtrip) ... ok test_to_base36_errors (utils_tests.test_http.Base36IntTests.test_to_base36_errors) ... ok test_to_int_errors (utils_tests.test_http.Base36IntTests.test_to_int_errors) ... ok test_values (utils_tests.test_http.Base36IntTests.test_values) ... ok test_allowed_hosts_str (utils_tests.test_http.IsSafeURLTests.test_allowed_hosts_str) ... ok test_bad_urls (utils_tests.test_http.IsSafeURLTests.test_bad_urls) ... ok test_basic_auth (utils_tests.test_http.IsSafeURLTests.test_basic_auth) ... ok test_good_urls (utils_tests.test_http.IsSafeURLTests.test_good_urls) ... ok test_is_safe_url_deprecated (utils_tests.test_http.IsSafeURLTests.test_is_safe_url_deprecated) ... ok test_no_allowed_hosts (utils_tests.test_http.IsSafeURLTests.test_no_allowed_hosts) ... ok test_secure_param_https_urls (utils_tests.test_http.IsSafeURLTests.test_secure_param_https_urls) ... ok test_secure_param_non_https_urls (utils_tests.test_http.IsSafeURLTests.test_secure_param_non_https_urls) ... ok test_custom_iterable_not_doseq (utils_tests.test_http.URLEncodeTests.test_custom_iterable_not_doseq) ... ok test_dict (utils_tests.test_http.URLEncodeTests.test_dict) ... ok test_dict_containing_empty_sequence_doseq (utils_tests.test_http.URLEncodeTests.test_dict_containing_empty_sequence_doseq) ... ok test_dict_containing_sequence_doseq (utils_tests.test_http.URLEncodeTests.test_dict_containing_sequence_doseq) ... ok test_dict_containing_sequence_not_doseq (utils_tests.test_http.URLEncodeTests.test_dict_containing_sequence_not_doseq) ... ok test_dict_containing_tuple_not_doseq (utils_tests.test_http.URLEncodeTests.test_dict_containing_tuple_not_doseq) ... ok test_dict_with_bytearray (utils_tests.test_http.URLEncodeTests.test_dict_with_bytearray) ... ok test_dict_with_bytes_values (utils_tests.test_http.URLEncodeTests.test_dict_with_bytes_values) ... ok test_dict_with_sequence_of_bytes (utils_tests.test_http.URLEncodeTests.test_dict_with_sequence_of_bytes) ... ok test_generator (utils_tests.test_http.URLEncodeTests.test_generator) ... ok test_multivaluedict (utils_tests.test_http.URLEncodeTests.test_multivaluedict) ... ok test_none (utils_tests.test_http.URLEncodeTests.test_none) ... ok test_none_in_generator (utils_tests.test_http.URLEncodeTests.test_none_in_generator) ... ok test_none_in_sequence (utils_tests.test_http.URLEncodeTests.test_none_in_sequence) ... ok test_tuples (utils_tests.test_http.URLEncodeTests.test_tuples) ... ok test_case_0 (utils_tests.test_jslex.JsToCForGettextTest.test_case_0) ... ok test_case_1 (utils_tests.test_jslex.JsToCForGettextTest.test_case_1) ... ok test_case_2 (utils_tests.test_jslex.JsToCForGettextTest.test_case_2) ... ok test_case_3 (utils_tests.test_jslex.JsToCForGettextTest.test_case_3) ... ok test_case_4 (utils_tests.test_jslex.JsToCForGettextTest.test_case_4) ... ok test_case_5 (utils_tests.test_jslex.JsToCForGettextTest.test_case_5) ... ok test_case_6 (utils_tests.test_jslex.JsToCForGettextTest.test_case_6) ... ok test_case_7 (utils_tests.test_jslex.JsToCForGettextTest.test_case_7) ... ok test_case_0 (utils_tests.test_jslex.JsTokensTest.test_case_0) ... ok test_case_1 (utils_tests.test_jslex.JsTokensTest.test_case_1) ... ok test_case_10 (utils_tests.test_jslex.JsTokensTest.test_case_10) ... ok test_case_11 (utils_tests.test_jslex.JsTokensTest.test_case_11) ... ok test_case_12 (utils_tests.test_jslex.JsTokensTest.test_case_12) ... ok test_case_13 (utils_tests.test_jslex.JsTokensTest.test_case_13) ... ok test_case_14 (utils_tests.test_jslex.JsTokensTest.test_case_14) ... ok test_case_15 (utils_tests.test_jslex.JsTokensTest.test_case_15) ... ok test_case_16 (utils_tests.test_jslex.JsTokensTest.test_case_16) ... ok test_case_17 (utils_tests.test_jslex.JsTokensTest.test_case_17) ... ok test_case_18 (utils_tests.test_jslex.JsTokensTest.test_case_18) ... ok test_case_19 (utils_tests.test_jslex.JsTokensTest.test_case_19) ... ok test_case_2 (utils_tests.test_jslex.JsTokensTest.test_case_2) ... ok test_case_20 (utils_tests.test_jslex.JsTokensTest.test_case_20) ... ok test_case_21 (utils_tests.test_jslex.JsTokensTest.test_case_21) ... ok test_case_22 (utils_tests.test_jslex.JsTokensTest.test_case_22) ... ok test_case_23 (utils_tests.test_jslex.JsTokensTest.test_case_23) ... ok test_case_24 (utils_tests.test_jslex.JsTokensTest.test_case_24) ... ok test_case_25 (utils_tests.test_jslex.JsTokensTest.test_case_25) ... ok test_case_26 (utils_tests.test_jslex.JsTokensTest.test_case_26) ... ok test_case_27 (utils_tests.test_jslex.JsTokensTest.test_case_27) ... ok test_case_28 (utils_tests.test_jslex.JsTokensTest.test_case_28) ... ok test_case_29 (utils_tests.test_jslex.JsTokensTest.test_case_29) ... ok test_case_3 (utils_tests.test_jslex.JsTokensTest.test_case_3) ... ok test_case_30 (utils_tests.test_jslex.JsTokensTest.test_case_30) ... ok test_case_31 (utils_tests.test_jslex.JsTokensTest.test_case_31) ... ok test_case_32 (utils_tests.test_jslex.JsTokensTest.test_case_32) ... ok test_case_4 (utils_tests.test_jslex.JsTokensTest.test_case_4) ... ok test_case_5 (utils_tests.test_jslex.JsTokensTest.test_case_5) ... ok test_case_6 (utils_tests.test_jslex.JsTokensTest.test_case_6) ... ok test_case_7 (utils_tests.test_jslex.JsTokensTest.test_case_7) ... ok test_case_8 (utils_tests.test_jslex.JsTokensTest.test_case_8) ... ok test_case_9 (utils_tests.test_jslex.JsTokensTest.test_case_9) ... ok test_autodiscover_modules_found (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_autodiscover_modules_found) ... ok test_autodiscover_modules_found_but_bad_module (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_autodiscover_modules_found_but_bad_module) ... ok test_autodiscover_modules_not_found (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_autodiscover_modules_not_found) ... ok test_autodiscover_modules_several_found (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_autodiscover_modules_several_found) ... ok test_autodiscover_modules_several_found_with_registry (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_autodiscover_modules_several_found_with_registry) ... ok test_autodiscover_modules_several_one_bad_module (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_autodiscover_modules_several_one_bad_module) ... ok test_validate_registry_keeps_intact (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_validate_registry_keeps_intact) ... ok test_validate_registry_resets_after_erroneous_module (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_validate_registry_resets_after_erroneous_module) ... ok test_validate_registry_resets_after_missing_module (utils_tests.test_module_loading.AutodiscoverModulesTestCase.test_validate_registry_resets_after_missing_module) ... ok test_import_string (utils_tests.test_module_loading.ModuleImportTests.test_import_string) ... ok test_decimal_numbers (utils_tests.test_numberformat.TestNumberFormat.test_decimal_numbers) ... ok test_decimal_subclass (utils_tests.test_numberformat.TestNumberFormat.test_decimal_subclass) ... ok test_float_numbers (utils_tests.test_numberformat.TestNumberFormat.test_float_numbers) ... ok test_format_number (utils_tests.test_numberformat.TestNumberFormat.test_format_number) ... ok test_format_string (utils_tests.test_numberformat.TestNumberFormat.test_format_string) ... ok test_large_number (utils_tests.test_numberformat.TestNumberFormat.test_large_number) ... ok test_add_lazy_safe_text_and_safe_text (utils_tests.test_safestring.SafeStringTest.test_add_lazy_safe_text_and_safe_text) ... ok test_mark_safe (utils_tests.test_safestring.SafeStringTest.test_mark_safe) ... ok test_mark_safe_as_decorator (utils_tests.test_safestring.SafeStringTest.test_mark_safe_as_decorator) mark_safe used as a decorator leaves the result of a function ... ok test_mark_safe_decorator_does_not_affect_dunder_html (utils_tests.test_safestring.SafeStringTest.test_mark_safe_decorator_does_not_affect_dunder_html) mark_safe doesn't affect a callable that has an __html__() method. ... ok test_mark_safe_decorator_does_not_affect_promises (utils_tests.test_safestring.SafeStringTest.test_mark_safe_decorator_does_not_affect_promises) mark_safe doesn't affect lazy strings (Promise objects). ... ok test_mark_safe_lazy (utils_tests.test_safestring.SafeStringTest.test_mark_safe_lazy) ... ok test_mark_safe_lazy_result_implements_dunder_html (utils_tests.test_safestring.SafeStringTest.test_mark_safe_lazy_result_implements_dunder_html) ... ok test_mark_safe_object_implementing_dunder_html (utils_tests.test_safestring.SafeStringTest.test_mark_safe_object_implementing_dunder_html) ... ok test_mark_safe_object_implementing_dunder_str (utils_tests.test_safestring.SafeStringTest.test_mark_safe_object_implementing_dunder_str) ... ok test_mark_safe_result_implements_dunder_html (utils_tests.test_safestring.SafeStringTest.test_mark_safe_result_implements_dunder_html) ... ok test_mark_safe_str (utils_tests.test_safestring.SafeStringTest.test_mark_safe_str) Calling str() on a SafeString instance doesn't lose the safe status. ... ok test_compress_sequence (utils_tests.test_text.TestUtilsText.test_compress_sequence) ... ok test_format_lazy (utils_tests.test_text.TestUtilsText.test_format_lazy) ... ok test_get_text_list (utils_tests.test_text.TestUtilsText.test_get_text_list) ... ok test_get_valid_filename (utils_tests.test_text.TestUtilsText.test_get_valid_filename) ... ok test_normalize_newlines (utils_tests.test_text.TestUtilsText.test_normalize_newlines) ... ok test_phone2numeric (utils_tests.test_text.TestUtilsText.test_phone2numeric) ... ok test_slugify (utils_tests.test_text.TestUtilsText.test_slugify) ... ok test_smart_split (utils_tests.test_text.TestUtilsText.test_smart_split) ... ok test_truncate_chars (utils_tests.test_text.TestUtilsText.test_truncate_chars) ... ok test_truncate_chars_html (utils_tests.test_text.TestUtilsText.test_truncate_chars_html) ... ok test_truncate_html_words (utils_tests.test_text.TestUtilsText.test_truncate_html_words) ... ok test_truncate_words (utils_tests.test_text.TestUtilsText.test_truncate_words) ... ok test_unescape_entities (utils_tests.test_text.TestUtilsText.test_unescape_entities) ... ok test_unescape_entities_deprecated (utils_tests.test_text.TestUtilsText.test_unescape_entities_deprecated) ... ok test_unescape_string_literal (utils_tests.test_text.TestUtilsText.test_unescape_string_literal) ... ok test_wrap (utils_tests.test_text.TestUtilsText.test_wrap) ... ok test_activate_invalid_timezone (utils_tests.test_timezone.TimezoneTests.test_activate_invalid_timezone) ... ok test_fixedoffset_negative_timedelta (utils_tests.test_timezone.TimezoneTests.test_fixedoffset_negative_timedelta) ... ok test_fixedoffset_timedelta (utils_tests.test_timezone.TimezoneTests.test_fixedoffset_timedelta) ... ok test_get_default_timezone (utils_tests.test_timezone.TimezoneTests.test_get_default_timezone) ... ok test_get_default_timezone_utc (utils_tests.test_timezone.TimezoneTests.test_get_default_timezone_utc) ... ok test_get_timezone_name (utils_tests.test_timezone.TimezoneTests.test_get_timezone_name) The _get_timezone_name() helper must return the offset for fixed offset ... ok test_is_aware (utils_tests.test_timezone.TimezoneTests.test_is_aware) ... ok test_is_naive (utils_tests.test_timezone.TimezoneTests.test_is_naive) ... ok test_localdate (utils_tests.test_timezone.TimezoneTests.test_localdate) ... ok test_make_aware (utils_tests.test_timezone.TimezoneTests.test_make_aware) ... ok test_make_aware2 (utils_tests.test_timezone.TimezoneTests.test_make_aware2) ... ok test_make_aware_no_tz (utils_tests.test_timezone.TimezoneTests.test_make_aware_no_tz) ... ok test_make_aware_pytz_ambiguous (utils_tests.test_timezone.TimezoneTests.test_make_aware_pytz_ambiguous) ... ok test_make_aware_pytz_non_existent (utils_tests.test_timezone.TimezoneTests.test_make_aware_pytz_non_existent) ... ok test_make_aware_zoneinfo_ambiguous (utils_tests.test_timezone.TimezoneTests.test_make_aware_zoneinfo_ambiguous) ... ok test_make_aware_zoneinfo_non_existent (utils_tests.test_timezone.TimezoneTests.test_make_aware_zoneinfo_non_existent) ... ok test_make_naive (utils_tests.test_timezone.TimezoneTests.test_make_naive) ... ok test_make_naive_no_tz (utils_tests.test_timezone.TimezoneTests.test_make_naive_no_tz) ... ok test_make_naive_pytz (utils_tests.test_timezone.TimezoneTests.test_make_naive_pytz) ... ok test_make_naive_zoneinfo (utils_tests.test_timezone.TimezoneTests.test_make_naive_zoneinfo) ... ok test_now (utils_tests.test_timezone.TimezoneTests.test_now) ... ok test_override (utils_tests.test_timezone.TimezoneTests.test_override) ... ok test_override_decorator (utils_tests.test_timezone.TimezoneTests.test_override_decorator) ... ok test_override_fixed_offset (utils_tests.test_timezone.TimezoneTests.test_override_fixed_offset) ... ok test_override_string_tz (utils_tests.test_timezone.TimezoneTests.test_override_string_tz) ... ok test_basic (utils_tests.test_topological_sort.TopologicalSortTests.test_basic) ... ok test_cyclic_dependency (utils_tests.test_topological_sort.TopologicalSortTests.test_cyclic_dependency) ... ok test_ambiguous_prefix (migrations.test_commands.MigrateTests.test_ambiguous_prefix) ... ok test_app_without_migrations (migrations.test_commands.MigrateTests.test_app_without_migrations) ... ok test_migrate (migrations.test_commands.MigrateTests.test_migrate) Tests basic usage of the migrate command. ... ok test_migrate_check (migrations.test_commands.MigrateTests.test_migrate_check) ... ok test_migrate_check_plan (migrations.test_commands.MigrateTests.test_migrate_check_plan) ... ok test_migrate_conflict_exit (migrations.test_commands.MigrateTests.test_migrate_conflict_exit) migrate exits if it detects a conflict. ... ok test_migrate_fake_initial (migrations.test_commands.MigrateTests.test_migrate_fake_initial) --fake-initial only works if all tables created in the initial ... ok test_migrate_fake_initial_case_insensitive (migrations.test_commands.MigrateTests.test_migrate_fake_initial_case_insensitive) ... ok test_migrate_fake_split_initial (migrations.test_commands.MigrateTests.test_migrate_fake_split_initial) Split initial migrations can be faked with --fake-initial. ... ok test_migrate_inconsistent_history (migrations.test_commands.MigrateTests.test_migrate_inconsistent_history) Running migrate with some migrations applied before their dependencies ... ok test_migrate_initial_false (migrations.test_commands.MigrateTests.test_migrate_initial_false) `Migration.initial = False` skips fake-initial detection. ... ok test_migrate_not_reflected_changes (migrations.test_commands.MigrateTests.test_migrate_not_reflected_changes) ... ok test_migrate_plan (migrations.test_commands.MigrateTests.test_migrate_plan) Tests migrate --plan output. ... ok test_migrate_record_replaced (migrations.test_commands.MigrateTests.test_migrate_record_replaced) Running a single squashed migration should record all of the original ... ok test_migrate_record_squashed (migrations.test_commands.MigrateTests.test_migrate_record_squashed) Running migrate for a squashed migration should record as run ... ok test_migrate_syncdb_app_label (migrations.test_commands.MigrateTests.test_migrate_syncdb_app_label) Running migrate --run-syncdb with an app_label only creates tables for ... ok test_migrate_syncdb_app_with_migrations (migrations.test_commands.MigrateTests.test_migrate_syncdb_app_with_migrations) ... ok test_migrate_syncdb_deferred_sql_executed_with_schemaeditor (migrations.test_commands.MigrateTests.test_migrate_syncdb_deferred_sql_executed_with_schemaeditor) For an app without migrations, editor.execute() is used for executing ... ok test_migrate_with_system_checks (migrations.test_commands.MigrateTests.test_migrate_with_system_checks) ... ok test_migrations_no_operations (migrations.test_commands.MigrateTests.test_migrations_no_operations) ... ok test_regression_22823_unmigrated_fk_to_migrated_model (migrations.test_commands.MigrateTests.test_regression_22823_unmigrated_fk_to_migrated_model) Assuming you have 3 apps, `A`, `B`, and `C`, such that: ... ok test_showmigrations_list (migrations.test_commands.MigrateTests.test_showmigrations_list) showmigrations --list displays migrations and whether or not they're ... ok test_showmigrations_no_migrations (migrations.test_commands.MigrateTests.test_showmigrations_no_migrations) ... ok test_showmigrations_plan (migrations.test_commands.MigrateTests.test_showmigrations_plan) Tests --plan output of showmigrations command ... ok test_showmigrations_plan_app_label_no_migrations (migrations.test_commands.MigrateTests.test_showmigrations_plan_app_label_no_migrations) ... ok test_showmigrations_plan_multiple_app_labels (migrations.test_commands.MigrateTests.test_showmigrations_plan_multiple_app_labels) `showmigrations --plan app_label` output with multiple app_labels. ... ok test_showmigrations_plan_no_migrations (migrations.test_commands.MigrateTests.test_showmigrations_plan_no_migrations) Tests --plan output of showmigrations command without migrations ... ok test_showmigrations_plan_single_app_label (migrations.test_commands.MigrateTests.test_showmigrations_plan_single_app_label) `showmigrations --plan app_label` output with a single app_label. ... ok test_showmigrations_plan_squashed (migrations.test_commands.MigrateTests.test_showmigrations_plan_squashed) Tests --plan output of showmigrations command with squashed migrations. ... ok test_showmigrations_unmigrated_app (migrations.test_commands.MigrateTests.test_showmigrations_unmigrated_app) ... ok test_sqlmigrate_ambiguous_prefix_squashed_migrations (migrations.test_commands.MigrateTests.test_sqlmigrate_ambiguous_prefix_squashed_migrations) ... ok test_sqlmigrate_backwards (migrations.test_commands.MigrateTests.test_sqlmigrate_backwards) sqlmigrate outputs reverse looking SQL. ... ok test_sqlmigrate_for_non_atomic_migration (migrations.test_commands.MigrateTests.test_sqlmigrate_for_non_atomic_migration) Transaction wrappers aren't shown for non-atomic migrations. ... ok test_sqlmigrate_for_non_transactional_databases (migrations.test_commands.MigrateTests.test_sqlmigrate_for_non_transactional_databases) Transaction wrappers aren't shown for databases that don't support ... ok test_sqlmigrate_forwards (migrations.test_commands.MigrateTests.test_sqlmigrate_forwards) sqlmigrate outputs forward looking SQL. ... ok test_sqlmigrate_replaced_migration (migrations.test_commands.MigrateTests.test_sqlmigrate_replaced_migration) ... ok test_sqlmigrate_squashed_migration (migrations.test_commands.MigrateTests.test_sqlmigrate_squashed_migration) ... ok test_unknown_prefix (migrations.test_commands.MigrateTests.test_unknown_prefix) ... ok test_content_type_already_present (middleware.test_security.SecurityMiddlewareTest.test_content_type_already_present) The middleware will not override an "X-Content-Type-Options" header ... ok test_content_type_off (middleware.test_security.SecurityMiddlewareTest.test_content_type_off) With SECURE_CONTENT_TYPE_NOSNIFF False, the middleware does not add an ... ok test_content_type_on (middleware.test_security.SecurityMiddlewareTest.test_content_type_on) With SECURE_CONTENT_TYPE_NOSNIFF set to True, the middleware adds ... ok test_no_redirect_ssl (middleware.test_security.SecurityMiddlewareTest.test_no_redirect_ssl) The middleware does not redirect secure requests. ... ok test_redirect_exempt (middleware.test_security.SecurityMiddlewareTest.test_redirect_exempt) The middleware does not redirect requests with URL path matching an ... ok test_redirect_ssl_host (middleware.test_security.SecurityMiddlewareTest.test_redirect_ssl_host) The middleware redirects to SECURE_SSL_HOST if given. ... ok test_referrer_policy_already_present (middleware.test_security.SecurityMiddlewareTest.test_referrer_policy_already_present) The middleware will not override a "Referrer-Policy" header already ... ok test_referrer_policy_off (middleware.test_security.SecurityMiddlewareTest.test_referrer_policy_off) With SECURE_REFERRER_POLICY set to None, the middleware does not add a ... ok test_referrer_policy_on (middleware.test_security.SecurityMiddlewareTest.test_referrer_policy_on) With SECURE_REFERRER_POLICY set to a valid value, the middleware adds a ... ok test_ssl_redirect_off (middleware.test_security.SecurityMiddlewareTest.test_ssl_redirect_off) With SECURE_SSL_REDIRECT False, the middleware does not redirect. ... ok test_ssl_redirect_on (middleware.test_security.SecurityMiddlewareTest.test_ssl_redirect_on) With SECURE_SSL_REDIRECT True, the middleware redirects any non-secure ... ok test_sts_already_present (middleware.test_security.SecurityMiddlewareTest.test_sts_already_present) The middleware will not override a "Strict-Transport-Security" header ... ok test_sts_include_subdomains (middleware.test_security.SecurityMiddlewareTest.test_sts_include_subdomains) With SECURE_HSTS_SECONDS non-zero and SECURE_HSTS_INCLUDE_SUBDOMAINS ... ok test_sts_no_include_subdomains (middleware.test_security.SecurityMiddlewareTest.test_sts_no_include_subdomains) With SECURE_HSTS_SECONDS non-zero and SECURE_HSTS_INCLUDE_SUBDOMAINS ... ok test_sts_no_preload (middleware.test_security.SecurityMiddlewareTest.test_sts_no_preload) With SECURE_HSTS_SECONDS non-zero and SECURE_HSTS_PRELOAD ... ok test_sts_off (middleware.test_security.SecurityMiddlewareTest.test_sts_off) With SECURE_HSTS_SECONDS=0, the middleware does not add a ... ok test_sts_on (middleware.test_security.SecurityMiddlewareTest.test_sts_on) With SECURE_HSTS_SECONDS=3600, the middleware adds ... ok test_sts_only_if_secure (middleware.test_security.SecurityMiddlewareTest.test_sts_only_if_secure) The "Strict-Transport-Security" header is not added to responses going ... ok test_sts_preload (middleware.test_security.SecurityMiddlewareTest.test_sts_preload) With SECURE_HSTS_SECONDS non-zero and SECURE_HSTS_PRELOAD True, the ... ok test_sts_subdomains_and_preload (middleware.test_security.SecurityMiddlewareTest.test_sts_subdomains_and_preload) With SECURE_HSTS_SECONDS non-zero, SECURE_HSTS_INCLUDE_SUBDOMAINS and ... ok test_xss_filter_already_present (middleware.test_security.SecurityMiddlewareTest.test_xss_filter_already_present) The middleware will not override an "X-XSS-Protection" header ... ok test_xss_filter_off (middleware.test_security.SecurityMiddlewareTest.test_xss_filter_off) With SECURE_BROWSER_XSS_FILTER set to False, the middleware does not ... ok test_xss_filter_on (middleware.test_security.SecurityMiddlewareTest.test_xss_filter_on) With SECURE_BROWSER_XSS_FILTER set to True, the middleware adds ... ok test_404_error_reporting (middleware.tests.BrokenLinkEmailsMiddlewareTest.test_404_error_reporting) ... ok test_404_error_reporting_ignored_url (middleware.tests.BrokenLinkEmailsMiddlewareTest.test_404_error_reporting_ignored_url) ... ok test_404_error_reporting_no_referer (middleware.tests.BrokenLinkEmailsMiddlewareTest.test_404_error_reporting_no_referer) ... ok test_custom_request_checker (middleware.tests.BrokenLinkEmailsMiddlewareTest.test_custom_request_checker) ... ok test_referer_equal_to_requested_url (middleware.tests.BrokenLinkEmailsMiddlewareTest.test_referer_equal_to_requested_url) Some bots set the referer to the current URL to avoid being blocked by ... ok test_referer_equal_to_requested_url_on_another_domain (middleware.tests.BrokenLinkEmailsMiddlewareTest.test_referer_equal_to_requested_url_on_another_domain) ... ok test_referer_equal_to_requested_url_without_trailing_slash_when_append_slash_is_set (middleware.tests.BrokenLinkEmailsMiddlewareTest.test_referer_equal_to_requested_url_without_trailing_slash_when_append_slash_is_set) ... ok test_referer_equal_to_requested_url_without_trailing_slash_when_append_slash_is_unset (middleware.tests.BrokenLinkEmailsMiddlewareTest.test_referer_equal_to_requested_url_without_trailing_slash_when_append_slash_is_unset) ... ok test_append_slash_disabled (middleware.tests.CommonMiddlewareTest.test_append_slash_disabled) Disabling append slash functionality should leave slashless URLs alone. ... ok test_append_slash_disabled_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_append_slash_disabled_custom_urlconf) Disabling append slash functionality should leave slashless URLs alone. ... ok test_append_slash_have_slash (middleware.tests.CommonMiddlewareTest.test_append_slash_have_slash) URLs with slashes should go unmolested. ... ok test_append_slash_have_slash_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_append_slash_have_slash_custom_urlconf) URLs with slashes should go unmolested. ... ok test_append_slash_leading_slashes (middleware.tests.CommonMiddlewareTest.test_append_slash_leading_slashes) Paths starting with two slashes are escaped to prevent open redirects. ... ok test_append_slash_no_redirect_on_POST_in_DEBUG (middleware.tests.CommonMiddlewareTest.test_append_slash_no_redirect_on_POST_in_DEBUG) While in debug mode, an exception is raised with a warning ... ok test_append_slash_no_redirect_on_POST_in_DEBUG_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_append_slash_no_redirect_on_POST_in_DEBUG_custom_urlconf) While in debug mode, an exception is raised with a warning ... ok test_append_slash_opt_out (middleware.tests.CommonMiddlewareTest.test_append_slash_opt_out) Views marked with @no_append_slash should be left alone. ... ok test_append_slash_quoted (middleware.tests.CommonMiddlewareTest.test_append_slash_quoted) URLs which require quoting should be redirected to their slash version. ... ok test_append_slash_quoted_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_append_slash_quoted_custom_urlconf) URLs which require quoting should be redirected to their slash version. ... ok test_append_slash_redirect (middleware.tests.CommonMiddlewareTest.test_append_slash_redirect) APPEND_SLASH should redirect slashless URLs to a valid pattern. ... ok test_append_slash_redirect_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_append_slash_redirect_custom_urlconf) APPEND_SLASH should redirect slashless URLs to a valid pattern. ... ok test_append_slash_redirect_querystring (middleware.tests.CommonMiddlewareTest.test_append_slash_redirect_querystring) APPEND_SLASH should preserve querystrings when redirecting. ... ok test_append_slash_redirect_querystring_have_slash (middleware.tests.CommonMiddlewareTest.test_append_slash_redirect_querystring_have_slash) APPEND_SLASH should append slash to path when redirecting a request ... ok test_append_slash_slashless_resource (middleware.tests.CommonMiddlewareTest.test_append_slash_slashless_resource) Matches to explicit slashless URLs should go unmolested. ... ok test_append_slash_slashless_resource_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_append_slash_slashless_resource_custom_urlconf) Matches to explicit slashless URLs should go unmolested. ... ok test_append_slash_slashless_unknown (middleware.tests.CommonMiddlewareTest.test_append_slash_slashless_unknown) APPEND_SLASH should not redirect to unknown resources. ... ok test_append_slash_slashless_unknown_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_append_slash_slashless_unknown_custom_urlconf) APPEND_SLASH should not redirect to unknown resources. ... ok test_content_length_header_added (middleware.tests.CommonMiddlewareTest.test_content_length_header_added) ... ok test_content_length_header_not_added_for_streaming_response (middleware.tests.CommonMiddlewareTest.test_content_length_header_not_added_for_streaming_response) ... ok test_content_length_header_not_changed (middleware.tests.CommonMiddlewareTest.test_content_length_header_not_changed) ... ok test_disallowed_user_agents (middleware.tests.CommonMiddlewareTest.test_disallowed_user_agents) ... ok test_non_ascii_query_string_does_not_crash (middleware.tests.CommonMiddlewareTest.test_non_ascii_query_string_does_not_crash) Regression test for #15152 ... ok test_prepend_www (middleware.tests.CommonMiddlewareTest.test_prepend_www) ... ok test_prepend_www_append_slash_have_slash (middleware.tests.CommonMiddlewareTest.test_prepend_www_append_slash_have_slash) ... ok test_prepend_www_append_slash_have_slash_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_prepend_www_append_slash_have_slash_custom_urlconf) ... ok test_prepend_www_append_slash_slashless (middleware.tests.CommonMiddlewareTest.test_prepend_www_append_slash_slashless) ... ok test_prepend_www_append_slash_slashless_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_prepend_www_append_slash_slashless_custom_urlconf) ... ok test_prepend_www_custom_urlconf (middleware.tests.CommonMiddlewareTest.test_prepend_www_custom_urlconf) ... ok test_response_redirect_class (middleware.tests.CommonMiddlewareTest.test_response_redirect_class) ... ok test_response_redirect_class_subclass (middleware.tests.CommonMiddlewareTest.test_response_redirect_class_subclass) ... ok test_etag_match (middleware.tests.ETagGZipMiddlewareTest.test_etag_match) GZipMiddleware allows 304 Not Modified responses. ... ok test_strong_etag_modified (middleware.tests.ETagGZipMiddlewareTest.test_strong_etag_modified) GZipMiddleware makes a strong ETag weak. ... ok test_weak_etag_not_modified (middleware.tests.ETagGZipMiddlewareTest.test_weak_etag_not_modified) GZipMiddleware doesn't modify a weak ETag. ... ok test_etag_extended_cache_control (middleware.tests.ConditionalGetMiddlewareTest.test_etag_extended_cache_control) ... ok test_if_modified_since_and_client_error (middleware.tests.ConditionalGetMiddlewareTest.test_if_modified_since_and_client_error) ... ok test_if_modified_since_and_last_modified_in_the_future (middleware.tests.ConditionalGetMiddlewareTest.test_if_modified_since_and_last_modified_in_the_future) ... ok test_if_modified_since_and_last_modified_in_the_past (middleware.tests.ConditionalGetMiddlewareTest.test_if_modified_since_and_last_modified_in_the_past) ... ok test_if_modified_since_and_no_last_modified (middleware.tests.ConditionalGetMiddlewareTest.test_if_modified_since_and_no_last_modified) ... ok test_if_modified_since_and_redirect (middleware.tests.ConditionalGetMiddlewareTest.test_if_modified_since_and_redirect) ... ok test_if_modified_since_and_same_last_modified (middleware.tests.ConditionalGetMiddlewareTest.test_if_modified_since_and_same_last_modified) ... ok test_if_none_match_and_client_error (middleware.tests.ConditionalGetMiddlewareTest.test_if_none_match_and_client_error) ... ok test_if_none_match_and_different_etag (middleware.tests.ConditionalGetMiddlewareTest.test_if_none_match_and_different_etag) ... ok test_if_none_match_and_no_etag (middleware.tests.ConditionalGetMiddlewareTest.test_if_none_match_and_no_etag) ... ok test_if_none_match_and_redirect (middleware.tests.ConditionalGetMiddlewareTest.test_if_none_match_and_redirect) ... ok test_if_none_match_and_same_etag (middleware.tests.ConditionalGetMiddlewareTest.test_if_none_match_and_same_etag) ... ok test_middleware_calculates_etag (middleware.tests.ConditionalGetMiddlewareTest.test_middleware_calculates_etag) ... ok test_middleware_wont_overwrite_etag (middleware.tests.ConditionalGetMiddlewareTest.test_middleware_wont_overwrite_etag) ... ok test_no_etag_no_store_cache (middleware.tests.ConditionalGetMiddlewareTest.test_no_etag_no_store_cache) ... ok test_no_etag_response_empty_content (middleware.tests.ConditionalGetMiddlewareTest.test_no_etag_response_empty_content) ... ok test_no_etag_streaming_response (middleware.tests.ConditionalGetMiddlewareTest.test_no_etag_streaming_response) ... ok test_no_head (middleware.tests.ConditionalGetMiddlewareTest.test_no_head) ConditionalGetMiddleware shouldn't compute and return an ETag on a ... ok test_no_if_modified_since_and_last_modified (middleware.tests.ConditionalGetMiddlewareTest.test_no_if_modified_since_and_last_modified) ... ok test_no_if_none_match_and_etag (middleware.tests.ConditionalGetMiddlewareTest.test_no_if_none_match_and_etag) ... ok test_no_unsafe (middleware.tests.ConditionalGetMiddlewareTest.test_no_unsafe) ConditionalGetMiddleware shouldn't return a conditional response on an ... ok test_not_modified_headers (middleware.tests.ConditionalGetMiddlewareTest.test_not_modified_headers) The 304 Not Modified response should include only the headers required ... ok test_compress_deterministic (middleware.tests.GZipMiddlewareTest.test_compress_deterministic) Compression results are the same for the same content and don't ... ok test_compress_file_response (middleware.tests.GZipMiddlewareTest.test_compress_file_response) Compression is performed on FileResponse. ... ok test_compress_non_200_response (middleware.tests.GZipMiddlewareTest.test_compress_non_200_response) Compression is performed on responses with a status other than 200 ... ok test_compress_response (middleware.tests.GZipMiddlewareTest.test_compress_response) Compression is performed on responses with compressible content. ... ok test_compress_streaming_response (middleware.tests.GZipMiddlewareTest.test_compress_streaming_response) Compression is performed on responses with streaming content. ... ok test_compress_streaming_response_unicode (middleware.tests.GZipMiddlewareTest.test_compress_streaming_response_unicode) Compression is performed on responses with streaming Unicode content. ... ok test_no_compress_compressed_response (middleware.tests.GZipMiddlewareTest.test_no_compress_compressed_response) Compression isn't performed on responses that are already compressed. ... ok test_no_compress_incompressible_response (middleware.tests.GZipMiddlewareTest.test_no_compress_incompressible_response) Compression isn't performed on responses with incompressible content. ... ok test_no_compress_short_response (middleware.tests.GZipMiddlewareTest.test_no_compress_short_response) Compression isn't performed on responses with short content. ... ok test_defaults_sameorigin (middleware.tests.XFrameOptionsMiddlewareTest.test_defaults_sameorigin) If the X_FRAME_OPTIONS setting is not set then it defaults to ... ok test_deny (middleware.tests.XFrameOptionsMiddlewareTest.test_deny) The X_FRAME_OPTIONS setting can be set to DENY to have the middleware ... ok test_dont_set_if_set (middleware.tests.XFrameOptionsMiddlewareTest.test_dont_set_if_set) If the X-Frame-Options header is already set then the middleware does ... ok test_is_extendable (middleware.tests.XFrameOptionsMiddlewareTest.test_is_extendable) The XFrameOptionsMiddleware method that determines the X-Frame-Options ... ok test_response_exempt (middleware.tests.XFrameOptionsMiddlewareTest.test_response_exempt) If the response has an xframe_options_exempt attribute set to False ... ok test_same_origin (middleware.tests.XFrameOptionsMiddlewareTest.test_same_origin) The X_FRAME_OPTIONS setting can be set to SAMEORIGIN to have the ... ok test_lag_negative_offset (db_functions.window.test_validation.ValidationTests.test_lag_negative_offset) ... ok test_lead_negative_offset (db_functions.window.test_validation.ValidationTests.test_lead_negative_offset) ... ok test_negative_num_buckets_ntile (db_functions.window.test_validation.ValidationTests.test_negative_num_buckets_ntile) ... ok test_nth_negative_nth_value (db_functions.window.test_validation.ValidationTests.test_nth_negative_nth_value) ... ok test_nth_null_expression (db_functions.window.test_validation.ValidationTests.test_nth_null_expression) ... ok test_null_source_lag (db_functions.window.test_validation.ValidationTests.test_null_source_lag) ... ok test_null_source_lead (db_functions.window.test_validation.ValidationTests.test_null_source_lead) ... ok test_modelform_factory_metaclass (model_forms.tests.CustomMetaclassTestCase.test_modelform_factory_metaclass) ... ok test_generic_relations (select_related.tests.SelectRelatedValidationTests.test_generic_relations) ... ok test_invalid_field (select_related.tests.SelectRelatedValidationTests.test_invalid_field) ... ok test_many_to_many_field (select_related.tests.SelectRelatedValidationTests.test_many_to_many_field) ... ok test_non_relational_field (select_related.tests.SelectRelatedValidationTests.test_non_relational_field) ... ok test_non_relational_field_nested (select_related.tests.SelectRelatedValidationTests.test_non_relational_field_nested) ... ok test_reverse_relational_field (select_related.tests.SelectRelatedValidationTests.test_reverse_relational_field) ... ok test_bad_callback (model_forms.tests.FormFieldCallbackTests.test_bad_callback) ... ok test_baseform_with_widgets_in_meta (model_forms.tests.FormFieldCallbackTests.test_baseform_with_widgets_in_meta) Regression for #13095: Using base forms with widgets defined in Meta should not raise errors. ... ok test_custom_callback (model_forms.tests.FormFieldCallbackTests.test_custom_callback) A custom formfield_callback is used if provided ... ok test_factory_with_widget_argument (model_forms.tests.FormFieldCallbackTests.test_factory_with_widget_argument) Regression for #15315: modelform_factory should accept widgets ... ok test_inherit_after_custom_callback (model_forms.tests.FormFieldCallbackTests.test_inherit_after_custom_callback) ... ok test_modelform_factory_with_all_fields (model_forms.tests.FormFieldCallbackTests.test_modelform_factory_with_all_fields) Regression for #19733 ... ok test_modelform_factory_without_fields (model_forms.tests.FormFieldCallbackTests.test_modelform_factory_without_fields) Regression for #19733 ... ok test_custom_error_messages (model_forms.tests.ModelFormCustomErrorTests.test_custom_error_messages) ... ok test_model_clean_error_messages (model_forms.tests.ModelFormCustomErrorTests.test_model_clean_error_messages) ... ok test_field_removal (model_forms.tests.ModelFormInheritanceTests.test_field_removal) ... ok test_field_removal_name_clashes (model_forms.tests.ModelFormInheritanceTests.test_field_removal_name_clashes) Form fields can be removed in subclasses by setting them to None ... ok test_form_subclass_inheritance (model_forms.tests.ModelFormInheritanceTests.test_form_subclass_inheritance) ... ok test_big_integer_field (model_forms.tests.ModelOtherFieldTests.test_big_integer_field) ... ok test_http_prefixing (model_forms.tests.ModelOtherFieldTests.test_http_prefixing) If the http:// prefix is omitted on form input, the field adds it again. (Refs #13613) ... ok test_modelform_non_editable_field (model_forms.tests.ModelOtherFieldTests.test_modelform_non_editable_field) When explicitly including a non-editable field in a ModelForm, the ... ok test_url_on_modelform (model_forms.tests.ModelOtherFieldTests.test_url_on_modelform) Check basic URL field validation on model forms ... ok test_setattr_raises_validation_error_field_specific (model_forms.tests.StrictAssignmentTests.test_setattr_raises_validation_error_field_specific) A model ValidationError using the dict form should put the error ... ok test_setattr_raises_validation_error_non_field (model_forms.tests.StrictAssignmentTests.test_setattr_raises_validation_error_non_field) A model ValidationError not using the dict form should put the error ... ok test_error_messages_overrides (model_forms.tests.TestFieldOverridesByFormMeta.test_error_messages_overrides) ... ok test_field_type_overrides (model_forms.tests.TestFieldOverridesByFormMeta.test_field_type_overrides) ... ok test_help_text_overrides (model_forms.tests.TestFieldOverridesByFormMeta.test_help_text_overrides) ... ok test_label_overrides (model_forms.tests.TestFieldOverridesByFormMeta.test_label_overrides) ... ok test_widget_overrides (model_forms.tests.TestFieldOverridesByFormMeta.test_widget_overrides) ... ok test_notrequired_overrides_notblank (model_forms.tests.ValidationTest.test_notrequired_overrides_notblank) ... ok test_validates_with_replaced_field_excluded (model_forms.tests.ValidationTest.test_validates_with_replaced_field_excluded) ... ok test_validates_with_replaced_field_not_specified (model_forms.tests.ValidationTest.test_validates_with_replaced_field_not_specified) ... ok test_repr (serializers.test_deserializedobject.TestDeserializedObjectTests.test_repr) ... ok test_lazy_string_encoding (serializers.test_json.DjangoJSONEncoderTests.test_lazy_string_encoding) ... ok test_timedelta (serializers.test_json.DjangoJSONEncoderTests.test_timedelta) ... ok test_forward_refs (serializers.test_jsonl.JsonSerializerTransactionTestCase.test_forward_refs) Objects ids can be referenced before they are ... ok test_forward_refs (serializers.test_json.JsonSerializerTransactionTestCase.test_forward_refs) Objects ids can be referenced before they are ... ok test_deserializer_pyyaml_error_message (serializers.test_yaml.NoYamlSerializerTestCase.test_deserializer_pyyaml_error_message) Using yaml deserializer without pyyaml raises ImportError ... ok test_dumpdata_pyyaml_error_message (serializers.test_yaml.NoYamlSerializerTestCase.test_dumpdata_pyyaml_error_message) Calling dumpdata produces an error when yaml package missing ... ok test_serializer_pyyaml_error_message (serializers.test_yaml.NoYamlSerializerTestCase.test_serializer_pyyaml_error_message) Using yaml serializer without pyyaml raises ImportError ... ok test_forward_refs (serializers.test_xml.XmlSerializerTransactionTestCase.test_forward_refs) Objects ids can be referenced before they are ... ok test_stream_class (serializers.tests.SerializerAPITests.test_stream_class) ... ok test_forward_refs (serializers.test_yaml.YamlSerializerTransactionTestCase.test_forward_refs) Objects ids can be referenced before they are ... ok test_builtin_serializers (serializers.tests.SerializerRegistrationTests.test_builtin_serializers) Requesting a list of serializer formats populates the registry ... ok test_get_unknown_deserializer (serializers.tests.SerializerRegistrationTests.test_get_unknown_deserializer) ... ok test_get_unknown_serializer (serializers.tests.SerializerRegistrationTests.test_get_unknown_serializer) #15889: get_serializer('nonsense') raises a SerializerDoesNotExist ... ok test_register (serializers.tests.SerializerRegistrationTests.test_register) Registering a new serializer populates the full registry. Refs #14823 ... ok test_unregister (serializers.tests.SerializerRegistrationTests.test_unregister) Unregistering a serializer doesn't cause the registry to be repopulated. Refs #14823 ... ok test_unregister_unknown_serializer (serializers.tests.SerializerRegistrationTests.test_unregister_unknown_serializer) ... ok test_bad_module (wsgi.tests.GetInternalWSGIApplicationTest.test_bad_module) ... ok test_bad_name (wsgi.tests.GetInternalWSGIApplicationTest.test_bad_name) ... ok test_default (wsgi.tests.GetInternalWSGIApplicationTest.test_default) If ``WSGI_APPLICATION`` is ``None``, the return value of ... ok test_success (wsgi.tests.GetInternalWSGIApplicationTest.test_success) If ``WSGI_APPLICATION`` is a dotted path, the referenced object is ... ok test_file_wrapper (wsgi.tests.WSGITest.test_file_wrapper) FileResponse uses wsgi.file_wrapper. ... ok test_get_wsgi_application (wsgi.tests.WSGITest.test_get_wsgi_application) get_wsgi_application() returns a functioning WSGI callable. ... ok test_no_models (no_models.tests.NoModelTests.test_no_models) It's possible to load an app with no models.py file. ... ok test_all (test_runner.test_discover_runner.DiscoverRunnerGetDatabasesTests.test_all) ... ok test_default_and_other (test_runner.test_discover_runner.DiscoverRunnerGetDatabasesTests.test_default_and_other) ... ok test_default_only (test_runner.test_discover_runner.DiscoverRunnerGetDatabasesTests.test_default_only) ... ok test_mixed (test_runner.test_discover_runner.DiscoverRunnerGetDatabasesTests.test_mixed) ... ok test_no_databases_required (test_runner.test_discover_runner.DiscoverRunnerGetDatabasesTests.test_no_databases_required) ... ok test_other_only (test_runner.test_discover_runner.DiscoverRunnerGetDatabasesTests.test_other_only) ... ok test_add_arguments_debug_mode (test_runner.test_discover_runner.DiscoverRunnerTests.test_add_arguments_debug_mode) ... ok test_buffer_mode_test_fail (test_runner.test_discover_runner.DiscoverRunnerTests.test_buffer_mode_test_fail) ... ok test_buffer_mode_test_pass (test_runner.test_discover_runner.DiscoverRunnerTests.test_buffer_mode_test_pass) ... ok test_buffer_with_parallel (test_runner.test_discover_runner.DiscoverRunnerTests.test_buffer_with_parallel) ... ok test_discovery_on_package (test_runner.test_discover_runner.DiscoverRunnerTests.test_discovery_on_package) ... ok test_dotted_test_class_django_testcase (test_runner.test_discover_runner.DiscoverRunnerTests.test_dotted_test_class_django_testcase) ... ok test_dotted_test_class_vanilla_unittest (test_runner.test_discover_runner.DiscoverRunnerTests.test_dotted_test_class_vanilla_unittest) ... ok test_dotted_test_method_django_testcase (test_runner.test_discover_runner.DiscoverRunnerTests.test_dotted_test_method_django_testcase) ... ok test_dotted_test_module (test_runner.test_discover_runner.DiscoverRunnerTests.test_dotted_test_module) ... ok test_duplicates_ignored (test_runner.test_discover_runner.DiscoverRunnerTests.test_duplicates_ignored) Tests shouldn't be discovered twice when discovering on overlapping paths. ... ok test_empty_label (test_runner.test_discover_runner.DiscoverRunnerTests.test_empty_label) If the test label is empty, discovery should happen on the current ... ok test_empty_test_case (test_runner.test_discover_runner.DiscoverRunnerTests.test_empty_test_case) ... ok test_exclude_tags (test_runner.test_discover_runner.DiscoverRunnerTests.test_exclude_tags) ... ok test_excluded_tags_displayed (test_runner.test_discover_runner.DiscoverRunnerTests.test_excluded_tags_displayed) ... ok test_faulthandler_already_enabled (test_runner.test_discover_runner.DiscoverRunnerTests.test_faulthandler_already_enabled) ... ok test_faulthandler_disabled (test_runner.test_discover_runner.DiscoverRunnerTests.test_faulthandler_disabled) ... ok test_faulthandler_enabled (test_runner.test_discover_runner.DiscoverRunnerTests.test_faulthandler_enabled) ... ok test_faulthandler_enabled_fileno (test_runner.test_discover_runner.DiscoverRunnerTests.test_faulthandler_enabled_fileno) ... ok test_file_path (test_runner.test_discover_runner.DiscoverRunnerTests.test_file_path) ... ok test_ignore_adjacent (test_runner.test_discover_runner.DiscoverRunnerTests.test_ignore_adjacent) When given a dotted path to a module, unittest discovery searches ... ok test_included_tags_displayed (test_runner.test_discover_runner.DiscoverRunnerTests.test_included_tags_displayed) ... ok test_init_debug_mode (test_runner.test_discover_runner.DiscoverRunnerTests.test_init_debug_mode) ... ok test_name_patterns (test_runner.test_discover_runner.DiscoverRunnerTests.test_name_patterns) ... ok test_overridable_get_test_runner_kwargs (test_runner.test_discover_runner.DiscoverRunnerTests.test_overridable_get_test_runner_kwargs) ... ok test_overridable_test_loader (test_runner.test_discover_runner.DiscoverRunnerTests.test_overridable_test_loader) ... ok test_overridable_test_runner (test_runner.test_discover_runner.DiscoverRunnerTests.test_overridable_test_runner) ... ok test_overridable_test_suite (test_runner.test_discover_runner.DiscoverRunnerTests.test_overridable_test_suite) ... ok test_pattern (test_runner.test_discover_runner.DiscoverRunnerTests.test_pattern) ... ok test_pdb_with_parallel (test_runner.test_discover_runner.DiscoverRunnerTests.test_pdb_with_parallel) ... ok test_reverse (test_runner.test_discover_runner.DiscoverRunnerTests.test_reverse) Reverse should reorder tests while maintaining the grouping specified ... ok test_tag_inheritance (test_runner.test_discover_runner.DiscoverRunnerTests.test_tag_inheritance) ... ok test_tags (test_runner.test_discover_runner.DiscoverRunnerTests.test_tags) ... ok test_testcase_ordering (test_runner.test_discover_runner.DiscoverRunnerTests.test_testcase_ordering) ... ok test_timings_captured (test_runner.test_discover_runner.DiscoverRunnerTests.test_timings_captured) ... ok test_timings_not_captured (test_runner.test_discover_runner.DiscoverRunnerTests.test_timings_not_captured) ... ok test_subtest (test_runner.test_parallel.ParallelTestRunnerTest.test_subtest) Passing subtests work. ... ok test_add_failing_subtests (test_runner.test_parallel.RemoteTestResultTest.test_add_failing_subtests) Failing subtests are added correctly using addSubTest(). ... ok test_pickle_errors_detection (test_runner.test_parallel.RemoteTestResultTest.test_pickle_errors_detection) ... ok test_autoincrement_reset1 (test_runner.tests.AutoIncrementResetTest.test_autoincrement_reset1) ... ok test_autoincrement_reset2 (test_runner.tests.AutoIncrementResetTest.test_autoincrement_reset2) ... ok test_format_discovery (fixtures.tests.FixtureTransactionTests.test_format_discovery) ... ok test_alter_id_type_with_fk (migrations.test_executor.ExecutorTests.test_alter_id_type_with_fk) ... ok test_apply_all_replaced_marks_replacement_as_applied (migrations.test_executor.ExecutorTests.test_apply_all_replaced_marks_replacement_as_applied) Applying all replaced migrations marks replacement as applied (#24628). ... ok test_atomic_operation_in_non_atomic_migration (migrations.test_executor.ExecutorTests.test_atomic_operation_in_non_atomic_migration) An atomic operation is properly rolled back inside a non-atomic ... ok test_custom_user (migrations.test_executor.ExecutorTests.test_custom_user) Regression test for #22325 - references to a custom user model defined in the ... ok test_detect_soft_applied_add_field_manytomanyfield (migrations.test_executor.ExecutorTests.test_detect_soft_applied_add_field_manytomanyfield) executor.detect_soft_applied() detects ManyToManyField tables from an ... ok test_empty_plan (migrations.test_executor.ExecutorTests.test_empty_plan) Re-planning a full migration of a fully-migrated set doesn't ... ok test_migrate_marks_replacement_applied_even_if_it_did_nothing (migrations.test_executor.ExecutorTests.test_migrate_marks_replacement_applied_even_if_it_did_nothing) A new squash migration will be marked as applied even if all its ... ok test_migrations_applied_and_recorded_atomically (migrations.test_executor.ExecutorTests.test_migrations_applied_and_recorded_atomically) Migrations are applied and recorded atomically. ... ok test_migrations_not_applied_on_deferred_sql_failure (migrations.test_executor.ExecutorTests.test_migrations_not_applied_on_deferred_sql_failure) Migrations are not recorded if deferred SQL application fails. ... ok test_mixed_plan_not_supported (migrations.test_executor.ExecutorTests.test_mixed_plan_not_supported) Although the MigrationExecutor interfaces allows for mixed migration ... ok test_non_atomic_migration (migrations.test_executor.ExecutorTests.test_non_atomic_migration) Applying a non-atomic migration works as expected. ... ok test_process_callback (migrations.test_executor.ExecutorTests.test_process_callback) #24129 - Tests callback process ... ok test_run (migrations.test_executor.ExecutorTests.test_run) Tests running a simple set of migrations. ... ok test_run_with_squashed (migrations.test_executor.ExecutorTests.test_run_with_squashed) Tests running a squashed migration from zero (should ignore what it replaces) ... ok test_soft_apply (migrations.test_executor.ExecutorTests.test_soft_apply) Tests detection of initial migrations already having been applied. ... ok test_unrelated_applied_migrations_mutate_state (migrations.test_executor.ExecutorTests.test_unrelated_applied_migrations_mutate_state) #26647 - Unrelated applied migrations should be part of the final ... ok test_unrelated_model_lookups_backwards (migrations.test_executor.ExecutorTests.test_unrelated_model_lookups_backwards) #24123 - All models of apps being unapplied which are ... ok test_unrelated_model_lookups_forwards (migrations.test_executor.ExecutorTests.test_unrelated_model_lookups_forwards) #24123 - All models of apps already applied which are ... ok test_no_testrunner (test_runner.tests.CustomTestRunnerOptionsCmdlineTests.test_no_testrunner) ... ok test_testrunner_equals (test_runner.tests.CustomTestRunnerOptionsCmdlineTests.test_testrunner_equals) ... ok test_testrunner_option (test_runner.tests.CustomTestRunnerOptionsCmdlineTests.test_testrunner_option) ... ok test_transaction_support (test_runner.tests.SQLiteInMemoryTestDbs.test_transaction_support) ... ok test_app_default_auto_field (model_options.test_default_pk.TestDefaultPK.test_app_default_auto_field) ... ok test_app_default_auto_field_non_auto (model_options.test_default_pk.TestDefaultPK.test_app_default_auto_field_non_auto) ... ok test_app_default_auto_field_none (model_options.test_default_pk.TestDefaultPK.test_app_default_auto_field_none) ... ok test_app_default_auto_field_nonexistent (model_options.test_default_pk.TestDefaultPK.test_app_default_auto_field_nonexistent) ... ok test_default_auto_field_setting (model_options.test_default_pk.TestDefaultPK.test_default_auto_field_setting) ... ok test_default_auto_field_setting_bigautofield_subclass (model_options.test_default_pk.TestDefaultPK.test_default_auto_field_setting_bigautofield_subclass) ... ok test_default_auto_field_setting_non_auto (model_options.test_default_pk.TestDefaultPK.test_default_auto_field_setting_non_auto) ... ok test_default_auto_field_setting_none (model_options.test_default_pk.TestDefaultPK.test_default_auto_field_setting_none) ... ok test_default_auto_field_setting_nonexistent (model_options.test_default_pk.TestDefaultPK.test_default_auto_field_setting_nonexistent) ... ok test_m2m_app_default_auto_field (model_options.test_default_pk.TestDefaultPK.test_m2m_app_default_auto_field) ... ok test_m2m_default_auto_field_setting (model_options.test_default_pk.TestDefaultPK.test_m2m_default_auto_field_setting) ... ok test_all_options_given (test_runner.tests.CustomTestRunnerOptionsSettingsTests.test_all_options_given) ... ok test_default_and_given_options (test_runner.tests.CustomTestRunnerOptionsSettingsTests.test_default_and_given_options) ... ok test_default_options (test_runner.tests.CustomTestRunnerOptionsSettingsTests.test_default_options) ... ok test_option_name_and_value_separated (test_runner.tests.CustomTestRunnerOptionsSettingsTests.test_option_name_and_value_separated) ... ok test_ticket_17477 (test_runner.tests.Ticket17477RegressionTests.test_ticket_17477) 'manage.py help test' works after r16352. ... ok test_abstract_model (admin_registration.tests.TestRegistration.test_abstract_model) Exception is raised when trying to register an abstract model. ... ok test_bare_registration (admin_registration.tests.TestRegistration.test_bare_registration) ... ok test_is_registered_model (admin_registration.tests.TestRegistration.test_is_registered_model) Checks for registered models should return true. ... ok test_is_registered_not_registered_model (admin_registration.tests.TestRegistration.test_is_registered_not_registered_model) Checks for unregistered models should return false. ... ok test_iterable_registration (admin_registration.tests.TestRegistration.test_iterable_registration) ... ok test_prevent_double_registration (admin_registration.tests.TestRegistration.test_prevent_double_registration) ... ok test_prevent_double_registration_for_custom_admin (admin_registration.tests.TestRegistration.test_prevent_double_registration_for_custom_admin) ... ok test_registration_with_model_admin (admin_registration.tests.TestRegistration.test_registration_with_model_admin) ... ok test_registration_with_star_star_options (admin_registration.tests.TestRegistration.test_registration_with_star_star_options) ... ok test_star_star_overrides (admin_registration.tests.TestRegistration.test_star_star_overrides) ... ok test_unregister_unregistered_model (admin_registration.tests.TestRegistration.test_unregister_unregistered_model) ... ok test_command_option (shell.tests.ShellCommandTestCase.test_command_option) ... ok test_command_option_globals (shell.tests.ShellCommandTestCase.test_command_option_globals) ... ok test_command_option_inline_function_call (shell.tests.ShellCommandTestCase.test_command_option_inline_function_call) ... ok test_shell_with_bpython_not_installed (shell.tests.ShellCommandTestCase.test_shell_with_bpython_not_installed) ... ok test_shell_with_ipython_not_installed (shell.tests.ShellCommandTestCase.test_shell_with_ipython_not_installed) ... ok test_stdin_read (shell.tests.ShellCommandTestCase.test_stdin_read) ... ok test_stdin_read_globals (shell.tests.ShellCommandTestCase.test_stdin_read_globals) ... ok test_stdin_read_inline_function_call (shell.tests.ShellCommandTestCase.test_stdin_read_inline_function_call) ... ok test_basic_registration (admin_registration.tests.TestRegistrationDecorator.test_basic_registration) ... ok test_custom_site_not_an_admin_site (admin_registration.tests.TestRegistrationDecorator.test_custom_site_not_an_admin_site) ... ok test_custom_site_registration (admin_registration.tests.TestRegistrationDecorator.test_custom_site_registration) ... ok test_empty_models_list_registration_fails (admin_registration.tests.TestRegistrationDecorator.test_empty_models_list_registration_fails) ... ok test_multiple_registration (admin_registration.tests.TestRegistrationDecorator.test_multiple_registration) ... ok test_wrapped_class_not_a_model_admin (admin_registration.tests.TestRegistrationDecorator.test_wrapped_class_not_a_model_admin) ... ok test_receiver_signal_list (dispatch.tests.ReceiverTestCase.test_receiver_signal_list) ... ok test_receiver_single_signal (dispatch.tests.ReceiverTestCase.test_receiver_single_signal) ... ok test_tablespace_for_indexed_field (model_options.test_tablespaces.TablespacesTests.test_tablespace_for_indexed_field) ... skipped "Database doesn't support feature(s): supports_tablespaces" test_tablespace_for_many_to_many_field (model_options.test_tablespaces.TablespacesTests.test_tablespace_for_many_to_many_field) ... skipped "Database doesn't support feature(s): supports_tablespaces" test_tablespace_for_model (model_options.test_tablespaces.TablespacesTests.test_tablespace_for_model) ... skipped "Database doesn't support feature(s): supports_tablespaces" test_tablespace_ignored_for_indexed_field (model_options.test_tablespaces.TablespacesTests.test_tablespace_ignored_for_indexed_field) ... ok test_tablespace_ignored_for_model (model_options.test_tablespaces.TablespacesTests.test_tablespace_ignored_for_model) ... ok test_get_or_create_integrityerror (get_or_create.tests.GetOrCreateTransactionTests.test_get_or_create_integrityerror) Regression test for #15117. Requires a TransactionTestCase on ... ok test_creation_in_transaction (get_or_create.tests.UpdateOrCreateTransactionTests.test_creation_in_transaction) Objects are selected and updated in a transaction to avoid race ... skipped "Database doesn't support feature(s): has_select_for_update" test_updates_in_transaction (get_or_create.tests.UpdateOrCreateTransactionTests.test_updates_in_transaction) Objects are selected and updated in a transaction to avoid race ... skipped "Database doesn't support feature(s): has_select_for_update" test_initialization_class_attributes (backends.base.test_base.DatabaseWrapperTests.test_initialization_class_attributes) The "initialization" class attributes like client_class and ... ok test_initialization_display_name (backends.base.test_base.DatabaseWrapperTests.test_initialization_display_name) ... ok test_runshell_use_environ (backends.base.test_client.SimpleDatabaseClientTests.test_runshell_use_environ) ... ok test_settings_to_cmd_args_env (backends.base.test_client.SimpleDatabaseClientTests.test_settings_to_cmd_args_env) ... ok test_mark_expected_failures_and_skips_call (backends.base.test_creation.TestDbCreationTests.test_mark_expected_failures_and_skips_call) mark_expected_failures_and_skips() isn't called unless ... ok test_migrate_test_setting_false (backends.base.test_creation.TestDbCreationTests.test_migrate_test_setting_false) ... ok test_migrate_test_setting_true (backends.base.test_creation.TestDbCreationTests.test_migrate_test_setting_true) ... ok test_custom_test_name (backends.base.test_creation.TestDbSignatureTests.test_custom_test_name) ... ok test_custom_test_name_with_test_prefix (backends.base.test_creation.TestDbSignatureTests.test_custom_test_name_with_test_prefix) ... ok test_default_name (backends.base.test_creation.TestDbSignatureTests.test_default_name) ... ok test_get_or_create_with_invalid_defaults (get_or_create.tests.InvalidCreateArgumentsTests.test_get_or_create_with_invalid_defaults) ... ok test_get_or_create_with_invalid_kwargs (get_or_create.tests.InvalidCreateArgumentsTests.test_get_or_create_with_invalid_kwargs) ... ok test_multiple_invalid_fields (get_or_create.tests.InvalidCreateArgumentsTests.test_multiple_invalid_fields) ... ok test_property_attribute_without_setter_defaults (get_or_create.tests.InvalidCreateArgumentsTests.test_property_attribute_without_setter_defaults) ... ok test_property_attribute_without_setter_kwargs (get_or_create.tests.InvalidCreateArgumentsTests.test_property_attribute_without_setter_kwargs) ... ok test_update_or_create_with_invalid_defaults (get_or_create.tests.InvalidCreateArgumentsTests.test_update_or_create_with_invalid_defaults) ... ok test_update_or_create_with_invalid_kwargs (get_or_create.tests.InvalidCreateArgumentsTests.test_update_or_create_with_invalid_kwargs) ... ok test_mark_expected_failures_and_skips (backends.base.test_creation.TestMarkTests.test_mark_expected_failures_and_skips) ... ok test_nonexistent_feature (backends.base.test_features.TestDatabaseFeatures.test_nonexistent_feature) ... ok test_get_constraints (backends.base.test_introspection.SimpleDatabaseIntrospectionTests.test_get_constraints) ... ok test_get_key_columns (backends.base.test_introspection.SimpleDatabaseIntrospectionTests.test_get_key_columns) ... ok test_get_relations (backends.base.test_introspection.SimpleDatabaseIntrospectionTests.test_get_relations) ... ok test_get_sequences (backends.base.test_introspection.SimpleDatabaseIntrospectionTests.test_get_sequences) ... ok test_get_table_description (backends.base.test_introspection.SimpleDatabaseIntrospectionTests.test_get_table_description) ... ok test_get_table_list (backends.base.test_introspection.SimpleDatabaseIntrospectionTests.test_get_table_list) ... ok test_adapt_datetimefield_value (backends.base.test_operations.SimpleDatabaseOperationTests.test_adapt_datetimefield_value) ... ok test_adapt_timefield_value (backends.base.test_operations.SimpleDatabaseOperationTests.test_adapt_timefield_value) ... ok test_adapt_timefield_value_none (backends.base.test_operations.SimpleDatabaseOperationTests.test_adapt_timefield_value_none) ... ok test_adapt_timefield_value_unaware (backends.base.test_operations.SimpleDatabaseOperationTests.test_adapt_timefield_value_unaware) ... ok test_adapt_unknown_value_date (backends.base.test_operations.SimpleDatabaseOperationTests.test_adapt_unknown_value_date) ... ok test_adapt_unknown_value_decimal (backends.base.test_operations.SimpleDatabaseOperationTests.test_adapt_unknown_value_decimal) ... ok test_adapt_unknown_value_time (backends.base.test_operations.SimpleDatabaseOperationTests.test_adapt_unknown_value_time) ... ok test_date_extract_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_date_extract_sql) ... ok test_date_trunc_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_date_trunc_sql) ... ok test_datetime_cast_date_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_datetime_cast_date_sql) ... ok test_datetime_cast_time_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_datetime_cast_time_sql) ... ok test_datetime_extract_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_datetime_extract_sql) ... ok test_datetime_trunc_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_datetime_trunc_sql) ... ok test_deferrable_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_deferrable_sql) ... ok test_end_transaction_rollback (backends.base.test_operations.SimpleDatabaseOperationTests.test_end_transaction_rollback) ... ok test_no_limit_value (backends.base.test_operations.SimpleDatabaseOperationTests.test_no_limit_value) ... ok test_pk_default_value (backends.base.test_operations.SimpleDatabaseOperationTests.test_pk_default_value) ... ok test_quote_name (backends.base.test_operations.SimpleDatabaseOperationTests.test_quote_name) ... ok test_regex_lookup (backends.base.test_operations.SimpleDatabaseOperationTests.test_regex_lookup) ... ok test_sequence_reset_by_name_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_sequence_reset_by_name_sql) ... ok test_set_time_zone_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_set_time_zone_sql) ... ok test_sql_flush (backends.base.test_operations.SimpleDatabaseOperationTests.test_sql_flush) ... ok test_tablespace_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_tablespace_sql) ... ok test_time_extract_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_time_extract_sql) ... ok test_time_trunc_sql (backends.base.test_operations.SimpleDatabaseOperationTests.test_time_trunc_sql) ... ok test_circular_reference (backends.base.test_creation.TestDeserializeDbFromString.test_circular_reference) ... ok test_circular_reference_with_natural_key (backends.base.test_creation.TestDeserializeDbFromString.test_circular_reference_with_natural_key) ... ok test_self_reference (backends.base.test_creation.TestDeserializeDbFromString.test_self_reference) ... ok test_serialize_db_to_string_base_manager (backends.base.test_creation.TestDeserializeDbFromString.test_serialize_db_to_string_base_manager) ... ok test_effective_default_callable (backends.base.test_schema.SchemaEditorTests.test_effective_default_callable) SchemaEditor.effective_default() shouldn't call callable defaults. ... ok test_clone_test_db_database_exists (backends.mysql.test_creation.DatabaseCreationTests.test_clone_test_db_database_exists) ... skipped 'MySQL tests' test_clone_test_db_options_ordering (backends.mysql.test_creation.DatabaseCreationTests.test_clone_test_db_options_ordering) ... skipped 'MySQL tests' test_create_test_db_database_exists (backends.mysql.test_creation.DatabaseCreationTests.test_create_test_db_database_exists) ... skipped 'MySQL tests' test_create_test_db_unexpected_error (backends.mysql.test_creation.DatabaseCreationTests.test_create_test_db_unexpected_error) ... skipped 'MySQL tests' test_sql_flush (backends.mysql.test_operations.MySQLOperationsTests.test_sql_flush) ... skipped 'MySQL tests.' test_sql_flush_sequences (backends.mysql.test_operations.MySQLOperationsTests.test_sql_flush_sequences) ... skipped 'MySQL tests.' test_get_sequences (backends.oracle.test_introspection.DatabaseSequenceTests.test_get_sequences) ... skipped 'Oracle tests' test_get_sequences_manually_created_index (backends.oracle.test_introspection.DatabaseSequenceTests.test_get_sequences_manually_created_index) ... skipped 'Oracle tests' test_bulk_batch_size (backends.oracle.test_operations.OperationsTests.test_bulk_batch_size) ... skipped 'Oracle tests' test_sequence_name_truncation (backends.oracle.test_operations.OperationsTests.test_sequence_name_truncation) ... skipped 'Oracle tests' test_sql_flush (backends.oracle.test_operations.OperationsTests.test_sql_flush) ... skipped 'Oracle tests' test_sql_flush_allow_cascade (backends.oracle.test_operations.OperationsTests.test_sql_flush_allow_cascade) ... skipped 'Oracle tests' test_sql_flush_sequences (backends.oracle.test_operations.OperationsTests.test_sql_flush_sequences) ... skipped 'Oracle tests' test_sql_flush_sequences_allow_cascade (backends.oracle.test_operations.OperationsTests.test_sql_flush_sequences_allow_cascade) ... skipped 'Oracle tests' test_hidden_no_data_found_exception (backends.oracle.tests.TransactionalTests.test_hidden_no_data_found_exception) ... skipped 'Oracle tests' test_password_with_at_sign (backends.oracle.tests.TransactionalTests.test_password_with_at_sign) ... skipped 'Oracle tests' test_create_test_db (backends.postgresql.test_creation.DatabaseCreationTests.test_create_test_db) ... skipped 'PostgreSQL tests' test_sql_table_creation_suffix_with_encoding (backends.postgresql.test_creation.DatabaseCreationTests.test_sql_table_creation_suffix_with_encoding) ... skipped 'PostgreSQL tests' test_sql_table_creation_suffix_with_encoding_and_template (backends.postgresql.test_creation.DatabaseCreationTests.test_sql_table_creation_suffix_with_encoding_and_template) ... skipped 'PostgreSQL tests' test_sql_table_creation_suffix_with_none_settings (backends.postgresql.test_creation.DatabaseCreationTests.test_sql_table_creation_suffix_with_none_settings) ... skipped 'PostgreSQL tests' test_sql_table_creation_suffix_with_template (backends.postgresql.test_creation.DatabaseCreationTests.test_sql_table_creation_suffix_with_template) ... skipped 'PostgreSQL tests' test_execute_sql_flush_statements (backends.base.test_operations.SqlFlushTests.test_execute_sql_flush_statements) ... ok test_sql_flush_no_tables (backends.base.test_operations.SqlFlushTests.test_sql_flush_no_tables) ... ok test_sql_flush (backends.postgresql.test_operations.PostgreSQLOperationsTests.test_sql_flush) ... skipped 'PostgreSQL tests.' test_sql_flush_allow_cascade (backends.postgresql.test_operations.PostgreSQLOperationsTests.test_sql_flush_allow_cascade) ... skipped 'PostgreSQL tests.' test_sql_flush_sequences (backends.postgresql.test_operations.PostgreSQLOperationsTests.test_sql_flush_sequences) ... skipped 'PostgreSQL tests.' test_sql_flush_sequences_allow_cascade (backends.postgresql.test_operations.PostgreSQLOperationsTests.test_sql_flush_sequences_allow_cascade) ... skipped 'PostgreSQL tests.' test_custom_test_name (backends.sqlite.test_creation.TestDbSignatureTests.test_custom_test_name) ... ok test_database_sharing_in_threads (backends.sqlite.tests.ThreadSharing.test_database_sharing_in_threads) ... ok test_references_column (backends.test_ddl_references.ColumnsTests.test_references_column) ... ok test_references_table (backends.test_ddl_references.ColumnsTests.test_references_table) ... ok test_rename_column_references (backends.test_ddl_references.ColumnsTests.test_rename_column_references) ... ok test_rename_table_references (backends.test_ddl_references.ColumnsTests.test_rename_table_references) ... ok test_repr (backends.test_ddl_references.ColumnsTests.test_repr) ... ok test_str (backends.test_ddl_references.ColumnsTests.test_str) ... ok test_autoincrement (backends.sqlite.tests.SchemaTests.test_autoincrement) auto_increment fields are created with the AUTOINCREMENT keyword ... ok test_constraint_checks_disabled_atomic_allowed (backends.sqlite.tests.SchemaTests.test_constraint_checks_disabled_atomic_allowed) SQLite schema editor is usable within an outer transaction as long as ... ok test_disable_constraint_checking_failure_disallowed (backends.sqlite.tests.SchemaTests.test_disable_constraint_checking_failure_disallowed) SQLite schema editor is not usable within an outer transaction if ... ok test_field_rename_inside_atomic_block (backends.sqlite.tests.SchemaTests.test_field_rename_inside_atomic_block) NotImplementedError is raised when a model field rename is attempted ... skipped 'Database has feature(s) supports_atomic_references_rename' test_table_rename_inside_atomic_block (backends.sqlite.tests.SchemaTests.test_table_rename_inside_atomic_block) NotImplementedError is raised when a table rename is attempted inside ... skipped 'Database has feature(s) supports_atomic_references_rename' test_references_column (backends.test_ddl_references.ForeignKeyNameTests.test_references_column) ... ok test_references_table (backends.test_ddl_references.ForeignKeyNameTests.test_references_table) ... ok test_rename_column_references (backends.test_ddl_references.ForeignKeyNameTests.test_rename_column_references) ... ok test_rename_table_references (backends.test_ddl_references.ForeignKeyNameTests.test_rename_table_references) ... ok test_repr (backends.test_ddl_references.ForeignKeyNameTests.test_repr) ... ok test_str (backends.test_ddl_references.ForeignKeyNameTests.test_str) ... ok test_references_column (backends.test_ddl_references.IndexNameTests.test_references_column) ... ok test_references_table (backends.test_ddl_references.IndexNameTests.test_references_table) ... ok test_rename_column_references (backends.test_ddl_references.IndexNameTests.test_rename_column_references) ... ok test_rename_table_references (backends.test_ddl_references.IndexNameTests.test_rename_table_references) ... ok test_repr (backends.test_ddl_references.IndexNameTests.test_repr) ... ok test_str (backends.test_ddl_references.IndexNameTests.test_str) ... ok test_references_column (backends.test_ddl_references.StatementTests.test_references_column) ... ok test_references_table (backends.test_ddl_references.StatementTests.test_references_table) ... ok test_rename_column_references (backends.test_ddl_references.StatementTests.test_rename_column_references) ... ok test_rename_table_references (backends.test_ddl_references.StatementTests.test_rename_table_references) ... ok test_repr (backends.test_ddl_references.StatementTests.test_repr) ... ok test_str (backends.test_ddl_references.StatementTests.test_str) ... ok test_references_column (backends.test_ddl_references.ExpressionsTests.test_references_column) ... ok test_references_table (backends.test_ddl_references.ExpressionsTests.test_references_table) ... ok test_rename_column_references (backends.test_ddl_references.ExpressionsTests.test_rename_column_references) ... ok test_rename_table_references (backends.test_ddl_references.ExpressionsTests.test_rename_table_references) ... ok test_rename_table_references_without_alias (backends.test_ddl_references.ExpressionsTests.test_rename_table_references_without_alias) ... ok test_str (backends.test_ddl_references.ExpressionsTests.test_str) ... ok test_references_table (backends.test_ddl_references.TableTests.test_references_table) ... ok test_rename_table_references (backends.test_ddl_references.TableTests.test_rename_table_references) ... ok test_repr (backends.test_ddl_references.TableTests.test_repr) ... ok test_str (backends.test_ddl_references.TableTests.test_str) ... ok test_format_number (backends.test_utils.TestUtils.test_format_number) ... ok test_split_identifier (backends.test_utils.TestUtils.test_split_identifier) ... ok test_truncate_name (backends.test_utils.TestUtils.test_truncate_name) ... ok test_callproc_kparams (backends.test_utils.CursorWrapperTests.test_callproc_kparams) ... skipped "Database doesn't support feature(s): create_test_procedure_with_int_param_sql, supports_callproc_kwargs" test_callproc_with_int_params (backends.test_utils.CursorWrapperTests.test_callproc_with_int_params) ... skipped "Database doesn't support feature(s): create_test_procedure_with_int_param_sql" test_callproc_without_params (backends.test_utils.CursorWrapperTests.test_callproc_without_params) ... skipped "Database doesn't support feature(s): create_test_procedure_without_params_sql" test_unsupported_callproc_kparams_raises_error (backends.test_utils.CursorWrapperTests.test_unsupported_callproc_kparams_raises_error) ... ok test_signal (backends.tests.ConnectionCreatedSignalTest.test_signal) ... skipped "Database doesn't support feature(s): test_db_allows_multiple_connections" test_check_constraints (backends.tests.FkConstraintsTests.test_check_constraints) Constraint checks should raise an IntegrityError when bad data is in the DB. ... ok test_check_constraints_sql_keywords (backends.tests.FkConstraintsTests.test_check_constraints_sql_keywords) ... ok test_disable_constraint_checks_context_manager (backends.tests.FkConstraintsTests.test_disable_constraint_checks_context_manager) When constraint checks are disabled (using context manager), should be ... ok test_disable_constraint_checks_manually (backends.tests.FkConstraintsTests.test_disable_constraint_checks_manually) When constraint checks are disabled, should be able to write bad data ... ok test_integrity_checks_on_creation (backends.tests.FkConstraintsTests.test_integrity_checks_on_creation) Try to create a model instance that violates a FK constraint. If it ... ok test_integrity_checks_on_update (backends.tests.FkConstraintsTests.test_integrity_checks_on_update) Try to update a model instance introducing a FK constraint violation. ... ok test_cached_db_features (backends.tests.BackendTestCase.test_cached_db_features) ... ok test_cursor_contextmanager (backends.tests.BackendTestCase.test_cursor_contextmanager) Cursors can be used as a context manager ... ok test_cursor_contextmanager_closing (backends.tests.BackendTestCase.test_cursor_contextmanager_closing) ... skipped 'Psycopg2 specific cursor.closed attribute needed' test_cursor_execute_with_pyformat (backends.tests.BackendTestCase.test_cursor_execute_with_pyformat) ... skipped "Database doesn't support feature(s): supports_paramstyle_pyformat" test_cursor_executemany (backends.tests.BackendTestCase.test_cursor_executemany) ... ok test_cursor_executemany_with_empty_params_list (backends.tests.BackendTestCase.test_cursor_executemany_with_empty_params_list) ... ok test_cursor_executemany_with_iterator (backends.tests.BackendTestCase.test_cursor_executemany_with_iterator) ... ok test_cursor_executemany_with_pyformat (backends.tests.BackendTestCase.test_cursor_executemany_with_pyformat) ... skipped "Database doesn't support feature(s): supports_paramstyle_pyformat" test_cursor_executemany_with_pyformat_iterator (backends.tests.BackendTestCase.test_cursor_executemany_with_pyformat_iterator) ... skipped "Database doesn't support feature(s): supports_paramstyle_pyformat" test_database_operations_helper_class (backends.tests.BackendTestCase.test_database_operations_helper_class) ... ok test_database_operations_init (backends.tests.BackendTestCase.test_database_operations_init) DatabaseOperations initialization doesn't query the database. ... ok test_duplicate_table_error (backends.tests.BackendTestCase.test_duplicate_table_error) Creating an existing table returns a DatabaseError ... ok test_is_usable_after_database_disconnects (backends.tests.BackendTestCase.test_is_usable_after_database_disconnects) is_usable() doesn't crash when the database disconnects (#21553). ... skipped "Database doesn't support feature(s): test_db_allows_multiple_connections" test_queries (backends.tests.BackendTestCase.test_queries) Test the documented API of connection.queries. ... ok test_queries_limit (backends.tests.BackendTestCase.test_queries_limit) The backend doesn't store an unlimited number of queries (#12581). ... skipped "Database doesn't support feature(s): test_db_allows_multiple_connections" test_timezone_none_use_tz_false (backends.tests.BackendTestCase.test_timezone_none_use_tz_false) ... ok test_unicode_fetches (backends.tests.BackendTestCase.test_unicode_fetches) ... ok test_unicode_password (backends.tests.BackendTestCase.test_unicode_password) ... ok test_sequence_name_length_limits_create (backends.tests.LongNameTest.test_sequence_name_length_limits_create) Test creation of model with long name and long pk name doesn't error. Ref #8901 ... ok test_sequence_name_length_limits_flush (backends.tests.LongNameTest.test_sequence_name_length_limits_flush) Sequence resetting as part of a flush with model with long name and ... ok test_sequence_name_length_limits_m2m (backends.tests.LongNameTest.test_sequence_name_length_limits_m2m) An m2m save of a model with a long name and a long m2m field name ... ok test_delete (sites_tests.tests.RequestSiteTests.test_delete) ... ok test_init_attributes (sites_tests.tests.RequestSiteTests.test_init_attributes) ... ok test_save (sites_tests.tests.RequestSiteTests.test_save) ... ok test_str (sites_tests.tests.RequestSiteTests.test_str) ... ok test_closing_non_shared_connections (backends.tests.ThreadTests.test_closing_non_shared_connections) A connection that is not explicitly shareable cannot be closed by ... ok test_connections_thread_local (backends.tests.ThreadTests.test_connections_thread_local) The connections are different for each thread (#17258). ... ok test_default_connection_thread_local (backends.tests.ThreadTests.test_default_connection_thread_local) The default connection (i.e. django.db.connection) is different for ... ok test_pass_connection_between_threads (backends.tests.ThreadTests.test_pass_connection_between_threads) A connection can be passed from one thread to the other (#17258). ... ok test_thread_sharing_count (backends.tests.ThreadTests.test_thread_sharing_count) ... ok test_actions_warn_on_pending_edits (admin_changelist.tests.SeleniumTests.test_actions_warn_on_pending_edits) ... skipped 'No browsers specified.' test_add_row_selection (admin_changelist.tests.SeleniumTests.test_add_row_selection) The status line for selected rows gets updated correctly (#22038). ... skipped 'No browsers specified.' test_modifier_allows_multiple_section (admin_changelist.tests.SeleniumTests.test_modifier_allows_multiple_section) Selecting a row and then selecting another row whilst holding shift ... skipped 'No browsers specified.' test_save_with_changes_warns_on_pending_action (admin_changelist.tests.SeleniumTests.test_save_with_changes_warns_on_pending_action) ... skipped 'No browsers specified.' test_save_without_changes_warns_on_pending_action (admin_changelist.tests.SeleniumTests.test_save_without_changes_warns_on_pending_action) ... skipped 'No browsers specified.' test_select_all_across_pages (admin_changelist.tests.SeleniumTests.test_select_all_across_pages) ... skipped 'No browsers specified.' test_flatten (admin_utils.tests.UtilsTests.test_flatten) ... ok test_flatten_fieldsets (admin_utils.tests.UtilsTests.test_flatten_fieldsets) Regression test for #18051 ... ok test_help_text_for_field (admin_utils.tests.UtilsTests.test_help_text_for_field) ... ok test_json_display_for_field (admin_utils.tests.UtilsTests.test_json_display_for_field) ... ok test_label_for_field (admin_utils.tests.UtilsTests.test_label_for_field) Tests for label_for_field ... ok test_label_for_field_form_argument (admin_utils.tests.UtilsTests.test_label_for_field_form_argument) ... ok test_label_for_property (admin_utils.tests.UtilsTests.test_label_for_property) ... ok test_list_display_for_value (admin_utils.tests.UtilsTests.test_list_display_for_value) ... ok test_list_display_for_value_boolean (admin_utils.tests.UtilsTests.test_list_display_for_value_boolean) ... ok test_null_display_for_field (admin_utils.tests.UtilsTests.test_null_display_for_field) Regression test for #12550: display_for_field should handle None ... ok test_number_formats_display_for_field (admin_utils.tests.UtilsTests.test_number_formats_display_for_field) ... ok test_number_formats_with_thousand_separator_display_for_field (admin_utils.tests.UtilsTests.test_number_formats_with_thousand_separator_display_for_field) ... ok test_quote (admin_utils.tests.UtilsTests.test_quote) ... ok test_related_name (admin_utils.tests.UtilsTests.test_related_name) Regression test for #13963 ... ok test_safestring_in_field_label (admin_utils.tests.UtilsTests.test_safestring_in_field_label) ... ok test_values_from_lookup_field (admin_utils.tests.UtilsTests.test_values_from_lookup_field) Regression test for #12654: lookup_field ... ok test_description_output (admin_docs.test_utils.TestUtils.test_description_output) ... ok test_initial_header_level (admin_docs.test_utils.TestUtils.test_initial_header_level) ... ok test_parse_docstring (admin_docs.test_utils.TestUtils.test_parse_docstring) ... ok test_parse_rst (admin_docs.test_utils.TestUtils.test_parse_rst) parse_rst() should use `cmsreference` as the default role. ... ok test_parse_rst_with_docstring_no_leading_line_feed (admin_docs.test_utils.TestUtils.test_parse_rst_with_docstring_no_leading_line_feed) ... ok test_publish_parts (admin_docs.test_utils.TestUtils.test_publish_parts) Django shouldn't break the default role for interpreted text ... ok test_title_output (admin_docs.test_utils.TestUtils.test_title_output) ... ok test_simplify_regex (admin_docs.test_views.AdminDocViewFunctionsTests.test_simplify_regex) ... ok test_foreign_data_wrapper (inspectdb.tests.InspectDBTransactionalTests.test_foreign_data_wrapper) ... skipped 'PostgreSQL specific SQL' test_include_materialized_views (inspectdb.tests.InspectDBTransactionalTests.test_include_materialized_views) inspectdb --include-views creates models for materialized views. ... skipped "Database doesn't support feature(s): can_introspect_materialized_views" test_include_partitions (inspectdb.tests.InspectDBTransactionalTests.test_include_partitions) inspectdb --include-partitions creates models for partitions. ... skipped 'PostgreSQL specific SQL' test_include_views (inspectdb.tests.InspectDBTransactionalTests.test_include_views) inspectdb --include-views creates models for database views. ... ok test_parameters (dbshell.test_oracle.OracleDbshellTests.test_parameters) ... skipped 'Requires cx_Oracle to be installed' test_with_rlwrap (dbshell.test_oracle.OracleDbshellTests.test_with_rlwrap) ... skipped 'Requires cx_Oracle to be installed' test_without_rlwrap (dbshell.test_oracle.OracleDbshellTests.test_without_rlwrap) ... skipped 'Requires cx_Oracle to be installed' test_basic_params_specified_in_settings (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_basic_params_specified_in_settings) ... ok test_can_connect_using_sockets (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_can_connect_using_sockets) ... ok test_crash_password_does_not_leak (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_crash_password_does_not_leak) ... ok test_fails_with_keyerror_on_incomplete_config (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_fails_with_keyerror_on_incomplete_config) ... ok test_options_charset (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_options_charset) ... ok test_options_non_deprecated_keys_preferred (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_options_non_deprecated_keys_preferred) ... ok test_options_override_settings_proper_values (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_options_override_settings_proper_values) ... ok test_parameters (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_parameters) ... ok test_ssl_certificate_is_added (dbshell.test_mysql.MySqlDbshellCommandTestCase.test_ssl_certificate_is_added) ... ok test_parameters (dbshell.test_sqlite.SqliteDbshellCommandTestCase.test_parameters) ... ok test_path_name (dbshell.test_sqlite.SqliteDbshellCommandTestCase.test_path_name) ... ok test_accent (dbshell.test_postgresql.PostgreSqlDbshellCommandTestCase.test_accent) ... ok test_basic (dbshell.test_postgresql.PostgreSqlDbshellCommandTestCase.test_basic) ... ok test_column (dbshell.test_postgresql.PostgreSqlDbshellCommandTestCase.test_column) ... ok test_crash_password_does_not_leak (dbshell.test_postgresql.PostgreSqlDbshellCommandTestCase.test_crash_password_does_not_leak) ... ok test_nopass (dbshell.test_postgresql.PostgreSqlDbshellCommandTestCase.test_nopass) ... ok test_parameters (dbshell.test_postgresql.PostgreSqlDbshellCommandTestCase.test_parameters) ... ok test_sigint_handler (dbshell.test_postgresql.PostgreSqlDbshellCommandTestCase.test_sigint_handler) SIGINT is ignored in Python and passed to psql to abort queries. ... skipped 'Requires a PostgreSQL connection' test_ssl_certificate (dbshell.test_postgresql.PostgreSqlDbshellCommandTestCase.test_ssl_certificate) ... ok test_command_missing (dbshell.tests.DbshellCommandTestCase.test_command_missing) ... ok test_passes_on_record (logging_tests.tests.CallbackFilterTest.test_passes_on_record) ... ok test_sense (logging_tests.tests.CallbackFilterTest.test_sense) ... ok test_django_logger (logging_tests.tests.DefaultLoggingTests.test_django_logger) The 'django' base logger only output anything when DEBUG=True. ... ok test_django_logger_debug (logging_tests.tests.DefaultLoggingTests.test_django_logger_debug) ... ok test_django_logger_info (logging_tests.tests.DefaultLoggingTests.test_django_logger_info) ... ok test_django_logger_warning (logging_tests.tests.DefaultLoggingTests.test_django_logger_warning) ... ok test_accepts_args (logging_tests.tests.AdminEmailHandlerTest.test_accepts_args) User-supplied arguments and the EMAIL_SUBJECT_PREFIX setting are used ... ok test_accepts_args_and_request (logging_tests.tests.AdminEmailHandlerTest.test_accepts_args_and_request) The subject is also handled if being passed a request object. ... ok test_custom_exception_reporter_is_used (logging_tests.tests.AdminEmailHandlerTest.test_custom_exception_reporter_is_used) ... ok test_customize_send_mail_method (logging_tests.tests.AdminEmailHandlerTest.test_customize_send_mail_method) ... ok test_default_exception_reporter_class (logging_tests.tests.AdminEmailHandlerTest.test_default_exception_reporter_class) ... ok test_disallowed_host_doesnt_crash (logging_tests.tests.AdminEmailHandlerTest.test_disallowed_host_doesnt_crash) ... ok test_emit_non_ascii (logging_tests.tests.AdminEmailHandlerTest.test_emit_non_ascii) #23593 - AdminEmailHandler should allow Unicode characters in the ... ok test_fail_silently (logging_tests.tests.AdminEmailHandlerTest.test_fail_silently) ... ok test_subject_accepts_newlines (logging_tests.tests.AdminEmailHandlerTest.test_subject_accepts_newlines) Newlines in email reports' subjects are escaped to prevent ... ok test_uses_custom_email_backend (logging_tests.tests.AdminEmailHandlerTest.test_uses_custom_email_backend) Refs #19325 ... ok test_cached_garbaged_collected (dispatch.tests.DispatcherTests.test_cached_garbaged_collected) Make sure signal caching sender receivers don't prevent garbage ... ok test_cannot_connect_no_kwargs (dispatch.tests.DispatcherTests.test_cannot_connect_no_kwargs) ... ok test_cannot_connect_non_callable (dispatch.tests.DispatcherTests.test_cannot_connect_non_callable) ... ok test_disconnection (dispatch.tests.DispatcherTests.test_disconnection) ... ok test_garbage_collected (dispatch.tests.DispatcherTests.test_garbage_collected) ... ok test_has_listeners (dispatch.tests.DispatcherTests.test_has_listeners) ... ok test_multiple_registration (dispatch.tests.DispatcherTests.test_multiple_registration) ... ok test_send (dispatch.tests.DispatcherTests.test_send) ... ok test_send_connected_no_sender (dispatch.tests.DispatcherTests.test_send_connected_no_sender) ... ok test_send_different_no_sender (dispatch.tests.DispatcherTests.test_send_different_no_sender) ... ok test_send_no_receivers (dispatch.tests.DispatcherTests.test_send_no_receivers) ... ok test_send_robust_fail (dispatch.tests.DispatcherTests.test_send_robust_fail) ... ok test_send_robust_ignored_sender (dispatch.tests.DispatcherTests.test_send_robust_ignored_sender) ... ok test_send_robust_no_receivers (dispatch.tests.DispatcherTests.test_send_robust_no_receivers) ... ok test_send_robust_success (dispatch.tests.DispatcherTests.test_send_robust_success) ... ok test_uid_registration (dispatch.tests.DispatcherTests.test_uid_registration) ... ok test_values_returned_by_disconnection (dispatch.tests.DispatcherTests.test_values_returned_by_disconnection) ... ok test_server_formatter_default_format (logging_tests.tests.LogFormattersTests.test_server_formatter_default_format) ... ok test_server_formatter_styles (logging_tests.tests.LogFormattersTests.test_server_formatter_styles) ... ok test_internal_server_error (logging_tests.tests.HandlerLoggingTests.test_internal_server_error) ... ok test_internal_server_error_599 (logging_tests.tests.HandlerLoggingTests.test_internal_server_error_599) ... ok test_multi_part_parser_error (logging_tests.tests.HandlerLoggingTests.test_multi_part_parser_error) ... ok test_page_found_no_warning (logging_tests.tests.HandlerLoggingTests.test_page_found_no_warning) ... ok test_page_not_found_raised (logging_tests.tests.HandlerLoggingTests.test_page_not_found_raised) ... ok test_page_not_found_warning (logging_tests.tests.HandlerLoggingTests.test_page_not_found_warning) ... ok test_permission_denied (logging_tests.tests.HandlerLoggingTests.test_permission_denied) ... ok test_redirect_no_warning (logging_tests.tests.HandlerLoggingTests.test_redirect_no_warning) ... ok test_uncaught_exception (logging_tests.tests.HandlerLoggingTests.test_uncaught_exception) ... ok test_i18n_page_found_no_warning (logging_tests.tests.I18nLoggingTests.test_i18n_page_found_no_warning) ... ok test_i18n_page_not_found_warning (logging_tests.tests.I18nLoggingTests.test_i18n_page_not_found_warning) ... ok test_require_debug_false_filter (logging_tests.tests.LoggingFiltersTest.test_require_debug_false_filter) Test the RequireDebugFalse filter class. ... ok test_require_debug_true_filter (logging_tests.tests.LoggingFiltersTest.test_require_debug_true_filter) Test the RequireDebugTrue filter class. ... ok test_suspicious_email_admins (logging_tests.tests.SecurityLoggerTest.test_suspicious_email_admins) ... ok test_suspicious_operation_creates_log_message (logging_tests.tests.SecurityLoggerTest.test_suspicious_operation_creates_log_message) ... ok test_suspicious_operation_uses_sublogger (logging_tests.tests.SecurityLoggerTest.test_suspicious_operation_uses_sublogger) ... ok test_configure_initializes_logging (logging_tests.tests.SetupConfigureLogging.test_configure_initializes_logging) ... ok test_no_limit (requests.test_data_upload_settings.DataUploadMaxMemorySizeFormPostTests.test_no_limit) ... ok test_size_exceeded (requests.test_data_upload_settings.DataUploadMaxMemorySizeFormPostTests.test_size_exceeded) ... ok test_size_not_exceeded (requests.test_data_upload_settings.DataUploadMaxMemorySizeFormPostTests.test_size_not_exceeded) ... ok test_data_upload_max_memory_size_exceeded (requests.test_data_upload_settings.DataUploadMaxMemorySizeGetTests.test_data_upload_max_memory_size_exceeded) ... ok test_empty_content_length (requests.test_data_upload_settings.DataUploadMaxMemorySizeGetTests.test_empty_content_length) ... ok test_no_limit (requests.test_data_upload_settings.DataUploadMaxMemorySizeGetTests.test_no_limit) ... ok test_size_not_exceeded (requests.test_data_upload_settings.DataUploadMaxMemorySizeGetTests.test_size_not_exceeded) ... ok test_file_passes (requests.test_data_upload_settings.DataUploadMaxMemorySizeMultipartPostTests.test_file_passes) ... ok test_no_limit (requests.test_data_upload_settings.DataUploadMaxMemorySizeMultipartPostTests.test_no_limit) ... ok test_size_exceeded (requests.test_data_upload_settings.DataUploadMaxMemorySizeMultipartPostTests.test_size_exceeded) ... ok test_size_not_exceeded (requests.test_data_upload_settings.DataUploadMaxMemorySizeMultipartPostTests.test_size_not_exceeded) ... ok test_no_limit (requests.test_data_upload_settings.DataUploadMaxNumberOfFieldsFormPost.test_no_limit) ... ok test_number_exceeded (requests.test_data_upload_settings.DataUploadMaxNumberOfFieldsFormPost.test_number_exceeded) ... ok test_number_not_exceeded (requests.test_data_upload_settings.DataUploadMaxNumberOfFieldsFormPost.test_number_not_exceeded) ... ok test_get_max_fields_exceeded (requests.test_data_upload_settings.DataUploadMaxNumberOfFieldsGet.test_get_max_fields_exceeded) ... ok test_get_max_fields_not_exceeded (requests.test_data_upload_settings.DataUploadMaxNumberOfFieldsGet.test_get_max_fields_not_exceeded) ... ok test_no_limit (requests.test_data_upload_settings.DataUploadMaxNumberOfFieldsMultipartPost.test_no_limit) ... ok test_number_exceeded (requests.test_data_upload_settings.DataUploadMaxNumberOfFieldsMultipartPost.test_number_exceeded) ... ok test_number_not_exceeded (requests.test_data_upload_settings.DataUploadMaxNumberOfFieldsMultipartPost.test_number_not_exceeded) ... ok test_no_limit (requests.test_data_upload_settings.DataUploadMaxNumberOfFilesMultipartPost.test_no_limit) ... ok test_number_exceeded (requests.test_data_upload_settings.DataUploadMaxNumberOfFilesMultipartPost.test_number_exceeded) ... ok test_number_not_exceeded (requests.test_data_upload_settings.DataUploadMaxNumberOfFilesMultipartPost.test_number_not_exceeded) ... ok test_is_ajax (requests.test_is_ajax_deprecations.TestDeprecatedIsAjax.test_is_ajax) ... ok test_absolute_url (requests.tests.BuildAbsoluteURITests.test_absolute_url) ... ok test_host_retrieval (requests.tests.BuildAbsoluteURITests.test_host_retrieval) ... ok test_request_path_begins_with_two_slashes (requests.tests.BuildAbsoluteURITests.test_request_path_begins_with_two_slashes) ... ok test_get_host_suggestion_of_allowed_host (requests.tests.HostValidationTests.test_get_host_suggestion_of_allowed_host) get_host() makes helpful suggestions if a valid-looking host is not in ALLOWED_HOSTS. ... ok test_get_port (requests.tests.HostValidationTests.test_get_port) ... ok test_get_port_with_x_forwarded_port (requests.tests.HostValidationTests.test_get_port_with_x_forwarded_port) ... ok test_host_validation_in_debug_mode (requests.tests.HostValidationTests.test_host_validation_in_debug_mode) If ALLOWED_HOSTS is empty and DEBUG is True, variants of localhost are ... ok test_http_get_host (requests.tests.HostValidationTests.test_http_get_host) ... ok test_http_get_host_with_x_forwarded_host (requests.tests.HostValidationTests.test_http_get_host_with_x_forwarded_host) ... ok test_split_domain_port_removes_trailing_dot (requests.tests.HostValidationTests.test_split_domain_port_removes_trailing_dot) ... ok test_custom_logging (logging_tests.tests.SettingsCustomLoggingTest.test_custom_logging) ... ok test_circular_dependency (logging_tests.tests.SettingsConfigTest.test_circular_dependency) ... ok test_basic (requests.tests.HttpHeadersTests.test_basic) ... ok test_parse_header_name (requests.tests.HttpHeadersTests.test_parse_header_name) ... ok test_base_request_headers (requests.tests.RequestHeadersTests.test_base_request_headers) ... ok test_wsgi_request_headers (requests.tests.RequestHeadersTests.test_wsgi_request_headers) ... ok test_wsgi_request_headers_get (requests.tests.RequestHeadersTests.test_wsgi_request_headers_get) ... ok test_wsgi_request_headers_getitem (requests.tests.RequestHeadersTests.test_wsgi_request_headers_getitem) ... ok test_abstract_model_not_instantiated (model_meta.tests.AbstractModelTests.test_abstract_model_not_instantiated) ... ok test_FILES_connection_error (requests.tests.RequestsTests.test_FILES_connection_error) If wsgi.input.read() raises an exception while trying to read() the ... ok test_POST_after_body_read (requests.tests.RequestsTests.test_POST_after_body_read) POST should be populated even if body is read first ... ok test_POST_after_body_read_and_stream_read (requests.tests.RequestsTests.test_POST_after_body_read_and_stream_read) POST should be populated even if body is read first, and then ... ok test_POST_after_body_read_and_stream_read_multipart (requests.tests.RequestsTests.test_POST_after_body_read_and_stream_read_multipart) POST should be populated even if body is read first, and then ... ok test_POST_binary_only (requests.tests.RequestsTests.test_POST_binary_only) ... ok test_POST_connection_error (requests.tests.RequestsTests.test_POST_connection_error) If wsgi.input.read() raises an exception while trying to read() the ... ok test_POST_immutable_for_multipart (requests.tests.RequestsTests.test_POST_immutable_for_multipart) MultiPartParser.parse() leaves request.POST immutable. ... ok test_POST_multipart_with_content_length_zero (requests.tests.RequestsTests.test_POST_multipart_with_content_length_zero) Multipart POST requests with Content-Length >= 0 are valid and need to be handled. ... ok test_alternate_charset_POST (requests.tests.RequestsTests.test_alternate_charset_POST) Test a POST with non-utf-8 payload encoding. ... ok test_body_after_POST_multipart_form_data (requests.tests.RequestsTests.test_body_after_POST_multipart_form_data) Reading body after parsing multipart/form-data is not allowed ... ok test_body_after_POST_multipart_related (requests.tests.RequestsTests.test_body_after_POST_multipart_related) Reading body after parsing multipart that isn't form-data is allowed ... ok test_get_raw_uri (requests.tests.RequestsTests.test_get_raw_uri) ... ok test_httprequest (requests.tests.RequestsTests.test_httprequest) ... ok test_httprequest_full_path (requests.tests.RequestsTests.test_httprequest_full_path) ... ok test_httprequest_full_path_with_query_string_and_fragment (requests.tests.RequestsTests.test_httprequest_full_path_with_query_string_and_fragment) ... ok test_httprequest_repr (requests.tests.RequestsTests.test_httprequest_repr) ... ok test_httprequest_repr_invalid_method_and_path (requests.tests.RequestsTests.test_httprequest_repr_invalid_method_and_path) ... ok test_limited_stream (requests.tests.RequestsTests.test_limited_stream) ... ok test_multipart_non_ascii_content_type (requests.tests.RequestsTests.test_multipart_non_ascii_content_type) ... ok test_multipart_without_boundary (requests.tests.RequestsTests.test_multipart_without_boundary) ... ok test_non_ascii_POST (requests.tests.RequestsTests.test_non_ascii_POST) ... ok test_read_after_value (requests.tests.RequestsTests.test_read_after_value) Reading from request is allowed after accessing request contents as ... ok test_read_by_lines (requests.tests.RequestsTests.test_read_by_lines) ... ok test_set_encoding_clears_GET (requests.tests.RequestsTests.test_set_encoding_clears_GET) ... ok test_set_encoding_clears_POST (requests.tests.RequestsTests.test_set_encoding_clears_POST) ... ok test_stream (requests.tests.RequestsTests.test_stream) ... ok test_value_after_read (requests.tests.RequestsTests.test_value_after_read) Construction of POST or body is not allowed after reading ... ok test_wsgirequest (requests.tests.RequestsTests.test_wsgirequest) ... ok test_wsgirequest_path_info (requests.tests.RequestsTests.test_wsgirequest_path_info) ... ok test_wsgirequest_path_with_force_script_name_trailing_slash (requests.tests.RequestsTests.test_wsgirequest_path_with_force_script_name_trailing_slash) The request's path is correctly assembled, regardless of whether or not ... ok test_wsgirequest_repr (requests.tests.RequestsTests.test_wsgirequest_repr) ... ok test_wsgirequest_script_url_double_slashes (requests.tests.RequestsTests.test_wsgirequest_script_url_double_slashes) WSGI squashes multiple successive slashes in PATH_INFO, WSGIRequest ... ok test_wsgirequest_with_force_script_name (requests.tests.RequestsTests.test_wsgirequest_with_force_script_name) The FORCE_SCRIPT_NAME setting takes precedence over the request's ... ok test_wsgirequest_with_script_name (requests.tests.RequestsTests.test_wsgirequest_with_script_name) The request's path is correctly assembled, regardless of whether or ... ok test_fields (model_meta.tests.DataTests.test_fields) ... ok test_local_concrete_fields (model_meta.tests.DataTests.test_local_concrete_fields) ... ok test_local_fields (model_meta.tests.DataTests.test_local_fields) ... ok test_label (model_meta.tests.LabelTests.test_label) ... ok test_label_lower (model_meta.tests.LabelTests.test_label_lower) ... ok test_get_data_field (model_meta.tests.GetFieldByNameTests.test_get_data_field) ... ok test_get_fields_only_searches_forward_on_apps_not_ready (model_meta.tests.GetFieldByNameTests.test_get_fields_only_searches_forward_on_apps_not_ready) ... ok test_get_generic_relation (model_meta.tests.GetFieldByNameTests.test_get_generic_relation) ... ok test_get_m2m_field (model_meta.tests.GetFieldByNameTests.test_get_m2m_field) ... ok test_get_related_m2m (model_meta.tests.GetFieldByNameTests.test_get_related_m2m) ... ok test_get_related_object (model_meta.tests.GetFieldByNameTests.test_get_related_object) ... ok test_get_fields_is_immutable (model_meta.tests.GetFieldsTests.test_get_fields_is_immutable) ... ok test_many_to_many (model_meta.tests.M2MTests.test_many_to_many) ... ok test_many_to_many_with_model (model_meta.tests.M2MTests.test_many_to_many_with_model) ... ok test_get_parent_list (model_meta.tests.ParentListTests.test_get_parent_list) ... ok test_private_fields (model_meta.tests.PrivateFieldsTests.test_private_fields) ... ok test_person (model_meta.tests.PropertyNamesTests.test_person) ... ok test_related_objects (model_meta.tests.RelatedObjectsTests.test_related_objects) ... ok test_related_objects_include_hidden (model_meta.tests.RelatedObjectsTests.test_related_objects_include_hidden) ... ok test_related_objects_include_hidden_local_only (model_meta.tests.RelatedObjectsTests.test_related_objects_include_hidden_local_only) ... ok test_related_objects_local (model_meta.tests.RelatedObjectsTests.test_related_objects_local) ... ok test_pk (model_meta.tests.ReturningFieldsTests.test_pk) ... ok test_isinstance_of_autofield (model_fields.test_autofield.AutoFieldInheritanceTests.test_isinstance_of_autofield) ... ok test_issubclass_of_autofield (model_fields.test_autofield.AutoFieldInheritanceTests.test_issubclass_of_autofield) ... ok test_boolean_field_doesnt_accept_empty_input (model_fields.test_booleanfield.ValidationTest.test_boolean_field_doesnt_accept_empty_input) ... ok test_nullbooleanfield_blank (model_fields.test_booleanfield.ValidationTest.test_nullbooleanfield_blank) NullBooleanField shouldn't throw a validation error when given a value ... ok test_deconstruct (model_fields.test_charfield.TestMethods.test_deconstruct) ... ok test_charfield_cleans_empty_string_when_blank_true (model_fields.test_charfield.ValidationTests.test_charfield_cleans_empty_string_when_blank_true) ... ok test_charfield_raises_error_on_empty_input (model_fields.test_charfield.ValidationTests.test_charfield_raises_error_on_empty_input) ... ok test_charfield_raises_error_on_empty_string (model_fields.test_charfield.ValidationTests.test_charfield_raises_error_on_empty_string) ... ok test_charfield_with_choices_cleans_valid_choice (model_fields.test_charfield.ValidationTests.test_charfield_with_choices_cleans_valid_choice) ... ok test_charfield_with_choices_raises_error_on_invalid_choice (model_fields.test_charfield.ValidationTests.test_charfield_with_choices_raises_error_on_invalid_choice) ... ok test_enum_choices_cleans_valid_string (model_fields.test_charfield.ValidationTests.test_enum_choices_cleans_valid_string) ... ok test_enum_choices_invalid_input (model_fields.test_charfield.ValidationTests.test_enum_choices_invalid_input) ... ok test_datefield_cleans_date (model_fields.test_datetimefield.ValidationTest.test_datefield_cleans_date) ... ok test_clear_cache_clears_relation_tree (model_meta.tests.RelationTreeTests.test_clear_cache_clears_relation_tree) ... ok test_first_relation_tree_access_populates_all (model_meta.tests.RelationTreeTests.test_first_relation_tree_access_populates_all) ... ok test_relations_related_objects (model_meta.tests.RelationTreeTests.test_relations_related_objects) ... ok test_formfield (model_fields.test_durationfield.TestFormField.test_formfield) ... ok test_invalid_string (model_fields.test_durationfield.TestValidation.test_invalid_string) ... ok test_dumping (model_fields.test_durationfield.TestSerialization.test_dumping) ... ok test_loading (model_fields.test_durationfield.TestSerialization.test_loading) ... ok test_callable_path (model_fields.test_filepathfield.FilePathFieldTests.test_callable_path) ... ok test_path (model_fields.test_filepathfield.FilePathFieldTests.test_path) ... ok test_choices_validation_supports_named_groups (model_fields.test_integerfield.ValidationTests.test_choices_validation_supports_named_groups) ... ok test_enum_choices_cleans_valid_string (model_fields.test_integerfield.ValidationTests.test_enum_choices_cleans_valid_string) ... ok test_enum_choices_invalid_input (model_fields.test_integerfield.ValidationTests.test_enum_choices_invalid_input) ... ok test_integerfield_cleans_valid_string (model_fields.test_integerfield.ValidationTests.test_integerfield_cleans_valid_string) ... ok test_integerfield_raises_error_on_empty_input (model_fields.test_integerfield.ValidationTests.test_integerfield_raises_error_on_empty_input) ... ok test_integerfield_raises_error_on_invalid_intput (model_fields.test_integerfield.ValidationTests.test_integerfield_raises_error_on_invalid_intput) ... ok test_integerfield_validates_zero_against_choices (model_fields.test_integerfield.ValidationTests.test_integerfield_validates_zero_against_choices) ... ok test_nullable_integerfield_cleans_none_on_null_and_blank_true (model_fields.test_integerfield.ValidationTests.test_nullable_integerfield_cleans_none_on_null_and_blank_true) ... ok test_nullable_integerfield_raises_error_with_blank_false (model_fields.test_integerfield.ValidationTests.test_nullable_integerfield_raises_error_with_blank_false) ... ok test_all_field_types_should_have_flags (model_fields.test_field_flags.FieldFlagsTests.test_all_field_types_should_have_flags) ... ok test_cardinality_m2m (model_fields.test_field_flags.FieldFlagsTests.test_cardinality_m2m) ... ok test_cardinality_m2o (model_fields.test_field_flags.FieldFlagsTests.test_cardinality_m2o) ... ok test_cardinality_o2m (model_fields.test_field_flags.FieldFlagsTests.test_cardinality_o2m) ... ok test_cardinality_o2o (model_fields.test_field_flags.FieldFlagsTests.test_cardinality_o2o) ... ok test_each_field_should_have_a_concrete_attribute (model_fields.test_field_flags.FieldFlagsTests.test_each_field_should_have_a_concrete_attribute) ... ok test_each_field_should_have_a_has_rel_attribute (model_fields.test_field_flags.FieldFlagsTests.test_each_field_should_have_a_has_rel_attribute) ... ok test_each_field_should_have_an_editable_attribute (model_fields.test_field_flags.FieldFlagsTests.test_each_field_should_have_an_editable_attribute) ... ok test_each_object_should_have_auto_created (model_fields.test_field_flags.FieldFlagsTests.test_each_object_should_have_auto_created) ... ok test_field_names_should_always_be_available (model_fields.test_field_flags.FieldFlagsTests.test_field_names_should_always_be_available) ... ok test_hidden_flag (model_fields.test_field_flags.FieldFlagsTests.test_hidden_flag) ... ok test_model_and_reverse_model_should_equal_on_relations (model_fields.test_field_flags.FieldFlagsTests.test_model_and_reverse_model_should_equal_on_relations) ... ok test_non_concrete_fields (model_fields.test_field_flags.FieldFlagsTests.test_non_concrete_fields) ... ok test_non_editable_fields (model_fields.test_field_flags.FieldFlagsTests.test_non_editable_fields) ... ok test_null (model_fields.test_field_flags.FieldFlagsTests.test_null) ... ok test_related_fields (model_fields.test_field_flags.FieldFlagsTests.test_related_fields) ... ok test_formfield (model_fields.test_jsonfield.TestFormField.test_formfield) ... ok test_formfield_custom_encoder_decoder (model_fields.test_jsonfield.TestFormField.test_formfield_custom_encoder_decoder) ... ok test_dumping (model_fields.test_jsonfield.TestSerialization.test_dumping) ... ok test_loading (model_fields.test_jsonfield.TestSerialization.test_loading) ... ok test_xml_serialization (model_fields.test_jsonfield.TestSerialization.test_xml_serialization) ... ok test_deconstruct (model_fields.test_jsonfield.TestMethods.test_deconstruct) ... ok test_deconstruct_custom_encoder_decoder (model_fields.test_jsonfield.TestMethods.test_deconstruct_custom_encoder_decoder) ... ok test_get_transforms (model_fields.test_jsonfield.TestMethods.test_get_transforms) ... ok test_key_transform_text_lookup_mixin_non_key_transform (model_fields.test_jsonfield.TestMethods.test_key_transform_text_lookup_mixin_non_key_transform) ... ok test_custom_encoder (model_fields.test_jsonfield.TestValidation.test_custom_encoder) ... ok test_invalid_decoder (model_fields.test_jsonfield.TestValidation.test_invalid_decoder) ... ok test_invalid_encoder (model_fields.test_jsonfield.TestValidation.test_invalid_encoder) ... ok test_validation_error (model_fields.test_jsonfield.TestValidation.test_validation_error) ... ok test_abstract_model_app_relative_foreign_key (model_fields.test_manytomanyfield.ManyToManyFieldTests.test_abstract_model_app_relative_foreign_key) ... ok test_abstract_model_pending_operations (model_fields.test_manytomanyfield.ManyToManyFieldTests.test_abstract_model_pending_operations) Many-to-many fields declared on abstract models should not add lazy ... ok test_AutoField (model_fields.test_promises.PromiseTest.test_AutoField) ... ok test_BinaryField (model_fields.test_promises.PromiseTest.test_BinaryField) ... ok test_BooleanField (model_fields.test_promises.PromiseTest.test_BooleanField) ... ok test_CharField (model_fields.test_promises.PromiseTest.test_CharField) ... ok test_DateField (model_fields.test_promises.PromiseTest.test_DateField) ... ok test_DateTimeField (model_fields.test_promises.PromiseTest.test_DateTimeField) ... ok test_DecimalField (model_fields.test_promises.PromiseTest.test_DecimalField) ... ok test_EmailField (model_fields.test_promises.PromiseTest.test_EmailField) ... ok test_FileField (model_fields.test_promises.PromiseTest.test_FileField) ... ok test_FilePathField (model_fields.test_promises.PromiseTest.test_FilePathField) ... ok test_FloatField (model_fields.test_promises.PromiseTest.test_FloatField) ... ok test_GenericIPAddressField (model_fields.test_promises.PromiseTest.test_GenericIPAddressField) ... ok test_IPAddressField (model_fields.test_promises.PromiseTest.test_IPAddressField) ... ok test_ImageField (model_fields.test_promises.PromiseTest.test_ImageField) ... ok test_IntegerField (model_fields.test_promises.PromiseTest.test_IntegerField) ... ok test_NullBooleanField (model_fields.test_promises.PromiseTest.test_NullBooleanField) ... ok test_PositiveBigIntegerField (model_fields.test_promises.PromiseTest.test_PositiveBigIntegerField) ... ok test_PositiveIntegerField (model_fields.test_promises.PromiseTest.test_PositiveIntegerField) ... ok test_PositiveSmallIntegerField (model_fields.test_promises.PromiseTest.test_PositiveSmallIntegerField) ... ok test_SlugField (model_fields.test_promises.PromiseTest.test_SlugField) ... ok test_SmallIntegerField (model_fields.test_promises.PromiseTest.test_SmallIntegerField) ... ok test_TextField (model_fields.test_promises.PromiseTest.test_TextField) ... ok test_TimeField (model_fields.test_promises.PromiseTest.test_TimeField) ... ok test_URLField (model_fields.test_promises.PromiseTest.test_URLField) ... ok test_deconstruct (model_fields.test_textfield.TestMethods.test_deconstruct) ... ok test_deconstruct (model_fields.test_uuid.TestMethods.test_deconstruct) ... ok test_to_python (model_fields.test_uuid.TestMethods.test_to_python) ... ok test_to_python_int_too_large (model_fields.test_uuid.TestMethods.test_to_python_int_too_large) ... ok test_to_python_int_values (model_fields.test_uuid.TestMethods.test_to_python_int_values) ... ok test_dumping (model_fields.test_uuid.TestSerialization.test_dumping) ... ok test_loading (model_fields.test_uuid.TestSerialization.test_loading) ... ok test_nullable_loading (model_fields.test_uuid.TestSerialization.test_nullable_loading) ... ok test_invalid_uuid (model_fields.test_uuid.TestValidation.test_invalid_uuid) ... ok test_uuid_instance_ok (model_fields.test_uuid.TestValidation.test_uuid_instance_ok) ... ok test_check (model_fields.tests.ChoicesTests.test_check) ... ok test_choices (model_fields.tests.ChoicesTests.test_choices) ... ok test_flatchoices (model_fields.tests.ChoicesTests.test_flatchoices) ... ok test_formfield (model_fields.tests.ChoicesTests.test_formfield) ... ok test_invalid_choice (model_fields.tests.ChoicesTests.test_invalid_choice) ... ok test_abstract_inherited_fields (model_fields.tests.BasicFieldTests.test_abstract_inherited_fields) Field instances from abstract models are not equal. ... ok test_choices_form_class (model_fields.tests.BasicFieldTests.test_choices_form_class) Can supply a custom choices form class to Field.formfield() ... ok test_deconstruct_nested_field (model_fields.tests.BasicFieldTests.test_deconstruct_nested_field) deconstruct() uses __qualname__ for nested class support. ... ok test_field_instance_is_picklable (model_fields.tests.BasicFieldTests.test_field_instance_is_picklable) Field instances can be pickled. ... ok test_field_name (model_fields.tests.BasicFieldTests.test_field_name) A defined field name (name="fieldname") is used instead of the model ... ok test_field_ordering (model_fields.tests.BasicFieldTests.test_field_ordering) Fields are ordered based on their creation. ... ok test_field_repr (model_fields.tests.BasicFieldTests.test_field_repr) __repr__() of a field displays its name. ... ok test_field_repr_nested (model_fields.tests.BasicFieldTests.test_field_repr_nested) __repr__() uses __qualname__ for nested class support. ... ok test_field_str (model_fields.tests.BasicFieldTests.test_field_str) ... ok test_field_verbose_name (model_fields.tests.BasicFieldTests.test_field_verbose_name) ... ok test_formfield_disabled (model_fields.tests.BasicFieldTests.test_formfield_disabled) Field.formfield() sets disabled for fields with choices. ... ok test_show_hidden_initial (model_fields.tests.BasicFieldTests.test_show_hidden_initial) Fields with choices respect show_hidden_initial as a kwarg to ... ok test_blank_in_choices (model_fields.tests.GetChoicesTests.test_blank_in_choices) ... ok test_blank_in_grouped_choices (model_fields.tests.GetChoicesTests.test_blank_in_grouped_choices) ... ok test_empty_choices (model_fields.tests.GetChoicesTests.test_empty_choices) ... ok test_lazy_strings_not_evaluated (model_fields.tests.GetChoicesTests.test_lazy_strings_not_evaluated) ... ok test_choices_and_field_display (model_fields.tests.GetFieldDisplayTests.test_choices_and_field_display) get_choices() interacts with get_FIELD_display() to return the expected ... ok test_empty_iterator_choices (model_fields.tests.GetFieldDisplayTests.test_empty_iterator_choices) get_choices() works with empty iterators. ... ok test_get_FIELD_display_translated (model_fields.tests.GetFieldDisplayTests.test_get_FIELD_display_translated) A translated display value is coerced to str. ... ok test_iterator_choices (model_fields.tests.GetFieldDisplayTests.test_iterator_choices) get_choices() works with Iterators. ... ok test_overriding_FIELD_display (model_fields.tests.GetFieldDisplayTests.test_overriding_FIELD_display) ... ok test_overriding_inherited_FIELD_display (model_fields.tests.GetFieldDisplayTests.test_overriding_inherited_FIELD_display) ... ok test_missing_alias (expressions.test_deprecation.GetGroupByColsTest.test_missing_alias) ... ok test_resolve_output_field (expressions.tests.CombinedExpressionTests.test_resolve_output_field) ... ok test_and (expressions.tests.CombinableTests.test_and) ... ok test_negation (expressions.tests.CombinableTests.test_negation) ... ok test_or (expressions.tests.CombinableTests.test_or) ... ok test_reversed_and (expressions.tests.CombinableTests.test_reversed_and) ... ok test_reversed_or (expressions.tests.CombinableTests.test_reversed_or) ... ok test_empty_group_by (expressions.tests.ExpressionWrapperTests.test_empty_group_by) ... ok test_non_empty_group_by (expressions.tests.ExpressionWrapperTests.test_non_empty_group_by) ... ok test_deconstruct (expressions.tests.FTests.test_deconstruct) ... ok test_deepcopy (expressions.tests.FTests.test_deepcopy) ... ok test_equal (expressions.tests.FTests.test_equal) ... ok test_hash (expressions.tests.FTests.test_hash) ... ok test_not_equal_Value (expressions.tests.FTests.test_not_equal_Value) ... ok test_equal (expressions.tests.OrderByTests.test_equal) ... ok test_hash (expressions.tests.OrderByTests.test_hash) ... ok test_aggregates (expressions.tests.ReprTests.test_aggregates) ... ok test_distinct_aggregates (expressions.tests.ReprTests.test_distinct_aggregates) ... ok test_expressions (expressions.tests.ReprTests.test_expressions) ... ok test_filtered_aggregates (expressions.tests.ReprTests.test_filtered_aggregates) ... ok test_functions (expressions.tests.ReprTests.test_functions) ... ok test_equal (expressions.tests.SimpleExpressionTests.test_equal) ... ok test_hash (expressions.tests.SimpleExpressionTests.test_hash) ... ok test_covering_func_index (indexes.tests.CoveringIndexTests.test_covering_func_index) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_covering_index (indexes.tests.CoveringIndexTests.test_covering_index) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_covering_partial_index (indexes.tests.CoveringIndexTests.test_covering_partial_index) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_condition_ignored (indexes.tests.PartialIndexConditionIgnoredTests.test_condition_ignored) ... skipped 'Database has feature(s) supports_partial_indexes' test_covering_ignored (indexes.tests.CoveringIndexIgnoredTests.test_covering_ignored) ... ok test_no_index_for_foreignkey (indexes.tests.SchemaIndexesMySQLTests.test_no_index_for_foreignkey) MySQL on InnoDB already creates indexes automatically for foreign keys. ... skipped 'MySQL tests' test_create_index_ignores_opclasses (indexes.tests.SchemaIndexesNotPostgreSQLTests.test_create_index_ignores_opclasses) ... ok test_ops_class (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class) ... skipped 'PostgreSQL tests' test_ops_class_columns_lists_sql (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_columns_lists_sql) ... skipped 'PostgreSQL tests' test_ops_class_descending (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_descending) ... skipped 'PostgreSQL tests' test_ops_class_descending_columns_list_sql (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_descending_columns_list_sql) ... skipped 'PostgreSQL tests' test_ops_class_descending_partial (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_descending_partial) ... skipped 'PostgreSQL tests' test_ops_class_include (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_include) ... skipped 'PostgreSQL tests' test_ops_class_include_tablespace (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_include_tablespace) ... skipped 'PostgreSQL tests' test_ops_class_multiple_columns (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_multiple_columns) ... skipped 'PostgreSQL tests' test_ops_class_partial (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_partial) ... skipped 'PostgreSQL tests' test_ops_class_partial_tablespace (indexes.tests.SchemaIndexesPostgreSQLTests.test_ops_class_partial_tablespace) ... skipped 'PostgreSQL tests' test_text_indexes (indexes.tests.SchemaIndexesPostgreSQLTests.test_text_indexes) Test creation of PostgreSQL-specific text indexes (#12234) ... skipped 'PostgreSQL tests' test_virtual_relation_indexes (indexes.tests.SchemaIndexesPostgreSQLTests.test_virtual_relation_indexes) Test indexes are not created for related objects ... skipped 'PostgreSQL tests' test_persistence (migration_test_data_persistence.tests.MigrationDataPersistenceTestCase.test_persistence) ... ok test_abstract_children (model_indexes.tests.SimpleIndexesTests.test_abstract_children) ... ok test_clone (model_indexes.tests.SimpleIndexesTests.test_clone) ... ok test_clone_with_expressions (model_indexes.tests.SimpleIndexesTests.test_clone_with_expressions) ... ok test_condition_must_be_q (model_indexes.tests.SimpleIndexesTests.test_condition_must_be_q) ... ok test_condition_requires_index_name (model_indexes.tests.SimpleIndexesTests.test_condition_requires_index_name) ... ok test_deconstruct_with_condition (model_indexes.tests.SimpleIndexesTests.test_deconstruct_with_condition) ... ok test_deconstruct_with_expressions (model_indexes.tests.SimpleIndexesTests.test_deconstruct_with_expressions) ... ok test_deconstruct_with_include (model_indexes.tests.SimpleIndexesTests.test_deconstruct_with_include) ... ok test_deconstruction (model_indexes.tests.SimpleIndexesTests.test_deconstruction) ... ok test_eq (model_indexes.tests.SimpleIndexesTests.test_eq) ... ok test_eq_func (model_indexes.tests.SimpleIndexesTests.test_eq_func) ... ok test_expressions_and_fields_mutually_exclusive (model_indexes.tests.SimpleIndexesTests.test_expressions_and_fields_mutually_exclusive) ... ok test_expressions_requires_index_name (model_indexes.tests.SimpleIndexesTests.test_expressions_requires_index_name) ... ok test_expressions_with_opclasses (model_indexes.tests.SimpleIndexesTests.test_expressions_with_opclasses) ... ok test_fields_tuple (model_indexes.tests.SimpleIndexesTests.test_fields_tuple) ... ok test_include_requires_index_name (model_indexes.tests.SimpleIndexesTests.test_include_requires_index_name) ... ok test_include_requires_list_or_tuple (model_indexes.tests.SimpleIndexesTests.test_include_requires_list_or_tuple) ... ok test_index_fields_strings (model_indexes.tests.SimpleIndexesTests.test_index_fields_strings) ... ok test_index_fields_type (model_indexes.tests.SimpleIndexesTests.test_index_fields_type) ... ok test_name_auto_generation (model_indexes.tests.SimpleIndexesTests.test_name_auto_generation) ... ok test_name_auto_generation_with_quoted_db_table (model_indexes.tests.SimpleIndexesTests.test_name_auto_generation_with_quoted_db_table) ... ok test_name_set (model_indexes.tests.SimpleIndexesTests.test_name_set) ... ok test_opclasses_and_fields_same_length (model_indexes.tests.SimpleIndexesTests.test_opclasses_and_fields_same_length) ... ok test_opclasses_requires_index_name (model_indexes.tests.SimpleIndexesTests.test_opclasses_requires_index_name) ... ok test_opclasses_requires_list_or_tuple (model_indexes.tests.SimpleIndexesTests.test_opclasses_requires_list_or_tuple) ... ok test_repr (model_indexes.tests.SimpleIndexesTests.test_repr) ... ok test_requires_field_or_expression (model_indexes.tests.SimpleIndexesTests.test_requires_field_or_expression) ... ok test_suffix (model_indexes.tests.SimpleIndexesTests.test_suffix) ... ok test_boolean_restriction_partial (indexes.tests.PartialIndexTests.test_boolean_restriction_partial) ... ok test_integer_restriction_partial (indexes.tests.PartialIndexTests.test_integer_restriction_partial) ... ok test_is_null_condition (indexes.tests.PartialIndexTests.test_is_null_condition) ... ok test_multiple_conditions (indexes.tests.PartialIndexTests.test_multiple_conditions) ... ok test_partial_func_index (indexes.tests.PartialIndexTests.test_partial_func_index) ... ok test_partial_index (indexes.tests.PartialIndexTests.test_partial_index) ... ok test_none_allowed (generic_relations.tests.TestInitWithNoneArgument.test_none_allowed) ... ok test_custom_form_meta_exclude (generic_inline_admin.tests.GenericInlineModelAdminTest.test_custom_form_meta_exclude) The custom ModelForm's `Meta.exclude` is respected by ... ok test_custom_form_meta_exclude_with_readonly (generic_inline_admin.tests.GenericInlineModelAdminTest.test_custom_form_meta_exclude_with_readonly) The custom ModelForm's `Meta.exclude` is respected when ... ok test_get_fieldsets (generic_inline_admin.tests.GenericInlineModelAdminTest.test_get_fieldsets) ... ok test_get_formset_kwargs (generic_inline_admin.tests.GenericInlineModelAdminTest.test_get_formset_kwargs) ... ok test_get_formsets_with_inlines_returns_tuples (generic_inline_admin.tests.GenericInlineModelAdminTest.test_get_formsets_with_inlines_returns_tuples) get_formsets_with_inlines() returns the correct tuples. ... ok test_get_inline_instances_override_get_inlines (generic_inline_admin.tests.GenericInlineModelAdminTest.test_get_inline_instances_override_get_inlines) ... ok test_no_deletion (generic_inline_admin.tests.NoInlineDeletionTest.test_no_deletion) ... ok test_https (servers.test_basehttp.WSGIRequestHandlerTestCase.test_https) ... ok test_log_message (servers.test_basehttp.WSGIRequestHandlerTestCase.test_log_message) ... ok test_strips_underscore_headers (servers.test_basehttp.WSGIRequestHandlerTestCase.test_strips_underscore_headers) WSGIRequestHandler ignores headers containing underscores. ... ok test_broken_pipe_errors (servers.test_basehttp.WSGIServerTestCase.test_broken_pipe_errors) WSGIServer handles broken pipe errors. ... ok test_unsaved_fk (model_fields.test_uuid.TestAsPrimaryKeyTransactionTests.test_unsaved_fk) ... ok test_bigautofield (introspection.tests.IntrospectionTests.test_bigautofield) ... ok test_django_table_names (introspection.tests.IntrospectionTests.test_django_table_names) ... ok test_django_table_names_retval_type (introspection.tests.IntrospectionTests.test_django_table_names_retval_type) ... ok test_get_constraints (introspection.tests.IntrospectionTests.test_get_constraints) ... ok test_get_constraints_index_types (introspection.tests.IntrospectionTests.test_get_constraints_index_types) ... ok test_get_constraints_indexes_orders (introspection.tests.IntrospectionTests.test_get_constraints_indexes_orders) Indexes have the 'orders' key with a list of 'ASC'/'DESC' values. ... ok test_get_constraints_unique_indexes_orders (introspection.tests.IntrospectionTests.test_get_constraints_unique_indexes_orders) ... ok test_get_key_columns (introspection.tests.IntrospectionTests.test_get_key_columns) ... ok test_get_primary_key_column (introspection.tests.IntrospectionTests.test_get_primary_key_column) ... ok test_get_relations (introspection.tests.IntrospectionTests.test_get_relations) ... ok test_get_relations_alt_format (introspection.tests.IntrospectionTests.test_get_relations_alt_format) With SQLite, foreign keys can be added with different syntaxes and ... ok test_get_table_description_col_lengths (introspection.tests.IntrospectionTests.test_get_table_description_col_lengths) ... ok test_get_table_description_names (introspection.tests.IntrospectionTests.test_get_table_description_names) ... ok test_get_table_description_nullable (introspection.tests.IntrospectionTests.test_get_table_description_nullable) ... ok test_get_table_description_types (introspection.tests.IntrospectionTests.test_get_table_description_types) ... ok test_installed_models (introspection.tests.IntrospectionTests.test_installed_models) ... ok test_postgresql_real_type (introspection.tests.IntrospectionTests.test_postgresql_real_type) ... skipped "Database doesn't support feature(s): has_real_datatype" test_sequence_list (introspection.tests.IntrospectionTests.test_sequence_list) ... ok test_smallautofield (introspection.tests.IntrospectionTests.test_smallautofield) ... ok test_table_names (introspection.tests.IntrospectionTests.test_table_names) ... ok test_table_names_with_views (introspection.tests.IntrospectionTests.test_table_names_with_views) ... ok test_unmanaged_through_model (introspection.tests.IntrospectionTests.test_unmanaged_through_model) ... ok test_live_server_url_is_class_property (servers.tests.LiveServerAddress.test_live_server_url_is_class_property) ... ok test_set_up_class (servers.tests.LiveServerTestCaseSetupTest.test_set_up_class) ... ok test_database_writes (servers.tests.LiveServerDatabase.test_database_writes) Data written to the database by a view can be read. ... ok test_fixtures_loaded (servers.tests.LiveServerDatabase.test_fixtures_loaded) Fixtures are properly loaded and visible to the live server thread. ... ok test_port_bind (servers.tests.LiveServerPort.test_port_bind) Each LiveServerTestCase binds to a unique port or fails to start a ... ok test_specified_port_bind (servers.tests.LiveServerPort.test_specified_port_bind) LiveServerTestCase.port customizes the server's port. ... ok test_check_model_instance_from_subview (servers.tests.LiveServerThreadedTests.test_check_model_instance_from_subview) ... ok test_view_calls_subview (servers.tests.LiveServerThreadedTests.test_view_calls_subview) ... ok test_domain_whitelist (validators.tests.DeprecationTests.test_domain_whitelist) ... ok test_domain_whitelist_access_warning (validators.tests.DeprecationTests.test_domain_whitelist_access_warning) ... ok test_domain_whitelist_set_warning (validators.tests.DeprecationTests.test_domain_whitelist_set_warning) ... ok test_whitelist (validators.tests.DeprecationTests.test_whitelist) ... ok test_whitelist_warning (validators.tests.DeprecationTests.test_whitelist_warning) ... ok test_max_length_validator_message (validators.tests.TestValidators.test_max_length_validator_message) ... ok test_message_dict (validators.tests.TestValidators.test_message_dict) ... ok test_message_list (validators.tests.TestValidators.test_message_list) ... ok test_regex_validator_flags (validators.tests.TestValidators.test_regex_validator_flags) ... ok test_single_message (validators.tests.TestValidators.test_single_message) ... ok test_validators (validators.tests.TestValidators.test_validators) ... ok test_all_if_match (conditional_processing.tests.ConditionalGet.test_all_if_match) ... ok test_all_if_none_match (conditional_processing.tests.ConditionalGet.test_all_if_none_match) ... ok test_both_headers (conditional_processing.tests.ConditionalGet.test_both_headers) ... ok test_both_headers_2 (conditional_processing.tests.ConditionalGet.test_both_headers_2) ... ok test_if_match (conditional_processing.tests.ConditionalGet.test_if_match) ... ok test_if_modified_since (conditional_processing.tests.ConditionalGet.test_if_modified_since) ... ok test_if_none_match (conditional_processing.tests.ConditionalGet.test_if_none_match) ... ok test_if_unmodified_since (conditional_processing.tests.ConditionalGet.test_if_unmodified_since) ... ok test_invalid_etag (conditional_processing.tests.ConditionalGet.test_invalid_etag) ... ok test_single_condition_1 (conditional_processing.tests.ConditionalGet.test_single_condition_1) ... ok test_single_condition_2 (conditional_processing.tests.ConditionalGet.test_single_condition_2) ... ok test_single_condition_3 (conditional_processing.tests.ConditionalGet.test_single_condition_3) ... ok test_single_condition_4 (conditional_processing.tests.ConditionalGet.test_single_condition_4) ... ok test_single_condition_5 (conditional_processing.tests.ConditionalGet.test_single_condition_5) ... ok test_single_condition_6 (conditional_processing.tests.ConditionalGet.test_single_condition_6) ... ok test_single_condition_7 (conditional_processing.tests.ConditionalGet.test_single_condition_7) ... ok test_single_condition_8 (conditional_processing.tests.ConditionalGet.test_single_condition_8) ... ok test_single_condition_9 (conditional_processing.tests.ConditionalGet.test_single_condition_9) ... ok test_single_condition_head (conditional_processing.tests.ConditionalGet.test_single_condition_head) ... ok test_unquoted (conditional_processing.tests.ConditionalGet.test_unquoted) The same quoted ETag should be set on the header regardless of whether ... ok test_unquoted_if_none_match (conditional_processing.tests.ConditionalGet.test_unquoted_if_none_match) ... ok test_weak_if_match (conditional_processing.tests.ConditionalGet.test_weak_if_match) If-Match comparisons use strong matching, so any comparison involving ... ok test_weak_if_none_match (conditional_processing.tests.ConditionalGet.test_weak_if_none_match) If-None-Match comparisons use weak matching, so weak and strong ETags ... ok test_without_conditions (conditional_processing.tests.ConditionalGet.test_without_conditions) ... ok test_duplicate_order_field (order_with_respect_to.tests.OrderWithRespectToTests.test_duplicate_order_field) ... ok test_add_action (admin_views.test_adminsite.SiteActionsTests.test_add_action) ... ok test_disable_action (admin_views.test_adminsite.SiteActionsTests.test_disable_action) ... ok test_get_action (admin_views.test_adminsite.SiteActionsTests.test_get_action) AdminSite.get_action() returns an action even if it's disabled. ... ok test_inline_add_another_widgets (admin_views.test_autocomplete_view.SeleniumTests.test_inline_add_another_widgets) ... skipped 'No browsers specified.' test_select (admin_views.test_autocomplete_view.SeleniumTests.test_select) ... skipped 'No browsers specified.' test_select_multiple (admin_views.test_autocomplete_view.SeleniumTests.test_select_multiple) ... skipped 'No browsers specified.' test_sidebar_can_be_closed (admin_views.test_nav_sidebar.SeleniumTests.test_sidebar_can_be_closed) ... skipped 'No browsers specified.' test_sidebar_starts_open (admin_views.test_nav_sidebar.SeleniumTests.test_sidebar_starts_open) ... skipped 'No browsers specified.' test_sidebar_state_persists (admin_views.test_nav_sidebar.SeleniumTests.test_sidebar_state_persists) ... skipped 'No browsers specified.' test_cancel_delete_confirmation (admin_views.tests.SeleniumTests.test_cancel_delete_confirmation) Cancelling the deletion of an object takes the user back one page. ... skipped 'No browsers specified.' test_cancel_delete_related_confirmation (admin_views.tests.SeleniumTests.test_cancel_delete_related_confirmation) Cancelling the deletion of an object with relations takes the user back ... skipped 'No browsers specified.' test_collapsible_fieldset (admin_views.tests.SeleniumTests.test_collapsible_fieldset) The 'collapse' class in fieldsets definition allows to ... skipped 'No browsers specified.' test_first_field_focus (admin_views.tests.SeleniumTests.test_first_field_focus) JavaScript-assisted auto-focus on first usable form field. ... skipped 'No browsers specified.' test_inline_uuid_pk_add_with_popup (admin_views.tests.SeleniumTests.test_inline_uuid_pk_add_with_popup) ... skipped 'No browsers specified.' test_inline_uuid_pk_delete_with_popup (admin_views.tests.SeleniumTests.test_inline_uuid_pk_delete_with_popup) ... skipped 'No browsers specified.' test_inline_uuid_pk_edit_with_popup (admin_views.tests.SeleniumTests.test_inline_uuid_pk_edit_with_popup) ... skipped 'No browsers specified.' test_inline_with_popup_cancel_delete (admin_views.tests.SeleniumTests.test_inline_with_popup_cancel_delete) Clicking ""No, take me back" on a delete popup closes the window. ... skipped 'No browsers specified.' test_input_element_font (admin_views.tests.SeleniumTests.test_input_element_font) Browsers' default stylesheets override the font of inputs. The admin ... skipped 'No browsers specified.' test_list_editable_popups (admin_views.tests.SeleniumTests.test_list_editable_popups) list_editable foreign keys have add/change popups. ... skipped 'No browsers specified.' test_list_editable_raw_id_fields (admin_views.tests.SeleniumTests.test_list_editable_raw_id_fields) ... skipped 'No browsers specified.' test_login_button_centered (admin_views.tests.SeleniumTests.test_login_button_centered) ... skipped 'No browsers specified.' test_populate_existing_object (admin_views.tests.SeleniumTests.test_populate_existing_object) The prepopulation works for existing objects too, as long as ... skipped 'No browsers specified.' test_prepopulated_fields (admin_views.tests.SeleniumTests.test_prepopulated_fields) The JavaScript-automated prepopulated fields work with the main form ... skipped 'No browsers specified.' test_search_input_filtered_page (admin_views.tests.SeleniumTests.test_search_input_filtered_page) ... skipped 'No browsers specified.' test_exception_in_async_render_passed_to_process_exception (middleware_exceptions.tests.AsyncMiddlewareTests.test_exception_in_async_render_passed_to_process_exception) ... ok test_exception_in_render_passed_to_process_exception (middleware_exceptions.tests.AsyncMiddlewareTests.test_exception_in_render_passed_to_process_exception) ... ok test_process_template_response (middleware_exceptions.tests.AsyncMiddlewareTests.test_process_template_response) ... ok test_process_template_response_returns_none (middleware_exceptions.tests.AsyncMiddlewareTests.test_process_template_response_returns_none) ... ok test_process_view_return_response (middleware_exceptions.tests.AsyncMiddlewareTests.test_process_view_return_response) ... ok test_view_exception_handled_by_process_exception (middleware_exceptions.tests.AsyncMiddlewareTests.test_view_exception_handled_by_process_exception) ... ok test_async_and_sync_middleware_chain_async_call (middleware_exceptions.tests.MiddlewareNotUsedTests.test_async_and_sync_middleware_chain_async_call) ... ok test_do_not_log_when_debug_is_false (middleware_exceptions.tests.MiddlewareNotUsedTests.test_do_not_log_when_debug_is_false) ... ok test_log (middleware_exceptions.tests.MiddlewareNotUsedTests.test_log) ... ok test_log_custom_message (middleware_exceptions.tests.MiddlewareNotUsedTests.test_log_custom_message) ... ok test_raise_exception (middleware_exceptions.tests.MiddlewareNotUsedTests.test_raise_exception) ... ok test_closes_connection_with_content_length (servers.tests.SingleTreadLiveServerViews.test_closes_connection_with_content_length) Contrast to ... ok test_exception_in_middleware_converted_before_prior_middleware (middleware_exceptions.tests.MiddlewareTests.test_exception_in_middleware_converted_before_prior_middleware) ... ok test_exception_in_render_passed_to_process_exception (middleware_exceptions.tests.MiddlewareTests.test_exception_in_render_passed_to_process_exception) ... ok test_process_template_response (middleware_exceptions.tests.MiddlewareTests.test_process_template_response) ... ok test_process_template_response_returns_none (middleware_exceptions.tests.MiddlewareTests.test_process_template_response_returns_none) ... ok test_process_view_return_none (middleware_exceptions.tests.MiddlewareTests.test_process_view_return_none) ... ok test_process_view_return_response (middleware_exceptions.tests.MiddlewareTests.test_process_view_return_response) ... ok test_response_from_process_exception_short_circuits_remainder (middleware_exceptions.tests.MiddlewareTests.test_response_from_process_exception_short_circuits_remainder) ... ok test_response_from_process_exception_when_return_response (middleware_exceptions.tests.MiddlewareTests.test_response_from_process_exception_when_return_response) ... ok test_templateresponse_from_process_view_passed_to_process_template_response (middleware_exceptions.tests.MiddlewareTests.test_templateresponse_from_process_view_passed_to_process_template_response) TemplateResponses returned from process_view() should be passed to any ... ok test_templateresponse_from_process_view_rendered (middleware_exceptions.tests.MiddlewareTests.test_templateresponse_from_process_view_rendered) TemplateResponses returned from process_view() must be rendered before ... ok test_view_exception_converted_before_middleware (middleware_exceptions.tests.MiddlewareTests.test_view_exception_converted_before_middleware) ... ok test_view_exception_handled_by_process_exception (middleware_exceptions.tests.MiddlewareTests.test_view_exception_handled_by_process_exception) ... ok test_async_and_sync_middleware_async_call (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_async_and_sync_middleware_async_call) ... ok test_async_and_sync_middleware_sync_call (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_async_and_sync_middleware_sync_call) ... ok test_async_middleware (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_async_middleware) ... ok test_async_middleware_async (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_async_middleware_async) ... ok test_async_process_template_response_returns_none_with_sync_client (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_async_process_template_response_returns_none_with_sync_client) ... ok test_not_sync_or_async_middleware (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_not_sync_or_async_middleware) ... ok test_sync_decorated_middleware (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_sync_decorated_middleware) ... ok test_sync_middleware (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_sync_middleware) ... ok test_sync_middleware_async (middleware_exceptions.tests.MiddlewareSyncAsyncTests.test_sync_middleware_async) ... ok test_missing_root_urlconf (middleware_exceptions.tests.RootUrlconfTests.test_missing_root_urlconf) ... ok test_default (responses.test_cookie.DeleteCookieTests.test_default) ... ok test_delete_cookie_samesite (responses.test_cookie.DeleteCookieTests.test_delete_cookie_samesite) ... ok test_delete_cookie_secure_prefix (responses.test_cookie.DeleteCookieTests.test_delete_cookie_secure_prefix) delete_cookie() sets the secure flag if the cookie name starts with ... ok test_delete_cookie_secure_samesite_none (responses.test_cookie.DeleteCookieTests.test_delete_cookie_secure_samesite_none) ... ok test_aware_expiration (responses.test_cookie.SetCookieTests.test_aware_expiration) set_cookie() accepts an aware datetime as expiration time. ... ok test_create_cookie_after_deleting_cookie (responses.test_cookie.SetCookieTests.test_create_cookie_after_deleting_cookie) Setting a cookie after deletion clears the expiry date. ... ok test_far_expiration (responses.test_cookie.SetCookieTests.test_far_expiration) Cookie will expire when a distant expiration time is provided. ... ok test_httponly_cookie (responses.test_cookie.SetCookieTests.test_httponly_cookie) ... ok test_invalid_samesite (responses.test_cookie.SetCookieTests.test_invalid_samesite) ... ok test_max_age_expiration (responses.test_cookie.SetCookieTests.test_max_age_expiration) Cookie will expire if max_age is provided. ... ok test_max_age_int (responses.test_cookie.SetCookieTests.test_max_age_int) ... ok test_near_expiration (responses.test_cookie.SetCookieTests.test_near_expiration) Cookie will expire when a near expiration time is provided. ... ok test_samesite (responses.test_cookie.SetCookieTests.test_samesite) ... ok test_unicode_cookie (responses.test_cookie.SetCookieTests.test_unicode_cookie) HttpResponse.set_cookie() works with Unicode data. ... ok test_compressed_response (responses.test_fileresponse.FileResponseTests.test_compressed_response) If compressed responses are served with the uncompressed Content-Type ... ok test_content_disposition_escaping (responses.test_fileresponse.FileResponseTests.test_content_disposition_escaping) ... ok test_file_from_buffer_response (responses.test_fileresponse.FileResponseTests.test_file_from_buffer_response) ... ok test_file_from_buffer_unnamed_attachment (responses.test_fileresponse.FileResponseTests.test_file_from_buffer_unnamed_attachment) ... ok test_file_from_disk_as_attachment (responses.test_fileresponse.FileResponseTests.test_file_from_disk_as_attachment) ... ok test_file_from_disk_response (responses.test_fileresponse.FileResponseTests.test_file_from_disk_response) ... ok test_file_from_named_pipe_response (responses.test_fileresponse.FileResponseTests.test_file_from_named_pipe_response) ... ok test_unicode_attachment (responses.test_fileresponse.FileResponseTests.test_unicode_attachment) ... ok test_closed (responses.tests.HttpResponseBaseTests.test_closed) ... ok test_setdefault (responses.tests.HttpResponseBaseTests.test_setdefault) HttpResponseBase.setdefault() should not change an existing header ... ok test_tell (responses.tests.HttpResponseBaseTests.test_tell) ... ok test_write (responses.tests.HttpResponseBaseTests.test_write) ... ok test_change_status_code (responses.tests.HttpResponseTests.test_change_status_code) ... ok test_charset_detection (responses.tests.HttpResponseTests.test_charset_detection) HttpResponse should parse charset from content_type. ... ok test_generator_cache (responses.tests.HttpResponseTests.test_generator_cache) ... ok test_invalid_status_code (responses.tests.HttpResponseTests.test_invalid_status_code) ... ok test_reason_phrase (responses.tests.HttpResponseTests.test_reason_phrase) ... ok test_repr (responses.tests.HttpResponseTests.test_repr) ... ok test_repr_no_content_type (responses.tests.HttpResponseTests.test_repr_no_content_type) ... ok test_response_content_charset (responses.tests.HttpResponseTests.test_response_content_charset) HttpResponse should encode based on charset. ... ok test_status_code (responses.tests.HttpResponseTests.test_status_code) ... ok test_valid_status_code_string (responses.tests.HttpResponseTests.test_valid_status_code_string) ... ok test_wrap_textiowrapper (responses.tests.HttpResponseTests.test_wrap_textiowrapper) ... ok test_custom_null_message (validation.test_custom_messages.CustomMessagesTests.test_custom_null_message) ... ok test_custom_simple_validator_message (validation.test_custom_messages.CustomMessagesTests.test_custom_simple_validator_message) ... ok test_custom_validator_passes_for_correct_value (validation.test_validators.TestModelsWithValidators.test_custom_validator_passes_for_correct_value) ... ok test_custom_validator_raises_error_for_incorrect_value (validation.test_validators.TestModelsWithValidators.test_custom_validator_raises_error_for_incorrect_value) ... ok test_field_validators_can_be_any_iterable (validation.test_validators.TestModelsWithValidators.test_field_validators_can_be_any_iterable) ... ok test_overridden_get_lookup (custom_lookups.tests.CustomisedMethodsTests.test_overridden_get_lookup) ... ok test_overridden_get_lookup_chain (custom_lookups.tests.CustomisedMethodsTests.test_overridden_get_lookup_chain) ... ok test_overridden_get_transform (custom_lookups.tests.CustomisedMethodsTests.test_overridden_get_transform) ... ok test_overridden_get_transform_chain (custom_lookups.tests.CustomisedMethodsTests.test_overridden_get_transform_chain) ... ok test_call_order (custom_lookups.tests.LookupTransformCallOrderTests.test_call_order) ... ok test_str (urlpatterns.test_resolvers.RegexPatternTests.test_str) ... ok test_resolver_cache_default__root_urlconf (urlpatterns.test_resolvers.ResolverCacheTests.test_resolver_cache_default__root_urlconf) ... ok test_str (urlpatterns.test_resolvers.RoutePatternTests.test_str) ... ok test_resolve_type_error_propagates (urlpatterns.tests.ConversionExceptionTests.test_resolve_type_error_propagates) ... ok test_resolve_value_error_means_no_match (urlpatterns.tests.ConversionExceptionTests.test_resolve_value_error_means_no_match) ... ok test_reverse_type_error_propagates (urlpatterns.tests.ConversionExceptionTests.test_reverse_type_error_propagates) ... ok test_reverse_value_error_means_no_match (urlpatterns.tests.ConversionExceptionTests.test_reverse_value_error_means_no_match) ... ok test_matching_urls (urlpatterns.tests.ConverterTests.test_matching_urls) ... ok test_nonmatching_urls (urlpatterns.tests.ConverterTests.test_nonmatching_urls) ... ok test_url_warning (urlpatterns.tests.DeprecationTests.test_url_warning) ... ok test_allows_non_ascii_but_valid_identifiers (urlpatterns.tests.ParameterRestrictionTests.test_allows_non_ascii_but_valid_identifiers) ... ok test_integer_parameter_name_causes_exception (urlpatterns.tests.ParameterRestrictionTests.test_integer_parameter_name_causes_exception) ... ok test_non_identifier_parameter_name_causes_exception (urlpatterns.tests.ParameterRestrictionTests.test_non_identifier_parameter_name_causes_exception) ... ok test_matching_urls_same_name (urlpatterns.tests.SameNameTests.test_matching_urls_same_name) ... ok test_404 (servers.tests.LiveServerViews.test_404) ... ok test_closes_connection_without_content_length (servers.tests.LiveServerViews.test_closes_connection_without_content_length) A HTTP 1.1 server is supposed to support keep-alive. Since our ... ok test_environ (servers.tests.LiveServerViews.test_environ) ... ok test_keep_alive_connection_clears_previous_request_data (servers.tests.LiveServerViews.test_keep_alive_connection_clears_previous_request_data) ... ok test_keep_alive_on_connection_with_content_length (servers.tests.LiveServerViews.test_keep_alive_on_connection_with_content_length) See `test_closes_connection_without_content_length` for details. This ... ok test_media_files (servers.tests.LiveServerViews.test_media_files) ... ok test_no_collectstatic_emulation (servers.tests.LiveServerViews.test_no_collectstatic_emulation) LiveServerTestCase reports a 404 status code when HTTP client ... ok test_protocol (servers.tests.LiveServerViews.test_protocol) Launched server serves with HTTP 1.1. ... ok test_static_files (servers.tests.LiveServerViews.test_static_files) ... ok test_view (servers.tests.LiveServerViews.test_view) ... ok test_converter_resolve (urlpatterns.tests.SimplifiedURLTests.test_converter_resolve) ... ok test_converter_reverse (urlpatterns.tests.SimplifiedURLTests.test_converter_reverse) ... ok test_converter_reverse_with_second_layer_instance_namespace (urlpatterns.tests.SimplifiedURLTests.test_converter_reverse_with_second_layer_instance_namespace) ... ok test_invalid_converter (urlpatterns.tests.SimplifiedURLTests.test_invalid_converter) ... ok test_path_inclusion_is_matchable (urlpatterns.tests.SimplifiedURLTests.test_path_inclusion_is_matchable) ... ok test_path_inclusion_is_reversible (urlpatterns.tests.SimplifiedURLTests.test_path_inclusion_is_reversible) ... ok test_path_lookup_with_double_inclusion (urlpatterns.tests.SimplifiedURLTests.test_path_lookup_with_double_inclusion) ... ok test_path_lookup_with_empty_string_inclusion (urlpatterns.tests.SimplifiedURLTests.test_path_lookup_with_empty_string_inclusion) ... ok test_path_lookup_with_inclusion (urlpatterns.tests.SimplifiedURLTests.test_path_lookup_with_inclusion) ... ok test_path_lookup_with_multiple_parameters (urlpatterns.tests.SimplifiedURLTests.test_path_lookup_with_multiple_parameters) ... ok test_path_lookup_with_typed_parameters (urlpatterns.tests.SimplifiedURLTests.test_path_lookup_with_typed_parameters) ... ok test_path_lookup_without_parameters (urlpatterns.tests.SimplifiedURLTests.test_path_lookup_without_parameters) ... ok test_path_reverse_with_parameter (urlpatterns.tests.SimplifiedURLTests.test_path_reverse_with_parameter) ... ok test_path_reverse_without_parameter (urlpatterns.tests.SimplifiedURLTests.test_path_reverse_without_parameter) ... ok test_path_trailing_newlines (urlpatterns.tests.SimplifiedURLTests.test_path_trailing_newlines) ... ok test_re_path (urlpatterns.tests.SimplifiedURLTests.test_re_path) ... ok test_re_path_with_missing_optional_parameter (urlpatterns.tests.SimplifiedURLTests.test_re_path_with_missing_optional_parameter) ... ok test_re_path_with_optional_parameter (urlpatterns.tests.SimplifiedURLTests.test_re_path_with_optional_parameter) ... ok test_two_variable_at_start_of_path_pattern (urlpatterns.tests.SimplifiedURLTests.test_two_variable_at_start_of_path_pattern) ... ok test_whitespace_in_route (urlpatterns.tests.SimplifiedURLTests.test_whitespace_in_route) ... ok test_request_attributes (context_processors.tests.RequestContextProcessorTests.test_request_attributes) The request object is available in the template and that its ... ok test_egg1 (app_loading.tests.EggLoadingTest.test_egg1) Models module can be loaded from an app in an egg ... ok test_egg2 (app_loading.tests.EggLoadingTest.test_egg2) Loading an app from an egg that has no models returns no models (and no error) ... ok test_egg3 (app_loading.tests.EggLoadingTest.test_egg3) Models module can be loaded from an app located under an egg's top-level package ... ok test_egg4 (app_loading.tests.EggLoadingTest.test_egg4) Loading an app with no models from under the top-level egg package generates no error ... ok test_egg5 (app_loading.tests.EggLoadingTest.test_egg5) Loading an app from an egg that has an import error in its models module raises that error ... ok test_get_model_only_returns_installed_models (app_loading.tests.GetModelsTest.test_get_model_only_returns_installed_models) ... ok test_get_models_only_returns_installed_models (app_loading.tests.GetModelsTest.test_get_models_only_returns_installed_models) ... ok test_domain (resolve_url.tests.ResolveUrlTests.test_domain) Passing a domain to resolve_url() returns the same domain. ... ok test_full_url (resolve_url.tests.ResolveUrlTests.test_full_url) Passing a full URL to resolve_url() results in the same url. ... ok test_lazy_reverse (resolve_url.tests.ResolveUrlTests.test_lazy_reverse) Passing the result of reverse_lazy is resolved to a real URL ... ok test_model (resolve_url.tests.ResolveUrlTests.test_model) Passing a model to resolve_url() results in get_absolute_url() being ... ok test_non_view_callable_raises_no_reverse_match (resolve_url.tests.ResolveUrlTests.test_non_view_callable_raises_no_reverse_match) Passing a non-view callable into resolve_url() raises a ... ok test_relative_path (resolve_url.tests.ResolveUrlTests.test_relative_path) Passing a relative URL path to resolve_url() results in the same url. ... ok test_url_path (resolve_url.tests.ResolveUrlTests.test_url_path) Passing a URL path to resolve_url() results in the same url. ... ok test_valid_view_name (resolve_url.tests.ResolveUrlTests.test_valid_view_name) Passing a view name to resolve_url() results in the URL path mapping ... ok test_view_function (resolve_url.tests.ResolveUrlTests.test_view_function) Passing a view function to resolve_url() results in the URL path ... ok test_connection_handler_no_databases (db_utils.tests.ConnectionHandlerTests.test_connection_handler_no_databases) Empty DATABASES and empty 'default' settings default to the dummy ... ok test_ensure_defaults_nonexistent_alias (db_utils.tests.ConnectionHandlerTests.test_ensure_defaults_nonexistent_alias) ... ok test_no_default_database (db_utils.tests.ConnectionHandlerTests.test_no_default_database) ... ok test_nonexistent_alias (db_utils.tests.ConnectionHandlerTests.test_nonexistent_alias) ... ok test_prepare_test_settings_nonexistent_alias (db_utils.tests.ConnectionHandlerTests.test_prepare_test_settings_nonexistent_alias) ... ok test_load_backend_invalid_name (db_utils.tests.LoadBackendTests.test_load_backend_invalid_name) ... ok test_assert_contains_renders_template_response (test_client_regress.tests.AssertContainsTests.test_assert_contains_renders_template_response) An unrendered SimpleTemplateResponse may be used in assertContains(). ... ok test_assert_contains_using_non_template_response (test_client_regress.tests.AssertContainsTests.test_assert_contains_using_non_template_response) auto-rendering does not affect responses that aren't ... ok test_assert_not_contains_renders_template_response (test_client_regress.tests.AssertContainsTests.test_assert_not_contains_renders_template_response) An unrendered SimpleTemplateResponse may be used in assertNotContains(). ... ok test_assert_not_contains_using_non_template_response (test_client_regress.tests.AssertContainsTests.test_assert_not_contains_using_non_template_response) auto-rendering does not affect responses that aren't instances (or ... ok test_binary_contains (test_client_regress.tests.AssertContainsTests.test_binary_contains) ... ok test_binary_not_contains (test_client_regress.tests.AssertContainsTests.test_binary_not_contains) ... ok test_contains (test_client_regress.tests.AssertContainsTests.test_contains) Responses can be inspected for content, including counting repeated substrings ... ok test_nontext_contains (test_client_regress.tests.AssertContainsTests.test_nontext_contains) ... ok test_nontext_not_contains (test_client_regress.tests.AssertContainsTests.test_nontext_not_contains) ... ok test_unicode_contains (test_client_regress.tests.AssertContainsTests.test_unicode_contains) Unicode characters can be found in template context ... ok test_unicode_not_contains (test_client_regress.tests.AssertContainsTests.test_unicode_not_contains) Unicode characters can be searched for, and not found in template context ... ok test_noerror_field (test_client_regress.tests.AssertFormErrorTests.test_noerror_field) An assertion is raised if the field doesn't have any errors ... ok test_unknown_error (test_client_regress.tests.AssertFormErrorTests.test_unknown_error) An assertion is raised if the field doesn't contain the provided error ... ok test_unknown_field (test_client_regress.tests.AssertFormErrorTests.test_unknown_field) An assertion is raised if the field name is unknown ... ok test_unknown_form (test_client_regress.tests.AssertFormErrorTests.test_unknown_form) An assertion is raised if the form name is unknown ... ok test_unknown_nonfield_error (test_client_regress.tests.AssertFormErrorTests.test_unknown_nonfield_error) An assertion is raised if the form's non field errors doesn't contain ... ok test_field_error (test_client_regress.tests.AssertFormsetErrorTests.test_field_error) No assertion is raised if the field contains the provided error ... ok test_no_error_field (test_client_regress.tests.AssertFormsetErrorTests.test_no_error_field) An assertion is raised if the field doesn't have any errors ... ok test_no_nonfield_error (test_client_regress.tests.AssertFormsetErrorTests.test_no_nonfield_error) An assertion is raised if the formsets non-field errors doesn't contain any errors. ... ok test_no_nonform_error (test_client_regress.tests.AssertFormsetErrorTests.test_no_nonform_error) An assertion is raised if the formsets non-form errors doesn't contain any errors. ... ok test_nonfield_error (test_client_regress.tests.AssertFormsetErrorTests.test_nonfield_error) No assertion is raised if the formsets non-field errors contains the provided error. ... ok test_nonform_error (test_client_regress.tests.AssertFormsetErrorTests.test_nonform_error) No assertion is raised if the formsets non-form errors contains the provided error. ... ok test_unknown_error (test_client_regress.tests.AssertFormsetErrorTests.test_unknown_error) An assertion is raised if the field doesn't contain the specified error ... ok test_unknown_field (test_client_regress.tests.AssertFormsetErrorTests.test_unknown_field) An assertion is raised if the field name is unknown ... ok test_unknown_formset (test_client_regress.tests.AssertFormsetErrorTests.test_unknown_formset) An assertion is raised if the formset name is unknown ... ok test_unknown_nonfield_error (test_client_regress.tests.AssertFormsetErrorTests.test_unknown_nonfield_error) An assertion is raised if the formsets non-field errors doesn't contain the provided error. ... ok test_unknown_nonform_error (test_client_regress.tests.AssertFormsetErrorTests.test_unknown_nonform_error) An assertion is raised if the formsets non-form errors doesn't contain the provided error. ... ok test_non_utf_payload (test_client_regress.tests.PayloadEncodingTests.test_non_utf_payload) Non-ASCII data as a non-UTF based encoding can be POSTed. ... ok test_simple_payload (test_client_regress.tests.PayloadEncodingTests.test_simple_payload) A simple ASCII-only text can be POSTed. ... ok test_utf16_payload (test_client_regress.tests.PayloadEncodingTests.test_utf16_payload) Non-ASCII data encoded as UTF-16 can be POSTed. ... ok test_utf8_payload (test_client_regress.tests.PayloadEncodingTests.test_utf8_payload) Non-ASCII data encoded as UTF-8 can be POSTed. ... ok test_circular_redirect (test_client_regress.tests.AssertRedirectsTests.test_circular_redirect) Circular redirect chains are caught and escaped ... ok test_incorrect_target (test_client_regress.tests.AssertRedirectsTests.test_incorrect_target) An assertion is raised if the response redirects to another target ... ok test_lost_query (test_client_regress.tests.AssertRedirectsTests.test_lost_query) An assertion is raised if the redirect location doesn't preserve GET parameters ... ok test_multiple_redirect_chain (test_client_regress.tests.AssertRedirectsTests.test_multiple_redirect_chain) You can follow a redirect chain of multiple redirects ... ok test_redirect_chain (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain) You can follow a redirect chain of multiple redirects ... ok test_redirect_chain_delete (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain_delete) A redirect chain will be followed from an initial DELETE request ... ok test_redirect_chain_head (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain_head) A redirect chain will be followed from an initial HEAD request ... ok test_redirect_chain_on_non_redirect_page (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain_on_non_redirect_page) An assertion is raised if the original page couldn't be retrieved as expected ... ok test_redirect_chain_options (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain_options) A redirect chain will be followed from an initial OPTIONS request ... ok test_redirect_chain_post (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain_post) A redirect chain will be followed from an initial POST post ... ok test_redirect_chain_put (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain_put) A redirect chain will be followed from an initial PUT request ... ok test_redirect_chain_to_non_existent (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain_to_non_existent) You can follow a chain to a nonexistent view. ... ok test_redirect_chain_to_self (test_client_regress.tests.AssertRedirectsTests.test_redirect_chain_to_self) Redirections to self are caught and escaped ... ok test_redirect_fetch_redirect_response (test_client_regress.tests.AssertRedirectsTests.test_redirect_fetch_redirect_response) Preserve extra headers of requests made with django.test.Client. ... ok test_redirect_on_non_redirect_page (test_client_regress.tests.AssertRedirectsTests.test_redirect_on_non_redirect_page) An assertion is raised if the original page couldn't be retrieved as expected ... ok test_redirect_page (test_client_regress.tests.AssertRedirectsTests.test_redirect_page) An assertion is raised if the original page couldn't be retrieved as expected ... ok test_redirect_scheme (test_client_regress.tests.AssertRedirectsTests.test_redirect_scheme) An assertion is raised if the response doesn't have the scheme specified in expected_url ... ok test_redirect_to_different_host (test_client_regress.tests.AssertRedirectsTests.test_redirect_to_different_host) The test client will preserve scheme, host and port changes ... ok test_redirect_to_self_with_changing_query (test_client_regress.tests.AssertRedirectsTests.test_redirect_to_self_with_changing_query) Redirections don't loop forever even if query is changing ... ok test_target_page (test_client_regress.tests.AssertRedirectsTests.test_target_page) An assertion is raised if the response redirect target cannot be retrieved as expected ... ok test_get_like_requests (test_client_regress.tests.QueryStringTests.test_get_like_requests) ... ok test_post_like_requests (test_client_regress.tests.QueryStringTests.test_post_like_requests) ... ok test_body_from_empty_request (test_client_regress.tests.ReadLimitedStreamTest.test_body_from_empty_request) HttpRequest.body on a test client GET request should return ... ok test_read_from_empty_request (test_client_regress.tests.ReadLimitedStreamTest.test_read_from_empty_request) HttpRequest.read() on a test client GET request should return the ... ok test_read_from_nonempty_request (test_client_regress.tests.ReadLimitedStreamTest.test_read_from_nonempty_request) HttpRequest.read() on a test client PUT request with some payload ... ok test_read_numbytes_from_empty_request (test_client_regress.tests.ReadLimitedStreamTest.test_read_numbytes_from_empty_request) HttpRequest.read(LARGE_BUFFER) on a test client GET request should ... ok test_read_numbytes_from_nonempty_request (test_client_regress.tests.ReadLimitedStreamTest.test_read_numbytes_from_nonempty_request) HttpRequest.read(LARGE_BUFFER) on a test client PUT request with ... ok test_add_binaryfield (migrations.test_operations.OperationTests.test_add_binaryfield) Tests the AddField operation on TextField/BinaryField. ... ok test_add_charfield (migrations.test_operations.OperationTests.test_add_charfield) Tests the AddField operation on TextField. ... ok test_add_constraint (migrations.test_operations.OperationTests.test_add_constraint) ... ok test_add_constraint_combinable (migrations.test_operations.OperationTests.test_add_constraint_combinable) ... ok test_add_constraint_percent_escaping (migrations.test_operations.OperationTests.test_add_constraint_percent_escaping) ... ok test_add_covering_unique_constraint (migrations.test_operations.OperationTests.test_add_covering_unique_constraint) ... ok test_add_deferred_unique_constraint (migrations.test_operations.OperationTests.test_add_deferred_unique_constraint) ... ok test_add_field (migrations.test_operations.OperationTests.test_add_field) Tests the AddField operation. ... ok test_add_field_m2m (migrations.test_operations.OperationTests.test_add_field_m2m) Tests the AddField operation with a ManyToManyField. ... ok test_add_field_preserve_default (migrations.test_operations.OperationTests.test_add_field_preserve_default) Tests the AddField operation's state alteration ... ok test_add_func_index (migrations.test_operations.OperationTests.test_add_func_index) ... ok test_add_index (migrations.test_operations.OperationTests.test_add_index) Test the AddIndex operation. ... ok test_add_index_state_forwards (migrations.test_operations.OperationTests.test_add_index_state_forwards) ... ok test_add_or_constraint (migrations.test_operations.OperationTests.test_add_or_constraint) ... ok test_add_partial_unique_constraint (migrations.test_operations.OperationTests.test_add_partial_unique_constraint) ... ok test_add_textfield (migrations.test_operations.OperationTests.test_add_textfield) Tests the AddField operation on TextField. ... ok test_alter_field (migrations.test_operations.OperationTests.test_alter_field) Tests the AlterField operation. ... ok test_alter_field_add_db_column_noop (migrations.test_operations.OperationTests.test_alter_field_add_db_column_noop) AlterField operation is a noop when adding only a db_column and the ... ok test_alter_field_m2m (migrations.test_operations.OperationTests.test_alter_field_m2m) ... ok test_alter_field_pk (migrations.test_operations.OperationTests.test_alter_field_pk) Tests the AlterField operation on primary keys (for things like PostgreSQL's SERIAL weirdness) ... ok test_alter_field_pk_fk (migrations.test_operations.OperationTests.test_alter_field_pk_fk) Tests the AlterField operation on primary keys changes any FKs pointing to it. ... ok test_alter_field_reloads_state_on_fk_target_changes (migrations.test_operations.OperationTests.test_alter_field_reloads_state_on_fk_target_changes) If AlterField doesn't reload state appropriately, the second AlterField ... ok test_alter_field_reloads_state_on_fk_with_to_field_related_name_target_type_change (migrations.test_operations.OperationTests.test_alter_field_reloads_state_on_fk_with_to_field_related_name_target_type_change) ... ok test_alter_field_reloads_state_on_fk_with_to_field_target_changes (migrations.test_operations.OperationTests.test_alter_field_reloads_state_on_fk_with_to_field_target_changes) If AlterField doesn't reload state appropriately, the second AlterField ... ok test_alter_field_reloads_state_on_fk_with_to_field_target_type_change (migrations.test_operations.OperationTests.test_alter_field_reloads_state_on_fk_with_to_field_target_type_change) ... ok test_alter_field_with_func_index (migrations.test_operations.OperationTests.test_alter_field_with_func_index) ... ok test_alter_field_with_index (migrations.test_operations.OperationTests.test_alter_field_with_index) Test AlterField operation with an index to ensure indexes created via ... ok test_alter_fk (migrations.test_operations.OperationTests.test_alter_fk) Creating and then altering an FK works correctly ... ok test_alter_fk_non_fk (migrations.test_operations.OperationTests.test_alter_fk_non_fk) Altering an FK to a non-FK works (#23244) ... ok test_alter_index_together (migrations.test_operations.OperationTests.test_alter_index_together) Tests the AlterIndexTogether operation. ... ok test_alter_index_together_remove (migrations.test_operations.OperationTests.test_alter_index_together_remove) ... ok test_alter_index_together_remove_with_unique_together (migrations.test_operations.OperationTests.test_alter_index_together_remove_with_unique_together) ... ok test_alter_model_managers (migrations.test_operations.OperationTests.test_alter_model_managers) The managers on a model are set. ... ok test_alter_model_managers_emptying (migrations.test_operations.OperationTests.test_alter_model_managers_emptying) The managers on a model are set. ... ok test_alter_model_options (migrations.test_operations.OperationTests.test_alter_model_options) Tests the AlterModelOptions operation. ... ok test_alter_model_options_emptying (migrations.test_operations.OperationTests.test_alter_model_options_emptying) The AlterModelOptions operation removes keys from the dict (#23121) ... ok test_alter_model_table (migrations.test_operations.OperationTests.test_alter_model_table) Tests the AlterModelTable operation. ... ok test_alter_model_table_m2m (migrations.test_operations.OperationTests.test_alter_model_table_m2m) AlterModelTable should rename auto-generated M2M tables. ... ok test_alter_model_table_none (migrations.test_operations.OperationTests.test_alter_model_table_none) Tests the AlterModelTable operation if the table name is set to None. ... ok test_alter_model_table_noop (migrations.test_operations.OperationTests.test_alter_model_table_noop) Tests the AlterModelTable operation if the table name is not changed. ... ok test_alter_order_with_respect_to (migrations.test_operations.OperationTests.test_alter_order_with_respect_to) Tests the AlterOrderWithRespectTo operation. ... ok test_alter_unique_together (migrations.test_operations.OperationTests.test_alter_unique_together) Tests the AlterUniqueTogether operation. ... ok test_alter_unique_together_remove (migrations.test_operations.OperationTests.test_alter_unique_together_remove) ... ok test_autofield__bigautofield_foreignfield_growth (migrations.test_operations.OperationTests.test_autofield__bigautofield_foreignfield_growth) A field may be migrated from AutoField to BigAutoField. ... ok test_column_name_quoting (migrations.test_operations.OperationTests.test_column_name_quoting) Column names that are SQL keywords shouldn't cause problems when used ... ok test_create_model (migrations.test_operations.OperationTests.test_create_model) Tests the CreateModel operation. ... ok test_create_model_inheritance (migrations.test_operations.OperationTests.test_create_model_inheritance) Tests the CreateModel operation on a multi-table inheritance setup. ... ok test_create_model_m2m (migrations.test_operations.OperationTests.test_create_model_m2m) Test the creation of a model with a ManyToMany field and the ... ok test_create_model_managers (migrations.test_operations.OperationTests.test_create_model_managers) The managers on a model are set. ... ok test_create_model_with_constraint (migrations.test_operations.OperationTests.test_create_model_with_constraint) ... ok test_create_model_with_covering_unique_constraint (migrations.test_operations.OperationTests.test_create_model_with_covering_unique_constraint) ... skipped "Database doesn't support feature(s): supports_covering_indexes" test_create_model_with_deferred_unique_constraint (migrations.test_operations.OperationTests.test_create_model_with_deferred_unique_constraint) ... ok test_create_model_with_duplicate_base (migrations.test_operations.OperationTests.test_create_model_with_duplicate_base) ... ok test_create_model_with_duplicate_field_name (migrations.test_operations.OperationTests.test_create_model_with_duplicate_field_name) ... ok test_create_model_with_duplicate_manager_name (migrations.test_operations.OperationTests.test_create_model_with_duplicate_manager_name) ... ok test_create_model_with_partial_unique_constraint (migrations.test_operations.OperationTests.test_create_model_with_partial_unique_constraint) ... ok test_create_model_with_unique_after (migrations.test_operations.OperationTests.test_create_model_with_unique_after) Tests the CreateModel operation directly followed by an ... ok test_create_proxy_model (migrations.test_operations.OperationTests.test_create_proxy_model) CreateModel ignores proxy models. ... ok test_create_unmanaged_model (migrations.test_operations.OperationTests.test_create_unmanaged_model) CreateModel ignores unmanaged models. ... ok test_delete_model (migrations.test_operations.OperationTests.test_delete_model) Tests the DeleteModel operation. ... ok test_delete_mti_model (migrations.test_operations.OperationTests.test_delete_mti_model) ... ok test_delete_proxy_model (migrations.test_operations.OperationTests.test_delete_proxy_model) Tests the DeleteModel operation ignores proxy models. ... ok test_model_with_bigautofield (migrations.test_operations.OperationTests.test_model_with_bigautofield) A model with BigAutoField can be created. ... ok test_remove_constraint (migrations.test_operations.OperationTests.test_remove_constraint) ... ok test_remove_covering_unique_constraint (migrations.test_operations.OperationTests.test_remove_covering_unique_constraint) ... ok test_remove_deferred_unique_constraint (migrations.test_operations.OperationTests.test_remove_deferred_unique_constraint) ... ok test_remove_field (migrations.test_operations.OperationTests.test_remove_field) Tests the RemoveField operation. ... ok test_remove_field_m2m (migrations.test_operations.OperationTests.test_remove_field_m2m) ... ok test_remove_field_m2m_with_through (migrations.test_operations.OperationTests.test_remove_field_m2m_with_through) ... ok test_remove_fk (migrations.test_operations.OperationTests.test_remove_fk) Tests the RemoveField operation on a foreign key. ... ok test_remove_func_index (migrations.test_operations.OperationTests.test_remove_func_index) ... ok test_remove_index (migrations.test_operations.OperationTests.test_remove_index) Test the RemoveIndex operation. ... ok test_remove_index_state_forwards (migrations.test_operations.OperationTests.test_remove_index_state_forwards) ... ok test_remove_partial_unique_constraint (migrations.test_operations.OperationTests.test_remove_partial_unique_constraint) ... ok test_rename_field (migrations.test_operations.OperationTests.test_rename_field) Tests the RenameField operation. ... ok test_rename_field_case (migrations.test_operations.OperationTests.test_rename_field_case) ... ok test_rename_field_reloads_state_on_fk_target_changes (migrations.test_operations.OperationTests.test_rename_field_reloads_state_on_fk_target_changes) If RenameField doesn't reload state appropriately, the AlterField ... ok test_rename_field_with_db_column (migrations.test_operations.OperationTests.test_rename_field_with_db_column) ... ok test_rename_m2m_model_after_rename_field (migrations.test_operations.OperationTests.test_rename_m2m_model_after_rename_field) RenameModel renames a many-to-many column after a RenameField. ... ok test_rename_m2m_target_model (migrations.test_operations.OperationTests.test_rename_m2m_target_model) ... ok test_rename_m2m_through_model (migrations.test_operations.OperationTests.test_rename_m2m_through_model) ... ok test_rename_missing_field (migrations.test_operations.OperationTests.test_rename_missing_field) ... ok test_rename_model (migrations.test_operations.OperationTests.test_rename_model) Tests the RenameModel operation. ... ok test_rename_model_state_forwards (migrations.test_operations.OperationTests.test_rename_model_state_forwards) RenameModel operations shouldn't trigger the caching of rendered apps ... ok test_rename_model_with_m2m (migrations.test_operations.OperationTests.test_rename_model_with_m2m) ... ok test_rename_model_with_self_referential_fk (migrations.test_operations.OperationTests.test_rename_model_with_self_referential_fk) Tests the RenameModel operation on model with self referential FK. ... ok test_rename_model_with_self_referential_m2m (migrations.test_operations.OperationTests.test_rename_model_with_self_referential_m2m) ... ok test_rename_model_with_superclass_fk (migrations.test_operations.OperationTests.test_rename_model_with_superclass_fk) Tests the RenameModel operation on a model which has a superclass that ... ok test_rename_referenced_field_state_forward (migrations.test_operations.OperationTests.test_rename_referenced_field_state_forward) ... ok test_repoint_field_m2m (migrations.test_operations.OperationTests.test_repoint_field_m2m) ... ok test_run_python (migrations.test_operations.OperationTests.test_run_python) Tests the RunPython operation ... ok test_run_python_atomic (migrations.test_operations.OperationTests.test_run_python_atomic) Tests the RunPython operation correctly handles the "atomic" keyword ... ok test_run_python_noop (migrations.test_operations.OperationTests.test_run_python_noop) #24098 - Tests no-op RunPython operations. ... ok test_run_python_related_assignment (migrations.test_operations.OperationTests.test_run_python_related_assignment) #24282 - Model changes to a FK reverse side update the model ... ok test_run_sql (migrations.test_operations.OperationTests.test_run_sql) Tests the RunSQL operation. ... ok test_run_sql_noop (migrations.test_operations.OperationTests.test_run_sql_noop) #24098 - Tests no-op RunSQL operations. ... ok test_run_sql_params (migrations.test_operations.OperationTests.test_run_sql_params) #23426 - RunSQL should accept parameters. ... ok test_run_sql_params_invalid (migrations.test_operations.OperationTests.test_run_sql_params_invalid) #23426 - RunSQL should fail when a list of statements with an incorrect ... ok test_separate_database_and_state (migrations.test_operations.OperationTests.test_separate_database_and_state) Tests the SeparateDatabaseAndState operation. ... ok test_separate_database_and_state2 (migrations.test_operations.OperationTests.test_separate_database_and_state2) A complex SeparateDatabaseAndState operation: Multiple operations both ... ok test_smallfield_autofield_foreignfield_growth (migrations.test_operations.OperationTests.test_smallfield_autofield_foreignfield_growth) A field may be migrated from SmallAutoField to AutoField. ... ok test_smallfield_bigautofield_foreignfield_growth (migrations.test_operations.OperationTests.test_smallfield_bigautofield_foreignfield_growth) A field may be migrated from SmallAutoField to BigAutoField. ... ok test_cookies (test_client_regress.tests.RequestFactoryEnvironmentTests.test_cookies) ... ok test_should_set_correct_env_variables (test_client_regress.tests.RequestFactoryEnvironmentTests.test_should_set_correct_env_variables) ... ok test_request (test_client_regress.tests.RequestFactoryStateTest.test_request) ... ok test_request_after_client (test_client_regress.tests.RequestFactoryStateTest.test_request_after_client) ... ok test_request_after_client_2 (test_client_regress.tests.RequestFactoryStateTest.test_request_after_client_2) ... ok test_client_headers (test_client_regress.tests.RequestHeadersTest.test_client_headers) A test client can receive custom headers ... ok test_client_headers_redirect (test_client_regress.tests.RequestHeadersTest.test_client_headers_redirect) Test client headers are preserved through redirects ... ok test_empty_string_data (test_client_regress.tests.RequestMethodStringDataTests.test_empty_string_data) Request a view with empty string data via request method GET/POST/HEAD ... ok test_json (test_client_regress.tests.RequestMethodStringDataTests.test_json) ... ok test_json_bytes (test_client_regress.tests.RequestMethodStringDataTests.test_json_bytes) ... ok test_json_charset (test_client_regress.tests.RequestMethodStringDataTests.test_json_charset) ... ok test_json_multiple_access (test_client_regress.tests.RequestMethodStringDataTests.test_json_multiple_access) ... ok test_json_structured_suffixes (test_client_regress.tests.RequestMethodStringDataTests.test_json_structured_suffixes) ... ok test_json_wrong_header (test_client_regress.tests.RequestMethodStringDataTests.test_json_wrong_header) ... ok test_patch (test_client_regress.tests.RequestMethodStringDataTests.test_patch) Request a view with string data via request method PATCH ... ok test_post (test_client_regress.tests.RequestMethodStringDataTests.test_post) Request a view with string data via request method POST ... ok test_put (test_client_regress.tests.RequestMethodStringDataTests.test_put) Request a view with string data via request method PUT ... ok test_delete (test_client_regress.tests.RequestMethodTests.test_delete) Request a view via request method DELETE ... ok test_get (test_client_regress.tests.RequestMethodTests.test_get) Request a view via request method GET ... ok test_head (test_client_regress.tests.RequestMethodTests.test_head) Request a view via request method HEAD ... ok test_options (test_client_regress.tests.RequestMethodTests.test_options) Request a view via request method OPTIONS ... ok test_patch (test_client_regress.tests.RequestMethodTests.test_patch) Request a view via request method PATCH ... ok test_post (test_client_regress.tests.RequestMethodTests.test_post) Request a view via request method POST ... ok test_put (test_client_regress.tests.RequestMethodTests.test_put) Request a view via request method PUT ... ok test_argument_with_space_get (test_client_regress.tests.URLEscapingTests.test_argument_with_space_get) Get a view that has a string argument that requires escaping ... ok test_argument_with_space_post (test_client_regress.tests.URLEscapingTests.test_argument_with_space_post) Post for a view that has a string argument that requires escaping ... ok test_simple_argument_get (test_client_regress.tests.URLEscapingTests.test_simple_argument_get) Get a view that has a simple string argument ... ok test_simple_argument_post (test_client_regress.tests.URLEscapingTests.test_simple_argument_post) Post for a view that has a simple string argument ... ok test_bad_404_template (test_client_regress.tests.TemplateExceptionTests.test_bad_404_template) Errors found when rendering 404 error templates are re-raised ... ok test_file_encoding (test_client_regress.tests.UploadedFileEncodingTest.test_file_encoding) ... ok test_guesses_content_type_on_file_encoding (test_client_regress.tests.UploadedFileEncodingTest.test_guesses_content_type_on_file_encoding) ... ok test_urlconf_was_changed (test_client_regress.tests.UrlconfSubstitutionTests.test_urlconf_was_changed) TestCase can enforce a custom URLconf on a per-test basis ... ok test_urlconf_was_reverted (test_client_regress.tests.zzUrlconfSubstitutionTests.test_urlconf_was_reverted) URLconf is reverted to original value after modification in a TestCase ... ok test_check_composite_foreign_object (foreign_object.tests.TestModelCheckTests.test_check_composite_foreign_object) ... ok test_check_subset_composite_foreign_object (foreign_object.tests.TestModelCheckTests.test_check_subset_composite_foreign_object) ... ok test_add01 (template_tests.filter_tests.test_add.AddTests.test_add01) ... ok test_add02 (template_tests.filter_tests.test_add.AddTests.test_add02) ... ok test_add03 (template_tests.filter_tests.test_add.AddTests.test_add03) ... ok test_add04 (template_tests.filter_tests.test_add.AddTests.test_add04) ... ok test_add05 (template_tests.filter_tests.test_add.AddTests.test_add05) ... ok test_add06 (template_tests.filter_tests.test_add.AddTests.test_add06) ... ok test_add07 (template_tests.filter_tests.test_add.AddTests.test_add07) ... ok test_add08 (template_tests.filter_tests.test_add.AddTests.test_add08) ... ok test_add09 (template_tests.filter_tests.test_add.AddTests.test_add09) ... ok test_add (template_tests.filter_tests.test_add.FunctionTests.test_add) ... ok test_backslashes (template_tests.filter_tests.test_addslashes.FunctionTests.test_backslashes) ... ok test_non_string_input (template_tests.filter_tests.test_addslashes.FunctionTests.test_non_string_input) ... ok test_quotes (template_tests.filter_tests.test_addslashes.FunctionTests.test_quotes) ... ok test_addslashes01 (template_tests.filter_tests.test_addslashes.AddslashesTests.test_addslashes01) ... ok test_addslashes02 (template_tests.filter_tests.test_addslashes.AddslashesTests.test_addslashes02) ... ok test_autoescape_stringfilter01 (template_tests.filter_tests.test_autoescape.AutoescapeStringfilterTests.test_autoescape_stringfilter01) ... ok test_autoescape_stringfilter02 (template_tests.filter_tests.test_autoescape.AutoescapeStringfilterTests.test_autoescape_stringfilter02) ... ok test_autoescape_stringfilter03 (template_tests.filter_tests.test_autoescape.AutoescapeStringfilterTests.test_autoescape_stringfilter03) ... ok test_autoescape_stringfilter04 (template_tests.filter_tests.test_autoescape.AutoescapeStringfilterTests.test_autoescape_stringfilter04) ... ok test_capfirst01 (template_tests.filter_tests.test_capfirst.CapfirstTests.test_capfirst01) ... ok test_capfirst02 (template_tests.filter_tests.test_capfirst.CapfirstTests.test_capfirst02) ... ok test_capfirst (template_tests.filter_tests.test_capfirst.FunctionTests.test_capfirst) ... ok test_center01 (template_tests.filter_tests.test_center.CenterTests.test_center01) ... ok test_center02 (template_tests.filter_tests.test_center.CenterTests.test_center02) ... ok test_center (template_tests.filter_tests.test_center.FunctionTests.test_center) ... ok test_non_string_input (template_tests.filter_tests.test_center.FunctionTests.test_non_string_input) ... ok test_chaining01 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining01) ... ok test_chaining02 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining02) ... ok test_chaining03 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining03) ... ok test_chaining04 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining04) ... ok test_chaining05 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining05) ... ok test_chaining06 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining06) ... ok test_chaining07 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining07) ... ok test_chaining08 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining08) ... ok test_chaining09 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining09) ... ok test_chaining10 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining10) ... ok test_chaining11 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining11) ... ok test_chaining12 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining12) ... ok test_chaining13 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining13) ... ok test_chaining14 (template_tests.filter_tests.test_chaining.ChainingTests.test_chaining14) ... ok test_cut01 (template_tests.filter_tests.test_cut.CutTests.test_cut01) ... ok test_cut02 (template_tests.filter_tests.test_cut.CutTests.test_cut02) ... ok test_cut03 (template_tests.filter_tests.test_cut.CutTests.test_cut03) ... ok test_cut04 (template_tests.filter_tests.test_cut.CutTests.test_cut04) ... ok test_cut05 (template_tests.filter_tests.test_cut.CutTests.test_cut05) ... ok test_cut06 (template_tests.filter_tests.test_cut.CutTests.test_cut06) ... ok test_character (template_tests.filter_tests.test_cut.FunctionTests.test_character) ... ok test_characters (template_tests.filter_tests.test_cut.FunctionTests.test_characters) ... ok test_non_matching_string (template_tests.filter_tests.test_cut.FunctionTests.test_non_matching_string) ... ok test_non_string_input (template_tests.filter_tests.test_cut.FunctionTests.test_non_string_input) ... ok test_default_if_none01 (template_tests.filter_tests.test_default.DefaultIfNoneTests.test_default_if_none01) ... ok test_default_if_none02 (template_tests.filter_tests.test_default.DefaultIfNoneTests.test_default_if_none02) ... ok test_date (template_tests.filter_tests.test_date.FunctionTests.test_date) ... ok test_escape_characters (template_tests.filter_tests.test_date.FunctionTests.test_escape_characters) ... ok test_no_args (template_tests.filter_tests.test_date.FunctionTests.test_no_args) ... ok test_date01 (template_tests.filter_tests.test_date.DateTests.test_date01) ... ok test_date02 (template_tests.filter_tests.test_date.DateTests.test_date02) ... ok test_date02_l10n (template_tests.filter_tests.test_date.DateTests.test_date02_l10n) Without arg and when USE_L10N is True, the active language's DATE_FORMAT ... ok test_date03 (template_tests.filter_tests.test_date.DateTests.test_date03) #9520: Make sure |date doesn't blow up on non-dates ... ok test_date04 (template_tests.filter_tests.test_date.DateTests.test_date04) ... ok test_date05 (template_tests.filter_tests.test_date.DateTests.test_date05) ... ok test_date06 (template_tests.filter_tests.test_date.DateTests.test_date06) ... ok test_date07 (template_tests.filter_tests.test_date.DateTests.test_date07) ... ok test_date08 (template_tests.filter_tests.test_date.DateTests.test_date08) ... ok test_date09 (template_tests.filter_tests.test_date.DateTests.test_date09) ... ok test_empty_string (template_tests.filter_tests.test_default.FunctionTests.test_empty_string) ... ok test_none (template_tests.filter_tests.test_default.FunctionTests.test_none) ... ok test_value (template_tests.filter_tests.test_default.FunctionTests.test_value) ... ok test_default01 (template_tests.filter_tests.test_default.DefaultTests.test_default01) ... ok test_default02 (template_tests.filter_tests.test_default.DefaultTests.test_default02) ... ok test_default03 (template_tests.filter_tests.test_default.DefaultTests.test_default03) ... ok test_default04 (template_tests.filter_tests.test_default.DefaultTests.test_default04) ... ok test_empty_string (template_tests.filter_tests.test_default_if_none.FunctionTests.test_empty_string) ... ok test_none (template_tests.filter_tests.test_default_if_none.FunctionTests.test_none) ... ok test_value (template_tests.filter_tests.test_default_if_none.FunctionTests.test_value) ... ok test_dictsort_complex_sorting_key (template_tests.filter_tests.test_dictsort.FunctionTests.test_dictsort_complex_sorting_key) Since dictsort uses dict.get()/getattr() under the hood, it can sort ... ok test_invalid_args (template_tests.filter_tests.test_dictsort.FunctionTests.test_invalid_args) Fail silently if invalid lookups are passed. ... ok test_invalid_values (template_tests.filter_tests.test_dictsort.FunctionTests.test_invalid_values) If dictsort is passed something other than a list of dictionaries, ... ok test_property_resolver (template_tests.filter_tests.test_dictsort.FunctionTests.test_property_resolver) ... ok test_sort (template_tests.filter_tests.test_dictsort.FunctionTests.test_sort) ... ok test_sort_list_of_tuple_like_dicts (template_tests.filter_tests.test_dictsort.FunctionTests.test_sort_list_of_tuple_like_dicts) ... ok test_sort_list_of_tuples (template_tests.filter_tests.test_dictsort.FunctionTests.test_sort_list_of_tuples) ... ok test_invalid_args (template_tests.filter_tests.test_dictsortreversed.FunctionTests.test_invalid_args) Fail silently if invalid lookups are passed. ... ok test_invalid_values (template_tests.filter_tests.test_dictsortreversed.FunctionTests.test_invalid_values) If dictsortreversed is passed something other than a list of ... ok test_sort (template_tests.filter_tests.test_dictsortreversed.FunctionTests.test_sort) ... ok test_sort_list_of_tuple_like_dicts (template_tests.filter_tests.test_dictsortreversed.FunctionTests.test_sort_list_of_tuple_like_dicts) ... ok test_sort_list_of_tuples (template_tests.filter_tests.test_dictsortreversed.FunctionTests.test_sort_list_of_tuples) ... ok test_false (template_tests.filter_tests.test_divisibleby.FunctionTests.test_false) ... ok test_true (template_tests.filter_tests.test_divisibleby.FunctionTests.test_true) ... ok test_non_string_input (template_tests.filter_tests.test_escape.FunctionTests.test_non_string_input) ... ok test_escape01 (template_tests.filter_tests.test_escape.EscapeTests.test_escape01) ... ok test_escape02 (template_tests.filter_tests.test_escape.EscapeTests.test_escape02) ... ok test_escape03 (template_tests.filter_tests.test_escape.EscapeTests.test_escape03) ... ok test_escape04 (template_tests.filter_tests.test_escape.EscapeTests.test_escape04) ... ok test_escape_lazy_string (template_tests.filter_tests.test_escape.EscapeTests.test_escape_lazy_string) ... ok test_escapejs01 (template_tests.filter_tests.test_escapejs.EscapejsTests.test_escapejs01) ... ok test_escapejs02 (template_tests.filter_tests.test_escapejs.EscapejsTests.test_escapejs02) ... ok test_backslashes (template_tests.filter_tests.test_escapejs.FunctionTests.test_backslashes) ... ok test_lazy_string (template_tests.filter_tests.test_escapejs.FunctionTests.test_lazy_string) ... ok test_paragraph_separator (template_tests.filter_tests.test_escapejs.FunctionTests.test_paragraph_separator) ... ok test_quotes (template_tests.filter_tests.test_escapejs.FunctionTests.test_quotes) ... ok test_script (template_tests.filter_tests.test_escapejs.FunctionTests.test_script) ... ok test_whitespace (template_tests.filter_tests.test_escapejs.FunctionTests.test_whitespace) ... ok test_formats (template_tests.filter_tests.test_filesizeformat.FunctionTests.test_formats) ... ok test_localized_formats (template_tests.filter_tests.test_filesizeformat.FunctionTests.test_localized_formats) ... ok test_negative_numbers (template_tests.filter_tests.test_filesizeformat.FunctionTests.test_negative_numbers) ... ok test_empty_string (template_tests.filter_tests.test_first.FunctionTests.test_empty_string) ... ok test_list (template_tests.filter_tests.test_first.FunctionTests.test_list) ... ok test_string (template_tests.filter_tests.test_first.FunctionTests.test_string) ... ok test_first01 (template_tests.filter_tests.test_first.FirstTests.test_first01) ... ok test_first02 (template_tests.filter_tests.test_first.FirstTests.test_first02) ... ok test_floatformat01 (template_tests.filter_tests.test_floatformat.FloatformatTests.test_floatformat01) ... ok test_floatformat02 (template_tests.filter_tests.test_floatformat.FloatformatTests.test_floatformat02) ... ok test_float_dunder_method (template_tests.filter_tests.test_floatformat.FunctionTests.test_float_dunder_method) ... ok test_force_grouping (template_tests.filter_tests.test_floatformat.FunctionTests.test_force_grouping) ... ok test_infinity (template_tests.filter_tests.test_floatformat.FunctionTests.test_infinity) ... ok test_inputs (template_tests.filter_tests.test_floatformat.FunctionTests.test_inputs) ... ok test_low_decimal_precision (template_tests.filter_tests.test_floatformat.FunctionTests.test_low_decimal_precision) #15789 ... ok test_negative_zero_values (template_tests.filter_tests.test_floatformat.FunctionTests.test_negative_zero_values) ... ok test_zero_values (template_tests.filter_tests.test_floatformat.FunctionTests.test_zero_values) ... ok test_force_escape01 (template_tests.filter_tests.test_force_escape.ForceEscapeTests.test_force_escape01) ... ok test_force_escape02 (template_tests.filter_tests.test_force_escape.ForceEscapeTests.test_force_escape02) ... ok test_force_escape03 (template_tests.filter_tests.test_force_escape.ForceEscapeTests.test_force_escape03) ... ok test_force_escape04 (template_tests.filter_tests.test_force_escape.ForceEscapeTests.test_force_escape04) ... ok test_force_escape05 (template_tests.filter_tests.test_force_escape.ForceEscapeTests.test_force_escape05) ... ok test_force_escape06 (template_tests.filter_tests.test_force_escape.ForceEscapeTests.test_force_escape06) ... ok test_force_escape07 (template_tests.filter_tests.test_force_escape.ForceEscapeTests.test_force_escape07) ... ok test_force_escape08 (template_tests.filter_tests.test_force_escape.ForceEscapeTests.test_force_escape08) ... ok test_escape (template_tests.filter_tests.test_force_escape.FunctionTests.test_escape) ... ok test_unicode (template_tests.filter_tests.test_force_escape.FunctionTests.test_unicode) ... ok test_string (template_tests.filter_tests.test_get_digit.FunctionTests.test_string) ... ok test_values (template_tests.filter_tests.test_get_digit.FunctionTests.test_values) ... ok test_unicode (template_tests.filter_tests.test_iriencode.FunctionTests.test_unicode) ... ok test_urlencoded (template_tests.filter_tests.test_iriencode.FunctionTests.test_urlencoded) ... ok test_iriencode01 (template_tests.filter_tests.test_iriencode.IriencodeTests.test_iriencode01) ... ok test_iriencode02 (template_tests.filter_tests.test_iriencode.IriencodeTests.test_iriencode02) ... ok test_iriencode03 (template_tests.filter_tests.test_iriencode.IriencodeTests.test_iriencode03) ... ok test_iriencode04 (template_tests.filter_tests.test_iriencode.IriencodeTests.test_iriencode04) ... ok test_autoescape (template_tests.filter_tests.test_join.FunctionTests.test_autoescape) ... ok test_autoescape_off (template_tests.filter_tests.test_join.FunctionTests.test_autoescape_off) ... ok test_list (template_tests.filter_tests.test_join.FunctionTests.test_list) ... ok test_noniterable_arg (template_tests.filter_tests.test_join.FunctionTests.test_noniterable_arg) ... ok test_noniterable_arg_autoescape_off (template_tests.filter_tests.test_join.FunctionTests.test_noniterable_arg_autoescape_off) ... ok test_join01 (template_tests.filter_tests.test_join.JoinTests.test_join01) ... ok test_join02 (template_tests.filter_tests.test_join.JoinTests.test_join02) ... ok test_join03 (template_tests.filter_tests.test_join.JoinTests.test_join03) ... ok test_join04 (template_tests.filter_tests.test_join.JoinTests.test_join04) ... ok test_join05 (template_tests.filter_tests.test_join.JoinTests.test_join05) ... ok test_join06 (template_tests.filter_tests.test_join.JoinTests.test_join06) ... ok test_join07 (template_tests.filter_tests.test_join.JoinTests.test_join07) ... ok test_join08 (template_tests.filter_tests.test_join.JoinTests.test_join08) ... ok test_basic (template_tests.filter_tests.test_json_script.JsonScriptTests.test_basic) ... ok test_empty_list (template_tests.filter_tests.test_last.LastTests.test_empty_list) ... ok test_last01 (template_tests.filter_tests.test_last.LastTests.test_last01) ... ok test_last02 (template_tests.filter_tests.test_last.LastTests.test_last02) ... ok test_list (template_tests.filter_tests.test_length.FunctionTests.test_list) ... ok test_safestring (template_tests.filter_tests.test_length.FunctionTests.test_safestring) ... ok test_string (template_tests.filter_tests.test_length.FunctionTests.test_string) ... ok test_length01 (template_tests.filter_tests.test_length.LengthTests.test_length01) ... ok test_length02 (template_tests.filter_tests.test_length.LengthTests.test_length02) ... ok test_length03 (template_tests.filter_tests.test_length.LengthTests.test_length03) ... ok test_length04 (template_tests.filter_tests.test_length.LengthTests.test_length04) ... ok test_length05 (template_tests.filter_tests.test_length.LengthTests.test_length05) ... ok test_length06 (template_tests.filter_tests.test_length.LengthTests.test_length06) ... ok test_length07 (template_tests.filter_tests.test_length.LengthTests.test_length07) ... ok test_empty_list (template_tests.filter_tests.test_length_is.FunctionTests.test_empty_list) ... ok test_string (template_tests.filter_tests.test_length_is.FunctionTests.test_string) ... ok test_block (select_for_update.tests.SelectForUpdateTests.test_block) A thread running a select_for_update that accesses rows being touched ... skipped "Database doesn't support feature(s): has_select_for_update" test_for_update_after_from (select_for_update.tests.SelectForUpdateTests.test_for_update_after_from) ... skipped "Database doesn't support feature(s): has_select_for_update" test_for_update_of_followed_by_values (select_for_update.tests.SelectForUpdateTests.test_for_update_of_followed_by_values) ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_of_followed_by_values_list (select_for_update.tests.SelectForUpdateTests.test_for_update_of_followed_by_values_list) ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_of_self_when_self_is_not_selected (select_for_update.tests.SelectForUpdateTests.test_for_update_of_self_when_self_is_not_selected) select_for_update(of=['self']) when the only columns selected are from ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_requires_transaction (select_for_update.tests.SelectForUpdateTests.test_for_update_requires_transaction) A TransactionManagementError is raised ... skipped "Database doesn't support feature(s): has_select_for_update" test_for_update_requires_transaction_only_in_execution (select_for_update.tests.SelectForUpdateTests.test_for_update_requires_transaction_only_in_execution) No TransactionManagementError is raised ... skipped "Database doesn't support feature(s): has_select_for_update" test_for_update_sql_generated (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_generated) The backend's FOR UPDATE variant appears in ... skipped "Database doesn't support feature(s): has_select_for_update" test_for_update_sql_generated_nowait (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_generated_nowait) The backend's FOR UPDATE NOWAIT variant appears in ... skipped "Database doesn't support feature(s): has_select_for_update_nowait" test_for_update_sql_generated_of (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_generated_of) The backend's FOR UPDATE OF variant appears in the generated SQL when ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_sql_generated_skip_locked (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_generated_skip_locked) The backend's FOR UPDATE SKIP LOCKED variant appears in ... skipped "Database doesn't support feature(s): has_select_for_update_skip_locked" test_for_update_sql_model_inheritance_generated_of (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_model_inheritance_generated_of) ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_sql_model_inheritance_nested_ptr_generated_of (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_model_inheritance_nested_ptr_generated_of) ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_sql_model_inheritance_ptr_generated_of (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_model_inheritance_ptr_generated_of) ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_sql_model_proxy_generated_of (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_model_proxy_generated_of) ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_sql_multilevel_model_inheritance_ptr_generated_of (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_multilevel_model_inheritance_ptr_generated_of) ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_for_update_sql_related_model_inheritance_generated_of (select_for_update.tests.SelectForUpdateTests.test_for_update_sql_related_model_inheritance_generated_of) ... skipped "Database doesn't support feature(s): has_select_for_update_of" test_model_inheritance_of_argument_raises_error_ptr_in_choices (select_for_update.tests.SelectForUpdateTests.test_model_inheritance_of_argument_raises_error_ptr_in_choices) ... skipped "Database doesn't support feature(s): has_select_for_update, has_select_for_update_of" test_model_proxy_of_argument_raises_error_proxy_field_in_choices (select_for_update.tests.SelectForUpdateTests.test_model_proxy_of_argument_raises_error_proxy_field_in_choices) ... skipped "Database doesn't support feature(s): has_select_for_update, has_select_for_update_of" test_nowait_and_skip_locked (select_for_update.tests.SelectForUpdateTests.test_nowait_and_skip_locked) ... ok test_nowait_raises_error_on_block (select_for_update.tests.SelectForUpdateTests.test_nowait_raises_error_on_block) If nowait is specified, we expect an error to be raised rather ... skipped "Database doesn't support feature(s): has_select_for_update_nowait" test_ordered_select_for_update (select_for_update.tests.SelectForUpdateTests.test_ordered_select_for_update) Subqueries should respect ordering as an ORDER BY clause may be useful ... ok test_raw_lock_not_available (select_for_update.tests.SelectForUpdateTests.test_raw_lock_not_available) Running a raw query which can't obtain a FOR UPDATE lock raises ... skipped "Database doesn't support feature(s): has_select_for_update" test_related_but_unselected_of_argument_raises_error (select_for_update.tests.SelectForUpdateTests.test_related_but_unselected_of_argument_raises_error) FieldError is raised if a relation field that is not followed in the ... skipped "Database doesn't support feature(s): has_select_for_update, has_select_for_update_of" test_reverse_one_to_one_of_arguments (select_for_update.tests.SelectForUpdateTests.test_reverse_one_to_one_of_arguments) Reverse OneToOneFields may be included in of=(...) as long as NULLs ... skipped "Database doesn't support feature(s): has_select_for_update, has_select_for_update_of" test_select_for_update_on_multidb (select_for_update.tests.SelectForUpdateTests.test_select_for_update_on_multidb) ... skipped "Database doesn't support feature(s): has_select_for_update" test_select_for_update_with_get (select_for_update.tests.SelectForUpdateTests.test_select_for_update_with_get) ... skipped "Database doesn't support feature(s): has_select_for_update" test_select_for_update_with_limit (select_for_update.tests.SelectForUpdateTests.test_select_for_update_with_limit) ... ok test_skip_locked_skips_locked_rows (select_for_update.tests.SelectForUpdateTests.test_skip_locked_skips_locked_rows) If skip_locked is specified, the locked row is skipped resulting in ... skipped "Database doesn't support feature(s): has_select_for_update_skip_locked" test_unrelated_of_argument_raises_error (select_for_update.tests.SelectForUpdateTests.test_unrelated_of_argument_raises_error) FieldError is raised if a non-relation field is specified in of=(...). ... skipped "Database doesn't support feature(s): has_select_for_update, has_select_for_update_of" test_unsuported_no_key_raises_error (select_for_update.tests.SelectForUpdateTests.test_unsuported_no_key_raises_error) NotSupportedError is raised if a SELECT...FOR NO KEY UPDATE... is run ... skipped "Database doesn't support feature(s): has_select_for_update" test_unsupported_nowait_raises_error (select_for_update.tests.SelectForUpdateTests.test_unsupported_nowait_raises_error) NotSupportedError is raised if a SELECT...FOR UPDATE NOWAIT is run on ... skipped "Database doesn't support feature(s): has_select_for_update" test_unsupported_of_raises_error (select_for_update.tests.SelectForUpdateTests.test_unsupported_of_raises_error) NotSupportedError is raised if a SELECT...FOR UPDATE OF... is run on ... skipped "Database doesn't support feature(s): has_select_for_update" test_unsupported_select_for_update_with_limit (select_for_update.tests.SelectForUpdateTests.test_unsupported_select_for_update_with_limit) ... skipped 'Database has feature(s) supports_select_for_update_with_limit' test_unsupported_skip_locked_raises_error (select_for_update.tests.SelectForUpdateTests.test_unsupported_skip_locked_raises_error) NotSupportedError is raised if a SELECT...FOR UPDATE SKIP LOCKED is run ... skipped "Database doesn't support feature(s): has_select_for_update" test_update_sql_generated_no_key (select_for_update.tests.SelectForUpdateTests.test_update_sql_generated_no_key) The backend's FOR NO KEY UPDATE variant appears in generated SQL when ... skipped "Database doesn't support feature(s): has_select_for_no_key_update" test_autoescape (template_tests.filter_tests.test_linebreaks.FunctionTests.test_autoescape) ... ok test_autoescape_off (template_tests.filter_tests.test_linebreaks.FunctionTests.test_autoescape_off) ... ok test_carriage (template_tests.filter_tests.test_linebreaks.FunctionTests.test_carriage) ... ok test_carriage_newline (template_tests.filter_tests.test_linebreaks.FunctionTests.test_carriage_newline) ... ok test_lazy_string_input (template_tests.filter_tests.test_linebreaks.FunctionTests.test_lazy_string_input) ... ok test_line (template_tests.filter_tests.test_linebreaks.FunctionTests.test_line) ... ok test_newline (template_tests.filter_tests.test_linebreaks.FunctionTests.test_newline) ... ok test_non_string_input (template_tests.filter_tests.test_linebreaks.FunctionTests.test_non_string_input) ... ok test_linebreaks01 (template_tests.filter_tests.test_linebreaks.LinebreaksTests.test_linebreaks01) ... ok test_linebreaks02 (template_tests.filter_tests.test_linebreaks.LinebreaksTests.test_linebreaks02) ... ok test_autoescape (template_tests.filter_tests.test_linebreaksbr.FunctionTests.test_autoescape) ... ok test_autoescape_off (template_tests.filter_tests.test_linebreaksbr.FunctionTests.test_autoescape_off) ... ok test_carriage (template_tests.filter_tests.test_linebreaksbr.FunctionTests.test_carriage) ... ok test_carriage_newline (template_tests.filter_tests.test_linebreaksbr.FunctionTests.test_carriage_newline) ... ok test_newline (template_tests.filter_tests.test_linebreaksbr.FunctionTests.test_newline) ... ok test_non_string_input (template_tests.filter_tests.test_linebreaksbr.FunctionTests.test_non_string_input) ... ok test_length_is01 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is01) ... ok test_length_is02 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is02) ... ok test_length_is03 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is03) ... ok test_length_is04 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is04) ... ok test_length_is05 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is05) ... ok test_length_is06 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is06) ... ok test_length_is07 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is07) ... ok test_length_is08 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is08) ... ok test_length_is09 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is09) ... ok test_length_is10 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is10) ... ok test_length_is11 (template_tests.filter_tests.test_length_is.LengthIsTests.test_length_is11) ... ok test_autoescape (template_tests.filter_tests.test_linenumbers.FunctionTests.test_autoescape) ... ok test_autoescape_off (template_tests.filter_tests.test_linenumbers.FunctionTests.test_autoescape_off) ... ok test_linenumbers (template_tests.filter_tests.test_linenumbers.FunctionTests.test_linenumbers) ... ok test_linenumbers2 (template_tests.filter_tests.test_linenumbers.FunctionTests.test_linenumbers2) ... ok test_non_string_input (template_tests.filter_tests.test_linenumbers.FunctionTests.test_non_string_input) ... ok test_linebreaksbr01 (template_tests.filter_tests.test_linebreaksbr.LinebreaksbrTests.test_linebreaksbr01) ... ok test_linebreaksbr02 (template_tests.filter_tests.test_linebreaksbr.LinebreaksbrTests.test_linebreaksbr02) ... ok test_linenumbers01 (template_tests.filter_tests.test_linenumbers.LinenumbersTests.test_linenumbers01) ... ok test_linenumbers02 (template_tests.filter_tests.test_linenumbers.LinenumbersTests.test_linenumbers02) ... ok test_less_than_string_length (template_tests.filter_tests.test_ljust.FunctionTests.test_less_than_string_length) ... ok test_ljust (template_tests.filter_tests.test_ljust.FunctionTests.test_ljust) ... ok test_non_string_input (template_tests.filter_tests.test_ljust.FunctionTests.test_non_string_input) ... ok test_lower (template_tests.filter_tests.test_lower.FunctionTests.test_lower) ... ok test_non_string_input (template_tests.filter_tests.test_lower.FunctionTests.test_non_string_input) ... ok test_unicode (template_tests.filter_tests.test_lower.FunctionTests.test_unicode) ... ok test_ljust01 (template_tests.filter_tests.test_ljust.LjustTests.test_ljust01) ... ok test_ljust02 (template_tests.filter_tests.test_ljust.LjustTests.test_ljust02) ... ok test_lower01 (template_tests.filter_tests.test_lower.LowerTests.test_lower01) ... ok test_lower02 (template_tests.filter_tests.test_lower.LowerTests.test_lower02) ... ok test_integer (template_tests.filter_tests.test_make_list.FunctionTests.test_integer) ... ok test_string (template_tests.filter_tests.test_make_list.FunctionTests.test_string) ... ok test_phone2numeric (template_tests.filter_tests.test_phone2numeric.FunctionTests.test_phone2numeric) ... ok test_make_list01 (template_tests.filter_tests.test_make_list.MakeListTests.test_make_list01) ... ok test_make_list02 (template_tests.filter_tests.test_make_list.MakeListTests.test_make_list02) ... ok test_make_list03 (template_tests.filter_tests.test_make_list.MakeListTests.test_make_list03) ... ok test_make_list04 (template_tests.filter_tests.test_make_list.MakeListTests.test_make_list04) ... ok test_decimals (template_tests.filter_tests.test_pluralize.FunctionTests.test_decimals) ... ok test_floats (template_tests.filter_tests.test_pluralize.FunctionTests.test_floats) ... ok test_integers (template_tests.filter_tests.test_pluralize.FunctionTests.test_integers) ... ok test_lists (template_tests.filter_tests.test_pluralize.FunctionTests.test_lists) ... ok test_no_len_type (template_tests.filter_tests.test_pluralize.FunctionTests.test_no_len_type) ... ok test_suffixes (template_tests.filter_tests.test_pluralize.FunctionTests.test_suffixes) ... ok test_value_error (template_tests.filter_tests.test_pluralize.FunctionTests.test_value_error) ... ok test_phone2numeric01 (template_tests.filter_tests.test_phone2numeric.Phone2numericTests.test_phone2numeric01) ... ok test_phone2numeric02 (template_tests.filter_tests.test_phone2numeric.Phone2numericTests.test_phone2numeric02) ... ok test_phone2numeric03 (template_tests.filter_tests.test_phone2numeric.Phone2numericTests.test_phone2numeric03) ... ok test_no_arguments (template_tests.filter_tests.test_pluralize.PluralizeTests.test_no_arguments) ... ok test_singular_and_plural_suffix (template_tests.filter_tests.test_pluralize.PluralizeTests.test_singular_and_plural_suffix) ... ok test_suffix (template_tests.filter_tests.test_pluralize.PluralizeTests.test_suffix) ... ok test_random01 (template_tests.filter_tests.test_random.RandomTests.test_random01) ... ok test_random02 (template_tests.filter_tests.test_random.RandomTests.test_random02) ... ok test_less_than_string_length (template_tests.filter_tests.test_rjust.FunctionTests.test_less_than_string_length) ... ok test_non_string_input (template_tests.filter_tests.test_rjust.FunctionTests.test_non_string_input) ... ok test_rjust (template_tests.filter_tests.test_rjust.FunctionTests.test_rjust) ... ok test_rjust01 (template_tests.filter_tests.test_rjust.RjustTests.test_rjust01) ... ok test_rjust02 (template_tests.filter_tests.test_rjust.RjustTests.test_rjust02) ... ok test_safe01 (template_tests.filter_tests.test_safe.SafeTests.test_safe01) ... ok test_safe02 (template_tests.filter_tests.test_safe.SafeTests.test_safe02) ... ok test_safeseq01 (template_tests.filter_tests.test_safeseq.SafeseqTests.test_safeseq01) ... ok test_safeseq02 (template_tests.filter_tests.test_safeseq.SafeseqTests.test_safeseq02) ... ok test_fail_silently (template_tests.filter_tests.test_slice.FunctionTests.test_fail_silently) ... ok test_index (template_tests.filter_tests.test_slice.FunctionTests.test_index) ... ok test_index_integer (template_tests.filter_tests.test_slice.FunctionTests.test_index_integer) ... ok test_negative_index (template_tests.filter_tests.test_slice.FunctionTests.test_negative_index) ... ok test_range (template_tests.filter_tests.test_slice.FunctionTests.test_range) ... ok test_range_multiple (template_tests.filter_tests.test_slice.FunctionTests.test_range_multiple) ... ok test_range_step (template_tests.filter_tests.test_slice.FunctionTests.test_range_step) ... ok test_zero_length (template_tests.filter_tests.test_slice.FunctionTests.test_zero_length) ... ok test_slice01 (template_tests.filter_tests.test_slice.SliceTests.test_slice01) ... ok test_slice02 (template_tests.filter_tests.test_slice.SliceTests.test_slice02) ... ok test_non_string_input (template_tests.filter_tests.test_slugify.FunctionTests.test_non_string_input) ... ok test_slugify (template_tests.filter_tests.test_slugify.FunctionTests.test_slugify) ... ok test_slugify_lazy_string (template_tests.filter_tests.test_slugify.FunctionTests.test_slugify_lazy_string) ... ok test_unicode (template_tests.filter_tests.test_slugify.FunctionTests.test_unicode) ... ok test_slugify01 (template_tests.filter_tests.test_slugify.SlugifyTests.test_slugify01) ... ok test_slugify02 (template_tests.filter_tests.test_slugify.SlugifyTests.test_slugify02) ... ok test_format (template_tests.filter_tests.test_stringformat.FunctionTests.test_format) ... ok test_invalid (template_tests.filter_tests.test_stringformat.FunctionTests.test_invalid) ... ok test_stringformat01 (template_tests.filter_tests.test_stringformat.StringformatTests.test_stringformat01) ... ok test_stringformat02 (template_tests.filter_tests.test_stringformat.StringformatTests.test_stringformat02) ... ok test_non_string_input (template_tests.filter_tests.test_striptags.FunctionTests.test_non_string_input) ... ok test_strip (template_tests.filter_tests.test_striptags.FunctionTests.test_strip) ... ok test_strip_lazy_string (template_tests.filter_tests.test_striptags.FunctionTests.test_strip_lazy_string) ... ok test_striptags01 (template_tests.filter_tests.test_striptags.StriptagsTests.test_striptags01) ... ok test_striptags02 (template_tests.filter_tests.test_striptags.StriptagsTests.test_striptags02) ... ok test_inputs (template_tests.filter_tests.test_time.FunctionTests.test_inputs) ... ok test_no_args (template_tests.filter_tests.test_time.FunctionTests.test_no_args) ... ok test_explicit_date (template_tests.filter_tests.test_timesince.FunctionTests.test_explicit_date) ... ok test_no_args (template_tests.filter_tests.test_timesince.FunctionTests.test_no_args) ... ok test_since_now (template_tests.filter_tests.test_timesince.FunctionTests.test_since_now) ... ok test_time00 (template_tests.filter_tests.test_time.TimeTests.test_time00) ... ok test_time00_l10n (template_tests.filter_tests.test_time.TimeTests.test_time00_l10n) ... ok test_time01 (template_tests.filter_tests.test_time.TimeTests.test_time01) ... ok test_time02 (template_tests.filter_tests.test_time.TimeTests.test_time02) ... ok test_time03 (template_tests.filter_tests.test_time.TimeTests.test_time03) ... ok test_time04 (template_tests.filter_tests.test_time.TimeTests.test_time04) ... ok test_time05 (template_tests.filter_tests.test_time.TimeTests.test_time05) ... ok test_time06 (template_tests.filter_tests.test_time.TimeTests.test_time06) ... ok test_explicit_date (template_tests.filter_tests.test_timeuntil.FunctionTests.test_explicit_date) ... ok test_no_args (template_tests.filter_tests.test_timeuntil.FunctionTests.test_no_args) ... ok test_until_now (template_tests.filter_tests.test_timeuntil.FunctionTests.test_until_now) ... ok test_timesince01 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince01) ... ok test_timesince02 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince02) ... ok test_timesince03 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince03) ... ok test_timesince04 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince04) ... ok test_timesince05 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince05) ... ok test_timesince06 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince06) ... ok test_timesince07 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince07) ... ok test_timesince08 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince08) ... ok test_timesince09 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince09) ... ok test_timesince10 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince10) ... ok test_timesince11 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince11) ... ok test_timesince12 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince12) ... ok test_timesince13 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince13) ... ok test_timesince14 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince14) ... ok test_timesince15 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince15) ... ok test_timesince16 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince16) ... ok test_timesince17 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince17) ... ok test_timesince18 (template_tests.filter_tests.test_timesince.TimesinceTests.test_timesince18) ... ok test_non_string_input (template_tests.filter_tests.test_title.FunctionTests.test_non_string_input) ... ok test_title (template_tests.filter_tests.test_title.FunctionTests.test_title) ... ok test_unicode (template_tests.filter_tests.test_title.FunctionTests.test_unicode) ... ok test_aware_naive_type_error (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_aware_naive_type_error) ... ok test_naive_aware_type_error (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_naive_aware_type_error) ... ok test_timeuntil01 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil01) ... ok test_timeuntil02 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil02) ... ok test_timeuntil03 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil03) ... ok test_timeuntil04 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil04) ... ok test_timeuntil05 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil05) ... ok test_timeuntil06 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil06) ... ok test_timeuntil07 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil07) ... ok test_timeuntil08 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil08) ... ok test_timeuntil09 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil09) ... ok test_timeuntil10 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil10) ... ok test_timeuntil11 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil11) ... ok test_timeuntil12 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil12) ... ok test_timeuntil13 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil13) ... ok test_timeuntil14 (template_tests.filter_tests.test_timeuntil.TimeuntilTests.test_timeuntil14) ... ok test_title1 (template_tests.filter_tests.test_title.TitleTests.test_title1) ... ok test_title2 (template_tests.filter_tests.test_title.TitleTests.test_title2) ... ok test_fail_silently_incorrect_arg (template_tests.filter_tests.test_truncatechars.TruncatecharsTests.test_fail_silently_incorrect_arg) ... ok test_truncatechars01 (template_tests.filter_tests.test_truncatechars.TruncatecharsTests.test_truncatechars01) ... ok test_truncatechars02 (template_tests.filter_tests.test_truncatechars.TruncatecharsTests.test_truncatechars02) ... ok test_invalid_arg (template_tests.filter_tests.test_truncatechars_html.FunctionTests.test_invalid_arg) ... ok test_truncate (template_tests.filter_tests.test_truncatechars_html.FunctionTests.test_truncate) ... ok test_truncate2 (template_tests.filter_tests.test_truncatechars_html.FunctionTests.test_truncate2) ... ok test_truncate3 (template_tests.filter_tests.test_truncatechars_html.FunctionTests.test_truncate3) ... ok test_truncate_something (template_tests.filter_tests.test_truncatechars_html.FunctionTests.test_truncate_something) ... ok test_truncate_unicode (template_tests.filter_tests.test_truncatechars_html.FunctionTests.test_truncate_unicode) ... ok test_truncate_zero (template_tests.filter_tests.test_truncatechars_html.FunctionTests.test_truncate_zero) ... ok test_invalid_number (template_tests.filter_tests.test_truncatewords.FunctionTests.test_invalid_number) ... ok test_non_string_input (template_tests.filter_tests.test_truncatewords.FunctionTests.test_non_string_input) ... ok test_overtruncate (template_tests.filter_tests.test_truncatewords.FunctionTests.test_overtruncate) ... ok test_truncate (template_tests.filter_tests.test_truncatewords.FunctionTests.test_truncate) ... ok test_truncate2 (template_tests.filter_tests.test_truncatewords.FunctionTests.test_truncate2) ... ok test_truncatewords01 (template_tests.filter_tests.test_truncatewords.TruncatewordsTests.test_truncatewords01) ... ok test_truncatewords02 (template_tests.filter_tests.test_truncatewords.TruncatewordsTests.test_truncatewords02) ... ok test_autoescape (template_tests.filter_tests.test_unordered_list.FunctionTests.test_autoescape) ... ok test_autoescape_off (template_tests.filter_tests.test_unordered_list.FunctionTests.test_autoescape_off) ... ok test_list (template_tests.filter_tests.test_unordered_list.FunctionTests.test_list) ... ok test_list_gettext (template_tests.filter_tests.test_unordered_list.FunctionTests.test_list_gettext) ... ok test_nested (template_tests.filter_tests.test_unordered_list.FunctionTests.test_nested) ... ok test_nested2 (template_tests.filter_tests.test_unordered_list.FunctionTests.test_nested2) ... ok test_nested3 (template_tests.filter_tests.test_unordered_list.FunctionTests.test_nested3) ... ok test_nested_generators (template_tests.filter_tests.test_unordered_list.FunctionTests.test_nested_generators) ... ok test_nested_multiple (template_tests.filter_tests.test_unordered_list.FunctionTests.test_nested_multiple) ... ok test_nested_multiple2 (template_tests.filter_tests.test_unordered_list.FunctionTests.test_nested_multiple2) ... ok test_ulitem (template_tests.filter_tests.test_unordered_list.FunctionTests.test_ulitem) ... ok test_ulitem_autoescape_off (template_tests.filter_tests.test_unordered_list.FunctionTests.test_ulitem_autoescape_off) ... ok test_invalid_arg (template_tests.filter_tests.test_truncatewords_html.FunctionTests.test_invalid_arg) ... ok test_truncate (template_tests.filter_tests.test_truncatewords_html.FunctionTests.test_truncate) ... ok test_truncate2 (template_tests.filter_tests.test_truncatewords_html.FunctionTests.test_truncate2) ... ok test_truncate3 (template_tests.filter_tests.test_truncatewords_html.FunctionTests.test_truncate3) ... ok test_truncate4 (template_tests.filter_tests.test_truncatewords_html.FunctionTests.test_truncate4) ... ok test_truncate_complex (template_tests.filter_tests.test_truncatewords_html.FunctionTests.test_truncate_complex) ... ok test_truncate_unicode (template_tests.filter_tests.test_truncatewords_html.FunctionTests.test_truncate_unicode) ... ok test_truncate_zero (template_tests.filter_tests.test_truncatewords_html.FunctionTests.test_truncate_zero) ... ok test_unordered_list01 (template_tests.filter_tests.test_unordered_list.UnorderedListTests.test_unordered_list01) ... ok test_unordered_list02 (template_tests.filter_tests.test_unordered_list.UnorderedListTests.test_unordered_list02) ... ok test_unordered_list03 (template_tests.filter_tests.test_unordered_list.UnorderedListTests.test_unordered_list03) ... ok test_unordered_list04 (template_tests.filter_tests.test_unordered_list.UnorderedListTests.test_unordered_list04) ... ok test_unordered_list05 (template_tests.filter_tests.test_unordered_list.UnorderedListTests.test_unordered_list05) ... ok test_non_string_input (template_tests.filter_tests.test_urlencode.FunctionTests.test_non_string_input) ... ok test_urlencode (template_tests.filter_tests.test_urlencode.FunctionTests.test_urlencode) ... ok test_upper01 (template_tests.filter_tests.test_upper.UpperTests.test_upper01) ... ok test_upper02 (template_tests.filter_tests.test_upper.UpperTests.test_upper02) ... ok test_non_string_input (template_tests.filter_tests.test_upper.FunctionTests.test_non_string_input) ... ok test_unicode (template_tests.filter_tests.test_upper.FunctionTests.test_unicode) ... ok test_upper (template_tests.filter_tests.test_upper.FunctionTests.test_upper) ... ok test_urlencode01 (template_tests.filter_tests.test_urlencode.UrlencodeTests.test_urlencode01) ... ok test_urlencode02 (template_tests.filter_tests.test_urlencode.UrlencodeTests.test_urlencode02) ... ok test_autoescape (template_tests.filter_tests.test_urlize.FunctionTests.test_autoescape) ... ok test_autoescape_off (template_tests.filter_tests.test_urlize.FunctionTests.test_autoescape_off) ... ok test_brackets (template_tests.filter_tests.test_urlize.FunctionTests.test_brackets) #19070 - Check urlize handles brackets properly ... ok test_email (template_tests.filter_tests.test_urlize.FunctionTests.test_email) ... ok test_exclamation_marks (template_tests.filter_tests.test_urlize.FunctionTests.test_exclamation_marks) #23715 - Check urlize correctly handles exclamation marks after TLDs ... ok test_https (template_tests.filter_tests.test_urlize.FunctionTests.test_https) ... ok test_idn (template_tests.filter_tests.test_urlize.FunctionTests.test_idn) #13704 - Check urlize handles IDN correctly ... ok test_invalid_email (template_tests.filter_tests.test_urlize.FunctionTests.test_invalid_email) #17592 - Check urlize don't crash on invalid email with dot-starting ... ok test_ipv4 (template_tests.filter_tests.test_urlize.FunctionTests.test_ipv4) ... ok test_ipv6 (template_tests.filter_tests.test_urlize.FunctionTests.test_ipv6) ... ok test_lazystring (template_tests.filter_tests.test_urlize.FunctionTests.test_lazystring) ... ok test_malformed (template_tests.filter_tests.test_urlize.FunctionTests.test_malformed) #16395 - Check urlize doesn't highlight malformed URIs ... ok test_nofollow (template_tests.filter_tests.test_urlize.FunctionTests.test_nofollow) #12183 - Check urlize adds nofollow properly - see #12183 ... ok test_non_string_input (template_tests.filter_tests.test_urlize.FunctionTests.test_non_string_input) ... ok test_parenthesis (template_tests.filter_tests.test_urlize.FunctionTests.test_parenthesis) #11911 - Check urlize keeps balanced parentheses ... ok test_quotation_marks (template_tests.filter_tests.test_urlize.FunctionTests.test_quotation_marks) #20364 - Check urlize correctly include quotation marks in links ... ok test_quote_commas (template_tests.filter_tests.test_urlize.FunctionTests.test_quote_commas) #20364 - Check urlize copes with commas following URLs in quotes ... ok test_quoting (template_tests.filter_tests.test_urlize.FunctionTests.test_quoting) #9655 - Check urlize doesn't overquote already quoted urls. The ... ok test_tlds (template_tests.filter_tests.test_urlize.FunctionTests.test_tlds) #16656 - Check urlize accepts more TLDs ... ok test_trailing_multiple_punctuation (template_tests.filter_tests.test_urlize.FunctionTests.test_trailing_multiple_punctuation) ... ok test_trailing_period (template_tests.filter_tests.test_urlize.FunctionTests.test_trailing_period) #18644 - Check urlize trims trailing period when followed by parenthesis ... ok test_unicode (template_tests.filter_tests.test_urlize.FunctionTests.test_unicode) ... ok test_uppercase (template_tests.filter_tests.test_urlize.FunctionTests.test_uppercase) #18071 - Check urlize accepts uppercased URL schemes ... ok test_url_split_chars (template_tests.filter_tests.test_urlize.FunctionTests.test_url_split_chars) ... ok test_urlencoded (template_tests.filter_tests.test_urlize.FunctionTests.test_urlencoded) ... ok test_urls (template_tests.filter_tests.test_urlize.FunctionTests.test_urls) ... ok test_word_with_dot (template_tests.filter_tests.test_urlize.FunctionTests.test_word_with_dot) ... ok test_wrapping_characters (template_tests.filter_tests.test_urlize.FunctionTests.test_wrapping_characters) ... ok test_urlize01 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize01) ... ok test_urlize02 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize02) ... ok test_urlize03 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize03) ... ok test_urlize04 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize04) ... ok test_urlize05 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize05) ... ok test_urlize06 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize06) ... ok test_urlize07 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize07) ... ok test_urlize08 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize08) ... ok test_urlize09 (template_tests.filter_tests.test_urlize.UrlizeTests.test_urlize09) ... ok test_autoescape (template_tests.filter_tests.test_urlizetrunc.FunctionTests.test_autoescape) ... ok test_autoescape_off (template_tests.filter_tests.test_urlizetrunc.FunctionTests.test_autoescape_off) ... ok test_non_string_input (template_tests.filter_tests.test_urlizetrunc.FunctionTests.test_non_string_input) ... ok test_overtruncate (template_tests.filter_tests.test_urlizetrunc.FunctionTests.test_overtruncate) ... ok test_query_string (template_tests.filter_tests.test_urlizetrunc.FunctionTests.test_query_string) ... ok test_truncate (template_tests.filter_tests.test_urlizetrunc.FunctionTests.test_truncate) ... ok test_urlizetrunc01 (template_tests.filter_tests.test_urlizetrunc.UrlizetruncTests.test_urlizetrunc01) ... ok test_urlizetrunc02 (template_tests.filter_tests.test_urlizetrunc.UrlizetruncTests.test_urlizetrunc02) ... ok test_count_multiple (template_tests.filter_tests.test_wordcount.FunctionTests.test_count_multiple) ... ok test_count_one (template_tests.filter_tests.test_wordcount.FunctionTests.test_count_one) ... ok test_empty_string (template_tests.filter_tests.test_wordcount.FunctionTests.test_empty_string) ... ok test_non_string_input (template_tests.filter_tests.test_wordcount.FunctionTests.test_non_string_input) ... ok test_wordcount01 (template_tests.filter_tests.test_wordcount.WordcountTests.test_wordcount01) ... ok test_wordcount02 (template_tests.filter_tests.test_wordcount.WordcountTests.test_wordcount02) ... ok test_indent (template_tests.filter_tests.test_wordwrap.FunctionTests.test_indent) ... ok test_indent2 (template_tests.filter_tests.test_wordwrap.FunctionTests.test_indent2) ... ok test_non_string_input (template_tests.filter_tests.test_wordwrap.FunctionTests.test_non_string_input) ... ok test_wrap (template_tests.filter_tests.test_wordwrap.FunctionTests.test_wrap) ... ok test_wrap_lazy_string (template_tests.filter_tests.test_wordwrap.FunctionTests.test_wrap_lazy_string) ... ok test_wordwrap01 (template_tests.filter_tests.test_wordwrap.WordwrapTests.test_wordwrap01) ... ok test_wordwrap02 (template_tests.filter_tests.test_wordwrap.WordwrapTests.test_wordwrap02) ... ok test_false (template_tests.filter_tests.test_yesno.FunctionTests.test_false) ... ok test_false_arguments (template_tests.filter_tests.test_yesno.FunctionTests.test_false_arguments) ... ok test_invalid_value (template_tests.filter_tests.test_yesno.FunctionTests.test_invalid_value) ... ok test_none (template_tests.filter_tests.test_yesno.FunctionTests.test_none) ... ok test_none_three_arguments (template_tests.filter_tests.test_yesno.FunctionTests.test_none_three_arguments) ... ok test_none_two_arguments (template_tests.filter_tests.test_yesno.FunctionTests.test_none_two_arguments) ... ok test_true (template_tests.filter_tests.test_yesno.FunctionTests.test_true) ... ok test_true_arguments (template_tests.filter_tests.test_yesno.FunctionTests.test_true_arguments) ... ok test_true (template_tests.filter_tests.test_yesno.YesNoTests.test_true) ... ok test_percent_formatting_in_blocktranslate (template_tests.syntax_tests.i18n.test_blocktranslate.MiscBlockTranslationTests.test_percent_formatting_in_blocktranslate) Python's %-formatting is properly escaped in blocktranslate, singular, ... ok test_percent_in_translatable_block (template_tests.syntax_tests.i18n.test_blocktranslate.MiscBlockTranslationTests.test_percent_in_translatable_block) ... ok test_percent_formatting_in_blocktranslate (template_tests.syntax_tests.i18n.test_blocktranslate.MiscTests.test_percent_formatting_in_blocktranslate) Python's %-formatting is properly escaped in blocktranslate, singular, ... ok test_percent_in_translatable_block (template_tests.syntax_tests.i18n.test_blocktranslate.MiscTests.test_percent_in_translatable_block) ... ok test_multiple_locale_btrans (template_tests.syntax_tests.i18n.test_blocktranslate.MultipleLocaleActivationBlockTransTests.test_multiple_locale_btrans) ... ok test_multiple_locale_deactivate_btrans (template_tests.syntax_tests.i18n.test_blocktranslate.MultipleLocaleActivationBlockTransTests.test_multiple_locale_deactivate_btrans) ... ok test_multiple_locale_direct_switch_btrans (template_tests.syntax_tests.i18n.test_blocktranslate.MultipleLocaleActivationBlockTransTests.test_multiple_locale_direct_switch_btrans) ... ok test_single_locale_activation (template_tests.syntax_tests.i18n.test_blocktranslate.MultipleLocaleActivationBlockTransTests.test_single_locale_activation) Simple baseline behavior with one locale for all the supported i18n ... ok test_multiple_locale_btrans (template_tests.syntax_tests.i18n.test_blocktranslate.MultipleLocaleActivationBlockTranslateTests.test_multiple_locale_btrans) ... ok test_multiple_locale_deactivate_btrans (template_tests.syntax_tests.i18n.test_blocktranslate.MultipleLocaleActivationBlockTranslateTests.test_multiple_locale_deactivate_btrans) ... ok test_multiple_locale_direct_switch_btrans (template_tests.syntax_tests.i18n.test_blocktranslate.MultipleLocaleActivationBlockTranslateTests.test_multiple_locale_direct_switch_btrans) ... ok test_single_locale_activation (template_tests.syntax_tests.i18n.test_blocktranslate.MultipleLocaleActivationBlockTranslateTests.test_single_locale_activation) Simple baseline behavior with one locale for all the supported i18n ... ok test_bad_placeholder_1 (template_tests.syntax_tests.i18n.test_blocktranslate.TranslationBlockTranslateTagTests.test_bad_placeholder_1) Error in translation file should not crash template rendering (#16516). ... ok test_bad_placeholder_2 (template_tests.syntax_tests.i18n.test_blocktranslate.TranslationBlockTranslateTagTests.test_bad_placeholder_2) Error in translation file should not crash template rendering (#18393). ... ok test_template_tags_pgettext (template_tests.syntax_tests.i18n.test_blocktranslate.TranslationBlockTranslateTagTests.test_template_tags_pgettext) {% blocktranslate %} takes message contexts into account (#14806). ... ok test_bad_placeholder_1 (template_tests.syntax_tests.i18n.test_blocktranslate.TranslationBlockTransnTagTests.test_bad_placeholder_1) Error in translation file should not crash template rendering (#16516). ... ok test_bad_placeholder_2 (template_tests.syntax_tests.i18n.test_blocktranslate.TranslationBlockTransnTagTests.test_bad_placeholder_2) Error in translation file should not crash template rendering (#18393). ... ok test_template_tags_pgettext (template_tests.syntax_tests.i18n.test_blocktranslate.TranslationBlockTransnTagTests.test_template_tags_pgettext) {% blocktranslate %} takes message contexts into account (#14806). ... ok test_blocktrans_syntax_error_missing_assignment (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_blocktrans_syntax_error_missing_assignment) ... ok test_blocktrans_tag_using_a_string_that_looks_like_str_fmt (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_blocktrans_tag_using_a_string_that_looks_like_str_fmt) ... ok test_count (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_count) ... ok test_count_not_number (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_count_not_number) ... ok test_i18n03 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n03) simple translation of a variable ... ok test_i18n04 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n04) simple translation of a variable and filter ... ok test_i18n05 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n05) simple translation of a string with interpolation ... ok test_i18n07 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n07) translation of singular form ... ok test_i18n08 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n08) translation of plural form ... ok test_i18n17 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n17) Escaping inside blocktranslate and translate works as if it was ... ok test_i18n18 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n18) ... ok test_i18n19 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n19) ... ok test_i18n21 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n21) ... ok test_i18n26 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n26) translation of plural form with extra field in singular form (#13568) ... ok test_i18n27 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n27) translation of singular form in Russian (#14126) ... ok test_i18n28 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n28) simple translation of multiple variables ... ok test_i18n34 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n34) ... ok test_i18n34_2 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n34_2) ... ok test_i18n34_3 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n34_3) ... ok test_i18n37 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n37) ... ok test_i18n39 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n39) ... ok test_i18n40 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n40) ... ok test_i18n41 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_i18n41) ... ok test_legacyi18n04 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_legacyi18n04) simple translation of a variable and filter ... ok test_legacyi18n07 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_legacyi18n07) translation of singular form ... ok test_legacyi18n08 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_legacyi18n08) translation of plural form ... ok test_legacyi18n17 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_legacyi18n17) ... ok test_legacyi18n18 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_legacyi18n18) ... ok test_legacyi18n26 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_legacyi18n26) ... ok test_legacyi18n27 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_legacyi18n27) ... ok test_legacyi18n28 (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_legacyi18n28) ... ok test_no_args_with (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_no_args_with) ... ok test_plural_bad_syntax (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_plural_bad_syntax) ... ok test_variable_twice (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_variable_twice) ... ok test_with_block (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_with_block) ... ok test_with_for (template_tests.syntax_tests.i18n.test_blocktranslate.I18nBlockTransTagTests.test_with_for) ... ok test_i18n32 (template_tests.syntax_tests.i18n.test_filters.I18nFiltersTests.test_i18n32) ... ok test_i18n33 (template_tests.syntax_tests.i18n.test_filters.I18nFiltersTests.test_i18n33) ... ok test_i18n38_2 (template_tests.syntax_tests.i18n.test_filters.I18nFiltersTests.test_i18n38_2) ... ok test_no_as_var (template_tests.syntax_tests.i18n.test_get_current_language.I18nGetCurrentLanguageTagTests.test_no_as_var) ... ok test_i18n12 (template_tests.syntax_tests.i18n.test_get_available_languages.GetAvailableLanguagesTagTests.test_i18n12) ... ok test_no_as_var (template_tests.syntax_tests.i18n.test_get_available_languages.GetAvailableLanguagesTagTests.test_no_as_var) ... ok test_no_as_var (template_tests.syntax_tests.i18n.test_get_current_language_bidi.I18nGetCurrentLanguageBidiTagTests.test_no_as_var) ... ok test_i18n28_2 (template_tests.syntax_tests.i18n.test_get_language_info.I18nGetLanguageInfoTagTests.test_i18n28_2) ... ok test_i18n29 (template_tests.syntax_tests.i18n.test_get_language_info.I18nGetLanguageInfoTagTests.test_i18n29) ... ok test_i18n38 (template_tests.syntax_tests.i18n.test_get_language_info.I18nGetLanguageInfoTagTests.test_i18n38) ... ok test_no_for_as (template_tests.syntax_tests.i18n.test_get_language_info.I18nGetLanguageInfoTagTests.test_no_for_as) ... ok test_i18n30 (template_tests.syntax_tests.i18n.test_get_language_info_list.GetLanguageInfoListTests.test_i18n30) ... ok test_i18n31 (template_tests.syntax_tests.i18n.test_get_language_info_list.GetLanguageInfoListTests.test_i18n31) ... ok test_i18n38_2 (template_tests.syntax_tests.i18n.test_get_language_info_list.GetLanguageInfoListTests.test_i18n38_2) ... ok test_no_for_as (template_tests.syntax_tests.i18n.test_get_language_info_list.GetLanguageInfoListTests.test_no_for_as) ... ok test_no_arg (template_tests.syntax_tests.i18n.test_language.I18nLanguageTagTests.test_no_arg) ... ok test_repr (template_tests.syntax_tests.i18n.test_translate.LocalizeNodeTests.test_repr) ... ok test_multiple_locale_deactivate_trans (template_tests.syntax_tests.i18n.test_translate.MultipleLocaleActivationTransTagTests.test_multiple_locale_deactivate_trans) ... ok test_multiple_locale_direct_switch_trans (template_tests.syntax_tests.i18n.test_translate.MultipleLocaleActivationTransTagTests.test_multiple_locale_direct_switch_trans) ... ok test_multiple_locale_trans (template_tests.syntax_tests.i18n.test_translate.MultipleLocaleActivationTransTagTests.test_multiple_locale_trans) ... ok test_single_locale_activation (template_tests.syntax_tests.i18n.test_translate.MultipleLocaleActivationTransTagTests.test_single_locale_activation) Simple baseline behavior with one locale for all the supported i18n ... ok test_multiple_locale_deactivate_trans (template_tests.syntax_tests.i18n.test_translate.MultipleLocaleActivationTranslateTagTests.test_multiple_locale_deactivate_trans) ... ok test_multiple_locale_direct_switch_trans (template_tests.syntax_tests.i18n.test_translate.MultipleLocaleActivationTranslateTagTests.test_multiple_locale_direct_switch_trans) ... ok test_multiple_locale_trans (template_tests.syntax_tests.i18n.test_translate.MultipleLocaleActivationTranslateTagTests.test_multiple_locale_trans) ... ok test_single_locale_activation (template_tests.syntax_tests.i18n.test_translate.MultipleLocaleActivationTranslateTagTests.test_single_locale_activation) Simple baseline behavior with one locale for all the supported i18n ... ok test_i18n01 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n01) simple translation of a string delimited by '. ... ok test_i18n02 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n02) simple translation of a string delimited by ". ... ok test_i18n06 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n06) simple translation of a string to German ... ok test_i18n09 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n09) simple non-translation (only marking) of a string to German ... ok test_i18n20 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n20) ... ok test_i18n22 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n22) ... ok test_i18n23 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n23) Using filters with the {% translate %} tag (#5972). ... ok test_i18n24 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n24) ... ok test_i18n25 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n25) ... ok test_i18n35 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n35) ... ok test_i18n36 (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_i18n36) ... ok test_syntax_error_bad_option (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_syntax_error_bad_option) ... ok test_syntax_error_context_as (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_syntax_error_context_as) ... ok test_syntax_error_context_noop (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_syntax_error_context_noop) ... ok test_syntax_error_duplicate_option (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_syntax_error_duplicate_option) ... ok test_syntax_error_missing_assignment (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_syntax_error_missing_assignment) ... ok test_syntax_error_missing_context (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_syntax_error_missing_context) ... ok test_syntax_error_no_arguments (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_syntax_error_no_arguments) ... ok test_trans_tag_using_a_string_that_looks_like_str_fmt (template_tests.syntax_tests.i18n.test_translate.I18nTransTagTests.test_trans_tag_using_a_string_that_looks_like_str_fmt) ... ok test_template_tags_pgettext (template_tests.syntax_tests.i18n.test_translate.TranslationTransTagTests.test_template_tags_pgettext) {% translate %} takes message contexts into account (#14806). ... ok test_template_tags_pgettext (template_tests.syntax_tests.i18n.test_translate.TranslationTranslateTagTests.test_template_tags_pgettext) {% translate %} takes message contexts into account (#14806). ... ok test_i18n13 (template_tests.syntax_tests.i18n.test_underscore_syntax.I18nStringLiteralTests.test_i18n13) ... ok test_i18n14 (template_tests.syntax_tests.i18n.test_underscore_syntax.I18nStringLiteralTests.test_i18n14) ... ok test_i18n15 (template_tests.syntax_tests.i18n.test_underscore_syntax.I18nStringLiteralTests.test_i18n15) ... ok test_i18n16 (template_tests.syntax_tests.i18n.test_underscore_syntax.I18nStringLiteralTests.test_i18n16) ... ok test_multiple_locale (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale) ... ok test_multiple_locale_deactivate (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale_deactivate) ... ok test_multiple_locale_direct_switch (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale_direct_switch) ... ok test_multiple_locale_filter (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale_filter) ... ok test_multiple_locale_filter_deactivate (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale_filter_deactivate) ... ok test_multiple_locale_filter_direct_switch (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale_filter_direct_switch) ... ok test_multiple_locale_loadi18n (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale_loadi18n) ... ok test_multiple_locale_loadi18n_deactivate (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale_loadi18n_deactivate) ... ok test_multiple_locale_loadi18n_direct_switch (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_multiple_locale_loadi18n_direct_switch) ... ok test_single_locale_activation (template_tests.syntax_tests.i18n.test_underscore_syntax.MultipleLocaleActivationTests.test_single_locale_activation) Simple baseline behavior with one locale for all the supported i18n ... ok test_autoescape_filters01 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_filters01) ... ok test_autoescape_filters02 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_filters02) ... ok test_autoescape_filtertag01 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_filtertag01) The "safe" and "escape" filters cannot work due to internal ... ok test_autoescape_ifequal01 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_ifequal01) ifequal compares unescaped vales. ... ok test_autoescape_literals01 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_literals01) Literal strings are safe. ... ok test_autoescape_lookup01 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_lookup01) Escape requirement survives lookup. ... ok test_autoescape_stringiterations01 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_stringiterations01) Iterating over strings outputs safe characters. ... ok test_autoescape_tag01 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag01) ... ok test_autoescape_tag02 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag02) ... ok test_autoescape_tag03 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag03) ... ok test_autoescape_tag04 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag04) ... ok test_autoescape_tag05 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag05) ... ok test_autoescape_tag06 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag06) ... ok test_autoescape_tag07 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag07) ... ok test_autoescape_tag08 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag08) Literal string arguments to filters, if used in the result, are safe. ... ok test_autoescape_tag09 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag09) ... ok test_autoescape_tag10 (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_autoescape_tag10) ... ok test_invalid_arg (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_invalid_arg) ... ok test_no_arg (template_tests.syntax_tests.test_autoescape.AutoescapeTagTests.test_no_arg) ... ok test_builtins01 (template_tests.syntax_tests.test_builtins.BuiltinsTests.test_builtins01) ... ok test_builtins02 (template_tests.syntax_tests.test_builtins.BuiltinsTests.test_builtins02) ... ok test_builtins03 (template_tests.syntax_tests.test_builtins.BuiltinsTests.test_builtins03) ... ok test_cache_fragment_cache (template_tests.syntax_tests.test_cache.CacheTests.test_cache_fragment_cache) When a cache called "template_fragments" is present, the cache tag ... ok test_cache_missing_backend (template_tests.syntax_tests.test_cache.CacheTests.test_cache_missing_backend) When a cache that doesn't exist is specified, the cache tag will ... ok test_cache_regression_20130 (template_tests.syntax_tests.test_cache.CacheTests.test_cache_regression_20130) ... ok test_basic_syntax01 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax01) Plain text should go through the template parser untouched. ... ok test_basic_syntax02 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax02) Variables should be replaced with their value in the current ... ok test_basic_syntax03 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax03) More than one replacement variable is allowed in a template ... ok test_basic_syntax04 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax04) Fail silently when a variable is not found in the current context ... ok test_basic_syntax06 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax06) A variable may not contain more than one word ... ok test_basic_syntax07 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax07) Raise TemplateSyntaxError for empty variable tags. ... ok test_basic_syntax08 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax08) Raise TemplateSyntaxError for empty variable tags. ... ok test_basic_syntax09 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax09) Attribute syntax allows a template to call an object's attribute ... ok test_basic_syntax10 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax10) Multiple levels of attribute access are allowed. ... ok test_basic_syntax11 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax11) Fail silently when a variable's attribute isn't found. ... ok test_basic_syntax12 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax12) Raise TemplateSyntaxError when trying to access a variable ... ok test_basic_syntax13 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax13) ... ok test_basic_syntax14 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax14) ... ok test_basic_syntax15 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax15) ... ok test_basic_syntax16 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax16) ... ok test_basic_syntax17 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax17) ... ok test_basic_syntax18 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax18) Attribute syntax allows a template to call a dictionary key's ... ok test_basic_syntax19 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax19) Fail silently when a variable's dictionary key isn't found. ... ok test_basic_syntax20 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax20) Fail silently when accessing a non-simple method ... ok test_basic_syntax20b (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax20b) Don't silence a TypeError if it was raised inside a callable. ... ok test_basic_syntax21 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax21) ... ok test_basic_syntax22 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax22) ... ok test_basic_syntax23 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax23) Treat "moo #} {{ cow" as the variable. Not ideal, but costly to work ... ok test_basic_syntax24 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax24) Embedded newlines make it not-a-tag. ... ok test_basic_syntax25 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax25) ... ok test_basic_syntax26 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax26) ... ok test_basic_syntax27 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax27) ... ok test_basic_syntax28 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax28) ... ok test_basic_syntax29 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax29) ... ok test_basic_syntax30 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax30) ... ok test_basic_syntax31 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax31) ... ok test_basic_syntax32 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax32) ... ok test_basic_syntax33 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax33) ... ok test_basic_syntax34 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax34) ... ok test_basic_syntax35 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax35) ... ok test_basic_syntax36 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax36) ... ok test_basic_syntax37 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax37) Call methods in the top level of the context. ... ok test_basic_syntax38 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_basic_syntax38) Call methods returned from dictionary lookups. ... ok test_ignores_strings_that_look_like_format_interpolation (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_ignores_strings_that_look_like_format_interpolation) ... ok test_unclosed_block (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_unclosed_block) ... ok test_unclosed_block2 (template_tests.syntax_tests.test_basic.BasicSyntaxTests.test_unclosed_block2) ... ok test_comment_syntax01 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax01) ... ok test_comment_syntax02 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax02) ... ok test_comment_syntax03 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax03) ... ok test_comment_syntax04 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax04) ... ok test_comment_syntax05 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax05) ... ok test_comment_syntax06 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax06) ... ok test_comment_syntax07 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax07) ... ok test_comment_syntax08 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax08) ... ok test_comment_syntax09 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax09) ... ok test_comment_syntax10 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax10) ... ok test_comment_syntax11 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax11) ... ok test_comment_syntax12 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_syntax12) ... ok test_comment_tag01 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_tag01) ... ok test_comment_tag02 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_tag02) ... ok test_comment_tag03 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_tag03) ... ok test_comment_tag04 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_tag04) ... ok test_comment_tag05 (template_tests.syntax_tests.test_comment.CommentSyntaxTests.test_comment_tag05) ... ok test_cache03 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache03) ... ok test_cache04 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache04) ... ok test_cache05 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache05) ... ok test_cache06 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache06) ... ok test_cache07 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache07) ... ok test_cache08 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache08) Allow first argument to be a variable. ... ok test_cache11 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache11) ... ok test_cache12 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache12) ... ok test_cache13 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache13) ... ok test_cache14 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache14) ... ok test_cache15 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache15) ... ok test_cache16 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache16) Regression test for #7460. ... ok test_cache17 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache17) Regression test for #11270. ... ok test_cache18 (template_tests.syntax_tests.test_cache.CacheTagTests.test_cache18) Test whitespace in filter arguments ... ok test_none_timeout (template_tests.syntax_tests.test_cache.CacheTagTests.test_none_timeout) A timeout of None means "cache forever". ... ok test_cycle01 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle01) ... ok test_cycle05 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle05) ... ok test_cycle07 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle07) ... ok test_cycle10 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle10) ... ok test_cycle11 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle11) ... ok test_cycle12 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle12) ... ok test_cycle13 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle13) ... ok test_cycle14 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle14) ... ok test_cycle15 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle15) ... ok test_cycle16 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle16) ... ok test_cycle17 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle17) ... ok test_cycle18 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle18) ... ok test_cycle19 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle19) ... ok test_cycle20 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle20) ... ok test_cycle21 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle21) ... ok test_cycle22 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle22) ... ok test_cycle23 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle23) ... ok test_cycle24 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle24) ... ok test_cycle25 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle25) ... ok test_cycle26 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle26) ... ok test_cycle27 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle27) ... ok test_cycle28 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle28) ... ok test_cycle29 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle29) A named {% cycle %} tag works inside an {% ifchanged %} block and a ... ok test_cycle30 (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle30) A {% with %} tag shouldn't reset the {% cycle %} variable. ... ok test_cycle_undefined (template_tests.syntax_tests.test_cycle.CycleTagTests.test_cycle_undefined) ... ok test_exception01 (template_tests.syntax_tests.test_exceptions.ExceptionsTests.test_exception01) Raise exception for invalid template name ... ok test_exception02 (template_tests.syntax_tests.test_exceptions.ExceptionsTests.test_exception02) Raise exception for invalid variable template name ... ok test_exception03 (template_tests.syntax_tests.test_exceptions.ExceptionsTests.test_exception03) Raise exception for extra {% extends %} tags ... ok test_exception04 (template_tests.syntax_tests.test_exceptions.ExceptionsTests.test_exception04) Raise exception for custom tags used in child with {% load %} tag in parent, not in child ... ok test_exception05 (template_tests.syntax_tests.test_exceptions.ExceptionsTests.test_exception05) Raise exception for block.super used in base template ... ok test_extends_node_repr (template_tests.syntax_tests.test_extends.ExtendsNodeTests.test_extends_node_repr) ... ok test_filter01 (template_tests.syntax_tests.test_filter_tag.FilterTagTests.test_filter01) ... ok test_filter02 (template_tests.syntax_tests.test_filter_tag.FilterTagTests.test_filter02) ... ok test_filter03 (template_tests.syntax_tests.test_filter_tag.FilterTagTests.test_filter03) ... ok test_filter04 (template_tests.syntax_tests.test_filter_tag.FilterTagTests.test_filter04) ... ok test_filter05 (template_tests.syntax_tests.test_filter_tag.FilterTagTests.test_filter05) ... ok test_filter05bis (template_tests.syntax_tests.test_filter_tag.FilterTagTests.test_filter05bis) ... ok test_filter06 (template_tests.syntax_tests.test_filter_tag.FilterTagTests.test_filter06) ... ok test_filter06bis (template_tests.syntax_tests.test_filter_tag.FilterTagTests.test_filter06bis) ... ok test_filter_syntax01 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax01) Basic filter usage ... ok test_filter_syntax02 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax02) Chained filters ... ok test_filter_syntax03 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax03) Allow spaces before the filter pipe ... ok test_filter_syntax04 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax04) Allow spaces after the filter pipe ... ok test_filter_syntax05 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax05) Raise TemplateSyntaxError for a nonexistent filter ... ok test_filter_syntax06 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax06) Raise TemplateSyntaxError when trying to access a filter containing ... ok test_filter_syntax07 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax07) Raise TemplateSyntaxError for invalid block tags ... ok test_filter_syntax08 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax08) Raise TemplateSyntaxError for empty block tags ... ok test_filter_syntax08_multi_line (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax08_multi_line) Raise TemplateSyntaxError for empty block tags in templates with ... ok test_filter_syntax09 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax09) Chained filters, with an argument to the first one ... ok test_filter_syntax10 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax10) Literal string as argument is always "safe" from auto-escaping. ... ok test_filter_syntax11 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax11) Variable as argument ... ok test_filter_syntax13 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax13) Fail silently for methods that raise an exception with a ... ok test_filter_syntax14 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax14) In methods that raise an exception without a ... ok test_filter_syntax15 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax15) Escaped backslash in argument ... ok test_filter_syntax16 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax16) Escaped backslash using known escape char ... ok test_filter_syntax17 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax17) Empty strings can be passed as arguments to filters ... ok test_filter_syntax18 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax18) Strings are converted to bytestrings in the final output. ... ok test_filter_syntax19 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax19) Numbers as filter arguments should work ... ok test_filter_syntax20 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax20) Filters should accept empty string constants ... ok test_filter_syntax21 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax21) Fail silently for non-callable attribute and dict lookups which ... ok test_filter_syntax22 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax22) Fail silently for non-callable attribute and dict lookups which ... ok test_filter_syntax23 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax23) In attribute and dict lookups that raise an unexpected exception ... ok test_filter_syntax24 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax24) In attribute and dict lookups that raise an unexpected exception ... ok test_filter_syntax25 (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_filter_syntax25) #16383 - Attribute errors from an @property value should be ... ok test_type_error_attribute (template_tests.syntax_tests.test_filter_syntax.FilterSyntaxTests.test_type_error_attribute) ... ok test_repr (template_tests.syntax_tests.test_for.ForNodeTests.test_repr) ... ok test_duplicate_block (template_tests.syntax_tests.test_extends.InheritanceTests.test_duplicate_block) ... ok test_extends_duplicate (template_tests.syntax_tests.test_extends.InheritanceTests.test_extends_duplicate) ... ok test_inheritance01 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance01) Standard template with no inheritance ... ok test_inheritance02 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance02) Standard two-level inheritance ... ok test_inheritance03 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance03) Three-level with no redefinitions on third level ... ok test_inheritance04 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance04) Two-level with no redefinitions on second level ... ok test_inheritance05 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance05) Two-level with double quotes instead of single quotes ... ok test_inheritance06 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance06) Three-level with variable parent-template name ... ok test_inheritance07 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance07) Two-level with one block defined, one block not defined ... ok test_inheritance08 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance08) Three-level with one block defined on this level, two blocks ... ok test_inheritance09 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance09) Three-level with second and third levels blank ... ok test_inheritance10 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance10) Three-level with space NOT in a block -- should be ignored ... ok test_inheritance11 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance11) Three-level with both blocks defined on this level, but none on ... ok test_inheritance12 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance12) Three-level with this level providing one and second level ... ok test_inheritance13 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance13) Three-level with this level overriding second level ... ok test_inheritance14 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance14) A block defined only in a child template shouldn't be displayed ... ok test_inheritance15 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance15) A block within another block ... ok test_inheritance16 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance16) A block within another block (level 2) ... ok test_inheritance17 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance17) {% load %} tag (parent -- setup for exception04) ... ok test_inheritance18 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance18) {% load %} tag (standard usage, without inheritance) ... ok test_inheritance19 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance19) {% load %} tag (within a child template) ... ok test_inheritance20 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance20) Two-level inheritance with {{ block.super }} ... ok test_inheritance21 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance21) Three-level inheritance with {{ block.super }} from parent ... ok test_inheritance22 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance22) Three-level inheritance with {{ block.super }} from grandparent ... ok test_inheritance23 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance23) Three-level inheritance with {{ block.super }} from parent and ... ok test_inheritance24 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance24) Inheritance from local context without use of template loader ... ok test_inheritance25 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance25) Inheritance from local context with variable parent template ... ok test_inheritance26 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance26) Set up a base template to extend ... ok test_inheritance27 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance27) Inheritance from a template that doesn't have any blocks ... ok test_inheritance29 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance29) Inheritance from a template with a space in its name should work. ... ok test_inheritance30 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance30) Base template, putting block in a conditional {% if %} tag ... ok test_inheritance31 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance31) ... ok test_inheritance32 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance32) ... ok test_inheritance33 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance33) Base template, putting block in a conditional {% if %} tag ... ok test_inheritance34 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance34) Inherit from a template with block wrapped in an {% if %} tag ... ok test_inheritance35 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance35) Inherit from a template with block wrapped in an {% if %} tag ... ok test_inheritance36 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance36) Base template, putting block in a {% for %} tag ... ok test_inheritance37 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance37) Inherit from a template with block wrapped in an {% for %} tag ... ok test_inheritance38 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance38) Inherit from a template with block wrapped in an {% for %} tag ... ok test_inheritance39 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance39) ... ok test_inheritance40 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance40) ... ok test_inheritance41 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance41) ... ok test_inheritance42 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance42) Expression starting and ending with a quote ... ok test_inheritance_28 (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance_28) Set up a base template with a space in it. ... ok test_inheritance_empty (template_tests.syntax_tests.test_extends.InheritanceTests.test_inheritance_empty) ... ok test_all_false_arguments_asvar (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_all_false_arguments_asvar) ... ok test_firstof01 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof01) ... ok test_firstof02 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof02) ... ok test_firstof03 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof03) ... ok test_firstof04 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof04) ... ok test_firstof05 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof05) ... ok test_firstof06 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof06) ... ok test_firstof07 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof07) ... ok test_firstof08 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof08) ... ok test_firstof09 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof09) ... ok test_firstof10 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof10) ... ok test_firstof11 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof11) ... ok test_firstof12 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof12) ... ok test_firstof13 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof13) ... ok test_firstof14 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof14) ... ok test_firstof15 (template_tests.syntax_tests.test_firstof.FirstOfTagTests.test_firstof15) ... ok test_repr (template_tests.syntax_tests.test_if.IfNodeTests.test_repr) ... ok test_for_tag01 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag01) ... ok test_for_tag02 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag02) ... ok test_for_tag_context (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_context) ForNode.render() pops the values it pushes to the context (#28001). ... ok test_for_tag_empty01 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_empty01) ... ok test_for_tag_empty02 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_empty02) ... ok test_for_tag_empty03 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_empty03) ... ok test_for_tag_filter_ws (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_filter_ws) #19882 ... ok test_for_tag_unpack01 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack01) ... ok test_for_tag_unpack03 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack03) ... ok test_for_tag_unpack04 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack04) ... ok test_for_tag_unpack05 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack05) ... ok test_for_tag_unpack06 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack06) ... ok test_for_tag_unpack07 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack07) ... ok test_for_tag_unpack08 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack08) ... ok test_for_tag_unpack09 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack09) A single loopvar doesn't truncate the list in val. ... ok test_for_tag_unpack10 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack10) ... ok test_for_tag_unpack11 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack11) ... ok test_for_tag_unpack12 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack12) ... ok test_for_tag_unpack13 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack13) ... ok test_for_tag_unpack14 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack14) ... ok test_for_tag_unpack_strs (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_unpack_strs) ... ok test_for_tag_vars01 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_vars01) ... ok test_for_tag_vars02 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_vars02) ... ok test_for_tag_vars03 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_vars03) ... ok test_for_tag_vars04 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_vars04) ... ok test_for_tag_vars05 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_vars05) ... ok test_for_tag_vars06 (template_tests.syntax_tests.test_for.ForTagTests.test_for_tag_vars06) ... ok test_invalid_arg (template_tests.syntax_tests.test_for.ForTagTests.test_invalid_arg) ... ok test_invalid_in_keyword (template_tests.syntax_tests.test_for.ForTagTests.test_invalid_in_keyword) ... ok test_unpack_double_quote (template_tests.syntax_tests.test_for.ForTagTests.test_unpack_double_quote) ... ok test_unpack_single_quote (template_tests.syntax_tests.test_for.ForTagTests.test_unpack_single_quote) ... ok test_unpack_vertical_bar (template_tests.syntax_tests.test_for.ForTagTests.test_unpack_vertical_bar) ... ok test_ifchanged_concurrency (template_tests.syntax_tests.test_if_changed.IfChangedTests.test_ifchanged_concurrency) #15849 -- ifchanged should be thread-safe. ... ok test_ifchanged_render_once (template_tests.syntax_tests.test_if_changed.IfChangedTests.test_ifchanged_render_once) #19890. The content of ifchanged template tag was rendered twice. ... ok test_include (template_tests.syntax_tests.test_if_changed.IfChangedTests.test_include) #23516 -- This works as a regression test only if the cached loader ... ok test_include_state (template_tests.syntax_tests.test_if_changed.IfChangedTests.test_include_state) Tests the node state for different IncludeNodes (#27974). ... ok test_ifchanged01 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged01) ... ok test_ifchanged02 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged02) ... ok test_ifchanged03 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged03) ... ok test_ifchanged04 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged04) ... ok test_ifchanged05 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged05) ... ok test_ifchanged06 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged06) ... ok test_ifchanged07 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged07) ... ok test_ifchanged08 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged08) ... ok test_ifchanged_else01 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_else01) Test the else clause of ifchanged. ... ok test_ifchanged_else02 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_else02) ... ok test_ifchanged_else03 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_else03) ... ok test_ifchanged_else04 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_else04) ... ok test_ifchanged_filter_ws (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_filter_ws) Test whitespace in filter arguments ... ok test_ifchanged_param01 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_param01) Test one parameter given to ifchanged. ... ok test_ifchanged_param02 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_param02) ... ok test_ifchanged_param03 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_param03) Test multiple parameters to ifchanged. ... ok test_ifchanged_param04 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_param04) Test a date+hour like construct, where the hour of the last day is ... ok test_ifchanged_param05 (template_tests.syntax_tests.test_if_changed.IfChangedTagTests.test_ifchanged_param05) Logically the same as above, just written with explicit ifchanged ... ok test_ifequal_warning (template_tests.syntax_tests.test_if_equal.DeprecationTests.test_ifequal_warning) ... ok test_ifnotequal_warning (template_tests.syntax_tests.test_if_equal.DeprecationTests.test_ifnotequal_warning) ... ok test_repr (template_tests.syntax_tests.test_if_equal.DeprecationTests.test_repr) ... ok test_else_if_tag_error01 (template_tests.syntax_tests.test_if.IfTagTests.test_else_if_tag_error01) ... ok test_if_is_both_variables_missing (template_tests.syntax_tests.test_if.IfTagTests.test_if_is_both_variables_missing) ... ok test_if_is_match (template_tests.syntax_tests.test_if.IfTagTests.test_if_is_match) ... ok test_if_is_no_match (template_tests.syntax_tests.test_if.IfTagTests.test_if_is_no_match) ... ok test_if_is_not_both_variables_missing (template_tests.syntax_tests.test_if.IfTagTests.test_if_is_not_both_variables_missing) ... ok test_if_is_not_match (template_tests.syntax_tests.test_if.IfTagTests.test_if_is_not_match) ... ok test_if_is_not_no_match (template_tests.syntax_tests.test_if.IfTagTests.test_if_is_not_no_match) ... ok test_if_is_not_variable_missing (template_tests.syntax_tests.test_if.IfTagTests.test_if_is_not_variable_missing) ... ok test_if_is_variable_missing (template_tests.syntax_tests.test_if.IfTagTests.test_if_is_variable_missing) ... ok test_if_tag01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag01) ... ok test_if_tag02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag02) ... ok test_if_tag03 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag03) ... ok test_if_tag04 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag04) ... ok test_if_tag05 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag05) ... ok test_if_tag06 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag06) ... ok test_if_tag07 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag07) ... ok test_if_tag08 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag08) ... ok test_if_tag09 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag09) ... ok test_if_tag10 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag10) ... ok test_if_tag11 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag11) ... ok test_if_tag12 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag12) ... ok test_if_tag13 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag13) ... ok test_if_tag_and01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_and01) ... ok test_if_tag_and02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_and02) ... ok test_if_tag_and03 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_and03) ... ok test_if_tag_and04 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_and04) ... ok test_if_tag_and05 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_and05) ... ok test_if_tag_and06 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_and06) ... ok test_if_tag_and07 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_and07) ... ok test_if_tag_and08 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_and08) ... ok test_if_tag_badarg01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_badarg01) Nonexistent args ... ok test_if_tag_badarg02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_badarg02) ... ok test_if_tag_badarg03 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_badarg03) ... ok test_if_tag_badarg04 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_badarg04) ... ok test_if_tag_eq01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_eq01) ... ok test_if_tag_eq02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_eq02) ... ok test_if_tag_eq03 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_eq03) ... ok test_if_tag_eq04 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_eq04) ... ok test_if_tag_eq05 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_eq05) ... ok test_if_tag_error01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error01) ... ok test_if_tag_error02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error02) ... ok test_if_tag_error03 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error03) ... ok test_if_tag_error04 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error04) ... ok test_if_tag_error05 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error05) ... ok test_if_tag_error06 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error06) ... ok test_if_tag_error07 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error07) ... ok test_if_tag_error08 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error08) ... ok test_if_tag_error09 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error09) ... ok test_if_tag_error10 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error10) ... ok test_if_tag_error11 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error11) ... ok test_if_tag_error12 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_error12) ... ok test_if_tag_filter01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_filter01) ... ok test_if_tag_filter02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_filter02) ... ok test_if_tag_gt_01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_gt_01) ... ok test_if_tag_gt_02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_gt_02) ... ok test_if_tag_gte_01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_gte_01) ... ok test_if_tag_gte_02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_gte_02) ... ok test_if_tag_in_01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_in_01) ... ok test_if_tag_in_02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_in_02) ... ok test_if_tag_lt_01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_lt_01) ... ok test_if_tag_lt_02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_lt_02) ... ok test_if_tag_lte_01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_lte_01) ... ok test_if_tag_lte_02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_lte_02) ... ok test_if_tag_not01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not01) ... ok test_if_tag_not02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not02) ... ok test_if_tag_not06 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not06) ... ok test_if_tag_not07 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not07) ... ok test_if_tag_not08 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not08) ... ok test_if_tag_not09 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not09) ... ok test_if_tag_not10 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not10) ... ok test_if_tag_not11 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not11) ... ok test_if_tag_not12 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not12) ... ok test_if_tag_not13 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not13) ... ok test_if_tag_not14 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not14) ... ok test_if_tag_not15 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not15) ... ok test_if_tag_not16 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not16) ... ok test_if_tag_not17 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not17) ... ok test_if_tag_not18 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not18) ... ok test_if_tag_not19 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not19) ... ok test_if_tag_not20 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not20) ... ok test_if_tag_not21 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not21) ... ok test_if_tag_not22 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not22) ... ok test_if_tag_not23 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not23) ... ok test_if_tag_not24 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not24) ... ok test_if_tag_not25 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not25) ... ok test_if_tag_not26 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not26) ... ok test_if_tag_not27 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not27) ... ok test_if_tag_not28 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not28) ... ok test_if_tag_not29 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not29) ... ok test_if_tag_not30 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not30) ... ok test_if_tag_not31 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not31) ... ok test_if_tag_not32 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not32) ... ok test_if_tag_not33 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not33) ... ok test_if_tag_not34 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not34) ... ok test_if_tag_not35 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not35) ... ok test_if_tag_not_in_01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not_in_01) ... ok test_if_tag_not_in_02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_not_in_02) ... ok test_if_tag_noteq01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_noteq01) ... ok test_if_tag_noteq02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_noteq02) ... ok test_if_tag_noteq03 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_noteq03) ... ok test_if_tag_noteq04 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_noteq04) ... ok test_if_tag_noteq05 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_noteq05) ... ok test_if_tag_or01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or01) ... ok test_if_tag_or02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or02) ... ok test_if_tag_or03 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or03) ... ok test_if_tag_or04 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or04) ... ok test_if_tag_or05 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or05) ... ok test_if_tag_or06 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or06) ... ok test_if_tag_or07 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or07) ... ok test_if_tag_or08 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or08) ... ok test_if_tag_or09 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_or09) multiple ORs ... ok test_if_tag_shortcircuit01 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_shortcircuit01) If evaluations are shortcircuited where possible ... ok test_if_tag_shortcircuit02 (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_shortcircuit02) The is_bad() function should not be evaluated. If it is, an ... ok test_if_tag_single_eq (template_tests.syntax_tests.test_if.IfTagTests.test_if_tag_single_eq) ... ok test_ifequal01 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal01) ... ok test_ifequal02 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal02) ... ok test_ifequal03 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal03) ... ok test_ifequal04 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal04) ... ok test_ifequal05 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal05) ... ok test_ifequal06 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal06) ... ok test_ifequal07 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal07) ... ok test_ifequal08 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal08) ... ok test_ifequal09 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal09) ... ok test_ifequal10 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal10) ... ok test_ifequal_filter01 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_filter01) ... ok test_ifequal_filter02 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_filter02) ... ok test_ifequal_filter03 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_filter03) ... ok test_ifequal_filter04 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_filter04) ... ok test_ifequal_filter05 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_filter05) ... ok test_ifequal_numeric01 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric01) ... ok test_ifequal_numeric02 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric02) ... ok test_ifequal_numeric03 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric03) ... ok test_ifequal_numeric04 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric04) ... ok test_ifequal_numeric05 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric05) ... ok test_ifequal_numeric06 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric06) ... ok test_ifequal_numeric07 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric07) ... ok test_ifequal_numeric08 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric08) ... ok test_ifequal_numeric09 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric09) ... ok test_ifequal_numeric10 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric10) ... ok test_ifequal_numeric11 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric11) ... ok test_ifequal_numeric12 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_numeric12) ... ok test_ifequal_split01 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split01) ... ok test_ifequal_split02 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split02) ... ok test_ifequal_split03 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split03) ... ok test_ifequal_split04 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split04) ... ok test_ifequal_split05 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split05) ... ok test_ifequal_split06 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split06) ... ok test_ifequal_split07 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split07) ... ok test_ifequal_split08 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split08) ... ok test_ifequal_split09 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split09) ... ok test_ifequal_split10 (template_tests.syntax_tests.test_if_equal.IfEqualTagTests.test_ifequal_split10) ... ok test_ifnotequal01 (template_tests.syntax_tests.test_if_equal.IfNotEqualTagTests.test_ifnotequal01) ... ok test_ifnotequal02 (template_tests.syntax_tests.test_if_equal.IfNotEqualTagTests.test_ifnotequal02) ... ok test_ifnotequal03 (template_tests.syntax_tests.test_if_equal.IfNotEqualTagTests.test_ifnotequal03) ... ok test_ifnotequal04 (template_tests.syntax_tests.test_if_equal.IfNotEqualTagTests.test_ifnotequal04) ... ok test_one_var (template_tests.syntax_tests.test_if_equal.IfNotEqualTagTests.test_one_var) ... ok test_extends_include_missing_baseloader (template_tests.syntax_tests.test_include.IncludeTests.test_extends_include_missing_baseloader) #12787 -- The correct template is identified as not existing ... ok test_extends_include_missing_cachedloader (template_tests.syntax_tests.test_include.IncludeTests.test_extends_include_missing_cachedloader) ... ok test_include_cache (template_tests.syntax_tests.test_include.IncludeTests.test_include_cache) {% include %} keeps resolved templates constant (#27974). The ... ok test_include_from_loader_get_template (template_tests.syntax_tests.test_include.IncludeTests.test_include_from_loader_get_template) ... ok test_include_immediate_missing (template_tests.syntax_tests.test_include.IncludeTests.test_include_immediate_missing) #16417 -- Include tags pointing to missing templates should not raise ... ok test_include_missing_template (template_tests.syntax_tests.test_include.IncludeTests.test_include_missing_template) The correct template is identified as not existing ... ok test_include_recursive (template_tests.syntax_tests.test_include.IncludeTests.test_include_recursive) ... ok test_include_template_argument (template_tests.syntax_tests.test_include.IncludeTests.test_include_template_argument) Support any render() supporting object ... ok test_include_template_iterable (template_tests.syntax_tests.test_include.IncludeTests.test_include_template_iterable) ... ok test_include_template_none (template_tests.syntax_tests.test_include.IncludeTests.test_include_template_none) ... ok test_invalidstr01 (template_tests.syntax_tests.test_invalid_string.InvalidStringTests.test_invalidstr01) ... ok test_invalidstr02 (template_tests.syntax_tests.test_invalid_string.InvalidStringTests.test_invalidstr02) ... ok test_invalidstr03 (template_tests.syntax_tests.test_invalid_string.InvalidStringTests.test_invalidstr03) ... ok test_invalidstr04 (template_tests.syntax_tests.test_invalid_string.InvalidStringTests.test_invalidstr04) ... ok test_invalidstr04_2 (template_tests.syntax_tests.test_invalid_string.InvalidStringTests.test_invalidstr04_2) ... ok test_invalidstr05 (template_tests.syntax_tests.test_invalid_string.InvalidStringTests.test_invalidstr05) ... ok test_invalidstr06 (template_tests.syntax_tests.test_invalid_string.InvalidStringTests.test_invalidstr06) ... ok test_invalidstr07 (template_tests.syntax_tests.test_invalid_string.InvalidStringTests.test_invalidstr07) ... ok test_include01 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include01) ... ok test_include02 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include02) ... ok test_include03 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include03) ... ok test_include04 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include04) ... ok test_include06 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include06) ... ok test_include07 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include07) ... ok test_include08 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include08) ... ok test_include09 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include09) ... ok test_include10 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include10) ... ok test_include11 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include11) ... ok test_include12 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include12) ... ok test_include13 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include13) ... ok test_include14 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include14) ... ok test_include_empty (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_empty) ... ok test_include_error01 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error01) ... ok test_include_error02 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error02) ... ok test_include_error03 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error03) ... ok test_include_error04 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error04) ... ok test_include_error05 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error05) ... ok test_include_error06 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error06) ... ok test_include_error07 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error07) ... ok test_include_error08 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error08) ... ok test_include_error09 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error09) ... ok test_include_error10 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_error10) ... ok test_include_fail1 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_fail1) ... ok test_include_fail2 (template_tests.syntax_tests.test_include.IncludeTagTests.test_include_fail2) ... ok test_list_index01 (template_tests.syntax_tests.test_list_index.ListIndexTests.test_list_index01) List-index syntax allows a template to access a certain item of a ... ok test_list_index02 (template_tests.syntax_tests.test_list_index.ListIndexTests.test_list_index02) Fail silently when the list index is out of range. ... ok test_list_index03 (template_tests.syntax_tests.test_list_index.ListIndexTests.test_list_index03) Fail silently when the list index is out of range. ... ok test_list_index04 (template_tests.syntax_tests.test_list_index.ListIndexTests.test_list_index04) Fail silently when variable is a dict without the specified key. ... ok test_list_index05 (template_tests.syntax_tests.test_list_index.ListIndexTests.test_list_index05) Dictionary lookup wins out when dict's key is a string. ... ok test_list_index06 (template_tests.syntax_tests.test_list_index.ListIndexTests.test_list_index06) But list-index lookup wins out when dict's key is an int, which ... ok test_list_index07 (template_tests.syntax_tests.test_list_index.ListIndexTests.test_list_index07) Dictionary lookup wins out when there is a string and int version ... ok test_load01 (template_tests.syntax_tests.test_load.LoadTagTests.test_load01) ... ok test_load02 (template_tests.syntax_tests.test_load.LoadTagTests.test_load02) ... ok test_load03 (template_tests.syntax_tests.test_load.LoadTagTests.test_load03) ... ok test_load04 (template_tests.syntax_tests.test_load.LoadTagTests.test_load04) ... ok test_load05 (template_tests.syntax_tests.test_load.LoadTagTests.test_load05) ... ok test_load06 (template_tests.syntax_tests.test_load.LoadTagTests.test_load06) ... ok test_load07 (template_tests.syntax_tests.test_load.LoadTagTests.test_load07) ... ok test_load08 (template_tests.syntax_tests.test_load.LoadTagTests.test_load08) ... ok test_load09 (template_tests.syntax_tests.test_load.LoadTagTests.test_load09) ... ok test_load10 (template_tests.syntax_tests.test_load.LoadTagTests.test_load10) ... ok test_load12 (template_tests.syntax_tests.test_load.LoadTagTests.test_load12) ... ok test_lorem1 (template_tests.syntax_tests.test_lorem.LoremTagTests.test_lorem1) ... ok test_lorem_default (template_tests.syntax_tests.test_lorem.LoremTagTests.test_lorem_default) ... ok test_lorem_incorrect_count (template_tests.syntax_tests.test_lorem.LoremTagTests.test_lorem_incorrect_count) ... ok test_lorem_multiple_paragraphs (template_tests.syntax_tests.test_lorem.LoremTagTests.test_lorem_multiple_paragraphs) ... ok test_lorem_random (template_tests.syntax_tests.test_lorem.LoremTagTests.test_lorem_random) ... ok test_lorem_syntax (template_tests.syntax_tests.test_lorem.LoremTagTests.test_lorem_syntax) ... ok test_multiline01 (template_tests.syntax_tests.test_multiline.MultilineTests.test_multiline01) ... ok test_namedendblocks01 (template_tests.syntax_tests.test_named_endblock.NamedEndblockTests.test_namedendblocks01) ... ok test_namedendblocks02 (template_tests.syntax_tests.test_named_endblock.NamedEndblockTests.test_namedendblocks02) ... ok test_namedendblocks03 (template_tests.syntax_tests.test_named_endblock.NamedEndblockTests.test_namedendblocks03) ... ok test_namedendblocks04 (template_tests.syntax_tests.test_named_endblock.NamedEndblockTests.test_namedendblocks04) ... ok test_namedendblocks05 (template_tests.syntax_tests.test_named_endblock.NamedEndblockTests.test_namedendblocks05) ... ok test_namedendblocks06 (template_tests.syntax_tests.test_named_endblock.NamedEndblockTests.test_namedendblocks06) Mixed named and unnamed endblocks ... ok test_namedendblocks07 (template_tests.syntax_tests.test_named_endblock.NamedEndblockTests.test_namedendblocks07) ... ok test_now01 (template_tests.syntax_tests.test_now.NowTagTests.test_now01) Simple case ... ok test_now02 (template_tests.syntax_tests.test_now.NowTagTests.test_now02) ... ok test_now03 (template_tests.syntax_tests.test_now.NowTagTests.test_now03) #15092 - Also accept simple quotes ... ok test_now04 (template_tests.syntax_tests.test_now.NowTagTests.test_now04) ... ok test_now05 (template_tests.syntax_tests.test_now.NowTagTests.test_now05) ... ok test_now06 (template_tests.syntax_tests.test_now.NowTagTests.test_now06) ... ok test_now07 (template_tests.syntax_tests.test_now.NowTagTests.test_now07) ... ok test_now_args (template_tests.syntax_tests.test_now.NowTagTests.test_now_args) ... ok test_numpy_array_index01 (template_tests.syntax_tests.test_numpy.NumpyTests.test_numpy_array_index01) Numpy's array-index syntax allows a template to access a certain ... ok test_numpy_array_index02 (template_tests.syntax_tests.test_numpy.NumpyTests.test_numpy_array_index02) Fail silently when the array index is out of range. ... ok test_regroup01 (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup01) ... ok test_regroup02 (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup02) Test for silent failure when target variable isn't found ... ok test_regroup03 (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup03) Regression tests for #17675 ... ok test_regroup04 (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup04) The join template filter has needs_autoescape = True ... ok test_regroup05 (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup05) ... ok test_regroup06 (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup06) ... ok test_regroup07 (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup07) ... ok test_regroup08 (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup08) ... ok test_regroup_unpack (template_tests.syntax_tests.test_regroup.RegroupTagTests.test_regroup_unpack) ... ok test_setup (template_tests.syntax_tests.test_setup.SetupTests.test_setup) Let's just make sure setup runs cases in the right order. ... ok test_resetcycle01 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle01) ... ok test_resetcycle02 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle02) ... ok test_resetcycle03 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle03) ... ok test_resetcycle04 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle04) ... ok test_resetcycle05 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle05) ... ok test_resetcycle06 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle06) ... ok test_resetcycle07 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle07) ... ok test_resetcycle08 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle08) ... ok test_resetcycle09 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle09) ... ok test_resetcycle10 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle10) ... ok test_resetcycle11 (template_tests.syntax_tests.test_resetcycle.ResetCycleTagTests.test_resetcycle11) ... ok test_simpletag_renamed01 (template_tests.syntax_tests.test_simple_tag.SimpleTagTests.test_simpletag_renamed01) ... ok test_simpletag_renamed02 (template_tests.syntax_tests.test_simple_tag.SimpleTagTests.test_simpletag_renamed02) ... ok test_simpletag_renamed03 (template_tests.syntax_tests.test_simple_tag.SimpleTagTests.test_simpletag_renamed03) ... ok test_spaceless01 (template_tests.syntax_tests.test_spaceless.SpacelessTagTests.test_spaceless01) ... ok test_spaceless02 (template_tests.syntax_tests.test_spaceless.SpacelessTagTests.test_spaceless02) ... ok test_spaceless03 (template_tests.syntax_tests.test_spaceless.SpacelessTagTests.test_spaceless03) ... ok test_spaceless04 (template_tests.syntax_tests.test_spaceless.SpacelessTagTests.test_spaceless04) ... ok test_spaceless05 (template_tests.syntax_tests.test_spaceless.SpacelessTagTests.test_spaceless05) ... ok test_spaceless06 (template_tests.syntax_tests.test_spaceless.SpacelessTagTests.test_spaceless06) ... ok test_static_prefixtag01 (template_tests.syntax_tests.test_static.StaticTagTests.test_static_prefixtag01) ... ok test_static_prefixtag02 (template_tests.syntax_tests.test_static.StaticTagTests.test_static_prefixtag02) ... ok test_static_prefixtag03 (template_tests.syntax_tests.test_static.StaticTagTests.test_static_prefixtag03) ... ok test_static_prefixtag04 (template_tests.syntax_tests.test_static.StaticTagTests.test_static_prefixtag04) ... ok test_static_prefixtag_without_as (template_tests.syntax_tests.test_static.StaticTagTests.test_static_prefixtag_without_as) ... ok test_static_quotes_urls (template_tests.syntax_tests.test_static.StaticTagTests.test_static_quotes_urls) ... ok test_static_statictag01 (template_tests.syntax_tests.test_static.StaticTagTests.test_static_statictag01) ... ok test_static_statictag02 (template_tests.syntax_tests.test_static.StaticTagTests.test_static_statictag02) ... ok test_static_statictag03 (template_tests.syntax_tests.test_static.StaticTagTests.test_static_statictag03) ... ok test_static_statictag04 (template_tests.syntax_tests.test_static.StaticTagTests.test_static_statictag04) ... ok test_static_statictag_without_path (template_tests.syntax_tests.test_static.StaticTagTests.test_static_statictag_without_path) ... ok test_templatetag01 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag01) ... ok test_templatetag02 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag02) ... ok test_templatetag03 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag03) ... ok test_templatetag04 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag04) ... ok test_templatetag05 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag05) ... ok test_templatetag06 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag06) ... ok test_templatetag07 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag07) ... ok test_templatetag08 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag08) ... ok test_templatetag09 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag09) ... ok test_templatetag10 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag10) ... ok test_templatetag11 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag11) ... ok test_templatetag12 (template_tests.syntax_tests.test_template_tag.TemplateTagTests.test_templatetag12) ... ok test_verbatim_tag01 (template_tests.syntax_tests.test_verbatim.VerbatimTagTests.test_verbatim_tag01) ... ok test_verbatim_tag02 (template_tests.syntax_tests.test_verbatim.VerbatimTagTests.test_verbatim_tag02) ... ok test_verbatim_tag03 (template_tests.syntax_tests.test_verbatim.VerbatimTagTests.test_verbatim_tag03) ... ok test_verbatim_tag04 (template_tests.syntax_tests.test_verbatim.VerbatimTagTests.test_verbatim_tag04) ... ok test_verbatim_tag05 (template_tests.syntax_tests.test_verbatim.VerbatimTagTests.test_verbatim_tag05) ... ok test_verbatim_tag06 (template_tests.syntax_tests.test_verbatim.VerbatimTagTests.test_verbatim_tag06) ... ok test_typeerror_as_var (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_typeerror_as_var) ... ok test_widthratio01 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio01) ... ok test_widthratio02 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio02) ... ok test_widthratio03 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio03) ... ok test_widthratio04 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio04) ... ok test_widthratio05 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio05) ... ok test_widthratio06 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio06) 62.5 should round to 62 ... ok test_widthratio07 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio07) 71.4 should round to 71 ... ok test_widthratio08 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio08) ... ok test_widthratio09 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio09) ... ok test_widthratio10 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio10) ... ok test_widthratio11 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio11) #10043: widthratio should allow max_width to be a variable ... ok test_widthratio12a (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio12a) ... ok test_widthratio12b (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio12b) ... ok test_widthratio13a (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio13a) ... ok test_widthratio13b (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio13b) ... ok test_widthratio14a (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio14a) ... ok test_widthratio14b (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio14b) ... ok test_widthratio15 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio15) Test whitespace in filter argument ... ok test_widthratio16 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio16) ... ok test_widthratio17 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio17) ... ok test_widthratio18 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio18) ... ok test_widthratio19 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio19) ... ok test_widthratio20 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio20) ... ok test_widthratio21 (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_widthratio21) ... ok test_zerodivisionerror_as_var (template_tests.syntax_tests.test_width_ratio.WidthRatioTagTests.test_zerodivisionerror_as_var) ... ok test_url01 (template_tests.syntax_tests.test_url.UrlTagTests.test_url01) ... ok test_url02 (template_tests.syntax_tests.test_url.UrlTagTests.test_url02) ... ok test_url02a (template_tests.syntax_tests.test_url.UrlTagTests.test_url02a) ... ok test_url02b (template_tests.syntax_tests.test_url.UrlTagTests.test_url02b) ... ok test_url02c (template_tests.syntax_tests.test_url.UrlTagTests.test_url02c) ... ok test_url03 (template_tests.syntax_tests.test_url.UrlTagTests.test_url03) ... ok test_url04 (template_tests.syntax_tests.test_url.UrlTagTests.test_url04) ... ok test_url05 (template_tests.syntax_tests.test_url.UrlTagTests.test_url05) ... ok test_url06 (template_tests.syntax_tests.test_url.UrlTagTests.test_url06) ... ok test_url08 (template_tests.syntax_tests.test_url.UrlTagTests.test_url08) ... ok test_url09 (template_tests.syntax_tests.test_url.UrlTagTests.test_url09) ... ok test_url10 (template_tests.syntax_tests.test_url.UrlTagTests.test_url10) ... ok test_url11 (template_tests.syntax_tests.test_url.UrlTagTests.test_url11) ... ok test_url12 (template_tests.syntax_tests.test_url.UrlTagTests.test_url12) ... ok test_url13 (template_tests.syntax_tests.test_url.UrlTagTests.test_url13) ... ok test_url14 (template_tests.syntax_tests.test_url.UrlTagTests.test_url14) ... ok test_url15 (template_tests.syntax_tests.test_url.UrlTagTests.test_url15) ... ok test_url18 (template_tests.syntax_tests.test_url.UrlTagTests.test_url18) ... ok test_url19 (template_tests.syntax_tests.test_url.UrlTagTests.test_url19) ... ok test_url20 (template_tests.syntax_tests.test_url.UrlTagTests.test_url20) ... ok test_url21 (template_tests.syntax_tests.test_url.UrlTagTests.test_url21) ... ok test_url_asvar01 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_asvar01) ... ok test_url_asvar02 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_asvar02) ... ok test_url_asvar03 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_asvar03) ... ok test_url_fail01 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail01) ... ok test_url_fail02 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail02) ... ok test_url_fail03 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail03) ... ok test_url_fail04 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail04) ... ok test_url_fail05 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail05) ... ok test_url_fail06 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail06) ... ok test_url_fail07 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail07) ... ok test_url_fail08 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail08) ... ok test_url_fail09 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail09) ... ok test_url_fail11 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail11) ... ok test_url_fail12 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail12) ... ok test_url_fail13 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail13) ... ok test_url_fail14 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail14) ... ok test_url_fail15 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail15) ... ok test_url_fail16 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail16) ... ok test_url_fail17 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail17) ... ok test_url_fail18 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail18) ... ok test_url_fail19 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_fail19) ... ok test_url_namespace01 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_namespace01) ... ok test_url_namespace02 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_namespace02) ... ok test_url_namespace03 (template_tests.syntax_tests.test_url.UrlTagTests.test_url_namespace03) ... ok test_url_namespace_explicit_current_app (template_tests.syntax_tests.test_url.UrlTagTests.test_url_namespace_explicit_current_app) ... ok test_url_namespace_no_current_app (template_tests.syntax_tests.test_url.UrlTagTests.test_url_namespace_no_current_app) ... ok test_repr (template_tests.syntax_tests.test_with.WithNodeTests.test_repr) ... ok test_legacywith01 (template_tests.syntax_tests.test_with.WithTagTests.test_legacywith01) ... ok test_legacywith02 (template_tests.syntax_tests.test_with.WithTagTests.test_legacywith02) ... ok test_with01 (template_tests.syntax_tests.test_with.WithTagTests.test_with01) ... ok test_with02 (template_tests.syntax_tests.test_with.WithTagTests.test_with02) ... ok test_with03 (template_tests.syntax_tests.test_with.WithTagTests.test_with03) ... ok test_with_error01 (template_tests.syntax_tests.test_with.WithTagTests.test_with_error01) ... ok test_with_error02 (template_tests.syntax_tests.test_with.WithTagTests.test_with_error02) ... ok test_get_template_directories (template_tests.test_autoreloader.Jinja2TemplateReloadTests.test_get_template_directories) ... ok test_reset_all_loaders (template_tests.test_autoreloader.Jinja2TemplateReloadTests.test_reset_all_loaders) ... ok test_watch_for_template_changes (template_tests.test_autoreloader.Jinja2TemplateReloadTests.test_watch_for_template_changes) ... ok test_get_template_directories (template_tests.test_autoreloader.TemplateReloadTests.test_get_template_directories) ... ok test_non_template_changed (template_tests.test_autoreloader.TemplateReloadTests.test_non_template_changed) ... ok test_reset_all_loaders (template_tests.test_autoreloader.TemplateReloadTests.test_reset_all_loaders) ... ok test_template_changed (template_tests.test_autoreloader.TemplateReloadTests.test_template_changed) ... ok test_template_dirs_ignore_empty_path (template_tests.test_autoreloader.TemplateReloadTests.test_template_dirs_ignore_empty_path) ... ok test_template_dirs_normalized_to_paths (template_tests.test_autoreloader.TemplateReloadTests.test_template_dirs_normalized_to_paths) ... ok test_watch_for_template_changes (template_tests.test_autoreloader.TemplateReloadTests.test_watch_for_template_changes) ... ok test_lazy_template_string (template_tests.test_base.TemplateTests.test_lazy_template_string) ... ok test_str (template_tests.test_base.VariableDoesNotExistTests.test_str) ... ok test_integer_literals (template_tests.test_base.VariableTests.test_integer_literals) ... ok test_nonliterals (template_tests.test_base.VariableTests.test_nonliterals) Variable names that aren't resolved as literals. ... ok test_context (template_tests.test_context.ContextTests.test_context) ... ok test_context_comparable (template_tests.test_context.ContextTests.test_context_comparable) #21765 -- equality comparison should work ... ok test_copy_request_context_twice (template_tests.test_context.ContextTests.test_copy_request_context_twice) #24273 -- Copy twice shouldn't raise an exception ... ok test_flatten_context (template_tests.test_context.ContextTests.test_flatten_context) ... ok test_flatten_context_with_context (template_tests.test_context.ContextTests.test_flatten_context_with_context) Context.push() with a Context argument should work. ... ok test_push_context_manager (template_tests.test_context.ContextTests.test_push_context_manager) ... ok test_push_context_manager_with_context_object (template_tests.test_context.ContextTests.test_push_context_manager_with_context_object) ... ok test_push_proper_layering (template_tests.test_context.ContextTests.test_push_proper_layering) ... ok test_render_context (template_tests.test_context.ContextTests.test_render_context) ... ok test_resolve_on_context_method (template_tests.test_context.ContextTests.test_resolve_on_context_method) #17778 -- Variable shouldn't resolve RequestContext methods ... ok test_set_upward (template_tests.test_context.ContextTests.test_set_upward) ... ok test_set_upward_empty_context (template_tests.test_context.ContextTests.test_set_upward_empty_context) ... ok test_set_upward_with_push (template_tests.test_context.ContextTests.test_set_upward_with_push) The highest context which has the given key is used. ... ok test_set_upward_with_push_no_match (template_tests.test_context.ContextTests.test_set_upward_with_push_no_match) The highest context is used if the given key isn't found. ... ok test_setdefault (template_tests.test_context.ContextTests.test_setdefault) ... ok test_update_context_manager (template_tests.test_context.ContextTests.test_update_context_manager) ... ok test_update_context_manager_with_context_object (template_tests.test_context.ContextTests.test_update_context_manager_with_context_object) ... ok test_update_proper_layering (template_tests.test_context.ContextTests.test_update_proper_layering) ... ok test_context_comparable (template_tests.test_context.RequestContextTests.test_context_comparable) ... ok test_include_only (template_tests.test_context.RequestContextTests.test_include_only) #15721 -- ``{% include %}`` and ``RequestContext`` should work ... ok test_modify_context_and_render (template_tests.test_context.RequestContextTests.test_modify_context_and_render) ... ok test_stack_size (template_tests.test_context.RequestContextTests.test_stack_size) Optimized RequestContext construction (#7116). ... ok test_decorated_filter (template_tests.test_custom.CustomFilterTests.test_decorated_filter) ... ok test_filter (template_tests.test_custom.CustomFilterTests.test_filter) ... ok test_15070_use_l10n (template_tests.test_custom.InclusionTagTests.test_15070_use_l10n) Inclusion tag passes down `use_l10n` of context to the ... ok test_include_tag_missing_context (template_tests.test_custom.InclusionTagTests.test_include_tag_missing_context) ... ok test_inclusion_tag_errors (template_tests.test_custom.InclusionTagTests.test_inclusion_tag_errors) ... ok test_inclusion_tag_registration (template_tests.test_custom.InclusionTagTests.test_inclusion_tag_registration) ... ok test_inclusion_tags (template_tests.test_custom.InclusionTagTests.test_inclusion_tags) ... ok test_inclusion_tags_from_template (template_tests.test_custom.InclusionTagTests.test_inclusion_tags_from_template) ... ok test_no_render_side_effect (template_tests.test_custom.InclusionTagTests.test_no_render_side_effect) #23441 -- InclusionNode shouldn't modify its nodelist at render time. ... ok test_render_context_is_cleared (template_tests.test_custom.InclusionTagTests.test_render_context_is_cleared) #24555 -- InclusionNode should push and pop the render_context stack ... ok test_simple_tag_errors (template_tests.test_custom.SimpleTagTests.test_simple_tag_errors) ... ok test_simple_tag_escaping_autoescape_off (template_tests.test_custom.SimpleTagTests.test_simple_tag_escaping_autoescape_off) ... ok test_simple_tag_explicit_escaping (template_tests.test_custom.SimpleTagTests.test_simple_tag_explicit_escaping) ... ok test_simple_tag_format_html_escaping (template_tests.test_custom.SimpleTagTests.test_simple_tag_format_html_escaping) ... ok test_simple_tag_missing_context (template_tests.test_custom.SimpleTagTests.test_simple_tag_missing_context) ... ok test_simple_tag_naive_escaping (template_tests.test_custom.SimpleTagTests.test_simple_tag_naive_escaping) ... ok test_simple_tag_registration (template_tests.test_custom.SimpleTagTests.test_simple_tag_registration) ... ok test_simple_tags (template_tests.test_custom.SimpleTagTests.test_simple_tags) ... ok test_load_annotated_function (template_tests.test_custom.TemplateTagLoadingTests.test_load_annotated_function) ... ok test_load_error (template_tests.test_custom.TemplateTagLoadingTests.test_load_error) ... ok test_load_error_egg (template_tests.test_custom.TemplateTagLoadingTests.test_load_error_egg) ... ok test_load_working_egg (template_tests.test_custom.TemplateTagLoadingTests.test_load_working_egg) ... ok test_cached_loader_priority (template_tests.test_engine.LoaderTests.test_cached_loader_priority) The order of template loader works. Refs #21460. ... ok test_loader_priority (template_tests.test_engine.LoaderTests.test_loader_priority) #21460 -- The order of template loader works. ... ok test_origin (template_tests.test_engine.LoaderTests.test_origin) ... ok test_autoescape_off (template_tests.test_engine.RenderToStringTest.test_autoescape_off) ... ok test_basic_context (template_tests.test_engine.RenderToStringTest.test_basic_context) ... ok test_multiple_engines_configured (template_tests.test_engine.GetDefaultTests.test_multiple_engines_configured) ... ok test_no_engines_configured (template_tests.test_engine.GetDefaultTests.test_no_engines_configured) ... ok test_single_engine_configured (template_tests.test_engine.GetDefaultTests.test_single_engine_configured) ... ok test_block_override_in_extended_included_template (template_tests.test_extends.ExtendsBehaviorTests.test_block_override_in_extended_included_template) ExtendsNode.find_template() initializes history with self.origin ... ok test_extend_cached (template_tests.test_extends.ExtendsBehaviorTests.test_extend_cached) ... ok test_extend_missing (template_tests.test_extends.ExtendsBehaviorTests.test_extend_missing) ... ok test_extend_recursive (template_tests.test_extends.ExtendsBehaviorTests.test_extend_recursive) ... ok test_extend_self_error (template_tests.test_extends.ExtendsBehaviorTests.test_extend_self_error) Catch if a template extends itself and no other matching ... ok test_normal_extend (template_tests.test_extends.ExtendsBehaviorTests.test_normal_extend) ... ok test_recursive_multiple_loaders (template_tests.test_extends.ExtendsBehaviorTests.test_recursive_multiple_loaders) ... ok test_unique_history_per_loader (template_tests.test_extends.ExtendsBehaviorTests.test_unique_history_per_loader) Extending should continue even if two loaders return the same ... ok test_dir1_extend (template_tests.test_extends_relative.ExtendsRelativeBehaviorTests.test_dir1_extend) ... ok test_dir1_extend1 (template_tests.test_extends_relative.ExtendsRelativeBehaviorTests.test_dir1_extend1) ... ok test_dir1_extend2 (template_tests.test_extends_relative.ExtendsRelativeBehaviorTests.test_dir1_extend2) ... ok test_dir1_extend3 (template_tests.test_extends_relative.ExtendsRelativeBehaviorTests.test_dir1_extend3) ... ok test_dir2_extend (template_tests.test_extends_relative.ExtendsRelativeBehaviorTests.test_dir2_extend) ... ok test_extend_error (template_tests.test_extends_relative.ExtendsRelativeBehaviorTests.test_extend_error) ... ok test_normal_extend (template_tests.test_extends_relative.ExtendsRelativeBehaviorTests.test_normal_extend) ... ok test_mixing1 (template_tests.test_extends_relative.ExtendsMixedBehaviorTests.test_mixing1) ... ok test_mixing2 (template_tests.test_extends_relative.ExtendsMixedBehaviorTests.test_mixing2) ... ok test_mixing_loop (template_tests.test_extends_relative.ExtendsMixedBehaviorTests.test_mixing_loop) ... ok test_dir2_include (template_tests.test_extends_relative.IncludeRelativeBehaviorTests.test_dir2_include) ... ok test_include_error (template_tests.test_extends_relative.IncludeRelativeBehaviorTests.test_include_error) ... ok test_normal_include (template_tests.test_extends_relative.IncludeRelativeBehaviorTests.test_normal_include) ... ok test_normal_include_variable (template_tests.test_extends_relative.IncludeRelativeBehaviorTests.test_normal_include_variable) ... ok test_filter (template_tests.test_library.FilterRegistrationTests.test_filter) ... ok test_filter_call (template_tests.test_library.FilterRegistrationTests.test_filter_call) ... ok test_filter_invalid (template_tests.test_library.FilterRegistrationTests.test_filter_invalid) ... ok test_filter_name_arg (template_tests.test_library.FilterRegistrationTests.test_filter_name_arg) ... ok test_filter_name_kwarg (template_tests.test_library.FilterRegistrationTests.test_filter_name_kwarg) ... ok test_filter_parens (template_tests.test_library.FilterRegistrationTests.test_filter_parens) ... ok test_inclusion_tag (template_tests.test_library.InclusionTagRegistrationTests.test_inclusion_tag) ... ok test_inclusion_tag_name (template_tests.test_library.InclusionTagRegistrationTests.test_inclusion_tag_name) ... ok test_inclusion_tag_wrapped (template_tests.test_library.InclusionTagRegistrationTests.test_inclusion_tag_wrapped) ... ok test_simple_tag (template_tests.test_library.SimpleTagRegistrationTests.test_simple_tag) ... ok test_simple_tag_invalid (template_tests.test_library.SimpleTagRegistrationTests.test_simple_tag_invalid) ... ok test_simple_tag_name_kwarg (template_tests.test_library.SimpleTagRegistrationTests.test_simple_tag_name_kwarg) ... ok test_simple_tag_parens (template_tests.test_library.SimpleTagRegistrationTests.test_simple_tag_parens) ... ok test_simple_tag_wrapped (template_tests.test_library.SimpleTagRegistrationTests.test_simple_tag_wrapped) ... ok test_tag (template_tests.test_library.TagRegistrationTests.test_tag) ... ok test_tag_call (template_tests.test_library.TagRegistrationTests.test_tag_call) ... ok test_tag_invalid (template_tests.test_library.TagRegistrationTests.test_tag_invalid) ... ok test_tag_name_arg (template_tests.test_library.TagRegistrationTests.test_tag_name_arg) ... ok test_tag_name_kwarg (template_tests.test_library.TagRegistrationTests.test_tag_name_kwarg) ... ok test_tag_parens (template_tests.test_library.TagRegistrationTests.test_tag_parens) ... ok test_cached_exception_no_traceback (template_tests.test_loaders.CachedLoaderTests.test_cached_exception_no_traceback) When a TemplateDoesNotExist instance is cached, the cached instance ... ok test_get_dirs (template_tests.test_loaders.CachedLoaderTests.test_get_dirs) ... ok test_get_template (template_tests.test_loaders.CachedLoaderTests.test_get_template) ... ok test_get_template_missing_debug_off (template_tests.test_loaders.CachedLoaderTests.test_get_template_missing_debug_off) With template debugging disabled, the raw TemplateDoesNotExist class ... ok test_get_template_missing_debug_on (template_tests.test_loaders.CachedLoaderTests.test_get_template_missing_debug_on) With template debugging enabled, a TemplateDoesNotExist instance ... ok test_template_name_lazy_string (template_tests.test_loaders.CachedLoaderTests.test_template_name_lazy_string) #26603 -- A template name specified as a lazy string should be forced ... ok test_template_name_leading_dash_caching (template_tests.test_loaders.CachedLoaderTests.test_template_name_leading_dash_caching) #26536 -- A leading dash in a template name shouldn't be stripped ... ok test_bytestring (template_tests.test_loaders.FileSystemLoaderTests.test_bytestring) ... ok test_case_sensitivity (template_tests.test_loaders.FileSystemLoaderTests.test_case_sensitivity) ... skipped 'This test only runs on case-sensitive file systems.' test_directory_security (template_tests.test_loaders.FileSystemLoaderTests.test_directory_security) ... ok test_file_does_not_exist (template_tests.test_loaders.FileSystemLoaderTests.test_file_does_not_exist) ... ok test_get_template (template_tests.test_loaders.FileSystemLoaderTests.test_get_template) ... ok test_loaders_dirs (template_tests.test_loaders.FileSystemLoaderTests.test_loaders_dirs) ... ok test_loaders_dirs_empty (template_tests.test_loaders.FileSystemLoaderTests.test_loaders_dirs_empty) An empty dirs list in loaders overrides top level dirs. ... ok test_notafile_error (template_tests.test_loaders.FileSystemLoaderTests.test_notafile_error) ... ok test_permissions_error (template_tests.test_loaders.FileSystemLoaderTests.test_permissions_error) ... ok test_unicode_dir_name (template_tests.test_loaders.FileSystemLoaderTests.test_unicode_dir_name) ... ok test_unicode_template_name (template_tests.test_loaders.FileSystemLoaderTests.test_unicode_template_name) ... ok test_get_template (template_tests.test_loaders.AppDirectoriesLoaderTests.test_get_template) ... ok test_not_installed (template_tests.test_loaders.AppDirectoriesLoaderTests.test_not_installed) ... ok test_get_template (template_tests.test_loaders.LocmemLoaderTests.test_get_template) ... ok test_log_on_variable_does_not_exist_not_silent (template_tests.test_logging.VariableResolveLoggingTests.test_log_on_variable_does_not_exist_not_silent) ... ok test_log_on_variable_does_not_exist_silent (template_tests.test_logging.VariableResolveLoggingTests.test_log_on_variable_does_not_exist_silent) ... ok test_no_log_when_variable_exists (template_tests.test_logging.VariableResolveLoggingTests.test_no_log_when_variable_exists) ... ok test_correct_exception_index (template_tests.test_nodelist.ErrorIndexTest.test_correct_exception_index) ... ok test_for (template_tests.test_nodelist.NodelistTest.test_for) ... ok test_if (template_tests.test_nodelist.NodelistTest.test_if) ... ok test_ifchanged (template_tests.test_nodelist.NodelistTest.test_ifchanged) ... ok test_ifequal (template_tests.test_nodelist.NodelistTest.test_ifequal) ... ok test_textnode_repr (template_tests.test_nodelist.TextNodeTest.test_textnode_repr) ... ok test_filter_args_count (template_tests.test_parser.ParserTests.test_filter_args_count) ... ok test_filter_parsing (template_tests.test_parser.ParserTests.test_filter_parsing) ... ok test_token_smart_split (template_tests.test_parser.ParserTests.test_token_smart_split) #7027 -- _() syntax should work with spaces ... ok test_variable_parsing (template_tests.test_parser.ParserTests.test_variable_parsing) ... ok test_custom_urlconf (template_tests.test_response.CustomURLConfTest.test_custom_urlconf) ... ok test_args (template_tests.test_response.TemplateResponseTest.test_args) ... ok test_context_processor_priority (template_tests.test_response.TemplateResponseTest.test_context_processor_priority) ... ok test_headers (template_tests.test_response.TemplateResponseTest.test_headers) ... ok test_kwargs (template_tests.test_response.TemplateResponseTest.test_kwargs) ... ok test_pickling (template_tests.test_response.TemplateResponseTest.test_pickling) ... ok test_render (template_tests.test_response.TemplateResponseTest.test_render) ... ok test_render_with_requestcontext (template_tests.test_response.TemplateResponseTest.test_render_with_requestcontext) ... ok test_repickling (template_tests.test_response.TemplateResponseTest.test_repickling) ... ok test_using (template_tests.test_response.TemplateResponseTest.test_using) ... ok test_args (template_tests.test_response.SimpleTemplateResponseTest.test_args) ... ok test_content_access_rendered (template_tests.test_response.SimpleTemplateResponseTest.test_content_access_rendered) ... ok test_content_access_unrendered (template_tests.test_response.SimpleTemplateResponseTest.test_content_access_unrendered) ... ok test_dict_context (template_tests.test_response.SimpleTemplateResponseTest.test_dict_context) ... ok test_explicit_baking (template_tests.test_response.SimpleTemplateResponseTest.test_explicit_baking) ... ok test_headers (template_tests.test_response.SimpleTemplateResponseTest.test_headers) ... ok test_iteration_rendered (template_tests.test_response.SimpleTemplateResponseTest.test_iteration_rendered) ... ok test_iteration_unrendered (template_tests.test_response.SimpleTemplateResponseTest.test_iteration_unrendered) ... ok test_kwargs (template_tests.test_response.SimpleTemplateResponseTest.test_kwargs) ... ok test_pickling (template_tests.test_response.SimpleTemplateResponseTest.test_pickling) ... ok test_pickling_cookie (template_tests.test_response.SimpleTemplateResponseTest.test_pickling_cookie) ... ok test_post_callbacks (template_tests.test_response.SimpleTemplateResponseTest.test_post_callbacks) Rendering a template response triggers the post-render callbacks ... ok test_render (template_tests.test_response.SimpleTemplateResponseTest.test_render) ... ok test_repickling (template_tests.test_response.SimpleTemplateResponseTest.test_repickling) ... ok test_set_content (template_tests.test_response.SimpleTemplateResponseTest.test_set_content) ... ok test_template_resolving (template_tests.test_response.SimpleTemplateResponseTest.test_template_resolving) ... ok test_using (template_tests.test_response.SimpleTemplateResponseTest.test_using) ... ok test_compile_filter_expression_error (template_tests.tests.TemplateTests.test_compile_filter_expression_error) 19819 -- Make sure the correct token is highlighted for ... ok test_compile_tag_error (template_tests.tests.TemplateTests.test_compile_tag_error) Errors raised while compiling nodes should include the token ... ok test_compile_tag_error_27584 (template_tests.tests.TemplateTests.test_compile_tag_error_27584) ... ok test_compile_tag_error_27956 (template_tests.tests.TemplateTests.test_compile_tag_error_27956) Errors in a child of {% extends %} are displayed correctly. ... ok test_extends_generic_template (template_tests.tests.TemplateTests.test_extends_generic_template) #24338 -- Allow extending django.template.backends.django.Template ... ok test_invalid_block_suggestion (template_tests.tests.TemplateTests.test_invalid_block_suggestion) Error messages should include the unexpected block name and be in all ... ok test_no_wrapped_exception (template_tests.tests.TemplateTests.test_no_wrapped_exception) # 16770 -- The template system doesn't wrap exceptions, but annotates ... ok test_node_origin (template_tests.tests.TemplateTests.test_node_origin) #25848 -- Set origin on Node so debugging tools can determine which ... ok test_string_origin (template_tests.tests.TemplateTests.test_string_origin) ... ok test_super_errors (template_tests.tests.TemplateTests.test_super_errors) #18169 -- NoReverseMatch should not be silence in block.super. ... ok test_unknown_block_tag (template_tests.tests.TemplateTests.test_unknown_block_tag) ... ok test_url_reverse_no_settings_module (template_tests.tests.TemplateTests.test_url_reverse_no_settings_module) #9005 -- url tag shouldn't require settings.SETTINGS_MODULE to ... ok test_url_reverse_view_name (template_tests.tests.TemplateTests.test_url_reverse_view_name) #19827 -- url tag should keep original strack trace when reraising ... ok test_cooperative_multiple_inheritance (forms_tests.field_tests.test_base.BasicFieldsTests.test_cooperative_multiple_inheritance) ... ok test_field_deepcopies_widget_instance (forms_tests.field_tests.test_base.BasicFieldsTests.test_field_deepcopies_widget_instance) ... ok test_field_sets_widget_is_required (forms_tests.field_tests.test_base.BasicFieldsTests.test_field_sets_widget_is_required) ... ok test_disabled_field_has_changed_always_false (forms_tests.field_tests.test_base.DisabledFieldTests.test_disabled_field_has_changed_always_false) ... ok test_boolean_picklable (forms_tests.field_tests.test_booleanfield.BooleanFieldTest.test_boolean_picklable) ... ok test_booleanfield_changed (forms_tests.field_tests.test_booleanfield.BooleanFieldTest.test_booleanfield_changed) ... ok test_booleanfield_clean_1 (forms_tests.field_tests.test_booleanfield.BooleanFieldTest.test_booleanfield_clean_1) ... ok test_booleanfield_clean_2 (forms_tests.field_tests.test_booleanfield.BooleanFieldTest.test_booleanfield_clean_2) ... ok test_disabled_has_changed (forms_tests.field_tests.test_booleanfield.BooleanFieldTest.test_disabled_has_changed) ... ok test_charfield_1 (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_1) ... ok test_charfield_2 (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_2) ... ok test_charfield_3 (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_3) ... ok test_charfield_4 (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_4) ... ok test_charfield_5 (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_5) ... ok test_charfield_disabled (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_disabled) ... ok test_charfield_length_not_int (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_length_not_int) Setting min_length or max_length to something that is not a number ... ok test_charfield_strip (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_strip) Values have whitespace stripped but not if strip=False. ... ok test_charfield_widget_attrs (forms_tests.field_tests.test_charfield.CharFieldTest.test_charfield_widget_attrs) CharField.widget_attrs() always returns a dictionary and includes ... ok test_clean_non_string (forms_tests.field_tests.test_charfield.CharFieldTest.test_clean_non_string) CharField.clean() calls str(value) before stripping it. ... ok test_null_characters_prohibited (forms_tests.field_tests.test_charfield.CharFieldTest.test_null_characters_prohibited) ... ok test_strip_before_checking_empty (forms_tests.field_tests.test_charfield.CharFieldTest.test_strip_before_checking_empty) A whitespace-only value, ' ', is stripped to an empty string and then ... ok test_choicefield_1 (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_1) ... ok test_choicefield_2 (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_2) ... ok test_choicefield_3 (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_3) ... ok test_choicefield_4 (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_4) ... ok test_choicefield_callable (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_callable) ... ok test_choicefield_callable_may_evaluate_to_different_values (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_callable_may_evaluate_to_different_values) ... ok test_choicefield_choices_default (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_choices_default) ... ok test_choicefield_disabled (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_disabled) ... ok test_choicefield_enumeration (forms_tests.field_tests.test_choicefield.ChoiceFieldTest.test_choicefield_enumeration) ... ok test_combofield_1 (forms_tests.field_tests.test_combofield.ComboFieldTest.test_combofield_1) ... ok test_combofield_2 (forms_tests.field_tests.test_combofield.ComboFieldTest.test_combofield_2) ... ok test_datetimefield_changed (forms_tests.field_tests.test_datetimefield.DateTimeFieldTest.test_datetimefield_changed) ... ok test_datetimefield_clean (forms_tests.field_tests.test_datetimefield.DateTimeFieldTest.test_datetimefield_clean) ... ok test_datetimefield_clean_input_formats (forms_tests.field_tests.test_datetimefield.DateTimeFieldTest.test_datetimefield_clean_input_formats) ... ok test_datetimefield_clean_invalid (forms_tests.field_tests.test_datetimefield.DateTimeFieldTest.test_datetimefield_clean_invalid) ... ok test_datetimefield_not_required (forms_tests.field_tests.test_datetimefield.DateTimeFieldTest.test_datetimefield_not_required) ... ok test_datefield_1 (forms_tests.field_tests.test_datefield.DateFieldTest.test_datefield_1) ... ok test_datefield_2 (forms_tests.field_tests.test_datefield.DateFieldTest.test_datefield_2) ... ok test_datefield_3 (forms_tests.field_tests.test_datefield.DateFieldTest.test_datefield_3) ... ok test_datefield_4 (forms_tests.field_tests.test_datefield.DateFieldTest.test_datefield_4) ... ok test_datefield_5 (forms_tests.field_tests.test_datefield.DateFieldTest.test_datefield_5) ... ok test_datefield_changed (forms_tests.field_tests.test_datefield.DateFieldTest.test_datefield_changed) ... ok test_datefield_strptime (forms_tests.field_tests.test_datefield.DateFieldTest.test_datefield_strptime) field.strptime() doesn't raise a UnicodeEncodeError (#16123) ... ok test_form_field (forms_tests.field_tests.test_datefield.DateFieldTest.test_form_field) ... ok test_form_label_association (forms_tests.field_tests.test_datefield.DateFieldTest.test_form_label_association) ... ok test_l10n_date_changed (forms_tests.field_tests.test_datefield.DateFieldTest.test_l10n_date_changed) DateField.has_changed() with SelectDateWidget works with a localized ... ok test_l10n_invalid_date_in (forms_tests.field_tests.test_datefield.DateFieldTest.test_l10n_invalid_date_in) ... ok test_decimalfield_1 (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_1) ... ok test_decimalfield_2 (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_2) ... ok test_decimalfield_3 (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_3) ... ok test_decimalfield_4 (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_4) ... ok test_decimalfield_5 (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_5) ... ok test_decimalfield_6 (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_6) ... ok test_decimalfield_changed (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_changed) ... ok test_decimalfield_localized (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_localized) A localized DecimalField's widget renders to a text input without ... ok test_decimalfield_scientific (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_scientific) ... ok test_decimalfield_support_decimal_separator (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_support_decimal_separator) ... ok test_decimalfield_support_thousands_separator (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_support_thousands_separator) ... ok test_decimalfield_widget_attrs (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_decimalfield_widget_attrs) ... ok test_enter_a_number_error (forms_tests.field_tests.test_decimalfield.DecimalFieldTest.test_enter_a_number_error) ... ok test_durationfield_clean (forms_tests.field_tests.test_durationfield.DurationFieldTest.test_durationfield_clean) ... ok test_durationfield_clean_not_required (forms_tests.field_tests.test_durationfield.DurationFieldTest.test_durationfield_clean_not_required) ... ok test_durationfield_integer_value (forms_tests.field_tests.test_durationfield.DurationFieldTest.test_durationfield_integer_value) ... ok test_durationfield_prepare_value (forms_tests.field_tests.test_durationfield.DurationFieldTest.test_durationfield_prepare_value) ... ok test_durationfield_render (forms_tests.field_tests.test_durationfield.DurationFieldTest.test_durationfield_render) ... ok test_overflow (forms_tests.field_tests.test_durationfield.DurationFieldTest.test_overflow) ... ok test_overflow_translation (forms_tests.field_tests.test_durationfield.DurationFieldTest.test_overflow_translation) ... ok test_email_regexp_for_performance (forms_tests.field_tests.test_emailfield.EmailFieldTest.test_email_regexp_for_performance) ... ok test_emailfield_1 (forms_tests.field_tests.test_emailfield.EmailFieldTest.test_emailfield_1) ... ok test_emailfield_min_max_length (forms_tests.field_tests.test_emailfield.EmailFieldTest.test_emailfield_min_max_length) ... ok test_emailfield_not_required (forms_tests.field_tests.test_emailfield.EmailFieldTest.test_emailfield_not_required) ... ok test_emailfield_strip_on_none_value (forms_tests.field_tests.test_emailfield.EmailFieldTest.test_emailfield_strip_on_none_value) ... ok test_emailfield_unable_to_set_strip_kwarg (forms_tests.field_tests.test_emailfield.EmailFieldTest.test_emailfield_unable_to_set_strip_kwarg) ... ok test_disabled_has_changed (forms_tests.field_tests.test_filefield.FileFieldTest.test_disabled_has_changed) ... ok test_file_picklable (forms_tests.field_tests.test_filefield.FileFieldTest.test_file_picklable) ... ok test_filefield_1 (forms_tests.field_tests.test_filefield.FileFieldTest.test_filefield_1) ... ok test_filefield_2 (forms_tests.field_tests.test_filefield.FileFieldTest.test_filefield_2) ... ok test_filefield_3 (forms_tests.field_tests.test_filefield.FileFieldTest.test_filefield_3) ... ok test_filefield_changed (forms_tests.field_tests.test_filefield.FileFieldTest.test_filefield_changed) The value of data will more than likely come from request.FILES. The ... ok test_allow_folders (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_allow_folders) ... ok test_clean (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_clean) ... ok test_fix_os_paths (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_fix_os_paths) ... ok test_match (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_match) ... ok test_no_options (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_no_options) ... ok test_nonexistent_path (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_nonexistent_path) ... ok test_recursive (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_recursive) ... ok test_recursive_folders_without_files (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_recursive_folders_without_files) ... ok test_recursive_no_folders_or_files (forms_tests.field_tests.test_filepathfield.FilePathFieldTest.test_recursive_no_folders_or_files) ... ok test_file_multiple (forms_tests.field_tests.test_filefield.MultipleFileFieldTest.test_file_multiple) ... ok test_file_multiple_empty (forms_tests.field_tests.test_filefield.MultipleFileFieldTest.test_file_multiple_empty) ... ok test_file_multiple_validation (forms_tests.field_tests.test_filefield.MultipleFileFieldTest.test_file_multiple_validation) ... ok test_decimalfield_support_decimal_separator (forms_tests.field_tests.test_floatfield.FloatFieldTest.test_decimalfield_support_decimal_separator) ... ok test_decimalfield_support_thousands_separator (forms_tests.field_tests.test_floatfield.FloatFieldTest.test_decimalfield_support_thousands_separator) ... ok test_floatfield_1 (forms_tests.field_tests.test_floatfield.FloatFieldTest.test_floatfield_1) ... ok test_floatfield_2 (forms_tests.field_tests.test_floatfield.FloatFieldTest.test_floatfield_2) ... ok test_floatfield_3 (forms_tests.field_tests.test_floatfield.FloatFieldTest.test_floatfield_3) ... ok test_floatfield_changed (forms_tests.field_tests.test_floatfield.FloatFieldTest.test_floatfield_changed) ... ok test_floatfield_localized (forms_tests.field_tests.test_floatfield.FloatFieldTest.test_floatfield_localized) A localized FloatField's widget renders to a text input without any ... ok test_floatfield_widget_attrs (forms_tests.field_tests.test_floatfield.FloatFieldTest.test_floatfield_widget_attrs) ... ok test_generic_ipaddress_as_generic (forms_tests.field_tests.test_genericipaddressfield.GenericIPAddressFieldTest.test_generic_ipaddress_as_generic) ... ok test_generic_ipaddress_as_generic_not_required (forms_tests.field_tests.test_genericipaddressfield.GenericIPAddressFieldTest.test_generic_ipaddress_as_generic_not_required) ... ok test_generic_ipaddress_as_ipv4_only (forms_tests.field_tests.test_genericipaddressfield.GenericIPAddressFieldTest.test_generic_ipaddress_as_ipv4_only) ... ok test_generic_ipaddress_as_ipv6_only (forms_tests.field_tests.test_genericipaddressfield.GenericIPAddressFieldTest.test_generic_ipaddress_as_ipv6_only) ... ok test_generic_ipaddress_invalid_arguments (forms_tests.field_tests.test_genericipaddressfield.GenericIPAddressFieldTest.test_generic_ipaddress_invalid_arguments) ... ok test_generic_ipaddress_normalization (forms_tests.field_tests.test_genericipaddressfield.GenericIPAddressFieldTest.test_generic_ipaddress_normalization) ... ok test_integerfield_1 (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_1) ... ok test_integerfield_2 (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_2) ... ok test_integerfield_3 (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_3) ... ok test_integerfield_4 (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_4) ... ok test_integerfield_5 (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_5) ... ok test_integerfield_big_num (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_big_num) ... ok test_integerfield_float (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_float) ... ok test_integerfield_localized (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_localized) A localized IntegerField's widget renders to a text input without any ... ok test_integerfield_subclass (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_subclass) Class-defined widget is not overwritten by __init__() (#22245). ... ok test_integerfield_unicode_number (forms_tests.field_tests.test_integerfield.IntegerFieldTest.test_integerfield_unicode_number) ... ok test_corrupted_image (forms_tests.field_tests.test_imagefield.ImageFieldTest.test_corrupted_image) ... ok test_file_extension_validation (forms_tests.field_tests.test_imagefield.ImageFieldTest.test_file_extension_validation) ... ok test_imagefield_annotate_with_bitmap_image_after_clean (forms_tests.field_tests.test_imagefield.ImageFieldTest.test_imagefield_annotate_with_bitmap_image_after_clean) This also tests the situation when Pillow doesn't detect the MIME type ... ok test_imagefield_annotate_with_image_after_clean (forms_tests.field_tests.test_imagefield.ImageFieldTest.test_imagefield_annotate_with_image_after_clean) ... ok test_widget_attrs_accept_false (forms_tests.field_tests.test_imagefield.ImageFieldTest.test_widget_attrs_accept_false) ... ok test_widget_attrs_accept_specified (forms_tests.field_tests.test_imagefield.ImageFieldTest.test_widget_attrs_accept_specified) ... ok test_widget_attrs_default_accept (forms_tests.field_tests.test_imagefield.ImageFieldTest.test_widget_attrs_default_accept) ... ok test_converted_value (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_converted_value) ... ok test_custom_encoder_decoder (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_custom_encoder_decoder) ... ok test_custom_widget_attribute (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_custom_widget_attribute) The widget can be overridden with an attribute. ... ok test_custom_widget_kwarg (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_custom_widget_kwarg) ... ok test_formfield_disabled (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_formfield_disabled) ... ok test_has_changed (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_has_changed) ... ok test_invalid (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_invalid) ... ok test_prepare_value (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_prepare_value) ... ok test_redisplay_wrong_input (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_redisplay_wrong_input) Displaying a bound form (typically due to invalid input). The form ... ok test_valid (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_valid) ... ok test_valid_empty (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_valid_empty) ... ok test_widget (forms_tests.field_tests.test_jsonfield.JSONFieldTest.test_widget) ... ok test_disabled_has_changed (forms_tests.field_tests.test_multiplechoicefield.MultipleChoiceFieldTest.test_disabled_has_changed) ... ok test_multiplechoicefield_1 (forms_tests.field_tests.test_multiplechoicefield.MultipleChoiceFieldTest.test_multiplechoicefield_1) ... ok test_multiplechoicefield_2 (forms_tests.field_tests.test_multiplechoicefield.MultipleChoiceFieldTest.test_multiplechoicefield_2) ... ok test_multiplechoicefield_3 (forms_tests.field_tests.test_multiplechoicefield.MultipleChoiceFieldTest.test_multiplechoicefield_3) ... ok test_multiplechoicefield_changed (forms_tests.field_tests.test_multiplechoicefield.MultipleChoiceFieldTest.test_multiplechoicefield_changed) ... ok test_bad_choice (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_bad_choice) ... ok test_clean (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_clean) ... ok test_clean_disabled_multivalue (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_clean_disabled_multivalue) ... ok test_disabled_has_changed (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_disabled_has_changed) ... ok test_form_as_table (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_form_as_table) ... ok test_form_as_table_data (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_form_as_table_data) ... ok test_form_cleaned_data (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_form_cleaned_data) ... ok test_has_changed_first_widget (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_has_changed_first_widget) Test when the first widget's data has changed. ... ok test_has_changed_last_widget (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_has_changed_last_widget) Test when the last widget's data has changed. This ensures that it is ... ok test_has_changed_no_initial (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_has_changed_no_initial) ... ok test_has_changed_same (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_has_changed_same) ... ok test_no_value (forms_tests.field_tests.test_multivaluefield.MultiValueFieldTest.test_no_value) If insufficient data is provided, None is substituted. ... ok test_nullbooleanfield_2 (forms_tests.field_tests.test_nullbooleanfield.NullBooleanFieldTest.test_nullbooleanfield_2) ... ok test_nullbooleanfield_3 (forms_tests.field_tests.test_nullbooleanfield.NullBooleanFieldTest.test_nullbooleanfield_3) ... ok test_nullbooleanfield_4 (forms_tests.field_tests.test_nullbooleanfield.NullBooleanFieldTest.test_nullbooleanfield_4) ... ok test_nullbooleanfield_changed (forms_tests.field_tests.test_nullbooleanfield.NullBooleanFieldTest.test_nullbooleanfield_changed) ... ok test_nullbooleanfield_clean (forms_tests.field_tests.test_nullbooleanfield.NullBooleanFieldTest.test_nullbooleanfield_clean) ... ok test_change_regex_after_init (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_change_regex_after_init) ... ok test_empty_value (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_empty_value) ... ok test_get_regex (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_get_regex) ... ok test_regexfield_1 (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_regexfield_1) ... ok test_regexfield_2 (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_regexfield_2) ... ok test_regexfield_3 (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_regexfield_3) ... ok test_regexfield_4 (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_regexfield_4) ... ok test_regexfield_strip (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_regexfield_strip) ... ok test_regexfield_unicode_characters (forms_tests.field_tests.test_regexfield.RegexFieldTest.test_regexfield_unicode_characters) ... ok test_empty_value (forms_tests.field_tests.test_slugfield.SlugFieldTest.test_empty_value) ... ok test_slugfield_normalization (forms_tests.field_tests.test_slugfield.SlugFieldTest.test_slugfield_normalization) ... ok test_slugfield_unicode_normalization (forms_tests.field_tests.test_slugfield.SlugFieldTest.test_slugfield_unicode_normalization) ... ok test_splitdatetimefield_1 (forms_tests.field_tests.test_splitdatetimefield.SplitDateTimeFieldTest.test_splitdatetimefield_1) ... ok test_splitdatetimefield_2 (forms_tests.field_tests.test_splitdatetimefield.SplitDateTimeFieldTest.test_splitdatetimefield_2) ... ok test_splitdatetimefield_changed (forms_tests.field_tests.test_splitdatetimefield.SplitDateTimeFieldTest.test_splitdatetimefield_changed) ... ok test_timefield_1 (forms_tests.field_tests.test_timefield.TimeFieldTest.test_timefield_1) ... ok test_timefield_2 (forms_tests.field_tests.test_timefield.TimeFieldTest.test_timefield_2) ... ok test_timefield_3 (forms_tests.field_tests.test_timefield.TimeFieldTest.test_timefield_3) ... ok test_timefield_changed (forms_tests.field_tests.test_timefield.TimeFieldTest.test_timefield_changed) ... ok test_typedchoicefield_1 (forms_tests.field_tests.test_typedchoicefield.TypedChoiceFieldTest.test_typedchoicefield_1) ... ok test_typedchoicefield_2 (forms_tests.field_tests.test_typedchoicefield.TypedChoiceFieldTest.test_typedchoicefield_2) ... ok test_typedchoicefield_3 (forms_tests.field_tests.test_typedchoicefield.TypedChoiceFieldTest.test_typedchoicefield_3) ... ok test_typedchoicefield_4 (forms_tests.field_tests.test_typedchoicefield.TypedChoiceFieldTest.test_typedchoicefield_4) ... ok test_typedchoicefield_5 (forms_tests.field_tests.test_typedchoicefield.TypedChoiceFieldTest.test_typedchoicefield_5) ... ok test_typedchoicefield_6 (forms_tests.field_tests.test_typedchoicefield.TypedChoiceFieldTest.test_typedchoicefield_6) ... ok test_typedchoicefield_has_changed (forms_tests.field_tests.test_typedchoicefield.TypedChoiceFieldTest.test_typedchoicefield_has_changed) ... ok test_typedchoicefield_special_coerce (forms_tests.field_tests.test_typedchoicefield.TypedChoiceFieldTest.test_typedchoicefield_special_coerce) A coerce function which results in a value not present in choices ... ok test_typedmultiplechoicefield_1 (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_1) ... ok test_typedmultiplechoicefield_2 (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_2) ... ok test_typedmultiplechoicefield_3 (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_3) ... ok test_typedmultiplechoicefield_4 (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_4) ... ok test_typedmultiplechoicefield_5 (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_5) ... ok test_typedmultiplechoicefield_6 (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_6) ... ok test_typedmultiplechoicefield_7 (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_7) ... ok test_typedmultiplechoicefield_has_changed (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_has_changed) ... ok test_typedmultiplechoicefield_special_coerce (forms_tests.field_tests.test_typedmultiplechoicefield.TypedMultipleChoiceFieldTest.test_typedmultiplechoicefield_special_coerce) A coerce function which results in a value not present in choices ... ok test_clean_value_with_dashes (forms_tests.field_tests.test_uuidfield.UUIDFieldTest.test_clean_value_with_dashes) ... ok test_uuidfield_1 (forms_tests.field_tests.test_uuidfield.UUIDFieldTest.test_uuidfield_1) ... ok test_uuidfield_2 (forms_tests.field_tests.test_uuidfield.UUIDFieldTest.test_uuidfield_2) ... ok test_uuidfield_3 (forms_tests.field_tests.test_uuidfield.UUIDFieldTest.test_uuidfield_3) ... ok test_uuidfield_4 (forms_tests.field_tests.test_uuidfield.UUIDFieldTest.test_uuidfield_4) ... ok test_url_regex_ticket11198 (forms_tests.field_tests.test_urlfield.URLFieldTest.test_url_regex_ticket11198) ... ok test_urlfield_1 (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_1) ... ok test_urlfield_10 (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_10) URLField correctly validates IPv6 (#18779). ... ok test_urlfield_2 (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_2) ... ok test_urlfield_5 (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_5) ... ok test_urlfield_6 (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_6) ... ok test_urlfield_7 (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_7) ... ok test_urlfield_9 (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_9) ... ok test_urlfield_normalization (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_normalization) ... ok test_urlfield_not_string (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_not_string) ... ok test_urlfield_strip_on_none_value (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_strip_on_none_value) ... ok test_urlfield_unable_to_set_strip_kwarg (forms_tests.field_tests.test_urlfield.URLFieldTest.test_urlfield_unable_to_set_strip_kwarg) ... ok test_booleanfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_booleanfield) ... ok test_charfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_charfield) ... ok test_choicefield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_choicefield) ... ok test_datefield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_datefield) ... ok test_datetimefield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_datetimefield) ... ok test_decimalfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_decimalfield) ... ok test_emailfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_emailfield) ... ok test_error_messages_escaping (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_error_messages_escaping) ... ok test_filefield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_filefield) ... ok test_floatfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_floatfield) ... ok test_generic_ipaddressfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_generic_ipaddressfield) ... ok test_integerfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_integerfield) ... ok test_multiplechoicefield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_multiplechoicefield) ... ok test_regexfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_regexfield) ... ok test_splitdatetimefield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_splitdatetimefield) ... ok test_subclassing_errorlist (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_subclassing_errorlist) ... ok test_timefield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_timefield) ... ok test_urlfield (forms_tests.tests.test_error_messages.FormsErrorMessagesTestCase.test_urlfield) ... ok test_attribute_class (forms_tests.tests.test_forms.RendererTests.test_attribute_class) ... ok test_attribute_instance (forms_tests.tests.test_forms.RendererTests.test_attribute_instance) ... ok test_attribute_override (forms_tests.tests.test_forms.RendererTests.test_attribute_override) ... ok test_default (forms_tests.tests.test_forms.RendererTests.test_default) ... ok test_kwarg_class (forms_tests.tests.test_forms.RendererTests.test_kwarg_class) ... ok test_kwarg_instance (forms_tests.tests.test_forms.RendererTests.test_kwarg_instance) ... ok test_invalid (forms_tests.tests.test_formsets.AllValidTests.test_invalid) all_valid() validates all forms, even when some are invalid. ... ok test_valid (forms_tests.tests.test_formsets.AllValidTests.test_valid) ... ok test_accessing_clean (forms_tests.tests.test_forms.FormsTestCase.test_accessing_clean) ... ok test_auto_id (forms_tests.tests.test_forms.FormsTestCase.test_auto_id) ... ok test_auto_id_false (forms_tests.tests.test_forms.FormsTestCase.test_auto_id_false) ... ok test_auto_id_on_form_and_field (forms_tests.tests.test_forms.FormsTestCase.test_auto_id_on_form_and_field) ... ok test_auto_id_true (forms_tests.tests.test_forms.FormsTestCase.test_auto_id_true) ... ok test_baseform_repr (forms_tests.tests.test_forms.FormsTestCase.test_baseform_repr) BaseForm.__repr__() should contain some basic information about the ... ok test_baseform_repr_dont_trigger_validation (forms_tests.tests.test_forms.FormsTestCase.test_baseform_repr_dont_trigger_validation) BaseForm.__repr__() shouldn't trigger the form validation. ... ok test_basic_processing_in_view (forms_tests.tests.test_forms.FormsTestCase.test_basic_processing_in_view) ... ok test_boundfield_bool (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_bool) BoundField without any choices (subwidgets) evaluates to True. ... ok test_boundfield_css_classes (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_css_classes) ... ok test_boundfield_empty_label (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_empty_label) ... ok test_boundfield_id_for_label (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_id_for_label) ... ok test_boundfield_id_for_label_override_by_attrs (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_id_for_label_override_by_attrs) If an id is provided in `Widget.attrs`, it overrides the generated ID, ... ok test_boundfield_initial_called_once (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_initial_called_once) Multiple calls to BoundField().value() in an unbound form should return ... ok test_boundfield_invalid_index (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_invalid_index) ... ok test_boundfield_label_tag (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_label_tag) ... ok test_boundfield_label_tag_custom_widget_id_for_label (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_label_tag_custom_widget_id_for_label) ... ok test_boundfield_label_tag_no_id (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_label_tag_no_id) If a widget has no id, label_tag just returns the text with no ... ok test_boundfield_slice (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_slice) ... ok test_boundfield_value_disabled_callable_initial (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_value_disabled_callable_initial) ... ok test_boundfield_values (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_values) ... ok test_boundfield_widget_type (forms_tests.tests.test_forms.FormsTestCase.test_boundfield_widget_type) ... ok test_callable_initial_data (forms_tests.tests.test_forms.FormsTestCase.test_callable_initial_data) ... ok test_changed_data (forms_tests.tests.test_forms.FormsTestCase.test_changed_data) ... ok test_changing_cleaned_data_in_clean (forms_tests.tests.test_forms.FormsTestCase.test_changing_cleaned_data_in_clean) ... ok test_changing_cleaned_data_nothing_returned (forms_tests.tests.test_forms.FormsTestCase.test_changing_cleaned_data_nothing_returned) ... ok test_checkbox_auto_id (forms_tests.tests.test_forms.FormsTestCase.test_checkbox_auto_id) ... ok test_class_prefix (forms_tests.tests.test_forms.FormsTestCase.test_class_prefix) ... ok test_cleaned_data_only_fields (forms_tests.tests.test_forms.FormsTestCase.test_cleaned_data_only_fields) ... ok test_custom_boundfield (forms_tests.tests.test_forms.FormsTestCase.test_custom_boundfield) ... ok test_custom_empty_values (forms_tests.tests.test_forms.FormsTestCase.test_custom_empty_values) Form fields can customize what is considered as an empty value ... ok test_datetime_changed_data_callable_with_microseconds (forms_tests.tests.test_forms.FormsTestCase.test_datetime_changed_data_callable_with_microseconds) ... ok test_datetime_clean_initial_callable_disabled (forms_tests.tests.test_forms.FormsTestCase.test_datetime_clean_initial_callable_disabled) ... ok test_dynamic_construction (forms_tests.tests.test_forms.FormsTestCase.test_dynamic_construction) ... ok test_dynamic_initial_data (forms_tests.tests.test_forms.FormsTestCase.test_dynamic_initial_data) ... ok test_empty_data_files_multi_value_dict (forms_tests.tests.test_forms.FormsTestCase.test_empty_data_files_multi_value_dict) ... ok test_empty_dict (forms_tests.tests.test_forms.FormsTestCase.test_empty_dict) ... ok test_empty_permitted (forms_tests.tests.test_forms.FormsTestCase.test_empty_permitted) ... ok test_empty_permitted_and_use_required_attribute (forms_tests.tests.test_forms.FormsTestCase.test_empty_permitted_and_use_required_attribute) ... ok test_empty_querydict_args (forms_tests.tests.test_forms.FormsTestCase.test_empty_querydict_args) ... ok test_error_dict (forms_tests.tests.test_forms.FormsTestCase.test_error_dict) ... ok test_error_dict_as_json_escape_html (forms_tests.tests.test_forms.FormsTestCase.test_error_dict_as_json_escape_html) #21962 - adding html escape flag to ErrorDict ... ok test_error_escaping (forms_tests.tests.test_forms.FormsTestCase.test_error_escaping) ... ok test_error_html_required_html_classes (forms_tests.tests.test_forms.FormsTestCase.test_error_html_required_html_classes) ... ok test_error_list (forms_tests.tests.test_forms.FormsTestCase.test_error_list) ... ok test_error_list_class_has_one_class_specified (forms_tests.tests.test_forms.FormsTestCase.test_error_list_class_has_one_class_specified) ... ok test_error_list_class_not_specified (forms_tests.tests.test_forms.FormsTestCase.test_error_list_class_not_specified) ... ok test_error_list_with_hidden_field_errors_has_correct_class (forms_tests.tests.test_forms.FormsTestCase.test_error_list_with_hidden_field_errors_has_correct_class) ... ok test_error_list_with_non_field_errors_has_correct_class (forms_tests.tests.test_forms.FormsTestCase.test_error_list_with_non_field_errors_has_correct_class) ... ok test_errorlist_override (forms_tests.tests.test_forms.FormsTestCase.test_errorlist_override) ... ok test_escaping (forms_tests.tests.test_forms.FormsTestCase.test_escaping) ... ok test_explicit_field_order (forms_tests.tests.test_forms.FormsTestCase.test_explicit_field_order) ... ok test_extracting_hidden_and_visible (forms_tests.tests.test_forms.FormsTestCase.test_extracting_hidden_and_visible) ... ok test_field_deep_copy_error_messages (forms_tests.tests.test_forms.FormsTestCase.test_field_deep_copy_error_messages) ... ok test_field_name (forms_tests.tests.test_forms.FormsTestCase.test_field_name) #5749 - `field_name` may be used as a key in _html_output(). ... ok test_field_name_with_hidden_input (forms_tests.tests.test_forms.FormsTestCase.test_field_name_with_hidden_input) BaseForm._html_output() should merge all the hidden input fields and ... ok test_field_name_with_hidden_input_and_non_matching_row_ender (forms_tests.tests.test_forms.FormsTestCase.test_field_name_with_hidden_input_and_non_matching_row_ender) BaseForm._html_output() should merge all the hidden input fields and ... ok test_field_named_data (forms_tests.tests.test_forms.FormsTestCase.test_field_named_data) ... ok test_field_order (forms_tests.tests.test_forms.FormsTestCase.test_field_order) ... ok test_field_with_css_class (forms_tests.tests.test_forms.FormsTestCase.test_field_with_css_class) `css_classes` may be used as a key in _html_output() (class comes ... ok test_field_without_css_classes (forms_tests.tests.test_forms.FormsTestCase.test_field_without_css_classes) `css_classes` may be used as a key in _html_output() (empty classes). ... ok test_filefield_initial_callable (forms_tests.tests.test_forms.FormsTestCase.test_filefield_initial_callable) ... ok test_filefield_with_fileinput_required (forms_tests.tests.test_forms.FormsTestCase.test_filefield_with_fileinput_required) ... ok test_form (forms_tests.tests.test_forms.FormsTestCase.test_form) ... ok test_form_html_attributes (forms_tests.tests.test_forms.FormsTestCase.test_form_html_attributes) ... ok test_form_with_disabled_fields (forms_tests.tests.test_forms.FormsTestCase.test_form_with_disabled_fields) ... ok test_form_with_iterable_boundfield (forms_tests.tests.test_forms.FormsTestCase.test_form_with_iterable_boundfield) ... ok test_form_with_iterable_boundfield_id (forms_tests.tests.test_forms.FormsTestCase.test_form_with_iterable_boundfield_id) ... ok test_form_with_noniterable_boundfield (forms_tests.tests.test_forms.FormsTestCase.test_form_with_noniterable_boundfield) ... ok test_forms_with_choices (forms_tests.tests.test_forms.FormsTestCase.test_forms_with_choices) ... ok test_forms_with_file_fields (forms_tests.tests.test_forms.FormsTestCase.test_forms_with_file_fields) ... ok test_forms_with_multiple_choice (forms_tests.tests.test_forms.FormsTestCase.test_forms_with_multiple_choice) ... ok test_forms_with_null_boolean (forms_tests.tests.test_forms.FormsTestCase.test_forms_with_null_boolean) ... ok test_forms_with_prefixes (forms_tests.tests.test_forms.FormsTestCase.test_forms_with_prefixes) ... ok test_forms_with_radio (forms_tests.tests.test_forms.FormsTestCase.test_forms_with_radio) ... ok test_get_initial_for_field (forms_tests.tests.test_forms.FormsTestCase.test_get_initial_for_field) ... ok test_has_error (forms_tests.tests.test_forms.FormsTestCase.test_has_error) ... ok test_help_text (forms_tests.tests.test_forms.FormsTestCase.test_help_text) ... ok test_hidden_data (forms_tests.tests.test_forms.FormsTestCase.test_hidden_data) ... ok test_hidden_initial_gets_id (forms_tests.tests.test_forms.FormsTestCase.test_hidden_initial_gets_id) ... ok test_hidden_widget (forms_tests.tests.test_forms.FormsTestCase.test_hidden_widget) ... ok test_html_output_with_hidden_input_field_errors (forms_tests.tests.test_forms.FormsTestCase.test_html_output_with_hidden_input_field_errors) ... ok test_html_safe (forms_tests.tests.test_forms.FormsTestCase.test_html_safe) ... ok test_id_on_field (forms_tests.tests.test_forms.FormsTestCase.test_id_on_field) ... ok test_initial_data (forms_tests.tests.test_forms.FormsTestCase.test_initial_data) ... ok test_initial_datetime_values (forms_tests.tests.test_forms.FormsTestCase.test_initial_datetime_values) ... ok test_iterable_boundfield_select (forms_tests.tests.test_forms.FormsTestCase.test_iterable_boundfield_select) ... ok test_label_has_required_css_class (forms_tests.tests.test_forms.FormsTestCase.test_label_has_required_css_class) #17922 - required_css_class is added to the label_tag() of required fields. ... ok test_label_split_datetime_not_displayed (forms_tests.tests.test_forms.FormsTestCase.test_label_split_datetime_not_displayed) ... ok test_label_suffix (forms_tests.tests.test_forms.FormsTestCase.test_label_suffix) ... ok test_label_tag_override (forms_tests.tests.test_forms.FormsTestCase.test_label_tag_override) BoundField label_suffix (if provided) overrides Form label_suffix ... ok test_multipart_encoded_form (forms_tests.tests.test_forms.FormsTestCase.test_multipart_encoded_form) ... ok test_multiple_choice_checkbox (forms_tests.tests.test_forms.FormsTestCase.test_multiple_choice_checkbox) ... ok test_multiple_choice_list_data (forms_tests.tests.test_forms.FormsTestCase.test_multiple_choice_list_data) ... ok test_multiple_hidden (forms_tests.tests.test_forms.FormsTestCase.test_multiple_hidden) ... ok test_multivalue_deep_copy (forms_tests.tests.test_forms.FormsTestCase.test_multivalue_deep_copy) #19298 -- MultiValueField needs to override the default as it needs ... ok test_multivalue_field_validation (forms_tests.tests.test_forms.FormsTestCase.test_multivalue_field_validation) ... ok test_multivalue_initial_data (forms_tests.tests.test_forms.FormsTestCase.test_multivalue_initial_data) #23674 -- invalid initial data should not break form.changed_data() ... ok test_multivalue_optional_subfields (forms_tests.tests.test_forms.FormsTestCase.test_multivalue_optional_subfields) ... ok test_only_hidden_fields (forms_tests.tests.test_forms.FormsTestCase.test_only_hidden_fields) ... ok test_optional_data (forms_tests.tests.test_forms.FormsTestCase.test_optional_data) ... ok test_specifying_labels (forms_tests.tests.test_forms.FormsTestCase.test_specifying_labels) ... ok test_subclassing_forms (forms_tests.tests.test_forms.FormsTestCase.test_subclassing_forms) ... ok test_templates_with_forms (forms_tests.tests.test_forms.FormsTestCase.test_templates_with_forms) ... ok test_unbound_form (forms_tests.tests.test_forms.FormsTestCase.test_unbound_form) ... ok test_unicode_values (forms_tests.tests.test_forms.FormsTestCase.test_unicode_values) ... ok test_update_error_dict (forms_tests.tests.test_forms.FormsTestCase.test_update_error_dict) ... ok test_use_required_attribute_false (forms_tests.tests.test_forms.FormsTestCase.test_use_required_attribute_false) ... ok test_use_required_attribute_true (forms_tests.tests.test_forms.FormsTestCase.test_use_required_attribute_true) ... ok test_validating_multiple_fields (forms_tests.tests.test_forms.FormsTestCase.test_validating_multiple_fields) ... ok test_validators_independence (forms_tests.tests.test_forms.FormsTestCase.test_validators_independence) The list of form field validators can be modified without polluting ... ok test_various_boolean_values (forms_tests.tests.test_forms.FormsTestCase.test_various_boolean_values) ... ok test_widget_output (forms_tests.tests.test_forms.FormsTestCase.test_widget_output) ... ok test_as_p (forms_tests.tests.test_formsets.FormsetAsTagTests.test_as_p) ... ok test_as_table (forms_tests.tests.test_formsets.FormsetAsTagTests.test_as_table) ... ok test_as_ul (forms_tests.tests.test_formsets.FormsetAsTagTests.test_as_ul) ... ok test_empty_formset_is_multipart (forms_tests.tests.test_formsets.TestEmptyFormSet.test_empty_formset_is_multipart) is_multipart() works with an empty formset. ... ok test_empty_formset_is_valid (forms_tests.tests.test_formsets.TestEmptyFormSet.test_empty_formset_is_valid) An empty formset still calls clean() ... ok test_empty_formset_media (forms_tests.tests.test_formsets.TestEmptyFormSet.test_empty_formset_media) Media is available on empty formset. ... ok test_customize_management_form_error (forms_tests.tests.test_formsets.TestIsBoundBehavior.test_customize_management_form_error) ... ok test_empty_forms_are_unbound (forms_tests.tests.test_formsets.TestIsBoundBehavior.test_empty_forms_are_unbound) ... ok test_form_errors_are_caught_by_formset (forms_tests.tests.test_formsets.TestIsBoundBehavior.test_form_errors_are_caught_by_formset) ... ok test_management_form_invalid_data (forms_tests.tests.test_formsets.TestIsBoundBehavior.test_management_form_invalid_data) ... ok test_no_data_error (forms_tests.tests.test_formsets.TestIsBoundBehavior.test_no_data_error) ... ok test_with_management_data_attrs_work_fine (forms_tests.tests.test_formsets.TestIsBoundBehavior.test_with_management_data_attrs_work_fine) ... ok test_lazy_labels (forms_tests.tests.test_i18n.FormsI18nTests.test_lazy_labels) ... ok test_non_ascii_choices (forms_tests.tests.test_i18n.FormsI18nTests.test_non_ascii_choices) ... ok test_non_ascii_label (forms_tests.tests.test_i18n.FormsI18nTests.test_non_ascii_label) ... ok test_select_translated_text (forms_tests.tests.test_i18n.FormsI18nTests.test_select_translated_text) ... ok test_dateField (forms_tests.tests.test_input_formats.CustomDateInputFormatsTests.test_dateField) DateFields can parse dates in the default format ... ok test_dateField_with_inputformat (forms_tests.tests.test_input_formats.CustomDateInputFormatsTests.test_dateField_with_inputformat) DateFields with manually specified input formats can accept those formats ... ok test_localized_dateField (forms_tests.tests.test_input_formats.CustomDateInputFormatsTests.test_localized_dateField) Localized DateFields act as unlocalized widgets ... ok test_localized_dateField_with_inputformat (forms_tests.tests.test_input_formats.CustomDateInputFormatsTests.test_localized_dateField_with_inputformat) Localized DateFields with manually specified input formats can accept those formats ... ok test_dateTimeField (forms_tests.tests.test_input_formats.CustomDateTimeInputFormatsTests.test_dateTimeField) DateTimeFields can parse dates in the default format ... ok test_dateTimeField_with_inputformat (forms_tests.tests.test_input_formats.CustomDateTimeInputFormatsTests.test_dateTimeField_with_inputformat) DateTimeFields with manually specified input formats can accept those formats ... ok test_localized_dateTimeField (forms_tests.tests.test_input_formats.CustomDateTimeInputFormatsTests.test_localized_dateTimeField) Localized DateTimeFields act as unlocalized widgets ... ok test_localized_dateTimeField_with_inputformat (forms_tests.tests.test_input_formats.CustomDateTimeInputFormatsTests.test_localized_dateTimeField_with_inputformat) Localized DateTimeFields with manually specified input formats can accept those formats ... ok test_localized_timeField (forms_tests.tests.test_input_formats.CustomTimeInputFormatsTests.test_localized_timeField) Localized TimeFields act as unlocalized widgets ... ok test_localized_timeField_with_inputformat (forms_tests.tests.test_input_formats.CustomTimeInputFormatsTests.test_localized_timeField_with_inputformat) Localized TimeFields with manually specified input formats can accept those formats ... ok test_timeField (forms_tests.tests.test_input_formats.CustomTimeInputFormatsTests.test_timeField) TimeFields can parse dates in the default format ... ok test_timeField_with_inputformat (forms_tests.tests.test_input_formats.CustomTimeInputFormatsTests.test_timeField_with_inputformat) TimeFields with manually specified input formats can accept those formats ... ok test_dateField (forms_tests.tests.test_input_formats.LocalizedDateTests.test_dateField) DateFields can parse dates in the default format ... ok test_dateField_with_inputformat (forms_tests.tests.test_input_formats.LocalizedDateTests.test_dateField_with_inputformat) DateFields with manually specified input formats can accept those formats ... ok test_localized_dateField (forms_tests.tests.test_input_formats.LocalizedDateTests.test_localized_dateField) Localized DateFields act as unlocalized widgets ... ok test_localized_dateField_with_inputformat (forms_tests.tests.test_input_formats.LocalizedDateTests.test_localized_dateField_with_inputformat) Localized DateFields with manually specified input formats can accept those formats ... ok test_dateTimeField (forms_tests.tests.test_input_formats.LocalizedDateTimeTests.test_dateTimeField) DateTimeFields can parse dates in the default format ... ok test_dateTimeField_with_inputformat (forms_tests.tests.test_input_formats.LocalizedDateTimeTests.test_dateTimeField_with_inputformat) DateTimeFields with manually specified input formats can accept those formats ... ok test_localized_dateTimeField (forms_tests.tests.test_input_formats.LocalizedDateTimeTests.test_localized_dateTimeField) Localized DateTimeFields act as unlocalized widgets ... ok test_localized_dateTimeField_with_inputformat (forms_tests.tests.test_input_formats.LocalizedDateTimeTests.test_localized_dateTimeField_with_inputformat) Localized DateTimeFields with manually specified input formats can accept those formats ... ok test_localized_timeField (forms_tests.tests.test_input_formats.LocalizedTimeTests.test_localized_timeField) Localized TimeFields act as unlocalized widgets ... ok test_localized_timeField_with_inputformat (forms_tests.tests.test_input_formats.LocalizedTimeTests.test_localized_timeField_with_inputformat) Localized TimeFields with manually specified input formats can accept those formats ... ok test_timeField (forms_tests.tests.test_input_formats.LocalizedTimeTests.test_timeField) TimeFields can parse dates in the default format ... ok test_timeField_with_inputformat (forms_tests.tests.test_input_formats.LocalizedTimeTests.test_timeField_with_inputformat) TimeFields with manually specified input formats can accept those formats ... ok test_dateField (forms_tests.tests.test_input_formats.SimpleDateFormatTests.test_dateField) DateFields can parse dates in the default format ... ok test_dateField_with_inputformat (forms_tests.tests.test_input_formats.SimpleDateFormatTests.test_dateField_with_inputformat) DateFields with manually specified input formats can accept those formats ... ok test_localized_dateField (forms_tests.tests.test_input_formats.SimpleDateFormatTests.test_localized_dateField) Localized DateFields in a non-localized environment act as unlocalized widgets ... ok test_localized_dateField_with_inputformat (forms_tests.tests.test_input_formats.SimpleDateFormatTests.test_localized_dateField_with_inputformat) Localized DateFields with manually specified input formats can accept those formats ... ok test_dateTimeField (forms_tests.tests.test_input_formats.SimpleDateTimeFormatTests.test_dateTimeField) DateTimeFields can parse dates in the default format ... ok test_dateTimeField_with_inputformat (forms_tests.tests.test_input_formats.SimpleDateTimeFormatTests.test_dateTimeField_with_inputformat) DateTimeFields with manually specified input formats can accept those formats ... ok test_localized_dateTimeField (forms_tests.tests.test_input_formats.SimpleDateTimeFormatTests.test_localized_dateTimeField) Localized DateTimeFields in a non-localized environment act as unlocalized widgets ... ok test_localized_dateTimeField_with_inputformat (forms_tests.tests.test_input_formats.SimpleDateTimeFormatTests.test_localized_dateTimeField_with_inputformat) Localized DateTimeFields with manually specified input formats can accept those formats ... ok test_localized_timeField (forms_tests.tests.test_input_formats.SimpleTimeFormatTests.test_localized_timeField) Localized TimeFields in a non-localized environment act as unlocalized widgets ... ok test_localized_timeField_with_inputformat (forms_tests.tests.test_input_formats.SimpleTimeFormatTests.test_localized_timeField_with_inputformat) Localized TimeFields with manually specified input formats can accept those formats ... ok test_timeField (forms_tests.tests.test_input_formats.SimpleTimeFormatTests.test_timeField) TimeFields can parse dates in the default format ... ok test_timeField_with_inputformat (forms_tests.tests.test_input_formats.SimpleTimeFormatTests.test_timeField_with_inputformat) TimeFields with manually specified input formats can accept those formats ... ok test_add_css_deduplication (forms_tests.tests.test_media.FormsMediaTestCase.test_add_css_deduplication) ... ok test_add_empty (forms_tests.tests.test_media.FormsMediaTestCase.test_add_empty) ... ok test_add_js_deduplication (forms_tests.tests.test_media.FormsMediaTestCase.test_add_js_deduplication) ... ok test_combine_media (forms_tests.tests.test_media.FormsMediaTestCase.test_combine_media) ... ok test_construction (forms_tests.tests.test_media.FormsMediaTestCase.test_construction) ... ok test_form_media (forms_tests.tests.test_media.FormsMediaTestCase.test_form_media) ... ok test_html_safe (forms_tests.tests.test_media.FormsMediaTestCase.test_html_safe) ... ok test_media_deduplication (forms_tests.tests.test_media.FormsMediaTestCase.test_media_deduplication) ... ok test_media_dsl (forms_tests.tests.test_media.FormsMediaTestCase.test_media_dsl) ... ok test_media_inheritance (forms_tests.tests.test_media.FormsMediaTestCase.test_media_inheritance) ... ok test_media_inheritance_extends (forms_tests.tests.test_media.FormsMediaTestCase.test_media_inheritance_extends) ... ok test_media_inheritance_from_property (forms_tests.tests.test_media.FormsMediaTestCase.test_media_inheritance_from_property) ... ok test_media_inheritance_single_type (forms_tests.tests.test_media.FormsMediaTestCase.test_media_inheritance_single_type) ... ok test_media_property (forms_tests.tests.test_media.FormsMediaTestCase.test_media_property) ... ok test_media_property_parent_references (forms_tests.tests.test_media.FormsMediaTestCase.test_media_property_parent_references) ... ok test_merge (forms_tests.tests.test_media.FormsMediaTestCase.test_merge) ... ok test_merge_css_three_way (forms_tests.tests.test_media.FormsMediaTestCase.test_merge_css_three_way) ... ok test_merge_js_three_way (forms_tests.tests.test_media.FormsMediaTestCase.test_merge_js_three_way) The relative order of scripts is preserved in a three-way merge. ... ok test_merge_js_three_way2 (forms_tests.tests.test_media.FormsMediaTestCase.test_merge_js_three_way2) ... ok test_merge_warning (forms_tests.tests.test_media.FormsMediaTestCase.test_merge_warning) ... ok test_multi_media (forms_tests.tests.test_media.FormsMediaTestCase.test_multi_media) ... ok test_multi_widget (forms_tests.tests.test_media.FormsMediaTestCase.test_multi_widget) ... ok test_get_renderer (forms_tests.tests.test_renderers.BaseTemplateRendererTests.test_get_renderer) ... ok test_installed_apps_template_found (forms_tests.tests.test_renderers.DjangoTemplatesTests.test_installed_apps_template_found) Can find a custom template in INSTALLED_APPS. ... ok test_installed_apps_template_found (forms_tests.tests.test_renderers.Jinja2Tests.test_installed_apps_template_found) Can find a custom template in INSTALLED_APPS. ... ok test_installed_apps_template_found (forms_tests.tests.test_renderers.TemplatesSettingTests.test_installed_apps_template_found) Can find a custom template in INSTALLED_APPS. ... ok test_error_dict_copy (forms_tests.tests.test_utils.FormsUtilsTestCase.test_error_dict_copy) ... ok test_error_dict_html_safe (forms_tests.tests.test_utils.FormsUtilsTestCase.test_error_dict_html_safe) ... ok test_error_list_html_safe (forms_tests.tests.test_utils.FormsUtilsTestCase.test_error_list_html_safe) ... ok test_flatatt (forms_tests.tests.test_utils.FormsUtilsTestCase.test_flatatt) ... ok test_flatatt_no_side_effects (forms_tests.tests.test_utils.FormsUtilsTestCase.test_flatatt_no_side_effects) flatatt() does not modify the dict passed in. ... ok test_validation_error (forms_tests.tests.test_utils.FormsUtilsTestCase.test_validation_error) ... ok test_textarea_trailing_newlines (forms_tests.tests.test_widgets.LiveWidgetTests.test_textarea_trailing_newlines) A roundtrip on a ModelForm doesn't alter the TextField value ... skipped 'No browsers specified.' test_invalid_loading_order (forms_tests.tests.tests.RelatedModelFormTests.test_invalid_loading_order) Test for issue 10405 ... ok test_valid_loading_order (forms_tests.tests.tests.RelatedModelFormTests.test_valid_loading_order) Test for issue 10405 ... ok test_modules (template_tests.syntax_tests.test_debug.DebugTests.test_modules) ... ok test_non_ascii (template_tests.syntax_tests.test_debug.DebugTests.test_non_ascii) ... ok test_non_debug (template_tests.syntax_tests.test_debug.DebugTests.test_non_debug) ... ok test_plain (template_tests.syntax_tests.test_debug.DebugTests.test_plain) ... ok test_script (template_tests.syntax_tests.test_debug.DebugTests.test_script) ... ok test_get_context_does_not_mutate_attrs (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_get_context_does_not_mutate_attrs) ... ok test_render_check_exception (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_render_check_exception) Calling check_test() shouldn't swallow exceptions (#17888). ... ok test_render_check_test (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_render_check_test) You can pass 'check_test' to the constructor. This is a callable that ... ok test_render_empty (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_render_empty) ... ok test_render_false (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_render_false) ... ok test_render_int (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_render_int) Integers are handled by value, not as booleans (#17114). ... ok test_render_none (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_render_none) ... ok test_render_true (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_render_true) ... ok test_render_value (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_render_value) Using any value that's not in ('', None, False, True) will check the ... ok test_value_from_datadict (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_value_from_datadict) The CheckboxInput widget will return False if the key is not found in ... ok test_value_from_datadict_string_int (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_value_from_datadict_string_int) ... ok test_value_omitted_from_data (forms_tests.widget_tests.test_checkboxinput.CheckboxInputTest.test_value_omitted_from_data) ... ok test_clear_input_checked_returns_false (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_clear_input_checked_returns_false) ClearableFileInput.value_from_datadict returns False if the clear ... ok test_clear_input_checked_returns_false_only_if_not_required (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_clear_input_checked_returns_false_only_if_not_required) ClearableFileInput.value_from_datadict never returns False if the field ... ok test_clear_input_renders (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_clear_input_renders) A ClearableFileInput with is_required False and rendered with an ... ok test_clear_input_renders_only_if_initial (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_clear_input_renders_only_if_initial) A ClearableFileInput instantiated with no initial value does not render ... ok test_clear_input_renders_only_if_not_required (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_clear_input_renders_only_if_not_required) A ClearableFileInput with is_required=True does not render a clear ... ok test_html_does_not_mask_exceptions (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_html_does_not_mask_exceptions) A ClearableFileInput should not mask exceptions produced while ... ok test_html_escaped (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_html_escaped) A ClearableFileInput should escape name, filename, and URL ... ok test_multiple_error (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_multiple_error) ... ok test_render_as_subwidget (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_render_as_subwidget) A ClearableFileInput as a subwidget of MultiWidget. ... ok test_render_disabled (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_render_disabled) ... ok test_return_false_if_url_does_not_exists (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_return_false_if_url_does_not_exists) ... ok test_url_as_property (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_url_as_property) ... ok test_use_required_attribute (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_use_required_attribute) ... ok test_value_omitted_from_data (forms_tests.widget_tests.test_clearablefileinput.ClearableFileInputTest.test_value_omitted_from_data) ... ok test_doesnt_localize_input_value (forms_tests.widget_tests.test_checkboxselectmultiple.CheckboxSelectMultipleTest.test_doesnt_localize_input_value) ... ok test_label (forms_tests.widget_tests.test_checkboxselectmultiple.CheckboxSelectMultipleTest.test_label) CheckboxSelectMultiple doesn't contain 'for="field_0"' in the