#django

yeah, that part makes sense. Issue is just that if I handle it in clean(), I still want to change the names of fields/which fields are shown whenever the user toggles countries

I guess that part would be in JS

then the validation in Django

Yeah

there's no sort of widget or package that handles this already? Ha

Because if you wanted to only let them enter a certain amount of digits based on country (depending on the countries format) that'd have to be handled by JS

And that's probably what you want

morenoh149: yeah, just pass a default value (hard coded or as a callable, however you want), then just overwrite it on save

sms: yeah, makes sense. Because otherwise, using for example a regex field, I'd have to change the regex when they toggle country... and I don't think that's possible w/out a page reload

Well you don't have to reload, you could use Ajax

Fair point. Seems a little crazy though to hit the server just to update the regex.

Yeah that's definitely overengineering

ok, I think I may keep this pure JS: there's enough of an eco-system there already that I don't think I'll even need to worry about clean(). Thanks for the info!

Np

I can't seem to get models that point to a created model in it's {post,pre}_save hooks

Is it possible to make SelectDateWidget show year only?

Greetings, all. Are there any general recommendations for project layout to support multiple API versions in a Django project?

exist some function in django that let me display a json response formated (like pprint) inside a template file?

samsagaz: There is nothing built in, but you can create a template tag for it using pygments.

is just for debuggin purpose, but dont want to get all the plain json because ir hard to read

oh, will search about it

samsagaz: This is what I have in my application: https://gist.github.com/tarkatronic/0b31eef92a7...

let me see

what @register.filter do? :/

it... registers a function as a template filter?

it registers a filter

so you can use it

otherwise it's just some function in some file

samsagaz: https://docs.djangoproject.com/en/1.11/howto/cu...

never used filters, will read about it

i was importing the pygments in the view :D

samsagaz: If you have this filter available to you, then all you need to do in your template is: {{ my_json_variable|jsonify }}

nice!

django is incredible

:)

im close...

Can I provide choices tuples as integers? But why do I need a list of two for this?

label and value

one for the value, one to display

and they both can be integers?

label might need to be a string

"1" vs 1 ... but try it out, maybe int is ok too.

Incredibe!

but i need to use <p> {{ content | jsonify | safe}} </p> to get it working :)

thanks TheJoey get it working very quick!

can I get the current year (e.g. 2017) from timezone.now?

empedokles78: yup

timezone.now().year

feasible?: https://dpaste.de/As6O

sure

nowever

remember that will be evaluated as soon as that code is imported

My coworkers like to squash migrations. I have a long running branch and I regularly get errors when I merge django.db.migrations.exceptions.NodeNotFoundError: Migration foo.0009_auto_20171121_0325 dependencies reference nonexistent parent node ('bar', '0008_auto_20171116_0430') into my long running branch. Is squashing migrations causing these issues?

FunkyBob, imported where? You don't suggest it?

tourdownunder: if the parent isn't there… then probably yes?

tourdownunder: i certainly wouldn't expect it to work, from a "conservative approach" perspective.

empedokles78: whatever imports it. if it's a models.py then django setup will import it

tourdownunder: more likely manually editingmigrations will cause it

or leafing out migrations from git

FunkyBob, so it's a bit ressource heavy putting choices inside the model?

empedokles78: in this specific case... you might have troubleif, for instance, aninstance is left running over the new year

Well, no. It runs once on first import. It's relatively short. You'll survive. The problem comes if the process that loads it stays running over a year boundary. The year will change but the choices will be last years'.

"this year" is not a constant :)

in this specific case, y ou'd want to set it in an overridden __init__

but as a general pattern, it's fine

It's a shame choices have to be baked into migrations (never quite understood that) or a callable would be on the table.

FunkyBob, can you provide an example? Overwriting __init__ seems advanced python :)

pfft

Thanks for your replies I've just been in standup

it's not rank beginner python, true, but it's something you should learn early on

FunkyBob, I had it in models, is it better to be placed in forms?

oh, well, yeah, can do in models...

not the same way, though

What's different?

you don't want to override __init__ on models

I think I've done that before. It wasn't pretty.

does anyone here use django-filters

once

enough to test itwas compatible withdjango-nap .... not sure if it still is

FunkyBob how was your experience with it?

I use it

FunkyBob, what do you override then?

It works for simple cases... but I still have cases where I just write my own filter functionality

do you really need to enforce the choices onthe model level, empedokles78 ?

given you'll aquire "invalid" years over time, that way

FunkyBob, I just thought it's easiest to bundle everything there, because I use also a modelform and specify the models fields in a class meta.

Why invalid?

hi - im trying to write a unit test in django for an existing project that runs with an existing oracle db - ive downloaded oracle vm and changed the settings as written in https://code.djangoproject.com/wiki/OracleTestS...

but i get this traceback https://dpaste.de/Rgvj