Mark Shannon writes:
> Hello all,
>
> I am pleased to announce that I am accepting PEP 484 (Type Hints).
Congratulations to all concerned!
> Python is your language, please use type-hints responsibly :)
+1 QOTW (not to mention ROTFLMAO)
___
Python
On Fri, May 22, 2015 at 05:24:53PM -0700, Larry Hastings wrote:
> On 05/22/2015 05:11 PM, Trent Nelson wrote:
> >Do we still support WS2K3? (Can I even install VS 2015 on that? I would
> >have thought not.)
>
> According to PCbuild/readme.txt, no. It says:
>
>This directory is used to build
On 05/22/2015 05:11 PM, Trent Nelson wrote:
Do we still support WS2K3? (Can I even install VS 2015 on that? I
would have thought not.)
According to PCbuild/readme.txt, no. It says:
This directory is used to build CPython for Microsoft Windows NT
version 6.0 or higher (Windows Vista, Wi
On Fri, May 22, 2015 at 10:06:48PM +, Steve Dower wrote:
> The Windows 7 buildbots are failing on test_asdl_parser, but I have no
> idea why – the test works for me just fine. Yury and Benjamin made the
> most recent changes to Python.asdl, but I have no idea what effect
> they would have here,
On 23 May 2015 01:15, "André Freitas" wrote:
>
> Hi there,
> My name is André Freitas, I'm 22 years old and I live in Portugal
(Porto). I'm currently finishing my Masters in Informatics and Computer
Science with a thesis in Mining Software Repositories, where I am able to
predict defects in Softwa
On Fri, May 22, 2015 at 11:44 PM, Eric Snow wrote:
> Hi all,
>
> After extended discussion over the last several months on import-sig,
> the resulting proposal for multi-phase (PEP 451) extension module
> initialization has finalized. The resulting PEP provides a clean,
> straight-forward, and ba
On 23 May 2015 07:45, "Eric Snow" wrote:
>
> Hi all,
>
> After extended discussion over the last several months on import-sig,
> the resulting proposal for multi-phase (PEP 451) extension module
> initialization has finalized. The resulting PEP provides a clean,
> straight-forward, and backward-c
> On May 22, 2015, at 2:52 PM, Guido van Rossum wrote:
>
> Congrats! Many thanks to all who contributed.
>
> On May 22, 2015 2:45 PM, "Eric Snow" wrote:
> Hi all,
>
> After extended discussion over the last several months on import-sig,
> the resulting proposal for multi-phase (PEP 451) exten
*From:*Larry Hastings [mailto:la...@midwinter.com] *On Behalf Of
*Larry Hastings
*Sent:* Friday, May 22, 2015 1530
*To:* Steve Dower; Python Dev; python-committers
*Cc:* Yury Selivanov; Benjamin Peterson
*Subject:* Re: [python-committers] Can we clean up the buildbots please?
Is MSVS 2015 the
Two of them are useless (x86 Windows Server 2003 [SB] and x86 XP-4, to be
precise), but the fact that everything other than test_asdl_parser passes is a
very valuable signal. AMD64 Windows 7 SP1 is also using the correct compiler.
Since some of our core developers are yet to upgrade, I’m not aga
On Sat, May 23, 2015 at 12:53 AM, Chris Barker wrote:
> On Fri, May 22, 2015 at 2:33 PM, Larry Hastings wrote:
>>
>> On 05/22/2015 02:29 PM, Chris Barker wrote:
>>
>> Is it too late to get the isclose() code (PEP 485) into 3.5?
>
> ...
>>
>> Hopefully you can find a core dev familiar enough wit
On 05/22/2015 03:06 PM, Steve Dower wrote:
The Windows 7 buildbots are failing on test_asdl_parser, but I have no
idea why – the test works for me just fine. Yury and Benjamin made the
most recent changes to Python.asdl, but I have no idea what effect
they would have here, or why it’s Windows
Right now we have eight online buildbots for Python trunk. Of those,
currently *six* are reporting errors in either the compile or test phases.
http://buildbot.python.org/all/waterfall?category=3.x.stable
There's one platform ("AMD64 Snow Leop") where the failures are sporadic
"stack ov
The Windows 7 buildbots are failing on test_asdl_parser, but I have no idea why
– the test works for me just fine. Yury and Benjamin made the most recent
changes to Python.asdl, but I have no idea what effect they would have here, or
why it’s Windows only.
The WS2K3 machine needs a reboot – I p
On Fri, May 22, 2015 at 2:33 PM, Larry Hastings wrote:
> On 05/22/2015 02:29 PM, Chris Barker wrote:
>
> Is it too late to get the isclose() code (PEP 485) into 3.5?
>
> ...
> Hopefully you can find a core dev familiar enough with the issues
> involved that they can (quickly!) guide it throug
Congrats! Many thanks to all who contributed.
On May 22, 2015 2:45 PM, "Eric Snow" wrote:
> Hi all,
>
> After extended discussion over the last several months on import-sig,
> the resulting proposal for multi-phase (PEP 451) extension module
> initialization has finalized. The resulting PEP prov
Hi all,
After extended discussion over the last several months on import-sig,
the resulting proposal for multi-phase (PEP 451) extension module
initialization has finalized. The resulting PEP provides a clean,
straight-forward, and backward-compatible way to import extension
modules using ModuleS
On 05/22/2015 02:29 PM, Chris Barker wrote:
Is it too late to get the isclose() code (PEP 485) into 3.5?
I posted the code here, and got a tiny bit of review, but have not yet
merged it into the source tree -- and don't know the process for
getting it committed to the official source.
So --
Is it too late to get the isclose() code (PEP 485) into 3.5?
I posted the code here, and got a tiny bit of review, but have not yet
merged it into the source tree -- and don't know the process for getting it
committed to the official source.
So -- too late, or should I try to get that merge done
Thanks Mark!
On May 22, 2015 1:52 PM, "Mark Shannon" wrote:
> Hello all,
>
> I am pleased to announce that I am accepting PEP 484 (Type Hints).
>
> Given the proximity of the beta release I thought I would get this
> announcement out now, even though there are some (very) minor details to
> iron
Hello all,
I am pleased to announce that I am accepting PEP 484 (Type Hints).
Given the proximity of the beta release I thought I would get this
announcement out now, even though there are some (very) minor details to
iron out.
(If you want to know the details, it's all at
https://github.com/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 13.05.15 um 09:59 schrieb Larry Hastings:
> When you say "branch testing", you mean "running the buildbots
> against it"? Right now the UI for doing that is pretty clunky.
> Kicking off a build against a server-side clone (iirc) requires
> clicking
Howdy howdy. It's-a me, Larry, your friendly neighborhood Python 3.5
Release Manager.
Somewhere around 2 or 3pm tomorrow I expect to tag Python 3.5 beta 1.
We'll actually release beta 1 on Sunday, once the binary installers are
all built.
Beta 1 is also feature-freeze, meaning no new fe
On Fri, May 22, 2015 at 10:23 AM, Jim J. Jewett
wrote:
>
>
> At Thu May 21 22:27:50 CEST 2015, Guido wrote:
>
> > I want to encourage users to think about annotations as types,
> > and for most users the distinction between type and class is
> > too subtle,
>
> So what is the distinction that you
At Thu May 21 22:27:50 CEST 2015, Guido wrote:
> I want to encourage users to think about annotations as types,
> and for most users the distinction between type and class is
> too subtle,
So what is the distinction that you are trying to make?
That a type refers to a variable (name), and a cl
On Fri, May 22, 2015 at 9:45 AM, Jim J. Jewett wrote:
>
>
> Mark Shannon wrote:
>
> > PY2, etc. really need to go.
> > Assuming that this code type checks OK:
> >
> > if typing.PY2:
> > type_safe_under_py2_only()
> > else:
> > type_safe_under_py3_only()
> >
> > Is the checker supposed
Mark Shannon wrote:
> PY2, etc. really need to go.
> Assuming that this code type checks OK:
>
> if typing.PY2:
> type_safe_under_py2_only()
> else:
> type_safe_under_py3_only()
>
> Is the checker supposed to pass this:
>
> if sys.hexversion < 0x0300:
> type_safe_under_py2_
ACTIVITY SUMMARY (2015-05-15 - 2015-05-22)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4833 ( -7)
closed 31194 (+71)
total 36027 (+64)
Open issues wit
Another draft. This is mostly a bunch of clarifications and minor edits,
but it also removes the four version/platform constants (PY2, PY3, WINDOWS,
POSIX) in favor of asking type checkers to recognize common version checks
e.g. using sys.version_info or sys.platform. This time I think the new
vers
Hi there,
My name is André Freitas, I'm 22 years old and I live in Portugal (Porto).
I'm currently finishing my Masters in Informatics and Computer Science with
a thesis in Mining Software Repositories, where I am able to predict
defects in Software components: https://github.com/andrefreitas/schwa
There's an issue about this at
http://psf.upfronthosting.co.za/roundup/meta/issue562
I believe the problem is not that of the SPF, but the fact that mail gets
sent using IPv6 from an address that has neither a name mapping to it nor a
reverse pointer from IP address to name in DNS. See the second-
31 matches
Mail list logo
