cx_Oracle 5.2.1 released

Hi all, A new version of the Oracle driver library was released. Highlights, as far as we're concerned, are support for Python 3.5 and for binding Booleans with Oracle 12. http://cx-oracle.readthedocs.org/en/latest/releasenotes.html Have fun, Shai.

Re: re-thinking middleware

I've updated DEP 5 with a new round of clarifications and tweaks based on the most recent feedback: https://github.com/django/deps/compare/62b0...master Carl -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" gro

Re: re-thinking middleware

On 01/10/2016 04:54 PM, Raphaël Barrois wrote: > I've got only one minor suggestion to the "backwards compatibility" > section of the DEP. > >> It currently states that "If the ``MIDDLEWARE`` setting is provided >> [...], the old ``MIDDLEWARE_CLASSES`` setting will be ignored. > > I suggest that,

Re: re-thinking middleware

On 01/11/2016 04:52 PM, Shai Berger wrote: > On Monday 11 January 2016 01:54:58 Raphaël Barrois wrote: >> I've got only one minor suggestion to the "backwards compatibility" >> section of the DEP. >> >>> It currently states that "If the ``MIDDLEWARE`` setting is provided >>> [...], the old ``MIDDLE

Re: re-thinking middleware

Hi Mat, On 01/12/2016 04:23 PM, Mat Clayton wrote: > +1 as well, this is really great work, on both patches! > > Modifying the middleware stack mid request would be very useful for us. > > We currently run 3 copies of the same code, with essentially different > urls.py and middlewares loaded, ea

Re: db.models.options help with a piece of code analysis.

Really, it's true! Thanks for help! -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googleg

Re: db.models.options help with a piece of code analysis.

FWIW, as Marteen pointed out, the `Meta` attribute is only available on abstract classes because of these lines . Simon Le lundi 18 janvier 2016 13:09:16 UTC-5, charettes a écrit :

Re: db.models.options help with a piece of code analysis.

Hi Elton, >From what I understand the line you pointed at doesn't delete the model `Meta` attribute but the `_meta.meta` attribute which makes it possible for `Bar.Meta` to subclass `Foo.Meta` even if `Foo.Meta.abstract is not True`. Simon Le lundi 18 janvier 2016 12:34:29 UTC-5, Elton Pereira

Re: db.models.options help with a piece of code analysis.

Hi Elton, Django makes the Meta class of abstract models available as Foo.Meta. This allows you to define common Meta options on the abstract base class, and inherit the base Meta in your concrete child models. So the above example won't work as you noted, but this will: class Foo(models.Model

Re: db.models.options help with a piece of code analysis.

Hello charettes! Analyzing the code further, I saw that it was impossible for the Bar Meta class inherits from Foo.Meta because when this code is executed, the Meta class ceases to exist because of this line

Re: db.models.options help with a piece of code analysis.

Thanks for help! -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post t