Django 2.1 released

Post by KyeRussell » Thu, Aug 02, 2018, 8:59 AM UTC

52-6F-62 wrote: post #59

jtchang wrote: post #44

For anyone thinking about picking up Django and is worried about the framework being obsolete I encourage you to take a look. Django is fantastic. I've worked with it for a number of years now and it can really help in the early stages of prototyping. Things I especially like about Django: * The built in admin letting you edit and view objects easily. * Being able to use it without using the views. Add django rest fr…

At work because I have lately needed to roll web server/api/admin/client apps (embellished CRUD situations with some other serverside processing to generate user output) and for those my go to for dev speed, platform speed, familiarity, and a few other concerns I generally go with Node/Express/TypeScript and it's great to work with. However for my personal site I used Django to give it a shot. Once I wrapped my head…

Post by Humphrey » Thu, Aug 02, 2018, 11:59 AM UTC

fredley wrote: post #7

I've been working with Django for almost my whole career, since 1.1. It's a joy to use, and blows any other web framework I've used out of the water when it comes to actually just building stuff. Django is a fantastic boring[1] tool, and seeing boring updates like this is great. 1: http://mcfunley.com/choose-boring-technology

Post by collinmanderson » Thu, Aug 02, 2018, 1:49 PM UTC

chocolatkey wrote: post #118

collinmanderson wrote: post #72

Earlier quoted context omitted.

I maintain a Django ecommerce site that's been running constantly since July 12, 2007 (at launch it was running against r4984, basically 0.96). Just upgraded it to 2.1 today.

Any struggle with the upgrade?

Post by lowercased » Thu, Aug 02, 2018, 2:55 PM UTC

caspar wrote: post #111

lowercased wrote: post #110

Open question re: django: https://docs.djangoproject.com/en/2.1/ref/models/fields/#nul... I've got a colleague who has been using django for a couple of years (and has 15+ years experience with python outside of web, as well as java, php, arduino hacking, 3d printing, etc). He pointed me to the link above re: nulls - I can't figure out why the default would be to convert a null to an empty string. All major databases…

> An empty string is "no user supplied data" and a null is "no value has been given at all" I assume you meant "an empty string is user supplied an empty string as data". That aside, you wouldn't normally switch that option on for a field (notice the default is false). However, Oracle DB stores empty strings as indistinguishable from NULLs[0], so an ORM supporting Oracle DB may want to have some support for convertin…

Post by blumomo » Sun, Aug 05, 2018, 12:20 PM UTC

audiolion wrote: post #108

blumomo wrote: post #73

Earlier quoted context omitted.

I'm a very happy ist of Pyramid. Using it professionally for various larger applications as well as for pet projects. It's very well thought through. We're providing a GraphQL and integrating it was a breeze.

I would be interested to hear about how you did pyramid and graphql, ive been following graphene but are there specific tie ins for pyramid? books? articles?

  from cornice import Service
  from pyramid.exceptions import HTTPBadRequest

  from ..schemas import schema


  graphql = Service(
      name='graphql',
      path='/graphql',
      description="GraphQL",
      accept='application/json',
      renderer='json',
  )


  @graphql.post(permission='readwrite')
  def post_graphql(request):
      query = request.json_body.get('query')
      variables = request.json_body.get('variables', None)
      if not query:
          raise HTTPBadRequest
      return schema.execute(query, variable_values=variables, context_value={
          'dbsession': request.dbsession,
          'user_id': request.authenticated_userid,
      })