News for hackers. Stuff that matters.
Re:Django 2.2 by jordigh on Monday April 01, 2019 @12:13PM (#19544868)
Trying to move, but it's tough. Old codebase, lots of deps, and no real benefit to upgrading to 3.6, nothing our end users will care about or notice (or pay for).

Upgrading to Python 3 is a chore. We have to do it, but it's not fun and it's barely useful.

Re:Django 2.2 by ses4j on Monday April 01, 2019 @12:24PM (#19545002)
Well said.
Re:Django 2.2 by PunchTornado on Monday April 01, 2019 @04:43PM (#19548026)
don't your users in 2020 care you are using an unsupported language? security wise
Re:Django 2.2 by user5994461 on Monday April 01, 2019 @05:27PM (#19548456)
Of course not. That's the point.
Re:Django 2.2 by PunchTornado on Tuesday April 02, 2019 @03:26PM (#19557722)
the users care that your site is secure, especially if you're using their confidential info.

can you achieve security with a dead language? I don't think so.

Re:Django 2.2 by jordigh on Wednesday April 03, 2019 @01:33PM (#19565314)
Users care very little about security, actually.
Re:Django 2.2 by bjt2n3904 on Monday April 01, 2019 @02:32PM (#19546531)
I would argue py3 has negative utility for that reason. Plus, the mess of 3.5 vs 3.6 vs 3.7.
Re:Django 2.2 by user5994461 on Monday April 01, 2019 @05:28PM (#19548465)
What happened between those?
Re:Django 2.2 by misterdoubt on Monday April 01, 2019 @05:45PM (#19548636)
Nothing obviously a "mess." Your guess is as good as mine.
Re:Django 2.2 by cpburns2009 on Monday April 01, 2019 @10:13PM (#19550443)
At worst async became a keyword in 3.5. I have to say I am enjoying f-strings from 3.6.