On Tue, Mar 28, 2017 at 11:07 PM, Ned Deily wrote:
> On Mar 28, 2017, at 08:49, INADA Naoki wrote:
>> Currently, changelog of Python 3.7a1 [1] contains changes between
>> 3.6b1 and 3.7a1.
>> So lot's of bugfixes are listed twice or more in changelog.
>> For example, "bpo-28258: Fixed build with E
On Mar 28, 2017 10:54 AM, "Steve Dower" wrote:
On 28Mar2017 1035, Paul Moore wrote:
> On 28 March 2017 at 18:05, Glenn Linderman wrote:
>
>> Somewhere I got the idea that extension authors were supposed to build
>> against the n.m.0 releases, expressly so that the extensions would then be
>> co
On 28Mar2017 1035, Paul Moore wrote:
On 28 March 2017 at 18:05, Glenn Linderman wrote:
Somewhere I got the idea that extension authors were supposed to build
against the n.m.0 releases, expressly so that the extensions would then be
compatible with the whole n.m.x series of releases. Did I drea
On 28 March 2017 at 18:05, Glenn Linderman wrote:
> Somewhere I got the idea that extension authors were supposed to build
> against the n.m.0 releases, expressly so that the extensions would then be
> compatible with the whole n.m.x series of releases. Did I dream that?
I've certainly never hear
On Mon, Mar 20, 2017 at 11:30 AM, Oleg Nesterov wrote:
> Hello,
>
> Let me first clarify, I do not claim this is a bug, I am trying to learn
> python and now I trying to understand yield-from.
Given that you haven't gotten a response here, you may want to take
this over to the core-mentors...@pyt
On 3/28/2017 9:18 AM, Paul Moore wrote:
On 28 March 2017 at 12:24, Miro Hrončok wrote:
I'd like some clarification on what ABI compatibility we can expect.
* Should the ABI be stable across patch releases (so calling
PySlice_AdjustIndices from an existing macro would be a bug)?
* Should the
On Mar 28, 2017 8:29 AM, "Serhiy Storchaka" wrote:
On 28.03.17 14:24, Miro Hrončok wrote:
> However, recently we found an issue with this approach [1]: an extension
> module built against Python 3.6.1 cannot be run on Python 3.6.0, because
> it uses a macro that, in 3.6.1, uses the new PySlice_A
On 28 March 2017 at 12:24, Miro Hrončok wrote:
> I'd like some clarification on what ABI compatibility we can expect.
> * Should the ABI be stable across patch releases (so calling
> PySlice_AdjustIndices from an existing macro would be a bug)?
> * Should the ABI be forward-compatible within a m
On 28.03.17 14:24, Miro Hrončok wrote:
However, recently we found an issue with this approach [1]: an extension
module built against Python 3.6.1 cannot be run on Python 3.6.0, because
it uses a macro that, in 3.6.1, uses the new PySlice_AdjustIndices
function.
The macro expanding to PySlice_Ad
Hi,
as per [0], ABI of the C API is generally not stable and the binary
compatibility may break between versions. It is hard from the text to
know whether it talks about minor versions (such as 3.6 vs 3.5) or patch
versions (such as 3.6.1 vs 3.6.0).
In Fedora we currently only keep track abo
On 3/28/2017 8:49 AM, INADA Naoki wrote:
Currently, changelog of Python 3.7a1 [1] contains changes between
3.6b1 and 3.7a1.
I think the changelog for x.(y+1).0a1 should start with the released
x.y.0. This used to be the case (with perhaps a few exceptions) when
x.y.0 was not branched off un
On Mar 28, 2017, at 08:49, INADA Naoki wrote:
> Currently, changelog of Python 3.7a1 [1] contains changes between
> 3.6b1 and 3.7a1.
> So lot's of bugfixes are listed twice or more in changelog.
> For example, "bpo-28258: Fixed build with Estonian locale..." are
> listed under 3.5.3rc1,
> 3.6.0b2
Steven, thanks for verifying bug on *nix.
On 3/28/2017 2:00 AM, Martin Panter wrote:
On 28 March 2017 at 03:11, Steven D'Aprano wrote:
On Mon, Mar 27, 2017 at 10:33:44PM -0400, Terry Reedy wrote:
https://bugs.python.org/issue29926 was opened as an IDLE issue, which
means that most watching th
Hi.
Currently, changelog of Python 3.7a1 [1] contains changes between
3.6b1 and 3.7a1.
So lot's of bugfixes are listed twice or more in changelog.
For example, "bpo-28258: Fixed build with Estonian locale..." are
listed under 3.5.3rc1,
3.6.0b2 and 3.7.0a1.
[1] https://docs.python.org/3.7/whatsnew
14 matches
Mail list logo
