I would like to take a step back,
I think that for removal of feature you need to make sure that the "old
way" is
not common enough. I think that in many context, users of Python see
DeprecationWarnings as a stick. A deprecation warning means you'll have to
do
some work. A pep or a document that l
On Fri, 4 May 2018 at 11:49, Serhiy Storchaka wrote:
> 04.05.18 20:57, Matthias Bussonnier пише:
> > But when I hit a DeprecationWarning message there is one crucial piece of
> > information missing most of the time: Since which version number it's
> > deprecated
> &
> As I wrote, it became very difficult to merge any PR on 2.7 because of
> that. We all run a race to be the first one to merge a change into
> 2.7. The next one will get a "conflict" even if the merged commit is
> unrelated (as I described: two different unrelated directories).
Couldn't miss-isli
On Tue, 29 May 2018 at 08:43, Paul G wrote:
> This doesn't seem like the best idea, since it would kick off dozens or
> hundreds of builds for every commit to the master branch.
>
Sorry if I was unclear, I was not suggesting to do that for PRs against
master, but do that only for 2.7, 3.4 and 3.
This may even be a bug/feature of IPython,
I see that inspect.signature(timedelta) fails, so if timedelta? says
Init signature: timedelta(self, /, *args, **kwargs)
Then this may be some IPython internal logic. The timedelta class seem to
use __new__ instead of __init__ (not sure why) and __new__
On Mon, 4 Jun 2018 at 17:29, Ivan Pozdeev via Python-Dev <
python-dev@python.org> wrote:
> On 05.06.2018 3:09, Matthias Bussonnier wrote:
>
> This may even be a bug/feature of IPython,
>
> I see that inspect.signature(timedelta) fails, so if timedelta? says
> Init s
> On Oct 29, 2015, at 11:46, Laura Creighton wrote:
>
> In a message of Thu, 29 Oct 2015 18:27:59 +, Paul Moore writes:
>> The idle issues seem to me to demonstrate that shadowing the stdlib is
>> a bad idea. Of course, consenting adults, and if you override you're
>> responsible for correct
> On Feb 3, 2016, at 13:22, Yury Selivanov wrote:
>
>
> An ideal way would be to calculate a hit/miss ratio over time
> for each cached opcode, but that would be an expensive
> calculation.
Do you mean like a sliding windows ?
Otherwise if you just want a let's say 20% miss threshold, you incr
> On Feb 4, 2016, at 08:22, Sven R. Kunze wrote:
>
> On 04.02.2016 16:57, Matthias Bussonnier wrote:
>>> On Feb 3, 2016, at 13:22, Yury Selivanov wrote:
>>>
>>>
>>> An ideal way would be to calculate a hit/miss ratio over time
>>>
> On Feb 8, 2016, at 06:40, Victor Stinner wrote:
>
> 2016-02-08 15:32 GMT+01:00 Victor Stinner :
>> Since 3.3, functions of the os module started to emit
>> DeprecationWarning when called with bytes filenames.
>> (...)
>> Recently, an user complained that os.walk() doesn't work with bytes on
>>
Hi all,
> On Feb 27, 2016, at 14:21, Alexander Walters wrote:
>
> Can we even ask github to pull it down and reasonably expect them to comply?
> Their entire model is built on everyone forking everyone else.
Why the model is everyone forking, some of the help page of GitHub actually
tell y
On Fri, Apr 1, 2016 at 9:21 AM, Chris Angelico wrote:
> On Fri, Apr 1, 2016 at 9:42 PM, Roberto Martínez
> wrote:
>> I am having a hard time trying to choose one of this two products:
>>
>> Phyton 27:
>> http://www.amazon.com/Phyton-27-Systemic-Bactericide-Fungicide/dp/B00VKPL8FU
>> Phyton 35:
>>
On Mon, 1 Oct 2018 at 13:38, Victor Stinner wrote:
> Le lun. 1 oct. 2018 à 22:32, Tres Seaver a écrit :
> > I'm pretty strongly -1 on the notion that folks who subscribe python-dev,
> > BPO, and the github repositories should need to *also* follow an
> > arbitrarily-growing set of Twitter accoun
Is it possible to change some of those deprecation from Warn-by-default (but
can add a warning filter to make them error) to error-by-default (but can add a
filter to make them only warnings).
That way it is easy to fix large projects (even w/o modifying the source) in
only a couple of lines o
Is it possible to change some of those deprecation from Warn-by-default (but
can add a warning filter to make them error) to error-by-default (but can add a
filter to make them only warnings).
That way it is easy to fix large projects (even w/o modifying the source) in
only a couple of lines o
Hi All,
# Too long didn't read:
In 3.9 inspect.getdoc(instance) behavior was changed and does not return the
documentation of type(instance) or it's superclass(es) – I think this is a
problematic change of for some project and interactive use to get info on
objects that get rarely directly co
It's still weird user experience as if you swap case .z and case z you don't
get the Unbound error anymore. SO it can work w/o global.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https:
Mark,
Thanks you this is an interesting proposal. I can see how many of the "magics"
provided by IPython/Jupyter could also be replaced by some of those macros.
A couple of questions – which I understand could be delegated to further
improvement to macros in a subsequent proposal.
- I'm no
18 matches
Mail list logo
