10.09.17 21:48, Ivan Levkivskyi пише:
# lib.py
from warnings import warn
deprecated_names = ["old_function", ...]
def _deprecated_old_function(arg, other):
...
def __getattr__(name):
if name in deprecated_names:
warn(f"{name} is deprecated", Deprecation
On 14 November 2017 at 03:08, Nathaniel Smith wrote:
> On Nov 13, 2017 6:47 PM, "Nick Coghlan" wrote:
>> and a pip.bat with the equivalent contents on Windows?
>> (Bonus: maybe this would fix the problem with upgrading pip on
>> Windows?)
>
> Depending on how the batch file was written, I think
Hi Brett,
The current documentation *cannot* be fixed, since
fixing it would entail adding an initial two-page essay
on "how to start Python on various platforms/systems"
(it is really NOT as simple as Windows=python, Linux=python3)
and such a PR will certainly by rejected.
In my opinion, the onl
On Tue, Nov 14, 2017 at 12:56 AM, Paul Moore wrote:
> On 14 November 2017 at 03:08, Nathaniel Smith wrote:
>> On Nov 13, 2017 6:47 PM, "Nick Coghlan" wrote:
>
>>> and a pip.bat with the equivalent contents on Windows?
>>> (Bonus: maybe this would fix the problem with upgrading pip on
>>> Windows
On 14 November 2017 at 16:47, Michel Desmoulin
wrote:
> General summary so far
> ###
>
>
> This debate has been very civil so far and quite productive, so thanks
> to everyone involved.
>
> Several issues and solution proposals have been mentioned, so I will
> make a summary h
On 13/11/2017 19:10, Barry Warsaw wrote:
> I love many of the ancillary tools that help improve the quality of my
> Python code, including flake8, coverage, and mypy. Each of these
> usually produces some great diagnostics, but none of them are perfect,
> so they also produce false positives tha
On Tue, 14 Nov 2017 12:14:50 +1000
Nick Coghlan wrote:
> >
> > I don't think Windows ever had python2.exe/python3.exe, but I could be
> > wrong.
>
> Not that I'm aware of in the python.org installers, and I don't think
> ActivePython does either. I'm less sure about Enthought or Anaconda
> (si
On Tue, 14 Nov 2017 07:45:09 +0100
Michel Desmoulin
wrote:
>
> I think it's wrong to have a different setup on different plateforms.
> Python is a portable language. It's also a language you use for quick
> scripts and from a lot of non professional devs.
>
> Unifying the python experience and m
On Tue, 14 Nov 2017 13:28:20 +0100
Antoine Pitrou wrote:
> On Tue, 14 Nov 2017 12:14:50 +1000
> Nick Coghlan wrote:
> > >
> > > I don't think Windows ever had python2.exe/python3.exe, but I could be
> > > wrong.
> >
> > Not that I'm aware of in the python.org installers, and I don't think
On 14 November 2017 at 10:02, Nathaniel Smith wrote:
> On Tue, Nov 14, 2017 at 12:56 AM, Paul Moore wrote:
>> On 14 November 2017 at 03:08, Nathaniel Smith wrote:
>>> On Nov 13, 2017 6:47 PM, "Nick Coghlan" wrote:
>>
and a pip.bat with the equivalent contents on Windows?
(Bonus: maybe
On Nov 14, 2017 02:39, "Chris Angelico" wrote:
On Tue, Nov 14, 2017 at 5:47 PM, Michel Desmoulin
wrote:
> Proposal B:
>
>
> Make pip and venv part of the standard and request debian that they
> provide it.
>
> Pros: straight forward.
>
> Cons: holy war in the making.
Cons: What doe
Hi Nick,
2017-11-14 11:07 GMT+01:00 Nick Coghlan :
> On 14 November 2017 at 16:47, Michel Desmoulin
> wrote:
>
>> Proposal A:
>> ---
>>
>> Suffix Python executable on Windows like on Unix, so that people will
>> type pythonX.X if they want a specify version.
>>
>> Pros: easy and discover
On Tue, Nov 14, 2017 at 12:24 AM, Serhiy Storchaka
wrote:
> 10.09.17 21:48, Ivan Levkivskyi пише:
>
>># lib.py
>>
>>from warnings import warn
>>
>>deprecated_names = ["old_function", ...]
>>
>>def _deprecated_old_function(arg, other):
>>...
>>
>>def __getattr__(name):
This is an idea I have been playing with and seems to hold some
promise. I think we should use a module instance as the standard
global namespace rather than directly using its dict. I have a
prototype version of CPython that does this, not working 100% yet
though.
Major changes:
- In the frame
On Nov 13, 2017, at 1:53 PM, Paul Moore wrote:
In principle, I agree with the ideas here, but there are some
practical issues that make them somewhat less straightforward than we
might like.
And practically beats principally ;-)
But yeah.
1) Add python2.exe and python3.exe files to the Windo
On Mon, Nov 13, 2017 at 5:37 PM, Barry Warsaw wrote:
> One of the things that bother me about end-line comments is that this is
> going to blow up line length limits.
Is that a problem? the linters can ignore lines to long if they are only
too long due to one of these :-)
> I think this could
On Tue, Nov 14, 2017 at 05:12:10PM -0800, Chris Barker wrote:
> On Mon, Nov 13, 2017 at 5:37 PM, Barry Warsaw wrote:
>
> > One of the things that bother me about end-line comments is that this is
> > going to blow up line length limits.
>
>
> Is that a problem? the linters can ignore lines to l
On 15 November 2017 at 06:34, Neil Schemenauer wrote:
> So, what is the purpose of all this trouble?
>
> - I believe quite a lot of Python internals can be simpler. For
> example, importlib is complicated by the fact that a dict is
> passed around when most of the logic would prefer to have
On 15 November 2017 at 01:23, Stephan Houben wrote:
> Hi Nick,
>
> 2017-11-14 11:07 GMT+01:00 Nick Coghlan :
>
>> On 14 November 2017 at 16:47, Michel Desmoulin > > wrote:
>>
>>> Proposal A:
>>> ---
>>>
>>> Suffix Python executable on Windows like on Unix, so that people will
>>> type pyt
>>> We still have to deal with the fact that basically every Unix
>>> environment is "advanced" in the above sense (the python2/python3
>>> split). I don't have a solution for that (other than "upgrade to
>>> Windows" ;-)).
>>
>> Provide the "py" command on linux and mac. And make it the default
>
20 matches
Mail list logo
