Hello,
Just for the record, we spent a good time discussion this change (to bring
> inheritance of Admin Actions in line with Python’s expected inheritance
> rules). We reviewed the entire history of the feature. We explored an
> alternative approach, which would have maintained BC. We put the dis
> I love where Django is headed. I love all of those breaking changes that
have to happen so we're not perpetually stuck with decisions from 2005.
+100 to this!!
Django user since 1.6 running on python2.6. Upgraded to 1.7 and python3.4
at the same time, and _that_ migration was hard. Everything
As someone who has spent over 12 years working with Django, I'd like to
offer an opposite point of view:
I love where Django is headed. I love all of those breaking changes that
have to happen so we're not perpetually stuck with decisions from 2005.
What I truly miss is strong static typing sup
Hello Pascal,
As we're getting to the end of useful arguments here, I'd like to ask you to
step back for a minute and take a calm look at what you're writing. Imagine you
were receiving such messages rather than sending them. Would you want to spend
more time collaborating with the person addre
Pascal, I don't think anyone here disagrees with your overall goal to
reduce the breaking changes. As someone that got handed a 1.2 project with
zero tests and updated it to 1.8, good test coverage to lay the foundation
for reviving an ambitious project that went comatose before being
prioriti
Hi Pascal.
> On 17 Aug 2019, at 18:21, Pkl wrote:
>
> In just 5 lines of discussion...
Just for the record, we spent a good time discussion this change (to bring
inheritance of Admin Actions in line with Python’s expected inheritance rules).
We reviewed the entire history of the feature. We
Pascal,
I have had a short reply sitting in draft status for a while but not found
the energy to read all of your posts.
I'd just like to chime in and echo the sentiment from Aymeric, Florian,
Luke, and Tim. I worked with Django for nearly 5 years before being
accepted onto the core team.
One of
Pascal, you can read about the reason for the action actions change on the
ticket https://code.djangoproject.com/ticket/29917 ...and on this mailing
list...
https://groups.google.com/d/topic/django-developers/-OWoYL_zryM/discussion.
I hesitate to link to things like that in the release notes be
Hello Luke,
thanks for your comments, mine are below
On Thursday, August 1, 2019 at 10:34:22 AM UTC+2, Luke Plant wrote:
>
> Hi Pascal,
>
> I know this is a very late reply, but there have been some things going
> round my head that I thought I should get down.
>
> *First,* some positive changes
Hi Pascal,
I know this is a very late reply, but there have been some things going
round my head that I thought I should get down.
*First,* some positive changes I think we can make from your suggestions:
1. I think in our release notes, for breaking changes that might need
some justificatio
Hello everyone,
(apologies in advance for the long post, but there are lots of aspects to
dig here, it's not for the pleasure of writing but a necessary to progress
on the relevance of a DEP)
*"As you can see, there's more than "blinding self-absorption" and "harmful
psychological bias" here
Hello World,
On Sunday, June 30, 2019 at 9:24:05 AM UTC+2, Aymeric Augustin wrote:
>
> As an experiment, let's just consider the first backwards-incompatible
> change from the latest release:
> https://docs.djangoproject.com/en/2.2/releases/2.2/#admin-actions-are-no-longer-collected-from-base-mo
Hello Pakal,
If I understand correctly, you're proposing that:
1. The Django project should maintain a higher level of backwards compatibility.
2. This would be easier to achieve outside the main codebase, in a submodule or
in a separate repository.
3. This would reduce the amount of work requir
13 matches
Mail list logo
