You can undo a migration manually using migrate, though if you're in
multiple-tip-migration scenario you may need to make a merge migration
first (but not apply it) or switch to a branch with only the migration you
wish to undo.
The more general rebase command would be interesting, though I've
I've had this situation come up too. It would indeed be very useful.
Django South had something vaguely related:
http://south.readthedocs.org/en/latest/tutorial/part3.html
However, the command did not make it over to built-in migrations.
On Monday, November 30, 2015 at 8:44:37 AM UTC-5, Shai
We're on schedule for 1.9 final tomorrow. There are 3 release blockers in
Trac, however, 1 blocker affects only master and the other two also affect
1.8 and thus aren't blockers for 1.9.
On Saturday, November 14, 2015 at 3:17:27 PM UTC-5, Tim Graham wrote:
>
> Sorry for the lack of updates, but
On Monday, November 30, 2015 at 7:02:05 PM UTC+1, Tim Graham wrote:
>
> Florian, your preference is to decline the change proposed by Chris and
> just deal with any support queries when people see a log like below? I
> understand it's not ideal to add workarounds for bugs in other software as
Actually, the SyntaxError issue isn't related to pip but to setuptools 5.5
and 5.5.1 (Debian stable ships the latter).
Florian, your preference is to decline the change proposed by Chris and
just deal with any support queries when people see a log like below? I
understand it's not ideal to add
Hello,
Part of my work lately was to help bring a large, complex project from Django
1.7 to 1.8. This effort was being done in parallel to continued development of
the project, in a separate branch. To make things more fun, the project uses
UUID fields for PKs in many models; on 1.7, this was
Hi Edwar,
Commenting on the ticket itself would be more appropriate. Also note
that the ticket's only been open 5 days - I'd suggest a little more
patience might be needed :)
T.
--
You received this message because you are subscribed to the Google Groups
"Django developers
