Re: Epydoc failed to generate documentation for Django 1.5

On 04-04-13 05:19, Kevin Veroneau wrote: | Import failed (but source code parsing was successful). | Error: ImproperlyConfigured: Requested setting DATABASES, but settings are not configured. |You must either define the environment variable DJANGO_SETTINGS_MODULE or call |

Re: Kickstarter for Django Admin?

Hi, I already wanted to look at hyperadmin, but got caught up reading what HATEOAS is and how it works first ;) I do have one question if you don't mind: With a REST/HATEOS backend you'd export links with appropriate rel attributes to tell the client what we can do. So far so good, but let's

Extending the DATABASES = {'xx': {'NAME': construct to carry additional information and / or virtual names

Dear Gurus: At the bottom of this text there will be a question. In order for you to provide a quality answer to the question, you need more information. Perhaps a lot more information. The next few paragraphs will attempt to provide that. They will also be an introduction to a couple of

Re: Extending the DATABASES = {'xx': {'NAME': construct to carry additional information and / or virtual names

On Thu, Apr 4, 2013 at 10:10 AM, VernonCole wrote: > In order to meet these goals, is it reasonable to do this?: Are there > better alternatives? > > 1) Assume that a Proxy based connection will be acceptable for inclusion > in django? > Best way to mentally think of this

Re: Kickstarter for Django Admin?

Currently you get the links through a link collection provider object attached to state; state.links.get__links() which collects links from its parents (endpoint and resource) and returns an empty set if none exist. I have been thinking about re-factoring this to something more robust. I find

model query get_or_create() thread safety and uniqueness -- proposal for transactional commit before final get

Greetings Developers, Today at work I fixed a thread safety issue in our code whereby two threads were calling get_or_create on the same URL which has a uniqueness constraint. It was in some cases raising an IntegrityError in sentry even after I converted our atomically incorrect code to use

Re: model query get_or_create() thread safety and uniqueness -- proposal for transactional commit before final get

There was a discussion on the subject here . Le jeudi 4 avril 2013 23:23:43 UTC-4, Matteius a écrit : > > > Greetings Developers, > > Today at work I fixed a thread safety issue in our code whereby two > threads were