#django

clock's ticking :)

so that means I can't use typescript right now - okay

might be possible via a plugin

with it being 'native' in later versions

but anyway, tomorrow will probably be another full day of this stuff, so I'm off to bed

night

xBBTx, are you sure you're not talking about 0.19? 0.17 seems to have been released a year ago, https://github.com/systemjs/systemjs/tree/0.17.0

okay, night!

I'm trying to make this query using Django's ORM: https://paste.debian.net/444785/

I managed to make the subquery in that query using the ORM

Is there a way I can make a raw query using an already built query as a table, as a subquery?

not in a stable way methinks.

:-(

Anyone see anything wrong with using hashers.make_password() to store a hashed version of someone's password as a session variable and then later use it to register/create a new User?

I have a 2-step purchase flow, with the first step being account details (username/password) and second step being billing info. I want to store the account details in the first step (but not yet register a new User with them), and then if the user comes back, I want them to be able to just skip to the billing step because I have their account details already in the session.

Seems to be working fine in my early testing, but figured I'd ask here in case I'm missing something about why this is bad

dshap: from a UX POV, why ask for the password if not creating the user yet?

Also, you can't assume the session data will still be there when they complete the billing step.

Koterpillar: I don't actually create users until they convert i.e. finish BOTH steps

You can just create the user in an inactive state.

dshap: why do you ask for the password then?

mattmcc: I plan to check if it's there, and if it's not, take them back to the first step. But if it is there, take them straight to billing as a convenience & conversion-improvement method

That seems like more work than creating the user up front and leaving it inactive.

mattmcc: issue with that is, then let's say they come back on another computer/browser and want to sign up

mattmcc: it will say username already exists....and i don't have a good setup right now for an existing user account who hasn't added billing info yet

Well, then they wouldn't have the same session either.

You can look them up by email and continue on..

right, new computer = need to fill out the form again, can use the same username they did before

Or username, whatever you're using.

I think I have a plan for how this will all work, UX-included, but I'm asking mainly about the tech-perspective of using hashers.make_password to store a hashed password in the session, and then attaching it to a new User later on with my_user.password instead of my_user.set_password() like I normally do on registration.

that *should* work..right?

I'm getting a column user_id not unique error. However, I'm using get_or_create. Shouldn't it get the existing object? https://dpaste.de/osd6

dshap: traceback

sorry, surfnturf_: traceback

Anyone have a preference for hosting? Is Linode still good?

dshap: I see no way to exploit this but that's all I can say; someone with access to that session, if you are storing it clientside, might be able to register with the same password?

up: what I'm doing wrong if LANGUAGE_CODE is empty here: https://dpaste.de/iDjq

surfnturf_: the user matches but bt_customer_id does not

Koterpillar: hmm im not storing the actual session variables client side, but obviously there is a session ID...but if somoene got ahold of one of my users' cookies I'd be in trouble anyway :-P

oh ic. ok thx

where did you see that in the traceback?

surfnturf_: I did not; but since user matches, something else must not. The only other thing is bt_customer_id

ok. just trying to learn how to debug better

Hey folks, wondering if anyone has any good suggestions for this problem. I need to provide forms (as in, pen and paper rather than django) that have some fields automatically filled in. Ideally the form would be editable by end users (so think a doc, or a pdf) and use some simple templating (eg {{ user.first_name }}) any suggestions on how I could go about this?

Azelphur: pandoc will get you from HTML to DOC or DOCX (and PDF too but wkhtmltopdf is better here).

Koterpillar: probly is that HTML isn't really editable by end users, so starting from HTML isn't great

Azelphur: so you want the users to edit the template, or the output?

the template

they'll break ti

the output they just get sent, and fill in pen and paper

they'll break it

I suppose they would :)

advice: lock down the substitutions to simple USER_FIRST_NAME and replace that verbatim; for formatting, possibly Markdown (that can be converted by pandoc too)

Interesting idea

Markdown could certainly work :)

they'll still break it

so, you should have a preview

indeed

Anyone use Pycharm? I cannot get it to switch git branches....