Regarding "forcing", the statement has a similar sentiment: "Third parties
may offer paid support for our projects on old Python versions for longer
than we support them ourselves. We won’t obstruct this, and it is a core
principle of free and open source software that this is possible." If Blue
With the release of IPython 5.0 LTS, it was mentioned as also being the
final Py2-compat release in the series with a reference to the "Python 3
Statement" https://python3statement.github.io/ Some of the prose in it
refers to just the Scientific Stack (Numpy, Scipy, MPL, et al.), but an
issue p
t; doesn't use.
>
> On Monday, March 7, 2016 at 11:04:48 AM UTC-5, Nick Timkovich wrote:
>>
>> By the presence of a "bits" measure in the documentation of the function
>> it seems to be known that it's a measure of interest. The benefit of adding
>>
uot;
> that
> calculates the length and then calls get_random_string?
> What would be the benefit of doing that in Django directly?
>
> Am 05.03.2016 um 00:15 schrieb Nick Timkovich:
> > Rather than guess at the appropriate string length to get some level of
> &g
Rather than guess at the appropriate string length to get some level of
security, I'd like to add a (minimum) bits of entropy argument to
get_random_string, so I could say something like get_random_string(bits=256)
and have it do the math for me: math.ceil(bits /
math.log2(len(allowed_chars))).
