On 9/11/20 2:02 PM, Tim Orling wrote:
> The reason for Django 2.2 is it is LTS. This version will now override
> unless the user sets PREFERRED_VERSION. The thrash on non-LTS Django is
> a PITA to support...
If we want to keep LTS as default but still offer newer releases as
second options, we
On Fri, Sep 11, 2020 at 2:40 PM Trevor Gamblin
wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 9/11/20 5:02 PM, Tim Orling wrote:
>
>
>
>
>
>
>
>
> The reason for Django 2.2 is it is LTS. This
>
> version will now override unless the user sets
>
> PREFERRED_VERSION. The thrash on non-LTS Django is a PITA
On 9/11/20 5:02 PM, Tim Orling wrote:
The reason for Django 2.2 is it is LTS. This version will now override
unless the user sets PREFERRED_VERSION. The thrash on non-LTS Django
is a PITA to support...
Alright, let's hold off on merging this one then. I'll revisit it some
time in the future.
The reason for Django 2.2 is it is LTS. This version will now override
unless the user sets PREFERRED_VERSION. The thrash on non-LTS Django is a
PITA to support...
On Fri, Sep 11, 2020 at 7:26 AM Trevor Gamblin
wrote:
> meta-python only contains a recipe for django 2.2.x, so
>
> add a recipe
meta-python only contains a recipe for django 2.2.x, so
add a recipe file for the newest branch.
Signed-off-by: Trevor Gamblin
---
.../recipes-devtools/python/python3-django_3.1.1.bb | 9 +
1 file changed, 9 insertions(+)
create mode 100644
