I came up with a PR that will raise a deprecation warning on variable
access - see the ticket.
On Wed, 14 Aug 2019 at 14:46, step21 wrote:
> I do not have a better idea right now, but also do not know the django
> core code that well. Personally, as you could get all TemplateViews via Ack
> or
I do not have a better idea right now, but also do not know the django core
code that well. Personally, as you could get all TemplateViews via Ack or
another code search method, I do not think replacing them would take long.
> Am 14.08.2019 um 09:45 schrieb Adam Johnson :
>
> Hi,
>
> After
I don't think the DSF has the capacity or the will to run a business
offering paid support contracts.
But nothing is stopping an enterprising individual or company from doing
so. All security patches are made public (eventually) and backporting fixes
would be fairly low effort.
I think that's sensible, including making the team public.
> This struck me as a little absurd: if we weren't going to dissolve it,
Nick should definitely be part of the old "Django Core".
It's not done yet, and while we're in this limbo stage, we're potentially
missing out on some good
Hi Fadi,
This is the developers mailing list dedicated to development of django
itself. Questions like this should be addressed to the users mailing list.
P.S: Do a search for "django model property decorator" (there is also a
cached_property decorator). It will help you find a solution.
--
You can create a drop down menu for this.
AGE_CHOICES = (
('11-20','11-20'),
('21-30', '21-30'),
)
class MyModel(models.Model):
color = models.CharField(max_length=6, choices=AGE_CHOICES, blank=True,
null=True)
Hope this helps...
With regards,
Shubham Gupta
--
You received
Hi,
After reading the ticket, I agree this could be deprecated as a backwards
incompatibility. The deprecation plan suggested by loic84 looks like it
could work but would be a bit unwieldy on large projects. Maybe there's
another path?
One thing that's not explicitly in the discussion: the view
Hi!
I think you've found the wrong mailing list for this post. This mailing
list is for 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
