#django

hard-coding asset urls is what i'm trying to avoid

what is the best way to mock out a call to a model's get method? (i.e. model.objects.get(id=1))

bmonty: in tests, I assume you mean?

have you looked at factory-boy ?

FunkyBob: Yes for testing, no I haven't seen factory boy...looking now

bmonty: you'll love it :)

factory-boy and Mock

Installed django 2.7.6 32 bit sucessfully

Then did a startproject and my settings.py file was MUCH shorter than normal.

Has there been a change in the minimum settings.py created by startproject?

Make that v1.6 :)

yeah I notices that the settings file is much shorter now

T150: Yes, a number of settings were removed from the boilerplate file.

T150: yeah, 1.6's default settings is far more practical and short

parsed_data = {StringIO} < O.o what does it supposed to mean

Fuyou: that appears to be creating a set

from StringIO class?

yeah, odd...

but out of context, who can say...

In context it should be creating empty dict

I don't know where StringIO came

neither do I

Could 2to3 put it there???

Yeah, why it would

no idea... you've not told us even where it is

well, that is appeared in one of my views. Just used it and get error

StringIO was used there, but then I 2to3

ed it and replaced later it with BytesIO

I quite sure I didn't put in my dict

some weird shit is going on )))

people still use 2t3?

I just use six

Well, I wanted more diving into py3 so I thought it's okay

Fuyou: the most common approach I see is to write Py2 or Py3, then use six to make it compatible with the other

Understood v1.6 default settings.py has been shortened. Thank you.

Mine ends abruptly at STATIC_URL = '/static/'

Can someone do a quick startproject test and check for that?

It just seems way short and I'd like to know if it's like that for others.

FunkyBob, ok, thx for info

T150: yep, looks right to me

82 line

s

82 lines. Yes, exactly what I'm getting. Thanks for checking!

T150: It's short on purpose. It's not that settings have gone away, it's that their defaults are adequate, so they don't need to be there.

There have always been a number of settings that never showed up in the boilerplate settings.py file.

there's also a number of now-default values that weren't before

and I'm so glad they are now :)

Thanks Matt & Bob. Guess I didn't get the memo when they shortened it.

After years of seeing the old default, the new one look so chopped off.

it's a good idea to read the 1.6 release notes, there's some big stuff in tehre

hmm...

Hello

If an app called "x" has a model called "y", what's the name of corresponding table when model "y" is stored in database?

x_y

I guess I read somewhere in docs that the table is named as x_y (?)

Thanks FunkyBob!

hmm.. the more I learn about using reST/sphinx... the more I think I'm missing

or maybe it's just RTDs style

Django automatically adds a primary key field "id" to all models automatically...

When I specify a foreign key relationship, the relationship is to "id" field of the table... What if I want the relationship to point to some other field which isn't primary key but is guaranteed to be unique?

AmberJ: then I'd question your understanding of relations :P

AmberJ: nah, there's a way, mentined in the docs, to specify which field it relates to