pylint 2.0 / astroid 2.0 released!

Hi folks, The pylint team is happy to announce the release of pylint 2.0 and astroid 2.0! This release only works with Python 3.4+, while older pylint releases are still maintained for Python 2 compatibility, at least until next year. You can find more details about what's new in this release

EuroPython 2018: Conference App available

We will be switching to the late bird rates for tickets on Monday next week (July 16), so this is your last chance to get tickets at the regular rate, which is about 30% less than the late bird rate. * EuroPython 2018 Tickets *

pylint 2.0 / astroid 2.0 released!

Hi folks, The pylint team is happy to announce the release of pylint 2.0 and astroid 2.0! This release only works with Python 3.4+, while older pylint releases are still maintained for Python 2 compatibility, at least until next year. You can find more details about what's new in this release

[issue34120] IDLE Caret/Focus Lost

New submission from Vlad Tudorache : When closing the IDLE's Preferences dialog the IDLE's Console window and/or Editor window (whichever was active before) doesn't show cursor/caret any more. One must click on Desktop or another window then click again in the IDLE's window in order to

[issue34047] IDLE: on macOS, scroll slider 'sticks' at bottom of file

Vlad Tudorache added the comment: I can reproduce this problem only with Tk 8.6.7, both compiled by myself or installed from ActiveState (Python 3.7 and 3.6 compiled by myself, too). I can't see it with Tk 8.6.8 provided with the installers, nor with Tk 8.5.18. -- nosy: +vtudorache

Re: Cult-like behaviour [was Re: Kindness]

Abdur-Rahmaan Janhangeer wrote: maybe another word for pep revocation is fork No, anyone can fork Python whenever they want, no discussion required, without affecting Python itself. Revoking a PEP would mean removing its implementation from the main CPython repository. -- Greg --

[issue34112] 3.7.0 build error with --enable-optimizations

Jayanth Koushik added the comment: Updating gcc to 8.1.0 fixed the problem. -- resolution: -> works for me stage: -> resolved status: open -> closed ___ Python tracker ___

Re: Cult-like behaviour [was Re: Kindness]

Paul Rubin : > Marko Rauhamaa writes: >> I have similar feelings, except that I'm not convinced Go is the answer. > > I don't think Go is the answer either, but it probably got strings > right. What is the answer? That's the ten-billion-dollar question, isn't it?! Marko --

Re: Cult-like behaviour [was Re: Kindness]

Steven D'Aprano : > Of course we have no idea what Marko's software is, or what it is doing, Correct, you don't, but the link Paul Rubin posted gives you an idea: Python 3 says: everything is Unicode (by default, except in certain situations, and except if we send you crazy reencoded

[issue29710] Incorrect representation caveat on bitwise operation docs

Nick Coghlan added the comment: OK, that makes sense to me. Given that, there'd be two changes proposed. 1. Replace the opening paragraph of https://docs.python.org/3/library/stdtypes.html#bitwise-operations-on-integer-types (the one I originally quoted when opening this issue) with the

Re: Cult-like behaviour [was Re: Kindness]

Paul Rubin : > Py3's unicode picture is described here and it isn't pretty: > http://lucumr.pocoo.org/2014/5/12/everything-about-unicode/ >From the link: The much more likely thing to happen is that people stick to Python 2 or build broken stuff on Python 3. Or they go with Go. Which uses

[issue29710] Incorrect representation caveat on bitwise operation docs

Tim Peters added the comment: Well, all 6 operations "are calculated as though carried out in two's complement with an infinite number of sign bits", so I'd float that part out of the footnote and into the main text. When, e.g., you're thinking of ints _as_ bitstrings, it's essentially

[issue34119] Able to name a variable as 'input'. This creates problem when using input() function.

Raymond Hettinger added the comment: While "shadowing a builtin" was irritating in your case, it is an unavoidable part of how Python works and is in some cases considered a feature. FWIW, there is a workaround. You can reference the real input() function directly in the __builtins__

Re: PEP 526 - var annotations and the spirit of python

Am 05.07.18 um 12:04 schrieb Steven D'Aprano: On Thu, 05 Jul 2018 09:17:20 +0200, Christian Gollwitzer wrote: Am 04.07.18 um 17:31 schrieb Steven D'Aprano: On Wed, 04 Jul 2018 13:48:26 +0100, Bart wrote: Presumably one type hint applies for the whole scope of the variable, not just the one

Re: Cult-like behaviour [was Re: Kindness]

@GregoryEwing maybe another word for pep revocation is fork Abdur-Rahmaan Janhangeer https://github.com/Abdur-rahmaanJ -- https://mail.python.org/mailman/listinfo/python-list

Re: Cult-like behaviour [was Re: Kindness]

Paul Rubin wrote: If you see the historical absence of an assignment operator in Python as a mistake, then the introduction of := is a fix for the mistake that only happened because people kept complaining. That's not quite the same thing. There was no a PEP saying that there would never be

[issue34119] Able to name a variable as 'input'. This creates problem when using input() function.

New submission from Kishore Aadada : When i used input as a variable name, there is no error provided. After that I am calling input() function to read data. In such case, below error is reported. Python 3.6.3 (v3.6.3:2c5fed8, Oct 3 2017, 17:26:49) [MSC v.1900 32 bit (Intel)] on win32 Type

<    1   2