#django

anyone know python-social-auth? how can i verify into templates if user is social authenticated?

clear

any help

?

kl4us: I always use django-allauth

but in general, you can access the user from a template

you are trying to differentiate social from other login?

jessamynsmith, yes

i'm using django-registration with python-social-auth

to have normal signin/signup and social signin

anyone used threading in management commands or at least doesn't think it's a bad idea

?

Not necessarily..

What are you doing?

Knyght: ....eeeeesh

parsing CSVs, adding each row as an object, bunch of relations, but each row is independent. Think it might speed things up, but not sure what the best way to do it is.

(or if it's worth doing at all, which I'm siding towards atm)

So, the ORM isn't great at bulk loading.

oh, I should mention it's currently slow mostly because we're making 2 external API calls per row

Knyght, I use multiprocessing to batch generate thumbnails

hmm, that reminds me

Ugh, the multiprocessing module :(

doesn't py3 have some new multiprocessing stuff, the pool thingies?

I remember pools of workers

I didn't use though

Is it possible to make a UUID type field that is blank at first?

when I do ( blank=True ) it says "badly formed hexadecimal UUID string"

cause I only want to add uuid under certain conditions but leave it blank for most

Knyght: Mostly it sticks the old stuff in the same namespace as some other types of worker pools and a new API

new API sounds good to me considering the old ones

microdex2, what if blank=True, null=True ?

I'm not sure if it makes much sense though

Knyght: They don't remove the old API, which was designed to usually work with import magic that can have subtle bugs and confusing behavior (and depend on whether its forking without execing, as is what it will do by default on some platforms, though this varies by manager and version and options)

Knyght: That is to say, you're still using that badness of it when you use the concurrent.futures version of the pool

as long as it's hidden from me :P

Knyght: It also didn't change the fact the API lacks a data model, just pickling willy nilly--which would be bad enough if you could tell really when it would pickle, but you cam't

Knyght: It's not hidden from you, it just prays things will work and you won't notice.

Knyght: Of course, all of that would be one thing if the communication layer actually worked, rather than breaking randomly sometimes, even on localhost

Fuyou: When I set it to null=True , the migrations seem to work, but the field is still not in the DB

the migration runs but the field doesn't get added

microdex2: You'll need to be NULLABLE, as otherwise it will try to coerce the blank value to a UUID. Which is not valid.

Oh, missed your latest messages.

Can you dpaste your migration?

schinckel

Hmm. Looks okay. Are you sure the migration is being applied?

how can I be sure of that?

it says OK OK OK on all the migrations

Look in the database table "django_migrations"

Could it have been faked? Try fake-reversing the migration, and re-applying

./manage.py migrate --fake core 0001