Not a hindrance, but something like not having a typed database, no auto completion over time, can be a real drawback (I know about django-types).
Finally, in my opinion, the best reason to not use Django is not the project itself (because it will do the job in 99% case), it's because all you learn is tied to Django.
Having learn Pydantic recently was a breed of fresh air, and I would reuse it in lots of projects, not only web projects.
I'm not sure what you mean? Django ORM works with common SQL databases, which are generally "typed"? Auto completion is generally a function of your IDE, and there are certainly IDE's with autocompletion that work well with Python and Django? I agree that Pydantic is a great library... I use it with Django quite often, as Django is a Python Library and it plays very well with other Python libraries like Pydantic.
Comments
Not a hindrance, but something like not having a typed database, no auto completion over time, can be a real drawback (I know about django-types).
Finally, in my opinion, the best reason to not use Django is not the project itself (because it will do the job in 99% case), it's because all you learn is tied to Django.
Having learn Pydantic recently was a breed of fresh air, and I would reuse it in lots of projects, not only web projects.
I'm not sure what you mean? Django ORM works with common SQL databases, which are generally "typed"? Auto completion is generally a function of your IDE, and there are certainly IDE's with autocompletion that work well with Python and Django? I agree that Pydantic is a great library... I use it with Django quite often, as Django is a Python Library and it plays very well with other Python libraries like Pydantic.