Relative Content

Tag Archive for django

Keeping “historical” migrations in Django-south

After a system has gone through many migrations, and evolved enough for a second version, does it make sense to keep the old migrations around? I mean, old versions will use them to upgrade to the new one, sure, but should a fresh install have its database go through all the “historical” changes before arriving at the current shape? My gut feeling is that a fresh install should create the database “as it is”, not go through every mistake that was made in the product lifecycle until reaching a stable condition.

Should one generally develop a client library for REST services to help prevent API breakages?

We have a project where UI code will be developed by the same team but in a different language (Python/Django) from the services layer (REST/Java). The code for each layer exits in different code repositories and which can follow different release cycles. I’m trying to come up with a process that will prevent/reduce breaking changes in the services layer from the perspective of the UI layer.

Django application strategy

I have been working a while on a Django project which has been growing a bit lately. I have been think a bit about what strategy to use to make it easier to handle. One thing I would like to get some input on would be if I should split my application into several smaller applications. That would make my view and model files smaller and separate some of the concerns.

Dependency conflicts due to Django version

I am currenlty working to integrate azureSQL to my website, but I am encountering this error that some of my packages require django version more than 4, others require version 2, what should I do?
this is the error I am getting :