Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have been developing using Django 1.5 a lot. Is it worth the time to shift from Django 1.5 to Django 1.6 or Django 1.7? I know, In 1.7, migration is into the core of Django. How different is it from south?
Django 1.6 is a relatively incremental update compared to Django 1.7.
Django 1.6 adds a few comfort features (i.e., simplified project templates and admin enabling by default) for new projects, and some minor overhauls in algorithms (i.e., model save). There are also a myriad of other features that make development relatively easier when compared to 1.5.
Django 1.7, as you've noted, includes the migration features. In addition, it forces Python 2.7 (which may or may not be an issue for you). The migration is based off of South, so it's similar to use. In addition to various improvements, the plugin focused on being database agnostic, improved autodetection and improved the migration file format.
With both of these updates, your workflow shouldn't change significantly.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
Im new to web development and trying to learn APIs through Django Rest Framework. I am actually confused about why we actually need to build an API. For example, I've seen tutorials of creating blog APIs, where it returns the posts and its info. Why would we need an API for that? We can simply create regular Django views to do the same. I've heard that APIs only provide the 'data', but I can also obtain data from regular Django. So why would you install a totally new 'sub' framework to do these for you?
Suppose you want to build a mobile application that serves some blog posts. have you thought about how you are going to fetch the blog posts from a back-end.
Take the case of instagram, the app fetches images,comments and tags from the django backend in the form of json data and can display relevant data on the application. in short, APIs can be used when the backend and frontend technologies are different and they can communicate through APIs
The biggest reason to use Django REST Framework is because it makes serialization so easy!
see this medium post
https://medium.com/#BennettGarner/build-your-first-rest-api-with-django-rest-framework-e394e39a482c
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I am currently working on a Project with Django backend and Flutter frontend. We have to do a Web application for the admin for adding data to the Rest framework/Database (excluding the admin panel).
My question is, should I add the web application to the existing API project, or should I start a completely new Project.
it's possible to start a new project and use the same database but i think it's not a true way according to the django principles and you can simply add another app in your project for your web application.
off course you know that django-rest-framework is a library based on django framework,not an another framework!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
What is the best way to learn Django 1.5 thouroughly? I have been a .NET developer and have a really good understanding of OOP, HTML5, CSS and JavaScript. I also have an entry-level knowledge of Python. I am completely new to MVC (or MVT, in this case).
I have a need to build apps with Django that provide users with features such as finding each other based on geographical distance, upload pictures and edit them online, natural language search, etc... (just to highlight that I need to know more than how to build a poll app or a simple blog).
My understanding is that the entry point to learn Django is by completing the tutorial at the Django project site. Then, what? What path would you recommend? I have seen that lots of learning resources on the web target versions lower than 1.5 and I couldn't really find books on 1.5. When reading reviews on learning material on 1.4, I often see they are outdated and not really applying to 1.5.
Also, I briefly looked at what it takes to deploy a Django app. Virtualenv, git, pip, etc... are all things unknown to me and it looks a bit scary for a guy used to deploy apps by uploading the compiled binaries through FTP.
Help in defining a clear path to learn how to bend Django to my will would be invaluable!
The official Django tutorial (as you are aware)
2 Scoops of Django e-book or paperback (https://django.2scoops.org/). There are lots of useful information in it, even about virtualenv, custom settings etc.
If you don't want to spend the few bucks for the excellent book, have a look at this github repository: https://github.com/jacobian/djangobook.com which is an ongoing project.
I'm a newbie to python and Django.
Here is the path that I am following in this order :
www.learnpythonthehardway.org (free html online)
do the djangoproject poll tutorial
gettingstartedwithdjango.com (GSWD)
It is important to follow these tutorials in this order because this will setup your environment for GSWD and it will go over virtualenv.
Also as mentioned, the 2Scoops book is a best practices book.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm using Django Grappelli as a skin for the Django admin interface. However, the design is not responsive. Users on mobile devices need to do a lot of zooming and panning. The mobile admin projects I've found so far seem to have been abandoned in their early stages. Does anyone know of one that is actively maintained?
Try this:
https://github.com/douglasmiranda/django-admin-bootstrap
It uses Bootstrap and is BSD licensed
Since version 1.9 Django uses a former third-party app called django-flat-theme. There's another app made by the same developer which adds responsiveness to the admin. This app is called django-flat-responsive.
That means, if you're on Django 1.9+ just add django-flat-responsive. If you're running an older version of Django you need django-flat-theme and django-flat-responsive.
As user mirek points out, all of this is already integrated into Django 2+.
This is what it looks like:
https://code.google.com/p/django-jqmobile/ and https://code.google.com/p/django-mobileadmin/ seems interesting too compared to the other one above
using jquerymobile is very light and benefits from html5 controls which looks like a native app when managing your django admin.
it could require some tweaks when it comes to other custom django apps to work properly with all functions of that app though.
Django Jet is another responsive admin interface http://jet.geex-arts.com/
https://github.com/ 750+ stars
I'm currently developing a website in Django v1.2.7. That's the version as per requirements, but I think I could change it without problems. I was thinking about using v1.3 (because of class-based views, etc), but the version 1.4 was released a few weeks ago. My questions are:
Does it worth migrating to Django 1.4?
What incompatibilities could I face when updating the version?
Both your questions are answered at the release page for 1.4