Re: End of extended support for Django 1.11

[Daniela Kim]

Mariusz,
Thank you for your response.

Would it be possible for the Django Fellows to vote to extend Django 1.11's 
EOL by a few weeks? For those of us with a large Django codebase, we were 
bitten by the onerous Python 2->3 upgrade and so the start of our Django 
upgrade was delayed by several weeks.

Also, given the current global situation with Covid-19, including (1) 
work-life difficulties/transitions for organizations and our developers and 
(2) an evermore global online presence with further exposure to online 
security threats, a graceful extension would be very much appreciated.

Thank you for your consideration.
Daniela


On Thursday, March 26, 2020 at 1:15:18 AM UTC-4, Mariusz Felisiak wrote:
>
> No, support of Django 1.11 ends on 1st April.
>
> 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/f5718ec3-6041-40db-93fd-b7b8b354e64a%40googlegroups.com.

Re: End of extended support for Django 1.11

[James Bennett]

The end of support simply means there will be no further releases, and
any showstopping bugs reported will not be fixed. It doesn't mean
Django itself will stop working. Also, the decision is in the hands of
the Technical Board, not the Django Fellows, so the correct process
would be to request that the Technical Board schedule additional
support/releases of Django 1.11.

That said, my personal opinion is that both the Python 2 EOL (2020-01)
and the Django 1.11 EOL (2020-04) were set years in advance;
organizations which waited until the last minute to do their upgrades
would simply wait until the last minute again if given an extension,
and be right back in the same problem. There has to be a cutoff date
at some point where we just say "sorry, but if you haven't prioritized
upgrading for years and years, we cannot tie up our open-source
project's resources because of that". And the announced cutoff, which
is in line with previous LTS releases of Django, seems as reasonable
as any other.


On Tue, Mar 31, 2020 at 6:57 AM Daniela Kim  wrote:
>
> Mariusz,
> Thank you for your response.
>
> Would it be possible for the Django Fellows to vote to extend Django 1.11's 
> EOL by a few weeks? For those of us with a large Django codebase, we were 
> bitten by the onerous Python 2->3 upgrade and so the start of our Django 
> upgrade was delayed by several weeks.
>
> Also, given the current global situation with Covid-19, including (1) 
> work-life difficulties/transitions for organizations and our developers and 
> (2) an evermore global online presence with further exposure to online 
> security threats, a graceful extension would be very much appreciated.
>
> Thank you for your consideration.
> Daniela
>
>
> On Thursday, March 26, 2020 at 1:15:18 AM UTC-4, Mariusz Felisiak wrote:
>>
>> No, support of Django 1.11 ends on 1st April.
>>
>> 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/f5718ec3-6041-40db-93fd-b7b8b354e64a%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/CAL13Cg_WBtBU%3D_ZrSPfgWfzP0U2PGsFXvcCMCY8GCcDRybS5tQ%40mail.gmail.com.

Re: End of extended support for Django 1.11

[Adam Johnson]

I agree with James, the cutoff date has been more than reasonable.

Also, if there aren't any show-stopping bugs you know about, asking for the
extension of the EOL "by a few weeks" doesn't really mean much. If we were
past the cutoff date, and a high impact, wide reaching bug was found - yes,
maybe I'd be in favour of a temporary extension and a bug fix release. But
there isn't any.

For smaller bug fixes, you can always backport them yourselves to your
fork. You can use the script on
https://code.djangoproject.com/wiki/CommitterTips#AutomatingBackports and
pip install the tarball from github:
https://adamj.eu/tech/2019/03/11/pip-install-from-a-git-repository/ .

On Tue, 31 Mar 2020 at 15:06, James Bennett  wrote:

> The end of support simply means there will be no further releases, and
> any showstopping bugs reported will not be fixed. It doesn't mean
> Django itself will stop working. Also, the decision is in the hands of
> the Technical Board, not the Django Fellows, so the correct process
> would be to request that the Technical Board schedule additional
> support/releases of Django 1.11.
>
> That said, my personal opinion is that both the Python 2 EOL (2020-01)
> and the Django 1.11 EOL (2020-04) were set years in advance;
> organizations which waited until the last minute to do their upgrades
> would simply wait until the last minute again if given an extension,
> and be right back in the same problem. There has to be a cutoff date
> at some point where we just say "sorry, but if you haven't prioritized
> upgrading for years and years, we cannot tie up our open-source
> project's resources because of that". And the announced cutoff, which
> is in line with previous LTS releases of Django, seems as reasonable
> as any other.
>
>
> On Tue, Mar 31, 2020 at 6:57 AM Daniela Kim  wrote:
> >
> > Mariusz,
> > Thank you for your response.
> >
> > Would it be possible for the Django Fellows to vote to extend Django
> 1.11's EOL by a few weeks? For those of us with a large Django codebase, we
> were bitten by the onerous Python 2->3 upgrade and so the start of our
> Django upgrade was delayed by several weeks.
> >
> > Also, given the current global situation with Covid-19, including (1)
> work-life difficulties/transitions for organizations and our developers and
> (2) an evermore global online presence with further exposure to online
> security threats, a graceful extension would be very much appreciated.
> >
> > Thank you for your consideration.
> > Daniela
> >
> >
> > On Thursday, March 26, 2020 at 1:15:18 AM UTC-4, Mariusz Felisiak wrote:
> >>
> >> No, support of Django 1.11 ends on 1st April.
> >>
> >> 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/f5718ec3-6041-40db-93fd-b7b8b354e64a%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/CAL13Cg_WBtBU%3D_ZrSPfgWfzP0U2PGsFXvcCMCY8GCcDRybS5tQ%40mail.gmail.com
> .
>


