Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +12201
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Rémi Lapeyre added the comment:
Hi @xtreak, sorry for that.
I think the issue may come from
https://github.com/python/cpython/blob/master/Objects/listobject.c#L2273-L2357
where ms.key_compare is set, the conditions on the first ifs looks weird to me
and I suspect ms.key_compare is set
Rémi Lapeyre added the comment:
The code segfaults at
https://github.com/python/cpython/blob/master/Objects/listobject.c#L2164 coming
from https://github.com/python/cpython/blob/master/Objects/listobject.c#L1324.
--
nosy: -elliot.gorokhovsky, zach.ware
Rémi Lapeyre added the comment:
On mac I confirm that 1e34da49ef2 segfaults and 6c6ddf97c4 gives the expected
result:
➜ cpython git:(6c6ddf97c4) ✗ ./python.exe tests.py
Traceback (most recent call last):
File "tests.py", line 1, in
[(1.0, 1.0), (False, "A"),
Rémi Lapeyre added the comment:
Hi @maxtrixise, thanks for PR,
> there is a function for the validation of an address with the netmask
Which one do you want to use?
--
___
Python tracker
<https://bugs.python.org/issu
Rémi Lapeyre added the comment:
Shouldn't this be kept for the documentation sprint?
--
nosy: +cheryl.sabella, remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue36
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue23607>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
components: +Library (Lib) -Extension Modules
___
Python tracker
<https://bugs.python.org/issue36121>
___
___
Python-bugs-list mailin
Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +12091
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36121>
___
___
Py
Rémi Lapeyre added the comment:
Hi Carlos, I think this can be added as a new `field_size_limit` keyword
argument to csv.reader().
I will work on it.
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue36
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue14534>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue36092>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
I see your point.
On the other hand, a new parameter would also increase the complexity for the
user.
Maybe it should not be seen as re-ordering but just a "zipping" them correctly:
@dataclass
class Parent:
i: int
j: int = 0
@dataclass
c
Rémi Lapeyre added the comment:
I think this is what is referring Кирилл Чуркин to:
Python 3.7.2 (default, Jan 13 2019, 12:50:01)
[Clang 10.0.0 (clang-1000.11.45.5)] on darwin
Type "help", "copyright", "credits" or "license" for more informatio
Rémi Lapeyre added the comment:
This is called banker rounding and is done on purpose to limit the accumulation
of errors when summing a list of rounded integers. You can read
https://en.m.wikipedia.org/wiki/Rounding#Round_half_to_even and look at IEEE
754 for more information
Rémi Lapeyre added the comment:
Yes it is. Thanks for finding that @Serhiy.
Since nobody objected to the change on the mailing list and people seem to
agree in issue 20092:
[R. David Murray]
To summarize for anyone like me who didn't follow that issue: __index__
means the object can
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue3991>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
This is also present in 3.7 and 3.8. I would look at it and propose a patch
tomorrow.
--
nosy: +remi.lapeyre
versions: +Python 3.7, Python 3.8
___
Python tracker
<https://bugs.python.org/issue36
Rémi Lapeyre added the comment:
> I am not sure what to with the int constructor. Should it try __index__
> before __int__? Or just make __index__ without __int__ setting the nb_int
> slot as was proposed by Nick in issue33039?
Shouldn't it try only __int__ since this wil
Rémi Lapeyre added the comment:
See also https://bugs.python.org/issue35889 which add repr to sqlite3.Row
--
___
Python tracker
<https://bugs.python.org/issue36
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue36051>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
Note: when repr do not round trip, I think it's common practice to use brackets:
instead of:
LifoQueue('a'...'c')
Example with Regex from https://docs.python.org/3/howto/regex.html:
>>> re.match(r'From\s+', 'From amk Thu May 14 19:1
Rémi Lapeyre added the comment:
Hi @matrixise, is it really an issue to iterate over all the elements of the
deque?
__repr__ won't be called on performance sensitive path and we already do this
for repr([0]*1), repr({i for i in range(1)}) and repr({i:i for i in
range(1
Rémi Lapeyre added the comment:
Is this an issue though? Shouldn't methods be defined in the class definition,
we don't expect setting a function as an attribute to a class to transform it
automatically to a method.
Why would we special case __class_getitem__ and not __init_subclass__
Rémi Lapeyre added the comment:
In some places, using a lot is also a deliberate choice to improve readability.
I think the boy scout rule is more appropriate for such changes.
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.
New submission from Rémi Lapeyre :
Hi, I'm working on issue 18765 (running pdb.post_mortem() on failing test
cases) where I need to control the behavior of a TestCase based on some outside
input.
For this issue, I want to add a new --pdb option to turn this feature on when
enabled
Change by Rémi Lapeyre :
--
components: +Library (Lib)
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue36036>
___
___
Python-bugs-list m
Rémi Lapeyre added the comment:
Other methods validate explicitly their arguments with _validate_value_types
for example.
Here it raises KeyError which does not seem to be the appropriate exception.
ConfigParser implementing the mapping protocol it seems weird to me to have
>>>
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue36028>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
Hi everybody, I opened PR 11781 to add a key argument to functions in the bisect
module. I agree with @dmtr's points that this addition is not a bad design.
As far as I can tell, the key function is at called at most once per item as
this
example where
Rémi Lapeyre added the comment:
> Why only sections? ConfigParser contains a lot of other information.
Indeed, the defaults might be useful too. Other things like options
can be sessions specific and could clutter the repr if added.
Would defaults() and sections() be the right behav
Change by Rémi Lapeyre :
--
title: Import configparser.ConfigParser repr -> Improve
configparser.ConfigParser repr
___
Python tracker
<https://bugs.python.org/issu
New submission from Rémi Lapeyre :
This is the current repr of the configparser.ConfigParser instances:
>>> import configparser
>>> config = configparser.ConfigParser()
>>> config['sec'] = {}
>>> config
I think this could be improved to read:
-
Rémi Lapeyre added the comment:
> Btw: The name "read_dict" [1] as well as its docstring say exactly the
> opposite of what it does. It acts as a "save_dict". Maybe that can be fixed
> on the go ...
The name `read_dict` is correct, it reads from the dict giv
Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +11943
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35954>
___
___
Py
Rémi Lapeyre added the comment:
You will find the line you want to change in
`Doc/reference/lexical_analysis.rst`
--
___
Python tracker
<https://bugs.python.org/issue35
Rémi Lapeyre added the comment:
Hi Magnien, if you have already used Git, everything should be familiar.
You have to clone the whole project, but the documentation leaves in the `Doc`
folder. There is a lot of information that you can get at
https://devguide.python.org/documenting/
If you
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue15753>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue35989>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue5996>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
has_key method has been removed in Python3 so I think we can remove it from the
DictProxy as well as nobody should be relying on it anymore.
--
___
Python tracker
<https://bugs.python.org/issue35
Change by Rémi Lapeyre :
--
keywords: +patch, patch, patch
pull_requests: +11841, 11842, 11843
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +11841
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Rémi Lapeyre :
--
keywords: +patch, patch
pull_requests: +11841, 11842
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Rémi Lapeyre added the comment:
Hi @giampaolo.rodola, I will post a PR for this issue.
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue35
Rémi Lapeyre added the comment:
Could it be
https://github.com/python/cpython/blob/master/Modules/mathmodule.c#L2565
When 0 is in the iterator, i_result get sets to 0 and then on the next
iteration x/i_result is 0/0 which is undefined behavior?
C99 6.5.5p5 - The result of the / operator
Rémi Lapeyre added the comment:
@xtreak, couldn't we have made `_Call` inherit from namedtuple to achieve a
similar result (albeit the handling of name would be weird)?
--
___
Python tracker
<https://bugs.python.org/issue21
Rémi Lapeyre added the comment:
I like this patch, working with calls often feels weird and this change
simplify attribute access.
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue21
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue35954>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue35912>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
Hi Mark Forrer, I opened a new PR to add this precision to assert_called_with
documentation.
--
nosy: +remi.lapeyre
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue35
Change by Rémi Lapeyre :
--
keywords: +patch, patch
pull_requests: +11800, 11801
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Rémi Lapeyre :
--
keywords: +patch, patch, patch
pull_requests: +11800, 11801, 11802
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +11800
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35946>
___
___
Py
Rémi Lapeyre added the comment:
Hi Ramy, thanks for bumping the issue.
The solution suggested by Piotr Dobrogost is backward compatible and I think
it's the right thing to do.
I opened a new PR thanks to the patch of Jérémie Detrey.
--
versions: +Python 3.7, Python 3.8 -Python 3.4
Change by Rémi Lapeyre :
--
pull_requests: +11797, 11798
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue17164>
___
___
Python-bugs-lis
Change by Rémi Lapeyre :
--
pull_requests: +11797, 11798, 11799
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue17164>
___
___
Python-
Change by Rémi Lapeyre :
--
pull_requests: +11797
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue17164>
___
___
Python-bugs-list mai
Rémi Lapeyre added the comment:
Thanks for your report Joseph, I opened a new PR to fix this.
--
nosy: +orsenthil
___
Python tracker
<https://bugs.python.org/issue35
Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +11796
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35922>
___
___
Py
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue17164>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
Hi Bangert, thanks for reporting the issue.
we need more information to reproduce the bug. Can you post the requirement.txt
file as a text file rather than a screenshot and the step to reproduce the
crash starting from an empty project?
Were you able
Rémi Lapeyre added the comment:
Hi @corona10, Antoine's message is from 2013 and inspect.getabsfile() is still
not documented, I think it's safe to say he's not working on it.
You can work on the issue and open a new PR on GitHub when you think it is
ready for review :)
--
nosy
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
versions: +Python 3.8 -Python 3.7
___
Python tracker
<https://bugs.python.org/issue4356>
___
___
Python-bugs-list m
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue35931>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue35932>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
pull_requests: +11764, 11765, 11766
___
Python tracker
<https://bugs.python.org/issue4356>
___
___
Python-bugs-list mailing list
Unsub
Change by Rémi Lapeyre :
--
pull_requests: +11764
___
Python tracker
<https://bugs.python.org/issue4356>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
pull_requests: +11764, 11765
___
Python tracker
<https://bugs.python.org/issue4356>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue35922>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
I agree with Karthikeyan, I would expect sort=True to sort all collections,
including tuples and lists for example.
--
___
Python tracker
<https://bugs.python.org/issue30
Change by Rémi Lapeyre :
--
keywords: +patch, patch
pull_requests: +11732, 11733
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Rémi Lapeyre :
--
keywords: +patch, patch, patch
pull_requests: +11732, 11733, 11734
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +11732
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Rémi Lapeyre added the comment:
Hi @Phil Dream, you reuse i in your inner loop, in the for statement.
By the way, I suggest you look at range() to replace your while loop:
https://docs.python.org/3/library/functions.html#func-range.
For your others questions, the mailing list are more
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue2>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
> A programmer want to instruct the computer to do something, without having to
> care about how it works.
This is not true, as a programmer you need to choose carefully your data
structures because they matter, for example there is a difference between
Rémi Lapeyre added the comment:
Hi @Maxpxt, I think your first solution is appropriate, do you want to open a
new pull request with your solution and an appropriate test case?
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.
Rémi Lapeyre added the comment:
@gregory.p.smith Do you think the debugHook should be added to the test case or
the test runner?
If we add it to the test case, how do you think the runner should tell the test
case what flags have been given on the command line?
I feel like adding a new
Rémi Lapeyre added the comment:
Hi, this is the only reason I still use pytest, I would love to be able to use
only unittest and the constant copy-paste is not a great solution and is not
very user friendly.
I would like to wotk on this issue.
StackOverflow has many example on how
Rémi Lapeyre added the comment:
I believe this is why Travis does a `make regen-all` to be sure everything is
up to date.
A patch to keep instructions up-to-date would be nice, newcomers are not
familiar with all `make regen-*` commands.
--
nosy: +remi.lapeyre
Rémi Lapeyre added the comment:
I opened a PR with @josh.r proposed change.
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue34
Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +11611
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34886>
___
___
Py
Change by Rémi Lapeyre :
--
keywords: +patch, patch, patch
pull_requests: +11611, 11612, 11613
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Rémi Lapeyre :
--
keywords: +patch, patch
pull_requests: +11611, 11612
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Rémi Lapeyre added the comment:
Hi josephsmeng, dict order preservation is now used in a lot of place in
Python. I will post a patch to make pprint use insertion order in a few hours.
--
nosy: +remi.lapeyre
___
Python tracker
<ht
Rémi Lapeyre added the comment:
I think the issue steems from the more general #27015 for which a PR is ready
that fixes the repr not only for ImportError but all other BaseException
subclasses that override __init__.
--
keywords: +patch
nosy: +remi.lapeyre
pull_requests: +11554
Change by Rémi Lapeyre :
--
versions: +Python 3.8 -Python 3.7
___
Python tracker
<https://bugs.python.org/issue35848>
___
___
Python-bugs-list mailing list
Unsub
Rémi Lapeyre added the comment:
I checked and io.TextIOBase is the only io.IOBase subclass to lack one of read,
readinto or write:
>>> import io, inspect
>>> for name, obj in inspect.getmembers(io, predicate=inspect.isclass):
... missing = {'read', 'readinto', 'write'
Rémi Lapeyre added the comment:
It may be relevant: Ruby accept whitespaces in the name of the morsel:
➜ ~ irb
irb(main):002:0> require "cgi"
=> true
irb(main):003:0> CGI::Cookie::parse "ASDF=stuff; ASDF space=more stuff"
=> {"ASDF&q
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue31456>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
> 2) Topological sorting usually is well-defined on totally connected graphs,
> so I do not know what exactly it means to topologically sort two disjoint
> graphs. This was one of the main drawbacks of the tuple-based approach, but I
> think it m
Rémi Lapeyre added the comment:
Wouldn't be the 5-th percentile be select(data, round(len(data)/20)?
--
___
Python tracker
<https://bugs.python.org/issue35
Change by Rémi Lapeyre :
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue20399>
___
___
Python-bugs-list mailing list
Unsubscribe:
Rémi Lapeyre added the comment:
Is this proposal still relevant? If so, I would like to work on its
implementation.
I think the third proposition to change the API to have a new `weights`
parameter is the best has it does not blindly suppose that a tuple is a pair
(value, weight) which
Change by Rémi Lapeyre :
--
versions: +Python 3.8 -Python 3.7
___
Python tracker
<https://bugs.python.org/issue20479>
___
___
Python-bugs-list mailing list
Unsub
Rémi Lapeyre added the comment:
I suggest we closed this issue in favor of #35775 to discuss adding a selection
function and the attached PR.
--
nosy: +remi.lapeyre
___
Python tracker
<https://bugs.python.org/issue30
Change by Rémi Lapeyre :
--
nosy: +rhettinger, steven.daprano
___
Python tracker
<https://bugs.python.org/issue35775>
___
___
Python-bugs-list mailing list
Unsub
Change by Rémi Lapeyre :
--
keywords: +patch, patch
pull_requests: +11337, 11338
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Rémi Lapeyre :
--
keywords: +patch
pull_requests: +11337
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35775>
___
___
Py
301 - 400 of 506 matches
Mail list logo
