Hi,
You may have come across the (relatively) new subresource integrity
(SRI)[1] security feature that is available in Chrome and Firefox (its
coming to Edge[2] and Safari[3]) - it enables a hash to be provided as an
attribute on a linked JavaScript or CSS tag that the browser can test
against
A difference is that a deprecation starting in 2.2 is in 2 releases (2.2,
2.3) while the deprecation starting in 3.0 is in 3 releases (3.0, 3.1, 3.2).
On Wednesday, January 25, 2017 at 10:30:40 AM UTC-5, Aymeric Augustin wrote:
>
> Hello Tim,
>
> On 25 Jan 2017, at 16:11, Tim Graham >
> wrote:
>
Hi all,
I have a use case where I need to use a custom reverse manager (Or Related
Manager?). Docs can be found here:
https://docs.djangoproject.com/en/1.10/topics/db/queries/#using-custom-reverse-manager
I was wondering if a default custom reverse manager exists. So instead of
having to explic
Hello Tim,
On 25 Jan 2017, at 16:11, Tim Graham wrote:
> - in Django 2.2 for removal in Django 3.1 (August 2020)
> - in Django 3.0 for removal in Django 4.0 (Dec. 2021)
Either option seems fine to me.
Are there advantages to starting the deprecation in a LTS (2.2) vs. in the
release that fol
If we go the deprecation route, when do you want to start those
deprecations? If deprecation start in Django 2.0, the removal happens in
Django 3.0 (December 2019). Do you think third-party apps will drop support
for Python 2 by then?
For removal at a later date, the deprecations could start:
-
For me, testing involves updating tests of third-party apps and my own
Django projects to run against the new version.
On Wednesday, January 25, 2017 at 7:37:48 AM UTC-5, Vimarsh Chaturvedi
wrote:
>
> Hey,
>
> I have recently started trying to contribute to Django.
> Wanted to know how can one
Try adding this to both entries in your DATABASES test settings:
'TEST': {
'CHARSET': 'utf8',
'COLLATION': 'utf8_general_ci',
},
On Wednesday, January 25, 2017 at 7:36:41 AM UTC-5, JA Robson wrote:
>
> hi, I'm on OSX (Sierra), am running a local MySQL, version 5.7.17, running
> django '2
hi, I'm on OSX (Sierra), am running a local MySQL, version 5.7.17, running
django '2.0.dev20170122010200', and python mysqlclient 1.3.9 and 1.3.1 (I
tried both versions).
when I try to run the tests, it consistently fails with this stack trace
Traceback (most recent call last):
File
"/Users/
> On 24 Jan 2017, at 19:25, Tim Graham wrote:
>
> Okay, I updated the PR to use a deprecation. I'd rather not complicate things
> with an accelerated deprecation.
+1
I think that’s the right way.
--
Aymeric.
--
You received this message because you are subscribed to the Google Groups
"Dja
Hey,
I have recently started trying to contribute to Django.
Wanted to know how can one help in testing for the final release?
Using the new features in small projects or is there a formal procedure for
testing?
On Wednesday, January 18, 2017 at 6:48:18 AM UTC+5:30, Tim Graham wrote:
>
> We
10 matches
Mail list logo
