From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Marcus Hoffmann <buildroot@bubu1.eu>,
Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/python-whitenoise: new package
Date: Mon, 5 Aug 2024 12:02:06 +0200 [thread overview]
Message-ID: <20240805120206.6da2d1a9@windsurf> (raw)
In-Reply-To: <20240216131815.318315-2-buildroot@bubu1.eu>
Hello Marcus,
On Fri, 16 Feb 2024 14:18:14 +0100
Marcus Hoffmann via buildroot <buildroot@buildroot.org> wrote:
> diff --git a/support/testing/tests/package/test_python_django.py b/support/testing/tests/package/test_python_django.py
> index 0973467a2a..ac1dc81359 100644
> --- a/support/testing/tests/package/test_python_django.py
> +++ b/support/testing/tests/package/test_python_django.py
> @@ -36,6 +36,7 @@ class TestPythonPy3Django(TestPythonDjango):
> config = TestPythonDjango.config + \
> """
> BR2_PACKAGE_PYTHON3=y
> + BR2_PACKAGE_PYTHON3_PY_PYC=y
> BR2_PACKAGE_PYTHON_DJANGO=y
> BR2_PACKAGE_PYTHON3_SQLITE=y
> """
I'm confused about this change. How is this related to whitenoise?
I see in reply to PATCH 1/2, you mentioned:
"""
The django test (and the whitenoise test introduced in the next patch)
actually both currently fail because of a problem with django 5.0 and
.pyc only installations. [1]
This now has "release blocker" priority at django and a proposed patch
(that I tested locally but hasn't been officially submitted to django
yet) so hopefully this will be fixed with the next django point release
in a couple of weeks.
"""
But now PATCH 1/2 is merged, but not PATCH 2/2. Could you clarify this
aspect? Is master broken because that snippet of PATCH 2/2 should have
been in PATCH 1/2, or?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-05 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 13:18 [Buildroot] [PATCH 1/2] support/testing: remove hardcoded sleep from python-django test Marcus Hoffmann via buildroot
2024-02-16 13:18 ` [Buildroot] [PATCH 2/2] package/python-whitenoise: new package Marcus Hoffmann via buildroot
2024-08-05 10:02 ` Thomas Petazzoni via buildroot [this message]
2024-08-07 10:25 ` Marcus Hoffmann via buildroot
2025-02-05 10:41 ` Thomas Petazzoni via buildroot
2025-02-05 10:41 ` Thomas Petazzoni via buildroot
2024-02-16 13:23 ` [Buildroot] [PATCH 1/2] support/testing: remove hardcoded sleep from python-django test Marcus Hoffmann via buildroot
2024-02-16 19:55 ` Arnout Vandecappelle via buildroot
2024-02-20 16:46 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240805120206.6da2d1a9@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=buildroot@bubu1.eu \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox