Django 2.0 released • Hacker News Board

Re: Django 2.0 released

#171

Post by rkuykendall-com » Mon, Dec 04, 2017, 5:54 PM UTC

maxerickson wrote: post #148

mcny wrote: post #118

Earlier quoted context omitted.

just yesterday someone at cuny sps told me a professor is teaching them flask using python 2.6... sigh

It'd likely be better to use Python 3, but the actual differences in syntax are pretty small, it's big Python 2 code bases that present a problem, not the switch over to using Python 3 syntax and names for new code.

Yeah, for the types of programs intro students write, it's basically "Okay, now add parens to your prints." And if they're running Python 2.7 they might be doing that already.

Re: Django 2.0 released

#172

Post by y4mi » Mon, Dec 04, 2017, 8:03 PM UTC

jefurii wrote: post #156

tschellenbach wrote: post #23

Nice this release will be the final push that tips over the balance towards Python 3. With Django taking the lead I think more projects will drop Python 2 support. Well it sure took a while, but glad the ecosystem is standardizing around 1 language again.

Time for Python 4!

Guido was imo pretty clear that there won't be backward incompatible changes for python 4, if at all

https://twitter.com/gvanrossum/status/501172370690699265?lan...

Re: Django 2.0 released

#173

Post by gojomo » Mon, Dec 04, 2017, 10:08 PM UTC

collinmanderson wrote: post #103

gojomo wrote: post #97

I wish they'd skip-jumped their version to "Django 3.0". That would have allowed a simpler message about the Python dependency: "Django 3.x requires Python 3.x".

Django 3.0 will be out soon enough (Dec 2019). There's going to be a major version bump every two years.

Alas, that doesn’t help for presenting a simple version story to low-attention beginners:

“Django 3.x requires Python 3.x”

“Ah, OK, so to use Python 2.x I should go back to Django 2.x?”

“No, Django 2.x requires Python 3.x. If you want to use Python 2.7 you should use Django 1.x.”

Re: Django 2.0 released

#174

Post by collinmanderson » Tue, Dec 05, 2017, 12:22 AM UTC

jordigh wrote: post #161

collinmanderson wrote: post #153

Earlier quoted context omitted.

Some things to do that could help everyone (this is what I do): If documented stuff changes, Please report it (though that likely means testing against the alpha / beta versions (or just master). Keep Django honest. If you find yourself using undocumented features, consider documenting them; that way they’re held to backward compatibility. Also, follow the development of Django and comment on the intentional breaks i…

> Also, follow the development of Django and comment on the intentional breaks if you think they’re not worth changing. I really don't want to be sucked into Django's drama: https://us.pycon.org/2015/schedule/presentation/381/ I've encountered very little sympathy from Django developers. Everyone seems to have just accepted that it breaks often and it's totally my fault for not keeping up with the breaking changes. E…

I hear you, and I've heard others say the same.

I think it would help if you bring it up on the Django-developers mailing list, if you haven't yet. I think that would help raise awareness about the issue, and I hope it would lead to some policy changes.

Re: Django 2.0 released

#175

Post by simonw » Tue, Dec 05, 2017, 11:47 PM UTC

Walkman wrote: post #108

simonw wrote: post #96

Earlier quoted context omitted.

I've ever understood this argument. Any library you can pick and mix into your Flask app you could just as easily pick and mix into your Django app. It's all just Python.

not really. Did you ever tried to use SQLAlchemy with Django? Good luck with that.

I built a project on Django and SQLAlchemy back in 2008/2009.

Re: Django 2.0 released

#176

Post by mastazi » Fri, Dec 08, 2017, 3:10 AM UTC

nielsole wrote: post #146

yeahdef wrote: post #91

Earlier quoted context omitted.

seconded, it's amazing how many people claim to make "REST APIs", but they fall so short in a lot of aspects. DRF makes it almost impossible if used correctly.

Could you elaborate what you mean? Looking at https://en.wikipedia.org/wiki/Representational_state_transfe... I would think that esp. ModelViewSets are pretty RESTful

The way I read the parent comment is that using DRF helps you building a truly RESTful API.

I think the "it" in the sentence:

> DRF makes it almost impossible if used correctly.

Refers to

> claim to make "REST APIs", but they fall so short in a lot of aspects

Re: Django 2.0 released

#177

Post by whatyoucantsay » Fri, Dec 08, 2017, 5:00 PM UTC

jlgaddis wrote: post #78

whatyoucantsay wrote: post #36

Earlier quoted context omitted.

> as it's the shortest path to a win. Rails is the "shortest path to a win". Django is well made, but it just hasn't had the same level of focus on RAD or the same level of intensity of community support. Edit: My goodness there are some insecure, vindictive Django advocates here! What I wrote above is the truth and no level of tribalism can change it.

FYI, I just downvoted you but for your edit, not your original comment. Perfectly legit, valid comments get downvoted here for bullshit reasons sometimes, I just ignore it and move on. (FWIW, I've never used Django. I'm not a developer.)

My only concern for karma is as a way to gain insight regarding the opinions of the community and how broken it is.

The parent comment being flagged to death is enlightening on both counts. I also appreciate your telling me you'd comment and vote on a thread about a Django release even though you've never used it and aren't a developer. That's simply fascinating!