.
On 11/25/14 7:16 PM, Andrew Pinkham wrote:
Hi,
Upgrading Django (to 1.7) Part IV: Upgrade Strategies is now available!
For the article:
afrg.co/updj17/a4/
For all of the material:
afrg.co/updj17/
I've also provided a checklist of upgrade steps
.
On 11/25/14 3:03 PM, Andrew Pinkham wrote:
Hi,
I have just updated Upgrading Django (to 1.7) Part III: Django 1.7's New
Features. The App Registry and System Check Framework sections have been
updated to be more accessible.
For the article:
afrg.co/updj17/a3/
For all of the material:
afrg.co
Excellent resource.
Thanks Andrew.
On Tue, Nov 25, 2014 at 10:16 PM, Andrew Pinkham <m...@andrewsforge.com>
wrote:
> Hi,
> Upgrading Django (to 1.7) Part IV: Upgrade Strategies is now available!
>
> For the article:
> afrg.co/updj17/a4/
>
> For all of the material:
Hi,
Upgrading Django (to 1.7) Part IV: Upgrade Strategies is now available!
For the article:
afrg.co/updj17/a4/
For all of the material:
afrg.co/updj17/
I've also provided a checklist of upgrade steps, as well as a list of all the
links used throughout the series:
afrg.co/updj17/cl
Hi,
I have just updated Upgrading Django (to 1.7) Part III: Django 1.7's New
Features. The App Registry and System Check Framework sections have been
updated to be more accessible.
For the article:
afrg.co/updj17/a3/
For all of the material:
afrg.co/updj17/
Part IV will be available before
Sounds good! Thanks!
--Fred
Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com -- Glad to be of service!
Open Source: Without walls and fences, we need no
Hi,
Thanks to feedback from Fred and a few others, I've started editing Part III to
make it more accessible.
Part IV was originally set to be published today. Unfortunately, it is not
ready to be published.
As soon as the new Part III and Part IV are available, I will let you know.
Thanks,
Andrew,
Yes, that explains a lot. I'd recommend including this explanation
in one of the articles of your current series.
BTW, one other thing to keep in mind is that we 1.4 users don't
know what an apps.py file is, so we don't appreciate not having
to create one, since we never did before.
Hi Fred,
Thanks again for the positive feedback!
I'm sorry I lost you at the App Registry section. I'm afraid I can't recommend
an article to help with the topic, either. Given your questions, I can see I
missed the mark. Let me give it another go (warning: this is neither
technically reviewed
On 10/8/14 11:30 PM, Andrew Pinkham wrote:
Hi,
Upgrading Django (to 1.7) Part III: Django 1.7's New Features is now available!
For the article:
afrg.co/updj17/a3/
For all of the material:
afrg.co/updj17/
Any feedback appreciated. I hope you find the material helpful.
Andrew
Andrew
Hi,
Upgrading Django (to 1.7) Part III: Django 1.7's New Features is now available!
For the article:
afrg.co/updj17/a3/
For all of the material:
afrg.co/updj17/
Any feedback appreciated. I hope you find the material helpful.
Andrew
--
You received this message because you are subscribed
Hi Fred,
Thanks again for the input! Glad you liked Part II.
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
On 10/1/14 11:36 PM, Andrew Pinkham wrote:
Any feedback appreciated. I hope you find the material helpful.
Andrew,
Excellent 2nd article. Thanks!
I especially liked the clear explanation of how South migrations
interact badly with initial_data fixtures. OK to use fixtures, but
load them
Stodge,
Part II focuses on migrations, and deals in passing with AppConfig objects via
data-migrations. Part III will take a closer look at the app registry, as we
will create a custom AppConfig objects for `roundtable`. There is a (very)
short section in Part III about import problems caused
Carsten,
Thank you for reading and for the positive feedback!
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
I will read this thanks. Does it cover this issue?
django.core.exceptions.AppRegistryNotReady: The translation infrastructure
> cannot be initialized before the apps registry is ready. Check that you
> don't make non-lazy gettext calls at import time.
>
I don't know if this has been a pain to
Hi Andrew,
Am 2014-10-02 um 05:36 schrieb Andrew Pinkham:
Any feedback appreciated. I hope you find the material helpful.
Also from me a hearty thanks for your article series!
It's very helpful, and very much appreciated!
Best regards,
Carsten
--
Cafu Engine * www.cafu.de
an open-source 3D
Hi,
Upgrading Django (to 1.7) Part II: Migrations in Django 1.6 and 1.7 is now
available!
For the article:
afrg.co/updj17/a2/
For all of the material:
afrg.co/updj17/
Any feedback appreciated. I hope you find the material helpful.
Andrew
--
You received this message because you
Fred, thanks a jillion for the excellent advice! I obviously missed that
bit in the data migration boilerplate.
On Saturday, September 27, 2014 9:29:10 AM UTC-5, Fred Stluka wrote:
>
> Bob,
>
> Are you referring directly to the models by name in the data
> migrations? That could be the
Hi Bob,
Thank you!
I spend a lot of Part II talking about schema and data migrations in both South
and native Django 1.7 migrations. When building data migrations, you should be
using historical models. In Django 1.7, you can request these models directly
from the app registry built on the fly
Benjamin,
Thank you!
The next two parts of the article will focus on why certain changes were made.
Please let me know if you think there were changes that I should have written
about. Depending on my schedule and feedback, I would be willing to consider
adding to the material if I've missed
Bob,
Are you referring directly to the models by name in the data
migrations? That could be the problem, because yes, the migration
would be using the latest models at the time that the migration is
executed, not the models as they stood at the time that the
migration was written.
There's a
The problem we ran into was not with the order of migrations, it was that
all of the migrations were running with the latest models.py code. The data
migration was trying to move data from one model field to another model
field, and the "from" field had been deleted from models.py.
This was
Bob,
You can control the order in which migrations run.
For South, see "depends_on" and "needed_by":
- http://south.readthedocs.org/en/latest/dependencies.html
For Django 1.7 migrations, see "dependencies":
- https://docs.djangoproject.com/en/dev/topics/migrations/#dependencies
--Fred
Andrew, thanks for the article, and the more-to-come.
When you get to data migrations, you might want to cover a problem I ran
into with them: when I had a data migration in the middle of a sequence of
other migrations, and then later wanted to set up a new environment, which
meant running all
Great summary - looking forward to the rest. Especially like some of the
backgrounder insights also explaining "why" certain things were done. I
think this often helps developers understand and use features better than
even the otherwise excellent and detailed online docs. Wonder if the Django
doc
Sabine,
I'm not sure about the new 1.7 Migrations, but with South,
restarting your migrations is easy.
I'm currently doing it on my project, because we have a
long convoluted history of changes before and after we
started using South, and have made some mistakes along
the way (like editing
Fred,
Thank you!
Good luck with the upgrade!
Andrew
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this
Hi Sabine,
Thank you! It is really nice getting positive feedback.
The migrations section (Part II next week!) is a very basic introduction, aimed
at people who have never used South or native migrations. One of the key
takeaways (hopefully) of the article is the fact that it is easy to
Andrew,
Good stuff! Thanks! We're still on 1.4, but planning a move
soon to 1.7. Very helpful.
--Fred
Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/
Bristle Software, Inc -- http://bristle.com --
Dear Andrew,
I read your article and it is great. I am really looking forward to your
followups. I was hoping for something like this went I attended Django Con
Europe. I struggle with the understanding the migrations the most. Usually
in the early phases of development I do not want
Hi,
I am writing a series of articles based on the presentation I gave at DjangoCon
US 2014. I put the first article online earlier today, and figured members of
this list might be interested in the material.
For all of the material:
afrg.co/updj17/
For the article:
afrg.co/updj17/a1/
32 matches
Mail list logo
