Did anyone else find Django Rest Framework to have quite a tough learning curve? I learnt Django quite quickly 2 years ago and I’ve been developing with it for some time now. I’m now learning React for frontend and I’d very much like to use DRF to serve my backend api, but dang it’s got quite a learning curve I feel.

eeehhh.... I guess, if you already know Django, learning DRF is just a piece of cake... 🤔 when I discovered DRF, I learnt it in 2 days or so

eeehhh.... I guess, if you already know Django, learning DRF is just a piece of cake... 🤔 when I discovered DRF, I learnt it in 2 days or so

If u really need a CMS, you can take a look into Wagtail, it has cool things such as stream fields, custom admin pannel not based on the django one and is easily integrable with existing django projects, if you just want to make a blog and dont want to build it from scratch, you can take a look to puput or coderedcms and if you dont need a CMS and just want a blog built with django you could for example check Zinnia

Well, I started with drf with no previous knowledge of django and found that the documentation (from both projects) were sufficient for a beginner

eeehhh.... I guess, if you already know Django, learning DRF is just a piece of cake... 🤔 when I discovered DRF, I learnt it in 2 days or so

2 days? 😏

You are messing with python 2 and 3

A question ) why there is always a change in syntax when update the version of python it will create a mess in the future and and lots of struggle . why

A question ) why there is always a change in syntax when update the version of python it will create a mess in the future and and lots of struggle . why

Welcome, please read the group rules before any activity: » Only English, avoid meta-question » Be civil, respect other people of the group » Off-topic is not allowed in the middle of ontopic conversation (go to @pythonofftopic instead) » Don't spam messages/stickers/commands » Promotions for other groups/channels related to django/python allowed, just make sure you are not spamming it (sharing too much) » Don't share NSFW content (ban) » Use dpaste.de, pastebin or github gist when sharing code and image sharing service to share images by joining this group, you agree with django code of conduct here is some resource to start with django

In py2 you can use __future__ module to use "future" syntax , so when you upgrade the version you won't have the mess you're talking about And there's 2to3 that can help ya so much

wtf, why link is not updated @Inchidi 🤮🤮🤮

which link?

which link?

oh okay

may i know how many years you learn python already?

Wish there was a syntax change software or executable for django especially when updating to a new version of django or even downgrading to test out some ancient feature or reusable app. If the devs at django can do this, I believe even google would be tempted to change their entire backend.... To django of course🙂

On official docs you always find a section to upgrade without much pain

Think of an upgrade from Django==1.8.5 to Django==2.0

2

Yeah I know I was trying at United Nations to upgrade from 1.8 to 1.11 and it wasn't so easy

then dont worry, i think you just took wrong tutorial

It was the official docs 😢

u see ..... I can begin to imagine my case. backwards compatability should be made a tradition in every language out there...... another priceless feature that makes GIT so successful. IMHO ..... django makes the work of upgrading purposely difficult and discouraging. In a way it makes the latest stable releases of django so much less interesting or exciting. If there was backwards compatability in django, every release would be another exciting story to tell. Look at JavaScript. That one's almost a sad story. There are programs that do a lot of checks and syntax adjustement for older code to be run on newer compilers. All this really basically exist because of lack of backward compatability If any of you guys know a language that's loyal to their origins but at the same time has room for improvement, please let me know. All this syntax upgrade and frustrating hours refactoring just because of a new version isn't where we shoould be in the 21st Century. Some might see me as a lazy developer. Aren't we all that way? If we weren't we'd be wix.com developers.... 😂😂

I don’t see it as such a big problem and think django developers take lot of care about backward compatibility... anyways, you can just have your test suite and run it with tox for example to try that everything works on new versions before pushing changes to production, even, my point of view is that if there was a bad design decision or some big improvement that can be solved by creating a new version with backward incompatible changes but with significant improvements to the software as for example happened with channels, py2 to py3 or lets say django urls to path, it should be welcome and seen as good news from a developer point of view as not doing it just makes you keep having a worse language/framework/library to develop with

Hmmmmmm.... So in conclusion, django is confident to say that you must suffer to upgrade your projects to their latest versions just because the latest versions are a better half of the framework. Still looks way way discouraging to me. I will think of refactoring to a new version when I know I don't have anything around me to hit when I get frustrated at very misleading error messages

Hmmmmmm.... So in conclusion, django is confident to say that you must suffer to upgrade your projects to their latest versions just because the latest versions are a better half of the framework. Still looks way way discouraging to me. I will think of refactoring to a new version when I know I don't have anything around me to hit when I get frustrated at very misleading error messages

Everything that is changed is properly documented, if you upgrade ur version regularly, there is almost no changes you have to do in ur source, even you can see what will be deprecated in next versions https://docs.djangoproject.com/en/2.1/internals/deprecation/

better half? you are not considering security issue?

I'm just 6 months old in django. I'm sure with time, my negative notions and misinterpretations would be relatively corrected. But all the resources shared here are valuable. Very valuable.

https://www.aeracode.org/2018/02/02/channels-20/ read this for example, he explains why backwards incompatible changes were needed for django channels, and how much he tried to avoid it, etc

I use non-english characters in my urls (other language) Browser shows urls correctly For example mysite.com/store/<other language> But when I email a url or print url in console it's wrong and like mysite.com/store/%D9%BE%D9%86 How can I solve this? I have no idea What should I search for

I can solve it like this But it's just a trick. List = url.split('/') And join items of list except last one. For last one I use slug that I have to make the url and email or do what ever with that string But as I said it's not a solution. It's a trick

Is there any updated django tutorial site in 2019

Anyone tell me that how can i fully customise django admin like a good CMS. For instance like charts, navigation something like WordPress.... One other thing that for this purpose default admin work after customise or i have to write myown admin panel.

Anyone tell me that how can i fully customise django admin like a good CMS. For instance like charts, navigation something like WordPress.... One other thing that for this purpose default admin work after customise or i have to write myown admin panel.

Wagtail was ok but not right

I just didn't like how it functioned. It seemed to be better for a small site and I needed something different.

if you're looking for a CMS, try wagtail if you feel the default admin page is not enough for you, you can customize it or write your own if you want 🙂

I've been playing wagtail for some time now cause I thought of using it for a client's site as he wanted to be able to post articles etc. It works, but I'm just not too fond of the post editor.

Have you created the post content via RichTextField or StreamField?

But which one you used?

Not working with 0.0.0.0:8000

try adding localhost

Tried putting * in allowed host

I'm using CreateView to create a post Django.views.generic.edit.CreateView How can I make a field optional?

I'm using CreateView to create a post Django.views.generic.edit.CreateView How can I make a field optional?