Re: Must be my and and can't be my code -- tracing back a URL pattern type mismatch

OK, I've gotten time to touch the code again, applied your suggestion, but there is no apparent change in behavior. For the sake of argument, I'm including the stack trace again. I'm not sure where my good debugging entry point is here. -- You received this message because you are subscribed

Re: Must be my and and can't be my code -- tracing back a URL pattern type mismatch

.. > > On Sunday, 31 March 2019 04:31:42 UTC+2, Josh Marshall wrote: >> >> I'm helping out on a project, but am running into a paradox of a bug must >> existing in the code, but no project code is called. Not sure how to deal >> with this one. It looks

Re: Must be my and and can't be my code -- tracing back a URL pattern type mismatch

Identical behavior. On Sunday, March 31, 2019 at 12:42:17 AM UTC-4, jlgimeno71 wrote: > > > On Sat, Mar 30, 2019 at 7:31 PM Josh Marshall > wrote: > >> I'm helping out on a project, but am running into a paradox of a bug must >> existing in the code, but no proje

Must be my and and can't be my code -- tracing back a URL pattern type mismatch

I'm helping out on a project, but am running into a paradox of a bug must existing in the code, but no project code is called. Not sure how to deal with this one. It looks related to URL setup and the urls.py file is practically identical to the examples. Can anyone make sense of this stack