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 permi
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
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
t
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/py
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 r
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
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 s
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,
mayb
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 tha
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 wee
10 matches
Mail list logo