-- 
Adam

-- 
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/CAMyDDM2ooXoGuJ3GuFSg%2B3hBra8GQPiUSmJek0EmEEQOYMuuFw%40mail.gmail.com.

Re: End of extended support for Django 1.11

[Mariusz Felisiak]

Personally, I'm counting the days and I'm against extending support of 
Django 1.11, just 1 day remaining.

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/5a85ab7e-ded9-49a1-b2fd-50c1bf38%40googlegroups.com.

Re: GSOC Proposal: 2FA

[Rohit Jha]

Hi, 

Thanks for the suggestion. 
I have updated the proposal giving more technical details. 
Regards 

On Sunday, March 29, 2020 at 10:17:38 AM UTC+5:30, Asif Saif Uddin wrote:
>
> can you elaborate more on the technical break down of the project steps?
>
> On Thursday, March 26, 2020 at 11:10:27 PM UTC+6, Rohit Jha wrote:
>>
>> Hi,
>>
>> Here is my proposal for GSoCon 2FA
>>
>>
>> https://docs.google.com/document/d/1f-9hOYHZ9rzLH7UEzdPmVi1n4jQJ92gDwYpqef1ZYMk/edit?usp=sharing
>>
>> Feedback and criticism is highly appreciated.
>> Thanks & Regards 
>>
>

-- 
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/da11e11f-47b1-47b2-a7f3-f094a2478f97%40googlegroups.com.

Re: End of extended support for Django 1.11

[Daniela Kim]

Thank you all. I am mostly concerned about a possible widespread security 
issue. Hopefully, this is only paranoia on my part. While I'll look out for 
Adam's "maybe" ;) in such an event, I'll also look into the links Adam 
shared in case we need to backport any fixes ourselves.

I appreciate the responses you have provided and thank you deeply for your 
ongoing dedication to this project and for the global web community at 
large. And yes, I completely agree that my organization needs to be more 
proactive on upgrades - this is a muscle we're improving day-by-day - 
including with this upgrade - though a few weeks late.

Best,
Daniela

-- 
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/73e34fd3-8c37-4366-bc2b-ffc4cf0fae7b%40googlegroups.com.

getting errors from my Django app

[Adam Geek]

this is what I get when I run:   python3 manage.py createsuperuser 


Traceback (most recent call last):

  File "manage.py", line 21, in 

main()

  File "manage.py", line 17, in main

execute_from_command_line(sys.argv)

  File 
"/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/core/management/__init__.py",
 
line 401, in execute_from_command_line

utility.execute()

  File 
"/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/core/management/__init__.py",
 
line 377, in execute

django.setup()

  File 
"/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/__init__.py",
 
line 24, in setup

apps.populate(settings.INSTALLED_APPS)

  File 
"/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/apps/registry.py",
 
line 114, in populate

app_config.import_models()

  File 
"/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/apps/config.py",
 
line 211, in import_models

self.models_module = import_module(models_module_name)

  File 
"/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/importlib/__init__.py",
 
line 127, in import_module

return _bootstrap._gcd_import(name[level:], package, level)

  File "", line 1014, in _gcd_import

  File "", line 991, in _find_and_load

  File "", line 975, in _find_and_load_unlocked

  File "", line 671, in _load_unlocked

  File "", line 783, in exec_module

  File "", line 219, in 
_call_with_frames_removed

  File "/Users/kabar/Desktop/wisdompets/adoption/models.py", line 3, in 


class pet(models.Model):

  File "/Users/kabar/Desktop/wisdompets/adoption/models.py", line 10, in pet

sex =models.CharField(choices= SEX_CHOICES,max_lenght=1,blank=True);

  File 
"/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/db/models/fields/__init__.py",
 
line 984, in __init__

super().__init__(*args, **kwargs)

TypeError: __init__() got an unexpected keyword argument 'max_lenght'


any help?

-- 
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/05e39666-2fd9-4a3d-abad-1a96fb3935b6%40googlegroups.com.

Re: getting errors from my Django app

[Adam Johnson]

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/3.0/faq/help/

Thanks for your understanding,

Adam

