Re: Django says a modification was made to Auth user when I didn't, and migration has a timestamp from the future. Help?

2018-06-22 Thread Melvyn Sopacua 
On vrijdag 22 juni 2018 05:36:42 CEST JJ Zolper wrote:
> It's Jun 21 at 11:30 pm in my world fyi.
> 
> On Thursday, June 21, 2018 at 11:34:50 PM UTC-4, JJ Zolper wrote:

And 23:30 + 4 = 27:30 = 3:30 next day. Django generates migration timestamps 
in UTC time.

> > You'll see the timestamp on this post and here's the migration it thinks
> > it needs to make:

Do you have a custom user model?
-- 
Melvyn Sopacua

-- 
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 group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2474311.fTER52XSdO%40fritzbook.
For more options, visit https://groups.google.com/d/optout.

Re: Django says a modification was made to Auth user when I didn't, and migration has a timestamp from the future. Help?

2018-06-21 Thread JJ Zolper 
It's Jun 21 at 11:30 pm in my world fyi.

On Thursday, June 21, 2018 at 11:34:50 PM UTC-4, JJ Zolper wrote:
>
> Hey everyone,
>
> So I did inherit this from someone else but I cannot phanthom how a change 
> to the django auth user would be maintained by git between developers.
>
> For some reason when I run makemigrations it thinks the django auth user 
> email field needs to be altered via migration?
>
> I'm so lost and I've tried resetting every scenario I could think of to 
> resolve this. Does anyone have any brilliant ideas?
>
> You'll see the timestamp on this post and here's the migration it thinks 
> it needs to make:
>
> # -*- coding: utf-8 -*-
>
> # Generated by Django 1.10.3 on 2018-06-22 03:29
>
> from __future__ import unicode_literals
>
>
> from django.db import migrations, models
>
>
>
> class Migration(migrations.Migration):
>
>
> dependencies = [
>
> ('auth', '0008_alter_user_username_max_length'),
>
> ]
>
>
> operations = [
>
> migrations.AlterField(
>
> model_name='user',
>
> name='email',
>
> field=models.EmailField(blank=True, max_length=254, 
> unique=True, verbose_name='email address'),
>
> ),
>
> ]
>
>
>  Yet I'll remove all of Django in python site packages and it still comes 
> back as something to migrate after it's been wiped clean.
>
>
> Thanks for your help. I'm out of ideas.
>
>
> Best,
>
>
> JJ
>

-- 
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 group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/14059aeb-5d0d-411b-b339-455073ade64b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django says a modification was made to Auth user when I didn't, and migration has a timestamp from the future. Help?

2018-06-21 Thread JJ Zolper 
Hey everyone,

So I did inherit this from someone else but I cannot phanthom how a change 
to the django auth user would be maintained by git between developers.

For some reason when I run makemigrations it thinks the django auth user 
email field needs to be altered via migration?

I'm so lost and I've tried resetting every scenario I could think of to 
resolve this. Does anyone have any brilliant ideas?

You'll see the timestamp on this post and here's the migration it thinks it 
needs to make:

# -*- coding: utf-8 -*-

# Generated by Django 1.10.3 on 2018-06-22 03:29

from __future__ import unicode_literals


from django.db import migrations, models



class Migration(migrations.Migration):


dependencies = [

('auth', '0008_alter_user_username_max_length'),

]


operations = [

migrations.AlterField(

model_name='user',

name='email',

field=models.EmailField(blank=True, max_length=254, 
unique=True, verbose_name='email address'),

),

]


 Yet I'll remove all of Django in python site packages and it still comes 
back as something to migrate after it's been wiped clean.


Thanks for your help. I'm out of ideas.


Best,


JJ

-- 
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 group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/17b4e9c6-5e94-43d9-8061-c41cbe8f6a67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.