On 10 November 2017 at 22:27, Guido van Rossum wrote:
> Picking up this thread as part of the PEP 562 and PEP 549 review. I like
> PEP 562 most, but I propose to add special-casing for `__dir__`. Not quite
> as proposed above (making the C level module_dir() look for `__all__`)
Picking up this thread as part of the PEP 562 and PEP 549 review. I like
PEP 562 most, but I propose to add special-casing for `__dir__`. Not quite
as proposed above (making the C level module_dir() look for `__all__`) but
a bit more general -- making module_dir() look for `__dir__` and call that
On 10 November 2017 at 21:19, Koos Zevenhoven wrote:
> On Fri, Nov 10, 2017 at 8:33 PM, Ivan Levkivskyi
> wrote:
>
>> On 10 November 2017 at 18:39, Koos Zevenhoven wrote:
>>
>>> On Wed, Sep 27, 2017 at 12:28 PM, Ivan Levkivskyi
On Fri, Nov 10, 2017 at 8:33 PM, Ivan Levkivskyi
wrote:
> On 10 November 2017 at 18:39, Koos Zevenhoven wrote:
>
>> On Wed, Sep 27, 2017 at 12:28 PM, Ivan Levkivskyi
>> wrote:
>>
>>>
>>>
>>
>>> After creating the class,
>>> the
On 10 November 2017 at 18:39, Koos Zevenhoven wrote:
> On Wed, Sep 27, 2017 at 12:28 PM, Ivan Levkivskyi
> wrote:
>
>>
>>
>
>> After creating the class,
>> the original bases are saved in ``__orig_bases__`` (currently this is also
>> done by the
On 10 November 2017 at 17:43, Guido van Rossum wrote:
> Hey Ivan,
>
> There seem to be some action items from this thread that I haven't seen
> reflected in the PEP source code yet.
> [...snip...]
> Then the next step I propose is a PR with a full implementation. After
> that
Hey Ivan,
There seem to be some action items from this thread that I haven't seen
reflected in the PEP source code yet.
- Change the title (I like "Core support for typing module and generic
types" but maybe it can be shortened to "Core support for generics in the
typing module" -- if you like
On 10 November 2017 at 11:37, Oleg Broytman wrote:
> On Fri, Nov 10, 2017 at 07:48:35AM +0100, Michel Desmoulin
> wrote:
>> On linux you
>> can't pip install, you need --users, admin rights or a virtualenv.
>
>Isn't it the same on Windows? For an
On Fri, Nov 10, 2017 at 09:50:22AM +, Paul Moore
wrote:
> The biggest reason we don't add Python to PATH, as I understand it, is
> because we need to consider the implications of people having multiple
> versions of Python installed.
Why not fix that the same way as
On Fri, Nov 10, 2017 at 07:48:35AM +0100, Michel Desmoulin
wrote:
> On linux you
> can't pip install, you need --users, admin rights or a virtualenv.
Isn't it the same on Windows? For an admin-installed Python you need
--users, admin rights or a virtualenv. And a
On 10 November 2017 at 10:01, Nick Coghlan wrote:
> On 10 November 2017 at 19:50, Paul Moore wrote:
>> On 10 November 2017 at 08:01, Nick Coghlan wrote:
>>> That tooling is venv:
>>>
>>> * it ensures you have "pip" on your PATH
>>> *
On 10 November 2017 at 19:50, Paul Moore wrote:
> On 10 November 2017 at 08:01, Nick Coghlan wrote:
>> That tooling is venv:
>>
>> * it ensures you have "pip" on your PATH
>> * it ensures you have "python" on your PATH
>> * it ensures that you have the
On 10 November 2017 at 08:01, Nick Coghlan wrote:
> You can't have it both ways - the only way we can systematically mask
> the environmental differences between Windows, Linux and Mac OS X is
> by providing tooling that actually masks those differences, which
> means
On 10 November 2017 at 17:05, Michel Desmoulin
wrote:
>
>> Which is why we advise getting into a virtual environment ASAP, such
>> that the only platform specific thing folks necessarily need to learn
>> to get started is how to get to that first working virtual
>>
14 matches
Mail list logo