Hi,
2015-06-23 0:10 GMT+02:00 Nick Coghlan :
> Chiming in again since I wasn't clear on this aspect last time: I'd also be
> +1 on parallel APIs that handle the chaining.
>
> Since the auto-chaining idea seems largely unpopular, that suggests to me
> that a parallel set of APIs would be the most r
On 23.06.2015 03:58, Zachary Ware wrote:
> On Thu, Jun 4, 2015 at 10:51 AM, Maciej Fijalkowski wrote:
>> On Thu, Jun 4, 2015 at 4:32 PM, R. David Murray
>> wrote:
>>> OK, so what you are saying is that speed.python.org will run a buildbot
>>> slave so that when a change is committed to cPython,
On 22/06/2015 18:03, Zachary Ware wrote:
> As you may know, Steve Dower put significant effort into rewriting the
> project files used by the Windows build as part of moving to VC14 as
> the official compiler for Python 3.5. Compared to the project files
> for 3.4 (and older), the new project file
Hi Zack,
On 23.06.15 06:42, Zachary Ware wrote:
> On Mon, Jun 22, 2015 at 10:37 PM, Nick Coghlan wrote:
>> I'd suggest explicitly reaching out to the Stackless folks to get
>> their feedback. As I believe the switched to a newer compiler and VC
>> runtime for Windows a while back, I suspect it wi
On 23 June 2015 at 05:33, Nick Coghlan wrote:
>
> > Also, since classes inside functions are commonly used in unit tests (at
> > least mine :-), I worry that *any* changes in this behavior might break
> > working code (no matter how much that "working" could be considered an
> > accident, it's st
[Apologies for the cross-posting! -BAW]
For Ubuntu 15.10 (Wily Werewolf), we want to make Python 3.5 the default
Python 3 version. It's currently undecided whether we will keep Python 3.4 as
a supported version, but a lot of that depends on how easily an archive port
to Python 3.5 goes. Ideally,
