Re: Fellow Reports - March 2022

2022-04-11 Thread Mariusz Felisiak 
Week ending April 3, 2022 

*Triaged: *
   https://code.djangoproject.com/ticket/33602 - date_hierarchy in admin 
reports an error with mysql-connector-python 8.0.28. (invalid) 
   https://code.djangoproject.com/ticket/33603 - Backslashes in template 
tag arguments are escaped (wontfix) 
   https://code.djangoproject.com/ticket/33604 - Allow 
CacheMiddleware.key_prefix to be a callable. (accepted) 
   https://code.djangoproject.com/ticket/33605 - Use of RegexValidator can 
cause migration generation to raise AttributeError (accepted) 
   https://code.djangoproject.com/ticket/33607 - PostgresIndex.create_sql() 
doesn't respect the using argument. (accepted) 
   https://code.djangoproject.com/ticket/33609 - Use assertCountEqual() in 
assertQuerysetEqual(). (wontfix) 
   https://code.djangoproject.com/ticket/33608 - select_related() to 
nullable FK with db_constraint=False do not promote OUTER joins. (invalid) 
   https://code.djangoproject.com/ticket/33611 - Allow View subclasses to 
define async method handlers. (accepted) 
   https://code.djangoproject.com/ticket/33464 - Resolve output_field when 
combining numeric expressions with MOD operator. (accepted) 
   https://code.djangoproject.com/ticket/33612 - Clone db failed in MariaDB 
10.7.3. (worksforme) 
   https://code.djangoproject.com/ticket/33613 - createsuperuser does not 
validate usernames that use a UniqueConstraint. (accepted) 

*Reviewed/committed: *
   https://github.com/django/django/pull/15372 - Corrected models.FileField 
signature in docs. 
   https://github.com/django/django/pull/12504 - Fixed #15619 -- Deprecated 
log out via GET requests. 
   https://github.com/django/django/pull/15402 - Fixed #16406 -- Added 
ResolveMatch.captured_kwargs and extra_kwargs. 
   https://github.com/django/django/pull/15556 - Refs #33397 -- Added extra 
tests for resolving an output_field of CombinedExpression. 
   https://github.com/django/django/pull/15271 - Fixed #33397 -- Corrected 
resolving output_field for 
DateField/DateTimeField/TimeField/DurationFields. 
   https://github.com/django/django/pull/15560 - Fixed #33613 -- Made 
createsuperuser detect uniqueness of USERNAME_FIELD when using 
Meta.constraints.

*Reviewed: *
   https://github.com/django/django/pull/15540 - Refs #32365 -- Deprecated 
django.utils.timezone.utc. 

*Authored: *
   https://github.com/django/django/pull/15550 - Updated various links to 
HTTPS and new locations. 
   https://github.com/django/django/pull/15552 - Updated Oracle docs links 
to Oracle 21c. 
   https://github.com/django/django/pull/15554 - Fixed #33598 -- Reverted 
"Removed unnecessary reuse_with_filtered_relation argument from Query 
methods." 
   https://github.com/django/djangoproject.com/pull/1157 - Moved Django 2.2 
to unsupported versions and added 5.x releases. 
   https://github.com/django/django/pull/15557 - Refs #24020 -- Removed 
redundant Query.get_loaded_field_names().

Best,
Mariusz

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b0c4b3c7-1c1f-4b10-a2f2-ed906a7dca12n%40googlegroups.com.

Re: Django security releases issued: 4.0.4, 3.2.13, and 2.2.28

2022-04-11 Thread אורי 
Hi,

Even if you decide to use only LTS releases, it's about time you upgrade to
3.2. There may be possibly another security patch of Django 2.2 released
before the end of the month (April 30), but from my experience even
security patches are applied not more than once a month, and therefore it's
not expected to release another security patch this month (April). You can
still use Django 2.2 at least until April 30, or even later, but if you
want to use a supported version then it's time to upgrade. The next time a
security patch is released, and it's not released to 2.2, then it will
definitely be the time to upgrade to at least Django 3.2.

Uri Rodberg, Speedy Net.
אורי
u...@speedy.net


On Mon, Apr 11, 2022 at 12:09 PM Wim Feijen  wrote:

> Hi,
>
> Thanks for the release!
>
> This has not directly to do with the security release, but I have a
> question about this remark: "Django 2.2 has reached the end of extended
> support. The final security release (2.2.28) was issued today. "
>
> As I understood it, Django 2.2 will be supported until the end of April,
> meaning the 30th of April will be the last day of support. Because the
> Django release cycle is once every eight months, and years are divided into
> four parts, so the support windows runs up to 1 May. Am I correct in this?
> Our internal update policies are based on this assumption, so it matters a
> lot to us.
>
> Thanks for your clarification,
>
> Wim
>
> Op maandag 11 april 2022 om 09:57:16 UTC+2 schreef Mariusz Felisiak:
>
>> Details are available on the Django project weblog:
>>
>> https://www.djangoproject.com/weblog/2022/apr/11/security-releases/
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/1e932359-0072-4ba0-96ae-a76bbbc25245n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CABD5YeGZhYkfKpsbxX8yMo6MhrHFsrNEqJc3FO3TZONPS%3DxO1A%40mail.gmail.com.

Re: Django security releases issued: 4.0.4, 3.2.13, and 2.2.28

2022-04-11 Thread 'Adam Johnson' via Django developers (Contributions to Django itself) 
>
> As I understood it, Django 2.2 will be supported until the end of April,
> meaning the 30th of April will be the last day of support. Because the
> Django release cycle is once every eight months, and years are divided into
> four parts, so the support windows runs up to 1 May. Am I correct in this?
> Our internal update policies are based on this assumption, so it matters a
> lot to us.


