>> In principle, this is fine with me, so go ahead.
>
> Done.
Thanks for looking into these!
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/option
Martin v. Löwis schrieb:
>> I would like to apply fixes for some CVE's which are addressed in 2.5 but not
>> yet in 2.4. this would include
>>
>> CVE-2007-4965
>> CVE-2008-1679
>> CVE-2008-1721
>> CVE-2008-2315
>> CVE-2008-3144
>> CVE-2008-1887
>> CVE-2008-4864
>
> Can you identify the revisions t
> I would like to apply fixes for some CVE's which are addressed in 2.5 but not
> yet in 2.4. this would include
>
> CVE-2007-4965
> CVE-2008-1679
> CVE-2008-1721
> CVE-2008-2315
> CVE-2008-3144
> CVE-2008-1887
> CVE-2008-4864
Can you identify the revisions that would need backporting?
I could o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Klose wrote:
> Martin v. Löwis schrieb:
>> Within a few weeks, we will release Python 2.5.3. This will be the last
>> bug fix release of Python 2.5, afterwards, future releases of 2.5 will
>> only include security fixes, and no binaries (for W
Martin v. Löwis schrieb:
> Within a few weeks, we will release Python 2.5.3. This will be the last
> bug fix release of Python 2.5, afterwards, future releases of 2.5 will
> only include security fixes, and no binaries (for Windows or OSX) will
> be provided anymore (from python.org).
>
> In princ
-On [20081020 19:07], A.M. Kuchling ([EMAIL PROTECTED]) wrote:
>This fixes a memory leak in itertools.chain(), which was greatly
>changed between 2.5 and 2.6, and the patch was to code not present in
>2.5. Are you sure this bug affected 2.5 at all?
No, my mind was caught up between versions, so R
> Since we tripped over these with Trac/Genshi we would appreciate if the
> following could be applied (if not already):
Ok, I've marked them as candidates for a backport.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyt
yOn Mon, Oct 20, 2008 at 11:57:36AM +0200, Jeroen Ruigrok van der Werven wrote:
> http://bugs.python.org/issue2231
This fixes a memory leak in itertools.chain(), which was greatly
changed between 2.5 and 2.6, and the patch was to code not present in
2.5. Are you sure this bug affected 2.5 at all?
Martin,
-On [20081007 09:27], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>Within a few weeks, we will release Python 2.5.3. This will be the last
>bug fix release of Python 2.5, afterwards, future releases of 2.5 will
>only include security fixes, and no binaries (for Windows or OSX) will
>be pr
Martin v. Löwis wrote:
>> May I suggest http://bugs.python.org/issue1040026 ?
>>
>> It has a fairly simple patch (posixmodule.diff), a new test
>> (test_posix5.PATCH), and it fixes a bug that makes os.times unusable on
>> common platforms.
>
> In the current form, I'm skeptical about applying this
> May I suggest http://bugs.python.org/issue1040026 ?
>
> It has a fairly simple patch (posixmodule.diff), a new test
> (test_posix5.PATCH), and it fixes a bug that makes os.times unusable on
> common platforms.
In the current form, I'm skeptical about applying this patch to 2.5.2.
It has the po
Martin v. Löwis wrote:
>> Just to emphasize this, "changes" means "bugfixes". (I'm mentioning this
>> mainly because of the people who joined for 2.6/3.0.) For more info,
>> see PEP6 about bugfix releases:
>> http://www.python.org/dev/peps/pep-0006/
>
> Thanks for clarifying this. For the last 2
Allow me to suggest that these get some attention:
http://bugs.python.org/issue3677
http://bugs.python.org/issue3367
Kristján
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.p
On Tue, Oct 07, 2008 at 09:27:24AM +0200, "Martin v. Löwis" wrote:
> Within a few weeks, we will release Python 2.5.3. This will be the last
> bug fix release of Python 2.5, afterwards, future releases of 2.5 will
> only include security fixes, and no binaries (for Windows or OSX) will
> be provide
> Just to emphasize this, "changes" means "bugfixes". (I'm mentioning this
> mainly because of the people who joined for 2.6/3.0.) For more info,
> see PEP6 about bugfix releases:
> http://www.python.org/dev/peps/pep-0006/
Thanks for clarifying this. For the last 2.5.x release in particular, we
On Tue, Oct 07, 2008, "Martin v. L?wis" wrote:
>
> In principle, the release will include all changes that are already on
> the release25-maint branch in subversion [1]. If you think that specific
> changes should be considered, please create an issue in the bug tracker
> [2], and label it with th
Within a few weeks, we will release Python 2.5.3. This will be the last
bug fix release of Python 2.5, afterwards, future releases of 2.5 will
only include security fixes, and no binaries (for Windows or OSX) will
be provided anymore (from python.org).
In principle, the release will include all ch
17 matches
Mail list logo
