#django

it seems like it is adding routes anyway and just excluding them from worker

even with --only-channel

well that's better than nothing

i think you should open an issue, imho this should be configurable

ok

hmm, i guess routing and listening for work is not the same issue

ideally i would like no one to listen and no routes to exist

on those default channels

yeah, i understood but i have no clue

if you want to +1 me :)

Sometimes when I run tests with fixtures, I get something like django.db.utils.InterfaceError: Problem installing fixture '/home/lynoure/PycharmProjects/usertools2/useraccounts/fixtures/test-fixtures.json': connection already closed

Seems like there is some shifting limit to how many TestCases with fixtures I can run in one go

fleetfox, where i do stick my overriden Route?

max3: sorry, i have no clue either, Layer seems to be coupled to it

yes

channels need work :)

monkey patch it is :)

there's #django-channels btw

ah you found it

does it have any traction? It was mostly dead when i tried

Any idea how I could solve that "connection already closed" thing?

Lynoure: when exception occurs in test setup it doesn't know how to recover

and you probably shouldn't do fixtures, try factories

def no_default_routes(self, *args, **kwargs): pass

:)

wow it has js client now

fleetfox: why?

fleetfox: I mean, other than this I'm really happy with the fixtures

because they are fragile and half assed :<

fleetfox: easy to use, mainstream django support, fast enough with the amounts of data I use, nicely documenting the test data needed

well the issue with support is it's iffy. If you aks for fixture support here pople will probably tell you to not use them :)

anyways whatever works for you

fleetfox: Well, what would be your recommended starting point docs wise for factories for someone who currently has a small set of fixtures needed by multiple apps and just wants to hassle-free move to using factories?

i'm using factoryboy, i don't really have strong opinions regarding fixtures, just reciting what i've seen in here

fleetfox: any idea why factories are not in django itself? Or if there is any plans for that?

it seems to be out of scope. Testing is very opinioned topic

fleetfox: most things in programming are :)

python just is blessed enough to avoid some of the topics, such as tabs vs spaces and other formating, by the virtue of syntax and PEP8

Unit testing custom fields. I assume I need to create a model with the field. It's not part of the app, so my guess is it's a test only model

I google'd around and found some examples, and it looks like I can create the model on the fly in the test setup.

however that seems to be missing in django 1.10+

connection.creation.sql_create_model

where else could I look for that or am I on the wrong track entirely?