migrate versioning question

[Dennis Backhaus]

Hello fellow migraters,

following scenario:

I took over the task to work on some new part of a customers webpage using TG2. The migrations that I will be doing will not effect their migrations they did so far or will do in the future. Currently they already have a few migrations in the migrations/version folder (73 to be exact) in the format "073_upgrade.py". While I work on my part of the project, they will also be working on their other parts and write further migrations. It would be great if I could just name my own migrations starting with an index of 10000 (like: "10000_upgrade.py") and go from there. So when at some point I merge their most recent code and migrations (74 to 85 as example) into my fork, I wont have any conflicting file names.

In other words: I do not want to add a migration called "073_upgrade.py" just to later have to rename it because meanwhile they added a "73" and a few more. I hope this makes sense and you can follow me.

The problem is:

If I do all this (rename my file to 10000) and run an upgrade, I receive a KeyError: <VerNum(74)> because I assume migrate expects a file starting with '74'.

Solution:

? That is what I need your help with.

Thanks a lot in advance,

Dennis