#django

foo: charfield inherits from Field, which means the **kwarg is there so it doesn't need to explicitly name the kwargs that Field would expect

[redacted]

what are people using for asynchronous tasks these days?

foo: https://stackoverflow.com/questions/5259025/dja...

jmelloy: asyncio

really?

I am

jmelloy: you mean job queues?

jmelloy: Celery?

yes, job queues

we've used celery before but i'm hoping there's some new hotness I don't know about

asyncio has queues too :D

If it ain't broke..

jmelloy: what is it about celery doesn't fit your needs?

that will shape the solutiolns

-l

jmelloy: https://github.com/cr0hn/aiotasks

I've found it likes to back up without warning or hang and freeze

I recently found an interesting one based on AWS SQS

jmelloy: which broker did you use?

rabbitmq

what's the one that uses SQS?

i've used mrq a bit and it seems fine

[redacted]

[redacted]

but in celery's defense, I do like their api

[redacted]

[redacted]

[redacted]

[redacted]

yes

[redacted]

[redacted]

foo: try doing that in __call__

[redacted]

you still have line 20

is line 34 right

[redacted]

[redacted]

ah i see, you could do that with a JsonField no?

[redacted]

I dabled in something similar with JsonField a few years back https://github.com/japrogramer/django-amorphous

[redacted]

I still think Luigi has an excellent name

foo: did the call work?

[redacted]

[redacted]

[redacted]

[redacted]

foo: are you getting any errors

[redacted]

foo: pretty sure init is called before call

not sure, let me check

yup, ok so if setting the attribute like i said by doing [somefield].widget.attr than you should already have an instance of a widget associated to the field, so __init__ has already been called before the attr was set

[redacted]

foo: self.fields['name_of_the_field'].widget = CustomWidget(kwarg=value)

how about something like that

[redacted]

foo: its now in the kwargs

so range(kwargs.pop('..'))

[redacted]

foo: since you are now setting the widget manually, do you need line 17? how are you using MultiField?

[redacted]

Its probably because since you set that attribute the field is trying to instantiate it

[redacted]

line 41

the number is hardcoded as 1

[redacted]

[redacted]

you need to get the value from self

probably a good idea, to have a default in init, just in case the user dosn't pass one

[redacted]

[redacted]

foo: line 39, initializes a field, without passing that value

I meant get that value from self in line 39

or dynamicly set that field in init if it makes more sense

[redacted]

[redacted]

yeah, i caught that. It probably makes more sense to put that in init

well it is available outside of init but thats a different topic

[redacted]

yes, Initialize the field in init

[redacted]

[redacted]

foo: self.fields['name'] = field

[redacted]

[redacted]

[redacted]

np

anyone in here a modoboa or uwsgi expert?