Can we provide a setting that lets you switch between the two? Then you can let
developers choose their poison?
On Friday, November 11, 2011 at 6:25 PM, hcarvalhoalves wrote:
> On 10 nov, 18:05, Paul McMillan wrote:
> > > There's no reason to not use JSON by default since it's adequate for
> >
send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
t the end for every model you think you touched).
>>
>> However, the patch Donald linked would be a lot easier to emulate, so I'm
>> not that against it.
>>
>> Andrew
>>
>>
>> On Sat, May 18, 2013 at 7:15 PM, Donald Stufft wrote:
>>&g
an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
This sounds ok to me.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
.
> Visit this group at http://groups.google.com/group/django-developers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
What do you mean by "clustering by default". CLUSTER is a one time operation.
You use to to arrange the orders of the row in a tabl
On May 21, 2013, at 12:11 PM, peter wrote:
> +1 on pre_syncdb
>
> On Tuesday, May 21, 2013 8:29:49 AM UTC-7, Shai Berger wrote:
> On Tuesday 21 May 2013, Donald Stufft wrote:
> > I run migrations in test. How else will you know your db reflects reality
> > :/
>
from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
I vote #3.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
opers?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
I think trying to get anyone to change their posting habit is a futile effort.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
gt;
Part of the reasoning of my original Change to make decorators classes was that
it enabled much easier customization of them. Currently you basically either
hope there was an option for doing what you wanted, or you copy/paste the
entire thing and modify it.
Using a class lets yo
elopers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
Backwards compatibility is easy. Just add a new hasher.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
essage because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.co
can be
> set in location.
Yes, any response which does not include secret data can be compressed.
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
el is going to be important. The application knows what
*kind* of data exists in a response body and wether or not it is safe to
compress it. The web server does not (except by crude heuristics such as path).
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04
is probably going to be one of the biggest blockers. Without CI it's
up to the merging developers to run the tests on all the combinations of stuff
we support which isn't the easiest or the quickest thing to setup and maintain.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA /
.
If anyone made any commits in the last hour you should probably double check to
make sure they are there. I'm pretty sure we got it restored but doesn't hurt
to double check.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
t; "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> For more options, visit https://groups.google.com/groups/opt_out.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
ely, but who knows).
According to Thomas Porin in the context of bcrypt pre-hashing the password is
fine (and we already do this in Django 1.6). I see no reason the same wouldn't
hold true for PBKDF2.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F
em. Moving away from pickle as the default serialization engine
ensures this property for the storage of session data.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-deve
7;s fast enough that it doesn't negatively
impact your site but as slow as possible otherwise. The higher the work
factor/iterations the harder it is to brute force, but the more negative
impact each login has.
I would tune bcrypt or PBKDF2 down before I implemented this custom
scheme.
--
The recommended build tool at the moment is setuptools.
It's up to the individual project to decide if they think the install story for
setutpools pre 3.4 is appropriate for them. This'll get better in general in
the future with MSI installers for setuptools and pip
> On Nov 24, 2013, at 2:37
ail to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msg
On Dec 4, 2013, at 5:51 PM, Florian Apolloner wrote:
> On Wednesday, December 4, 2013 11:20:39 PM UTC+1, Donald Stufft wrote:
> entry points are kinda wonky with pip 1.4, pip 1.5 makes them sane. You would
> not need a Windows specific Wheel with pip 1.5
>
> Is there a test-pyp
st to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAG_XiSBmOU%3D4orZnW13bw-ZLT_O416unynhtnQ9%3DhgPtL9Bbtw%40mail.gmail.com.
> For more options, visit https://groups.google.com/groups/opt_out.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.googl
rt 3.2?
>
> Donald might be able to offer better hard numbers based on e.g. PyPI
> usage, but my impression is that usage of 3.2 is very low, and dropping
> it for 1.8 would not be a major problem.
These numbers are about a month old, but https://gist.github.com/dstufft/8455306
>
Accepted and it stays that way until it gets implemented and
committed. Then it changes from accepted to final and the PEP process is done.
One thing i’m not sure of, how is DEPs going to work without a BDFL? Generally
they are used to get feedback and provide a clear concise argument to the BDFL
googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/5fab23be-1411-4813-bfbe-e
or the registration system
since generally most pieces of a site do not interact with the
registration system, especially not at the level as they would for
the generic concept of users or database migrations.
--
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9
ipt would break
with this setting although i’m inclined to say you shouldn’t change
the setting in that case.
--
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
--
You received this message because you are subscribed to the Google Groups
"Django de
On August 3, 2014 at 9:48:53 PM, Adam Brenecki (adambrene...@gmail.com) wrote:
> The patch I've written implements this mitigation, with one difference:
> instead of using xor, it uses a Vigenère cipher (as suggested by FunkyBob),
> as xor was creating non-printable characters which caused problems
I think we could
just pull permissions from GitHub?
---
Donald Stufft
PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving
d/django-developers/2d66a232-1f19-4bcc-8178-7e1e060f497b%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message be
ible lower case alpha numeric of 6
characters or less in under a minute on a single regular desktop/server.. I
don’t believe the distinction is useful.
---------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
--
You received this message
s happen to use md5(md5(pass) + md5(pass)) for passwords?
You can implement them still sure, there’s nothing stopping you.
You can also do bcrypt(md5(md5(pass) + md5(pass)) and then you’ve fixed the
issue without needing to issue a password reset.
-
Donald Stufft
PGP: 0x6E3
vial to migrate the database to make the hashed
password conform to the format.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
--
You received this message because you are subscribed to the Google Groups
"Django developers (Cont
, at least from
Python, it’s not any harder to connect to a TLS’d Redis server.
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
--
You received this message because you are subscribed to the Google Groups
"Django developers (Co
g at this specific thing too closely, maybe it’s time for Django
to gain a required dependency instead of bundling or reinventing everything?
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
--
You received this message because you
n ImageField, or
bcrypt, etc. Having ``pip install Django`` work but not ``pip install Django
psycopg2`` when you’re running a site that uses PostgreSQL doesn’t get you
anything extra there.
-
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 D
but nice quality of life things are:
* Massively reduced verbosity on install.
* Nicer progress bars.
> Anyway as long as Django is installed in a virtualenv this shouldn't be too
> much of an issue, but I think we should expect some issues from the users and
> these should
P/Websocket and you don't have to go and
teach say, Erlang how to ASGI.
[1] This gets exposed in a variety of ways in different servers. In gunicorn it
shows up as a SystemExit exception, in uWSGI I believe it shows up as an
IOError. In something like Twisted or AsyncIO it would
> On May 6, 2016, at 1:45 PM, Andrew Godwin wrote:
>
> Want to just cover a few more things I didn't in my reply to Aymeric.
>
> On Fri, May 6, 2016 at 9:11 AM, Donald Stufft <mailto:don...@stufft.io>> wrote:
>
> In short, I think that the message bus add
d a queue to allow
calling sync user code from an async process, you just use the primitives
provided by the async framework.
-----
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
--
You received this message because you are subscribed to the Goog
l to install as a pure python library like pytz.
[1] Using the now public metrics database.
—
Donald Stufft
--
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 s
contains more than
> 100 characters and that isn’t a joke. How would it fit on a passport?
See #6 of
https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
—
Donald Stufft
--
You received this message because you are subscribed to the Google Groups
"Django
101 - 146 of 146 matches
Mail list logo
