On Tue, Oct 2, 2018 at 8:54 PM Michael Felt wrote:
>
>
>
> On 10/2/2018 4:45 PM, Erik Bray wrote:
> > Michael, if there are any PRs you want to point me to that I might be
> > able to help review please do.
> A little trick I learned:
> https://github.com/python/cpy
On Tue, Oct 2, 2018 at 6:41 PM Simon Cross
wrote:
>
> Are there any core devs that Michael or Erik could collaborate with?
> Rather than rely on adhoc patch review from random core developers.
>
> Michael and Eric: Question -- are you interested in becoming core
> developers at least for the purpo
On Tue, Oct 2, 2018 at 3:53 AM Tres Seaver wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/01/2018 06:41 PM, Michael Felt wrote:
>
> > And, while you may not give a damn about anything other than Windows,
> > macos and/or Linux - there are other platforms that would like a
> >
On Wed, Sep 5, 2018 at 4:32 PM Paul Moore wrote:
>
> On Wed, 5 Sep 2018 at 14:47, Zachary Ware
> wrote:
> >
> > On Wed, Sep 5, 2018 at 6:23 AM Antoine Pitrou wrote:
> > > On Wed, 5 Sep 2018 11:03:48 +0100
> > > Paul Moore wrote:
> > > > On Wed, 5 Sep 2018 at 10:55, Victor Stinner wrote:
> > >
On Fri, Aug 10, 2018 at 6:49 PM Steve Dower wrote:
>
> On 10Aug2018 0354, Erik Bray wrote:
> > Thanks! I'm not sure what you mean by "on other OS's" though. Do you
> > mean other OS's that happen to use Windows-style PE/COFF binaries?
> > Bec
On Thu, Aug 9, 2018 at 7:21 PM Steve Dower wrote:
>
> On 09Aug2018 0818, Erik Bray wrote:
> > On Mon, Aug 6, 2018 at 8:11 PM Eddie Elizondo wrote:
> >> 3) Special case the initialization of PyType_Type and PyBaseObject_Type
> >> within PyType_Ready to now make all
On Mon, Aug 6, 2018 at 8:11 PM Eddie Elizondo wrote:
>
> Background:
>
> Through the implementation of an alternate runtime I've been poking around
> some of the class initialization routines and I found out that there was a
> subtle bug with PyType_Ready and the header initializer PyVarObject_H
On Mon, Jul 30, 2018 at 5:26 PM Nick Coghlan wrote:
>
> On 26 July 2018 at 02:13, Erik Bray wrote:
> > I think a new approach that might be more practical for actually
> > getting this platform re-supported, is to go ahead and add a CI build,
> > and just skip all kn
On Sat, Jul 21, 2018 at 6:30 PM Jeroen Demeyer wrote:
>
> Hello,
>
> I finally managed to get some real-life benchmarks for why we need a
> faster C calling protocol (see PEPs 576, 579, 580).
>
> I focused on the Cython compilation of SageMath. By default, a function
> in Cython is an instance of
On Wed, Nov 8, 2017 at 3:39 PM Erik Bray wrote:
>
> Hi folks,
>
> As some people here know I've been working off and on for a while to
> improve CPython's support of Cygwin. I'm motivated in part by a need
> to have software working on Python 3.x on Cy
On Mon, Apr 16, 2018 at 4:49 AM, Shell Xu wrote:
> Well, I'm not sure weather or not this is what you're looking for, but pep-8
> (https://www.python.org/dev/peps/pep-0008/) suggest like this:
>
> For Python 3.0 and beyond, the following policy is prescribed for the
> standard library (see PEP 313
On Tue, Dec 26, 2017 at 3:00 PM, Benjamin Peterson wrote:
> I imagine Cython already takes care of this?
This appears to have a distinct purpose, albeit not unrelated to
Cython. The OP's program would generate boilerplate C code for
extension types the rest of which would perhaps be implemented
Sorry, completely fat-fingered my autocomplete and sent to to wrong list.
On Tue, Dec 19, 2017 at 12:12 PM, Erik Bray wrote:
> Hi all,
>
> I have a ticket [1] that's hung up on a failure in one doctest in the
> form of sage.doctest.sources.FileDocTestSource._test_enough_doctes
Hi all,
I have a ticket [1] that's hung up on a failure in one doctest in the
form of sage.doctest.sources.FileDocTestSource._test_enough_doctests.
This test has been there since, it seems, as long as the current
doctest framework has been in place and nobody seems to have
questioned it. Its exp
On Wed, Nov 8, 2017 at 5:28 PM, Zachary Ware
wrote:
> On Wed, Nov 8, 2017 at 8:39 AM, Erik Bray wrote:
>> a platform--in particular it's not clear when a buildbot is considered
>> "stable", or how to achieve that without getting necessary fixes
>> merged int
Hi folks,
As some people here know I've been working off and on for a while to
improve CPython's support of Cygwin. I'm motivated in part by a need
to have software working on Python 3.x on Cygwin for the foreseeable
future, preferably with minimal graft. (As an incidental side-effect
Python's t
On Fri, Sep 8, 2017 at 4:37 PM, Nick Coghlan wrote:
> On 8 September 2017 at 00:30, Masayuki YAMAMOTO
> wrote:
>> Hi folks,
>>
>> I submit PEP 539 third draft for the finish. Thank you for all the advice
>> and the help!
>
> Thank you Erik & Yamamoto-san for all of your work on this PEP!
>
> The
On Thu, Aug 31, 2017 at 10:16 AM, Masayuki YAMAMOTO
wrote:
> Hi python-dev,
>
> Since Erik started the PEP 539 thread on python-ideas, I've collected
> feedbacks in the discussion and pull-request, and tried improvement for the
> API specification and reference implementation, as the result I thin
On Thu, May 4, 2017 at 6:25 PM, Antoine Pitrou wrote:
> On Thu, 4 May 2017 11:24:27 +0900
> INADA Naoki wrote:
>> Hi, Nick and all core devs who are interested in this PEP.
>>
>> I'm reviewing PEP 538 and I want to accept it in this month.
>> It will reduces much UnicodeError pains which server-s
On Wed, May 3, 2017 at 10:22 AM, Victor Stinner
wrote:
> Hi,
>
> I spent last week working on fixing buildbots:
>
>https://www.python.org/dev/buildbot/
>
Thanks!
> * Add more buildbots! Zachary Ware proposed to add a buildbot running
> "regen-all" to check that generated files are up to date
On Fri, Apr 21, 2017 at 12:09 PM, Justus Schwabedal
wrote:
> Hi everyone,
>
> I possibly found a bug in class initialization and would like to fix it.
> Because it's my first journey to core-dev, I would really appreciate the
> help of a mentor that I may ask a few questions to get me up to speed.
Hi all,
I've been working on compiling/installing Python on Cygwin and have
hit upon an odd issue in the Makefile that seems to have been around
for as long as there's been Cygwin support in it.
When building Python on Cygwin, both a libpython-X.Y.dll and a
libpython-X.Y.dll.a are created. The l
On Fri, Sep 25, 2015 at 6:27 PM, Chris Barker - NOAA Federal
wrote:
>
> You can use "Windows SDK for Windows 7 and .NET Framework 4".
>
> http://www.microsoft.com/en-us/download/details.aspx?id=8279
>
>
> Thanks. Last time I tried that route, it was for 64 bit py2.7. And it
> required some kludgin
On Tue, Jul 14, 2015 at 6:22 PM, Robert Collins
wrote:
> For clarity, I think we should:
> - remove the assret check, it is I think spurious.
> - add a set of functions to the mock module that should be used in
> preference to Mock.assert*
> - mark the Mock.assert* functions as PendingDeprecati
On Mon, Jul 6, 2015 at 6:21 AM, Antoine Pitrou wrote:
> On Mon, 6 Jul 2015 14:22:46 +1000
> Nick Coghlan wrote:
>>
>> The main change from the last version discussed on python-ideas
>
> Was it discussed there? That list has become totally useless, I've
> stopped following it.
Considering that a
On Sun, Jan 5, 2014 at 11:21 AM, Larry Hastings wrote:
> Now, properly converting a function to work with Argument Clinic does not
> change its behavior. Internally, the code performing argument parsing
> should be nigh-identical; it should call the same PyArg_Parse function, with
> the same argu
On Sat, Mar 2, 2013 at 10:36 AM, Nick Coghlan wrote:
> In addition, it may be appropriate for importlib to offer a
> "write_module" method that accepts (module name, target path,
> contents). This would:
>
> 1. Allow in-process caches to be invalidated implicitly and
> selectively when new modules
On Sun, Feb 3, 2013 at 5:24 PM, Vinay Sajip wrote:
> Éric Araujo netwok.org> writes:
>
>> Looks like we agree that a basic tool able to bootstrap the packaging
>> story is needed :)
>
> Agreed. Just because distutils can't easily/reliably build things that are
> better built with SCons/WAF/tup/wh
On Fri, Sep 14, 2012 at 1:57 PM, Daniel Holth wrote:
> On Fri, Sep 14, 2012 at 1:43 PM, Erik Bray wrote:
>> On Fri, Sep 14, 2012 at 12:30 PM, Daniel Holth wrote:
>>> Add to metadata 1.3:
>>>
>>> Description-File: README(\..+)?
>>>
>>> Mea
On Fri, Sep 14, 2012 at 12:30 PM, Daniel Holth wrote:
> Add to metadata 1.3:
>
> Description-File: README(\..+)?
>
> Meaning the description should be read from a file in the same
> directory as PKG-INFO or METADATA (including in the .dist-info
> directories) and we strongly recommend it be named
On Thu, Sep 13, 2012 at 5:38 AM, Antoine Pitrou wrote:
> On Thu, 13 Sep 2012 11:14:17 +1000
> Nick Coghlan wrote:
>> On Thu, Sep 13, 2012 at 8:43 AM, R. David Murray
>> wrote:
>> > When the removal was being pondered, the possibility of keeping certain
>> > bits that were more ready than others
On Mon, Aug 27, 2012 at 10:56 AM, Daniel Holth wrote:
> On Wed, Aug 15, 2012 at 10:49 AM, Daniel Holth wrote:
>> I've drafted some edits to Metadata 1.2 with valuable feedback from
> ...
>> (full changeset on
>> https://bitbucket.org/dholth/python-peps/changeset/537e83bd4068)
>
> Metadata 1.2 is
On Wed, Sep 2, 2009 at 10:35 AM, James Y Knight wrote:
> On Sep 2, 2009, at 6:15 AM, Rob Cliffe wrote:
>
>> So - the syntax restriction seems not only inconsistent, but pointless; it
>> doesn't forbid anything, but merely means we have to do it in a slightly
>> convoluted (unPythonesque) way. So p
33 matches
Mail list logo
