It was tried in https://code.djangoproject.com/ticket/27878 but it caused
problems, particularly on Windows.
On Friday, April 6, 2018 at 6:35:50 PM UTC-4, Josh Smeaton wrote:
>
> I think you're right and PEP394 is the relevant text:
> https://www.python.org/dev/peps/pep-0394/
>
> TL;DR
>
> For n
I think you're right and PEP394 is the relevant
text: https://www.python.org/dev/peps/pep-0394/
TL;DR
For now, *python* should refer to python2 and *python3* should be used to
refer to python 3.
On Saturday, 7 April 2018 07:07:35 UTC+10, Bobby Mozumder wrote:
>
> The header of manage.py has: #
The header of manage.py has: #!/usr/bin/env python
Shoudn’t it be: #!/usr/bin/env python3
Since 2.0 is now only Python3. Both my Mac OS & FreeBSD environments have
Python 3.5+ as “python3". (I’m not sure about Linux or other environments).
Is that a bug I need to file?
-bobby
--
You received
The issue with obscuring any values that equal the sensitive variable is
that functions can do arbitrary things to the data, e.g. splitting a name
into first and last, combining first and last name strings into a full
name, stripping whitespace, generating a SQL query with the sensitive data,
etc.
To the best of my knowledge JetBrains fundled the money to Django for that
specific purpose -- so yes the funding should be here if needed. That said,
there is no decission on a) whether we actually want type hints and b) if
the should be inline or stubs. Those two points have to be cleared firs
My only concern is that it would greatly reduce the usefulness of the
exception reporter, and might lead to people removing the
sensitive_variables decorator in order to see exception tracebacks.
Perhaps rather than obscure all local variables below the decorated
function, we could obscure any var
+1 Seems sensible to me too! Maybe the common arguments can even be put
under a header like 'common arguments', if argparse allows that.
On 6 April 2018 at 07:31, Carlton Gibson wrote:
> Hi David.
>
> Your suggestion seems sensible, good even. (To me at least. 🙂)
>
> If you'd be happy to do the
Hi Tim, do you know if JetBrains still willing to fund the project as the
upcoming django 2.1 will only support python 3.5+ that pave the way for
inline annotations.
On Wednesday, August 17, 2016 at 11:41:03 PM UTC+10, Tim Graham wrote:
>
> The JetBrains announcement that they want to fund the p