P.S. this is a Python error, the hint is right there in the error message:
"TypeError: __init__() got an unexpected keyword argument 'max_lenght'". I
think you meant max_length.

On Tue, 31 Mar 2020 at 19:52, Adam Geek  wrote:

>
> this is what I get when I run:   python3 manage.py createsuperuser
>
>
> Traceback (most recent call last):
>
>   File "manage.py", line 21, in 
>
> main()
>
>   File "manage.py", line 17, in main
>
> execute_from_command_line(sys.argv)
>
>   File
> "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/core/management/__init__.py",
> line 401, in execute_from_command_line
>
> utility.execute()
>
>   File
> "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/core/management/__init__.py",
> line 377, in execute
>
> django.setup()
>
>   File
> "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/__init__.py",
> line 24, in setup
>
> apps.populate(settings.INSTALLED_APPS)
>
>   File
> "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/apps/registry.py",
> line 114, in populate
>
> app_config.import_models()
>
>   File
> "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/apps/config.py",
> line 211, in import_models
>
> self.models_module = import_module(models_module_name)
>
>   File
> "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/importlib/__init__.py",
> line 127, in import_module
>
> return _bootstrap._gcd_import(name[level:], package, level)
>
>   File "", line 1014, in _gcd_import
>
>   File "", line 991, in _find_and_load
>
>   File "", line 975, in
> _find_and_load_unlocked
>
>   File "", line 671, in _load_unlocked
>
>   File "", line 783, in exec_module
>
>   File "", line 219, in
> _call_with_frames_removed
>
>   File "/Users/kabar/Desktop/wisdompets/adoption/models.py", line 3, in
> 
>
> class pet(models.Model):
>
>   File "/Users/kabar/Desktop/wisdompets/adoption/models.py", line 10, in
> pet
>
> sex =models.CharField(choices= SEX_CHOICES,max_lenght=1,blank=True);
>
>   File
> "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages/django/db/models/fields/__init__.py",
> line 984, in __init__
>
> super().__init__(*args, **kwargs)
>
> TypeError: __init__() got an unexpected keyword argument 'max_lenght'
>
>
> any help?
>
> --
> 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/05e39666-2fd9-4a3d-abad-1a96fb3935b6%40googlegroups.com
> 
> .
>


-- 
Adam

-- 
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/CAMyDDM3A9hVaw1NkbUf%2BVkWaAadTbYX73LsefeDuHeoA6iE-3Q%40mail.gmail.com.

Migrations for dropping columns/tables must not have CASCADE keyword

[Marcin Nowak]

Hi.

My question is about these two:

https://github.com/django/django/blob/master/django/db/backends/base/schema.py#L55
https://github.com/django/django/blob/master/django/db/backends/base/schema.py#L64

Both are loose cannons. All dependent objects are silently destroyed during 
dropping table or column.
Please fix this.
 
Motivation:
I didn't checked what SQL is generated for dropping column.
As a result Django destroyed silently all my views dependent on the column, 
which was dropped.
The database I'm using is PostgreSQL.

Kind Regards,
Marcin

-- 
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/b21b2791-539f-46e0-a60c-f90c208ca020%40googlegroups.com.

Re: Migrations for dropping columns/tables must not have CASCADE keyword

[Adam Johnson]

Hi Marcin,

I'm sorry to hear that your views got dropped. I hope they were easy to
recreate.

I imagine the reason the migrations framework uses CASCADE is because we
assume Django manages all your database. I know without CASCADE, PostgreSQL
(at least) can also be hard to fight against with permissions, sequence
objects, triggers, and other objects that might be related to a table.

I'm not sure how feasible it would be to just remove the keyword. It would
probably give a different bad migrations experience to other users. Is
there a way to make CASCADE apply to some object types and not others?

There has been discussion of making view-based models in Django, that would
maybe solve it for you in a different way by providing a way to manage
views through the migrations framework. What do you think of that?

Thanks,

Adam

On Tue, 31 Mar 2020 at 23:26, Marcin Nowak  wrote:

> Hi.
>
> My question is about these two:
>
>
> https://github.com/django/django/blob/master/django/db/backends/base/schema.py#L55
>
> https://github.com/django/django/blob/master/django/db/backends/base/schema.py#L64
>
> Both are loose cannons. All dependent objects are silently destroyed
> during dropping table or column.
> Please fix this.
>
> Motivation:
> I didn't checked what SQL is generated for dropping column.
> As a result Django destroyed silently all my views dependent on the
> column, which was dropped.
> The database I'm using is PostgreSQL.
>
> Kind Regards,
> Marcin
>
> --
> 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/b21b2791-539f-46e0-a60c-f90c208ca020%40googlegroups.com
> 
> .
>


-- 
Adam

-- 
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/CAMyDDM2ME5Siqd4QdGjQy8QeeEq1TLjD7NboRB6q4mqvBhFWLg%40mail.gmail.com.