I think the answer here is: we don't commit to which day in the month is
the day that support ends.

Carlton summarized this on Twitter (
https://mobile.twitter.com/carltongibson/status/1501097294954905600 )
recently:

PSA: If you need to know the **exact** day LTS support ends, you waited too
> long.
>
> Django 2.2 is EOL next month folks.
>

Typically security/bugfix releases are monthly, near the start of the
month. So announcing this release as the end of support is to be expected.

My personal advice is to not use LTS releases, and upgrade to each new
feature version. There's not really a huge difference in stability, and
you'll reduce the risk by upgrading more frequently.

On Mon, Apr 11, 2022 at 10:09 AM Wim Feijen  wrote:

> Hi,
>
> Thanks for the release!
>
> This has not directly to do with the security release, but I have a
> question about this remark: "Django 2.2 has reached the end of extended
> support. The final security release (2.2.28) was issued today. "
>
> As I understood it, Django 2.2 will be supported until the end of April,
> meaning the 30th of April will be the last day of support. Because the
> Django release cycle is once every eight months, and years are divided into
> four parts, so the support windows runs up to 1 May. Am I correct in this?
> Our internal update policies are based on this assumption, so it matters a
> lot to us.
>
> Thanks for your clarification,
>
> Wim
>
> Op maandag 11 april 2022 om 09:57:16 UTC+2 schreef Mariusz Felisiak:
>
>> Details are available on the Django project weblog:
>>
>> https://www.djangoproject.com/weblog/2022/apr/11/security-releases/
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/1e932359-0072-4ba0-96ae-a76bbbc25245n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2LKGWGUekzuOTc%2BR8FGGZBwV93AOv4WGfsgoy-S_CFtQ%40mail.gmail.com.

Re: Django issus

2022-04-11 Thread 'Adam Johnson' via Django developers (Contributions to Django itself) 
Hi!

I think you've found the wrong mailing list for this post. This mailing
list is for discussing the development of Django itself, not for support
using Django. This means the discussions of bugs and features in Django
itself, rather than in your code using it. People on this list are unlikely
to answer your support query with their limited time and energy.

For support, please follow the "Getting Help" page:
https://docs.djangoproject.com/en/stable/faq/help/ . This will help you
find people who are willing to support you, and to ask your question in a
way that makes it easy for them to answer.

Thanks for your understanding and all the best,

Adam

On Mon, Apr 11, 2022 at 10:20 AM Fab  wrote:

> Actually you need to just fix the import error. The error will say where's
> it's happening. Could it be you are importing `employee` when you should be
> `Employee`?
>
> On Monday, 11 April 2022 at 09:54:08 UTC+1 Fab wrote:
>
>> Can you share your models and migrations files?
>>
>> On Saturday, 9 April 2022 at 17:14:00 UTC+1 hanenmd...@gmail.com wrote:
>>
>>> hello !
>>> I whish that you are fine, i try to migrate my model my model name is
>>> employee but it dosent work the issus msj is ImportError:cannot import name
>>> 'employee' from 'polls.models'
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/3eac30d4-d3ec-459b-9ea1-c0197abf6eafn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2vvNXmYsk-RJmp_o5pnBuLCWwbD5CoAeEKgsevUjMFkw%40mail.gmail.com.

Re: Django issus

2022-04-11 Thread Fab 
Actually you need to just fix the import error. The error will say where's 
it's happening. Could it be you are importing `employee` when you should be 
`Employee`?

On Monday, 11 April 2022 at 09:54:08 UTC+1 Fab wrote:

> Can you share your models and migrations files?
>
> On Saturday, 9 April 2022 at 17:14:00 UTC+1 hanenmd...@gmail.com wrote:
>
>> hello !
>> I whish that you are fine, i try to migrate my model my model name is 
>> employee but it dosent work the issus msj is ImportError:cannot import name 
>> 'employee' from 'polls.models'
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/3eac30d4-d3ec-459b-9ea1-c0197abf6eafn%40googlegroups.com.

Re: Django security releases issued: 4.0.4, 3.2.13, and 2.2.28

2022-04-11 Thread Wim Feijen 
Hi, 

Thanks for the release!

This has not directly to do with the security release, but I have a 
question about this remark: "Django 2.2 has reached the end of extended 
support. The final security release (2.2.28) was issued today. "

As I understood it, Django 2.2 will be supported until the end of April, 
meaning the 30th of April will be the last day of support. Because the 
Django release cycle is once every eight months, and years are divided into 
four parts, so the support windows runs up to 1 May. Am I correct in this? 
Our internal update policies are based on this assumption, so it matters a 
lot to us. 

Thanks for your clarification,

Wim

Op maandag 11 april 2022 om 09:57:16 UTC+2 schreef Mariusz Felisiak:

> Details are available on the Django project weblog:
>
> https://www.djangoproject.com/weblog/2022/apr/11/security-releases/
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1e932359-0072-4ba0-96ae-a76bbbc25245n%40googlegroups.com.

Re: Django issus

2022-04-11 Thread Fab 
Can you share your models and migrations files?

On Saturday, 9 April 2022 at 17:14:00 UTC+1 hanenmd...@gmail.com wrote:

> hello !
> I whish that you are fine, i try to migrate my model my model name is 
> employee but it dosent work the issus msj is ImportError:cannot import name 
> 'employee' from 'polls.models'
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ad5a1340-7083-4943-b258-78b0e5a92e02n%40googlegroups.com.

Django security releases issued: 4.0.4, 3.2.13, and 2.2.28

2022-04-11 Thread Mariusz Felisiak 

Details are available on the Django project weblog:

https://www.djangoproject.com/weblog/2022/apr/11/security-releases/

--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ff3a4a17-2a7e-7215-a5d1-ec4a17b79636%40gmail.com.