#django

‎joshbright‎: You are right, some magics happening! I done an other mistake! I used form.fields.ip.id_for_label in template instade of form.ip.id_for_label :))

‎joshbright‎: Thanks!

nkuttler: I'm not sure if save_formset is the right place ?

Yaser_Amiri: im glad I could help!

Is it best to use AbstractUser when creating the User model?

Given that AbstractUser adds extensibility to the base User model that Django gives you

Anyone have any thoughts on AbstractUser vs base User model?

so google doesn't allow me to change my password to one i have used in the past

moretango: one sec

so when i use the password reset once, i can have to go through all my devices and change the stupid password. who comes up with such crap :(

moldy: they also use those old passwords to recover accounts

moretango: you may want to watch this (great talk at last djangocon about working wth the user model): https://www.youtube.com/watch?v=uLPZYuj7yTg

v0lksman: yes, it's all crap. i want to have an option "stop trying to protect me from myself"

im hesitant to answer a question about extending users without knowing more about the situation

v0lksman: they also spam you with e-mails every time you log in if you use tools to improve your privacy

yep

getting done with them..just wish there was a viable alternative

joshbright: Thank you for that, I'm watching the video now.

in their support feedback e-mail, only the option "everything is fine" is a proper link. "i need further assistance" is some javascript thing that doesn't work here :p

I gotta say, I feel that using a hash that is then checked to see if it is unique as the unique_id for a user seems to be the way to go.

User's generally want to be able to freely change their username.

I've got a management command that's running a logger via Python's standard `logger = logging.getLogger(__file__)`

Is there a simple way to silence this logger unless there's an error, in which case we spit out all of the logging?

This is so that cron won't email us.

Or maybe we should run this command via cronic.

anyone super familiar with debug toolbar? I'm getting a strange error when it's enabled and I have an include in a particular template, same include on a different template works fine. unorderable types: int() < str() is the error. when I look at the context in the trace there is a dict called context_layers that is being populated and one of the keys is indeed an in not a string like the rest. Any ideas why that might be? (debug=1.9.1)

yellow

JordiGH: use an appropriate logging level?

moldy: How do I modify it?

For the duration of a management command, I mean.

something roughly like this (untested): https://dpaste.de/8wH6

JordiGH: lines 22 and 25 are the interesting ones

JordiGH: then set DJANGO_LOG_LEVEL from cron

and log with ``logger.error()`` or such

moldy: Hm, I think it's easier to just use cronic in that case.

v0lksman: i’ve used it in the past, but, im no expert. I can’t seem to tell what context_layers is, but, it sorta sounds like something django does internally. Is the thing that is a string in one include, and an int in another something you control, or, is it just some odd thing your seeing? Can you provide the traceback?

Hello everyone! I'm having a wild time with a specific encoding issue. when i try to enter data into a model field via the admin, and the data contains odd characters (in this case delta, permil and degree symbols) i get a 500 error. I obviously need to escape them, but when i use escape() or conditional_escape i get a mysql error ~ (1366, "Incorrect string value: '\\xCE\\xB41' for column 'abstract' at row 1")

JordiGH: cronic looks interesting indeed, i haven't used it yet

Heh, I haven't touched my hobby project so long, I was lucky to forget how big is undertaking it was )

sixtycycles: are you on python2 or 3? what encoding does your column/table have in mysql?

ah i guess they left =(

hm, we also have so new mechanic of url including?

Would it be a big deal to upgrade a codebase from 1.11 to 2.0?

mguy: probably not, the bigger job is being python 3 compatible

I'm upgrading 1.11 to 2.0 with changing auth user model now >_<