In article ,
Terry Reedy wrote:
>Aahz wrote:
>>
>> Um, what? You mean 3.1rc1, right? Nevertheless, my understanding is
>> that 2.7 is mostly restricted to code landed in 3.1, so your second
>> statement is roughly correct.
>
>My understanding is that 2.7 will come out about the same time as 3.2
On Jun 6, 5:16 am, Steven D'Aprano wrote:
> On Sat, 06 Jun 2009 01:47:21 +0200, Christian Heimes wrote:
> > Terry Reedy wrote:
> >> A wrapper could go on PyPI now so it can be tested in use *before*
> >> going in the stdlib. No commit or pre-review needed either.
>
> > Here you gohttp://pypi.pyth
On Sat, 06 Jun 2009 01:47:21 +0200, Christian Heimes wrote:
> Terry Reedy wrote:
>> A wrapper could go on PyPI now so it can be tested in use *before*
>> going in the stdlib. No commit or pre-review needed either.
>
> Here you go http://pypi.python.org/pypi/md6
>
> It's still a bit rough, total
Aahz wrote:
Um, what? You mean 3.1rc1, right? Nevertheless, my understanding is
that 2.7 is mostly restricted to code landed in 3.1, so your second
statement is roughly correct.
My understanding is that 2.7 will come out about the same time as 3.2
and will contain 3.2 backports also. New f
Aahz wrote:
> Um, what? You mean 3.1rc1, right? Nevertheless, my understanding is
> that 2.7 is mostly restricted to code landed in 3.1, so your second
> statement is roughly correct.
Oh, d...! Of course you are right, Aahz. As far as I can remember 2.7
will only contain backports of 3.1 feature
Christian Heimes wrote:
...
2.7rc1 is already out. There is no way a new piece of code will land in
the 2.7 release.
Christian
3.1rc1 is out, but 2.7 is not even in alpha.
See pep 373 for the 2.7 schedule; 3.1's schedule is on pep 375.
--Scott David Daniels
scott.dani...@acm.org
--
http://ma
In article ,
Christian Heimes wrote:
>Terry Reedy schrieb:
>> Christian Heimes wrote:
>>>
>>> Somebody has to write and add a md6 wrapper to the standard library.
>>> It's going to take some time, at least 18 months until Python 2.8 and
>>
>> 2.7 is next
>
>2.7rc1 is already out. There is no wa
Terry Reedy wrote:
> A wrapper could go on PyPI now so it can be tested in use *before* going
> in the stdlib. No commit or pre-review needed either.
Here you go http://pypi.python.org/pypi/md6
It's still a bit rough, totally untested but it should work.
Christian
--
http://mail.python.org/ma
Terry Reedy schrieb:
> Christian Heimes wrote:
>> mik...@gmail.com schrieb:
>>> As every one related to security probably knows, Rivest (and his
>>> friends) have a new hashing algorithm which is supposed to have none
>>> of the weaknesses of MD5 (and as a side benefit - not too many rainbow
>>> ta
Robert Kern wrote:
On 2009-06-05 16:09, mik...@gmail.com wrote:
It's not that I need it, I can sure use it. I can also write a wrapper
myself.
My secret agenda is too see if other people want it and write it as an
addition to the standard lib, thus wetting my feet in Python Core
Development wi
Christian Heimes wrote:
mik...@gmail.com schrieb:
As every one related to security probably knows, Rivest (and his
friends) have a new hashing algorithm which is supposed to have none
of the weaknesses of MD5 (and as a side benefit - not too many rainbow
tables yet). His code if publicly availab
On 2009-06-05 16:09, mik...@gmail.com wrote:
On Jun 5, 11:46 pm, Christian Heimes wrote:
mik...@gmail.com schrieb:
As every one related to security probably knows, Rivest (and his
friends) have a new hashing algorithm which is supposed to have none
of the weaknesses of MD5 (and as a side bene
On Jun 5, 11:46 pm, Christian Heimes wrote:
> mik...@gmail.com schrieb:
>
> > As every one related to security probably knows, Rivest (and his
> > friends) have a new hashing algorithm which is supposed to have none
> > of the weaknesses of MD5 (and as a side benefit - not too many rainbow
> > tab
mik...@gmail.com schrieb:
> As every one related to security probably knows, Rivest (and his
> friends) have a new hashing algorithm which is supposed to have none
> of the weaknesses of MD5 (and as a side benefit - not too many rainbow
> tables yet). His code if publicly available under the MIT li
As every one related to security probably knows, Rivest (and his
friends) have a new hashing algorithm which is supposed to have none
of the weaknesses of MD5 (and as a side benefit - not too many rainbow
tables yet). His code if publicly available under the MIT license.
Is there a reason not to a
15 matches
Mail list logo
