On 1 October 2015 at 10:19, Alexander Belopolsky
wrote:
> It has been my understanding that some PEPs may be discussed on specialized
> mailings lists, but a notice would be given on python-dev prior to any
> acceptance.
No, that only applies for changes that actually impact the reference
interpr
On September 30, 2015 at 9:14:42 PM, Alexander Belopolsky
(alexander.belopol...@gmail.com) wrote:
> On Wed, Sep 30, 2015 at 8:32 PM, Donald Stufft wrote:
> >
> > I don’t see any requirement to post PEPs to python-dev if they have a
> Discussions-To header in PEP 1.
>
>
> When I faced a similar
On Sep 30, 2015, at 09:14 PM, Alexander Belopolsky wrote:
>When I faced a similar situation with PEP 495, Guido's advise was "I think
>that a courtesy message to python-dev is appropriate, with a link to the
>PEP and an invitation to discuss its merits on datetime-sig." [1]
Certainly Discussions-
On Wed, Sep 30, 2015 at 8:32 PM, Donald Stufft wrote:
>
> I don’t see any requirement to post PEPs to python-dev if they have a
Discussions-To header in PEP 1.
When I faced a similar situation with PEP 495, Guido's advise was "I think
that a courtesy message to python-dev is appropriate, with a
On September 30, 2015 at 8:20:53 PM, Alexander Belopolsky
(alexander.belopol...@gmail.com) wrote:
> It has been my understanding that some PEPs may be discussed on specialized
> mailings lists, but a notice would be given on python-dev prior to any
> acceptance.
>
I don’t see any requirement to
It has been my understanding that some PEPs may be discussed on specialized
mailings lists, but a notice would be given on python-dev prior to any
acceptance.
I have recently received a notification that since PEP 470 has been
accepted, I can no longer use external hosting for one of the packages
It should be possible with Wine.
Am 30.09.2015 22:50 schrieb "Laurent Gautier" :
> Hi Carl,
>
> Looks promising.
>
> Any chance the effort would consider cross-compiling (from Linux) as a
> possible objective ?
>
> Best,
>
> Laurent
>
> On Wed, Sep 30, 2015, 3:58 PM Carl Kleffner wrote:
>
>> Conc
Hi Carl,
Looks promising.
Any chance the effort would consider cross-compiling (from Linux) as a
possible objective ?
Best,
Laurent
On Wed, Sep 30, 2015, 3:58 PM Carl Kleffner wrote:
> Concerning the claims that mingw is difficult:
>
> The mingwpy package is a sligthly modified mingw-w64 bas
Concerning the claims that mingw is difficult:
The mingwpy package is a sligthly modified mingw-w64 based gcc toolchain,
that is in development. It is designed for simple use and for much better
compatibility to the standard MSVC python builds. It should work out of the
box, as long as the \Script
On 30 September 2015 at 16:57, Chris Barker - NOAA Federal
wrote:
>> 1. Install "Windows SDK for Windows 7 and .NET Framework 4" (v7.1)
>> 2. Work from an SDK command prompt (with the environment variables
>> set, and the SDK on PATH).
>> 3. Set DISTUTILS_USE_SDK=1
>> 4. Done.
>
> This, unfortunat
TL;DR -- yes, documenting this in packaging.python.org would be great!
> Part of the problem here is that people put up postings saying "do
> this" having checked that it works for them, and then others say "but
> it doesn't work", without giving any information as to why or
> providing any means
On 30 September 2015 at 01:31, Chris Barker - NOAA Federal
wrote:
> It may be -- I've still have to test. Neither Windows nor py3 are my
> primary production versions.
Part of the problem here is that people put up postings saying "do
this" having checked that it works for them, and then others s
12 matches
Mail list logo
