On Tue, Nov 29, 2011 at 4:59 PM, Nadeem Vawda wrote:
> "liblzma-dev"; on Fedora I believe the correct package is "xz-devel".
"xz-devel" is right. I just verified a build of the new module on a
fresh F16 system.
--
Meador
___
Python-Dev mailing list
Congrats, this is an excellent feature.
On Wed, Nov 30, 2011 at 10:34 AM, Amaury Forgeot d'Arc
wrote:
> 2011/11/29 Nadeem Vawda
>>
>> I'm pleased to announce that as of changeset 74d182cf0187, the
>> standard library now includes support for the LZMA compression
>> algorithm
>
>
> Congratulation
I like this article on it:
http://semver.org/
The following snippets being relevant here:
Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards
compatible functionality is introduced to the public API. It MUST be
incremented if any public API functionality is marked as deprecated
2011/11/29 Nick Coghlan :
> On Wed, Nov 30, 2011 at 1:13 AM, Barry Warsaw wrote:
>> On Nov 29, 2011, at 01:59 PM, Antoine Pitrou wrote:
>>
>>>Well, that's why I think the version number components are not
>>>correctly named. I don't think any of the 2.x or 3.x releases can be
>>>called "minor" by
On Wed, Nov 30, 2011 at 1:13 AM, Barry Warsaw wrote:
> On Nov 29, 2011, at 01:59 PM, Antoine Pitrou wrote:
>
>>Well, that's why I think the version number components are not
>>correctly named. I don't think any of the 2.x or 3.x releases can be
>>called "minor" by any stretch of the word. A quick
2011/11/29 Nadeem Vawda
> I'm pleased to announce that as of changeset 74d182cf0187, the
> standard library now includes support for the LZMA compression
> algorithm
Congratulations!
> I'd like to ask the owners of (non-Windows) buildbots to install the
> XZ Utils development headers so that
On Tue, 29 Nov 2011 23:36:58 +0100
nadeem.vawda wrote:
> http://hg.python.org/cpython/rev/74d182cf0187
> changeset: 73794:74d182cf0187
> user:Nadeem Vawda
> date:Wed Nov 30 00:25:06 2011 +0200
> summary:
> Issue #6715: Add module for compression using the LZMA algorithm.
Cong
Hey folks,
I'm pleased to announce that as of changeset 74d182cf0187, the
standard library now includes support for the LZMA compression
algorithm (as well as the associated .xz and .lzma file formats). The
new lzma module has a very similar API to the existing bz2 module; it
should serve as a dro
Am 29.11.2011 13:46, schrieb Petri Lehtinen:
> Michael Foord wrote:
>> We tend to see 3.2 -> 3.3 as a "major version" increment, but that's
>> just Python's terminology.
>
> Even though (in the documentation) Python's version number components
> are called major, minor, micro, releaselevel and ser
On Nov 29, 2011, at 01:59 PM, Antoine Pitrou wrote:
>Well, that's why I think the version number components are not
>correctly named. I don't think any of the 2.x or 3.x releases can be
>called "minor" by any stretch of the word. A quick glance at
>http://docs.python.org/dev/whatsnew/index.html sh
On Tue, Nov 29, 2011 at 02:46:06PM +0200, Petri Lehtinen wrote:
> Michael Foord wrote:
> > We tend to see 3.2 -> 3.3 as a "major version" increment, but that's
> > just Python's terminology.
>
> Even though (in the documentation) Python's version number components
> are called major, minor, micro,
On Tue, 29 Nov 2011 14:46:06 +0200
Petri Lehtinen wrote:
> Michael Foord wrote:
> > We tend to see 3.2 -> 3.3 as a "major version" increment, but that's
> > just Python's terminology.
>
> Even though (in the documentation) Python's version number components
> are called major, minor, micro, relea
Nick Coghlan wrote:
> > So, in this context, if the tracker "create patch" diff from BASE, it
> > is not "safe" to merge changes from mainline to the branch, because if
> > so "create patch" would include code not related to my work.
>
> No, "Create Patch" is smarter than that. What it does (or tr
Michael Foord wrote:
> We tend to see 3.2 -> 3.3 as a "major version" increment, but that's
> just Python's terminology.
Even though (in the documentation) Python's version number components
are called major, minor, micro, releaselevel and serial, in this
order? So when the minor version component
14 matches
Mail list logo