Max Bachmann added the comment:
Thanks Dennis. This helped me track down the issue in rapidfuzz.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Max Bachmann added the comment:
It appears this only occurs when a C Extension is involved. When the so is
imported first it is preferred over the .py file that the user would like to
import. I could not find any documentation on this behavior, so I assume that
this is not the intended.
My
New submission from Max Bachmann :
In my environment I installed the following two libraries:
```
pip install rapidfuzz
pip install python-Levenshtein
```
Those two libraries have the following structures:
rapidfuzz
|-distance
|- __init__.py (from . import Levenshtein)
|- Levenshtein.*.so
Max Katsev added the comment:
Note that deepcopy doesn't work either, even though it looks like it does at
the first glance (which is arguably worse since it's harder to notice):
Python 3.8.6 (default, Jun 4 2021, 05:16:01)
>>> import copy, os, subprocess
>>> env_co
Max added the comment:
option 1 looks most attractive to me (and will also look most attractive in the
rendering, IMHO -- certainly better than "await" "x", in any case).
P.S.: OK, thanks for explanations concerning 3.6 - 3.8. I do understand that it
won't be fixe
Max added the comment:
Thanks for fixing the typo, didn't knnow how to do that when I spotted it (I'm
new to this).
You also removed Python version 3.6, 3.7, 3.8, however, I just tested on
pythonanywhere,
>>> sys.version
'3.7.0 (default, Aug 22 2018, 20:50:05) \n[GCC 5.4.0 201606
New submission from Max :
Nobody seems to have noticed this AFAICS:
If you type, e.g., help('+') to get help on operator precedence, the fist
column gives a lit of operators for each row corresponding to a given
precedence. However, the row for "not" (and similar for "await&q
Max Bachmann added the comment:
As far as a I understood this is caused by the same reason:
```
>>> s = '123\U00010900456'
>>> s
'123ऀ456'
>>> list(s)
['1', '2', '3', 'ऀ', '4', '5', '6']
# note that everything including the commas is mirrored until ] is reached
Max Bachmann added the comment:
> That is using Python 3.9 in the xfce4-terminal. Which xterm are you using?
This was in the default gnome terminal that is pre-installed on Fedora 34 and
on windows I directly opened the Python Terminal. I just installed
xfce4-terminal on my Fedora 34 mach
Max Bachmann added the comment:
This is the result of copy pasting example posted above on windows using
```
Python 3.7.8 (tags/v3.7.8:4b47a5b6ba, Jun 28 2020, 08:53:46) [MSC v.1916 64 bit
(AMD64)] on win32
```
which appears to run into similar problems:
```
>>> s
New submission from Max Bachmann :
I noticed that when using the Unicode character \U00010900 when inserting the
character as character:
Here is the result on the Python console both for 3.6 and 3.9:
```
>>> s = '0ऀ00'
>>> s
'0ऀ00'
>>> ls = list(s)
>>> ls
['0
Change by Max Marrone :
--
title: Signaling an asyncio subprocess raises ProcessLookupError, depending on
timing -> Signaling an asyncio subprocess might raise ProcessLookupError, even
if you haven't called .wait() yet
___
Python tracker
<
New submission from Max Marrone :
# Summary
Basic use of `asyncio.subprocess.Process.terminate()` can raise a
`ProcessLookupError`, depending on the timing of the subprocess's exit.
I assume (but haven't checked) that this problem extends to `.kill()` and
`.send_signal()`.
This breaks
Change by Max Bélanger :
--
nosy: +maxbelanger
nosy_count: 4.0 -> 5.0
pull_requests: +24011
pull_request: https://github.com/python/cpython/pull/25274
___
Python tracker
<https://bugs.python.org/issu
Change by Max Bélanger :
--
nosy: +maxbelanger
nosy_count: 18.0 -> 19.0
pull_requests: +24010
pull_request: https://github.com/python/cpython/pull/25274
___
Python tracker
<https://bugs.python.org/issu
Change by Max Prokop :
--
components: +2to3 (2.x to 3.x conversion tool), Argument Clinic, Build, C API,
Cross-Build, Demos and Tools, Distutils, Documentation, asyncio, ctypes
nosy: +Alex.Willmer, asvetlov, dstufft, eric.araujo, larry, yselivanov
type: enhancement -> compile er
New submission from Max Bachmann :
The documentation stated, that the PyUnicode_KIND macro has the following
interface:
- int PyUnicode_KIND(PyObject *o)
However it actually returns a value of the underlying type of the
PyUnicode_Kind enum. This could be e.g. an unsigned int as well
Max Bolingbroke added the comment:
As of Python 3.7.9 this also affects \xf9\xd6 which should be \u7881 in
Unicode. This character is the second character of 宏碁 which is the name of the
Taiwanese electronics manufacturer Acer.
You can work around the issue using big5hkscs just like
Change by Max Bélanger :
--
keywords: +patch
nosy: +maxbelanger
nosy_count: 1.0 -> 2.0
pull_requests: +23495
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24719
___
Python tracker
<https://bugs.python.org/i
New submission from Max Parry :
The German alphabet has four extra characters (ä, ö, ü and ß) when compared to
the UK/USA alphabet. Until 2017 the character ß was normally only lower case.
Upper case ß was represented by SS. In 2017 upper case ß was introduced,
although SS is still often
New submission from Max Bachmann :
The documentation of PyObject_Call here:
https://docs.python.org/3/c-api/call.html#c.PyObject_Call
states, that it is the equivalent of the Python expression: callable(*args,
**kwargs).
so I would expect:
PyObject* args = PyTuple_New(0);
PyObject* kwargs
Change by Max Desiatov :
--
nosy: -MaxDesiatov
___
Python tracker
<https://bugs.python.org/issue41100>
___
___
Python-bugs-list mailing list
Unsubscribe:
Max added the comment:
I've just noticed an issue with the current version of the patch. It should
also include 0x20 (space) since that can also be used to manipulate the request.
--
___
Python tracker
<https://bugs.python.org/issue39
Max added the comment:
I agree that the solution is quite restrictive.
Restricting to ASCII characters alone would certainly work.
--
___
Python tracker
<https://bugs.python.org/issue39
New submission from Max :
I recently came across a bug during a pentest that's allowed me to perform some
really interesting attacks on a target. While originally discovered in
requests, I had been forwarded to one of the urllib3 developers after agreeing
that fixing it at it's lowest level
Change by Max Vorobev :
--
keywords: +patch
pull_requests: +17708
stage: test needed -> patch review
pull_request: https://github.com/python/cpython/pull/18336
___
Python tracker
<https://bugs.python.org/issu
Max Coplan added the comment:
Well I’ve submitted a fix for it. It isn’t perfect. Well, while it doesn’t
look perfect, it actually worked with everything I’ve thrown at it, and seems
to be a very robust and sufficient fix.
--
___
Python tracker
Change by Max Coplan :
--
title: asyncio cannot handle Python3 IPv4Address or IPv6 Address -> asyncio
cannot handle Python3 IPv4Address
___
Python tracker
<https://bugs.python.org/issu
Change by Max Coplan :
--
keywords: +patch
pull_requests: +16913
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/17434
___
Python tracker
<https://bugs.python.org/issu
New submission from Max Coplan :
Trying to use new Python 3 `IPv4Address`s fails with the following error
```
File
"/usr/local/Cellar/python/3.7.5/Frameworks/Python.framework/Versions/3.7/lib/python3.7/asyncio/base_events.py",
line 1270, in _ensure_resolved
info = _ipaddr_info(
Change by Max :
--
keywords: +patch
pull_requests: +15979
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/16398
___
Python tracker
<https://bugs.python.org/issu
New submission from Max Voss :
Hello all,
I've been trying to understand multiprocessing for a while, I tried multiple
times. The PR is a suggested enhancement to the example that made it "click"
for me. Or should I say, produced a working result that made sense to me.
Detail
New submission from Max :
I believe in both cases below, the ouptu should be ['a', 'b']; the extra ' '
inserted in the list is incorrect:
python3.6
Python 3.6.2 (default, Aug 4 2017, 14:35:04)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or
Change by Max Bowsher :
--
nosy: +Max Bowsher
___
Python tracker
<https://bugs.python.org/issue35203>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Max Bélanger :
--
keywords: +patch
pull_requests: +9599
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35139>
___
___
Py
Change by Max Bélanger :
--
keywords: +patch
pull_requests: +9469
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35080>
___
___
Py
Change by Max Bélanger :
--
keywords: +patch
pull_requests: +9308
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35025>
___
___
Py
Change by Max Bélanger :
--
keywords: +patch
pull_requests: +9307
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35022>
___
___
Py
Max Rees <maxcr...@me.com> added the comment:
Actually the symlinks don't need to be broken. It fails for any kind of symlink
on musl.
$ ls -l /tmp/symtest
lrwxrwxrwx 1 mcrees mcrees 10 Apr 18 21:16 empty -> /var/empty
-rw-r--r-- 1 mcrees mcrees 0 Apr 18 21:16 regular
lrwxrwxrwx
Change by Max Bélanger <aero...@gmail.com>:
--
keywords: +patch
pull_requests: +4703
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by Max Bélanger <aero...@gmail.com>:
--
keywords: +patch
pull_requests: +4702
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by Max Bélanger <aero...@gmail.com>:
--
keywords: +patch
pull_requests: +4700
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Change by Max Bélanger <aero...@gmail.com>:
--
keywords: +patch
pull_requests: +4148
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<https://bugs.pyt
Max Rothman <max.r.roth...@gmail.com> added the comment:
Hi, I'd like to wrap this ticket up and get some kind of resolution, whether
it's accepted or not. I'm new to the Python community, what's the right way to
prompt a discussion about this sort of thing? Should I have taken it
Max Rothman added the comment:
Hi, just wanted to ping this again and see if there was any movement.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Max Rothman added the comment:
> Generally the called with asserts can only be used to match the *actual
> call*, and they don't determine "equivalence".
That's fair, but as unittest.mock stands now, it *does* check equivalence, but
only partially, which is more confusing to u
Changes by Max Vorobev <vmax0...@gmail.com>:
--
pull_requests: +2595
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30825>
___
_
New submission from Max Vorobev:
Line terminator defaults to '\r\n' while detecting dialect in csv.Sniffer
--
components: Library (Lib)
messages: 297497
nosy: Max Vorobev
priority: normal
severity: normal
status: open
title: csv.Sniffer does not detect lineterminator
type: behavior
Max Rothman added the comment:
I'd be happy to look at submitting a patch for this, but it'd be helpful to be
able to ask questions of someone more familiar with unittest.mock's code.
--
___
Python tracker <rep...@bugs.python.org>
New submission from Max Rothman:
For a function f with the signature f(foo=None), the following three calls are
equivalent:
f(None)
f(foo=None)
f()
However, only the first two are equivalent in the eyes of
unittest.mock.Mock.assert_called_with:
>>> with patch('__main__.f', auto
New submission from Max Ehrlich:
On line 393 of multiprocessing/connection.py, the size of the payload to be
sent is serialized as an integer. This fails for sending large payloads. It
should probably be serialized as a long or better yet a long long.
--
components: Library (Lib
Max Staff added the comment:
...at least those are the only two ways that I can think of.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Max Staff added the comment:
Yes I know about the errno. There would be two ways to resolve this:
One way would be by introducing a new exception class which would be nice
because it's almost impossible to reliably check the allowed filename length
(except for trial and error) and I have
New submission from Max Staff:
There are different ways to catch exceptions of the type "OSError": By using
"except OSError as e:" and then checking the errno or by using "except
FileNotFoundError e:" or "except FileExistsError e:" or whatever error
Max added the comment:
Ah sorry about that ... Yes, everything works fine when used properly.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
New submission from Max:
This probably shouldn't happen:
import enum
class E(enum.Enum):
A = enum.auto
B = enum.auto
x = E.B.value
print(x) #
print(E(x)) # E.A
The first print() is kinda ok, I don't really care about which value was used
New submission from Max:
The documentation states that subprocess.STDOUT is:
Special value that can be used as the stderr argument to Popen and indicates
that standard error should go into the same handle as standard output.
However, when Popen is called with stdout=None, stderr
Max added the comment:
Correction: this PR is useful for `ProcessPoolExecutor` as well. I thought
`chunksize` parameter handles infinite generators already, but I was wrong.
And, as long as the number of items prefetched is a multiple of `chunksize`,
there are no issues with the chunksize
Max added the comment:
I'm also concerned about this (undocumented) inconsistency between map and
Executor.map.
I think you would want to make your PR limited to `ThreadPoolExecutor`. The
`ProcessPoolExecutor` already does everything you want with its `chunksize`
paramater, and adding
Max added the comment:
Sorry, this should be just a documentation issue.
I just realized that __eq__ = None isn't correct anyway, so instead we should
just document that Hashable cannot check for __eq__ and that explicitly
deriving from Hashable suppresses hashability.
--
components
New submission from Max:
I think collections.abc.Hashable.__subclasshook__ should check __eq__ method in
addition to __hash__ method. This helps detect classes that are unhashable due
to:
to __eq__ = None
Of course, it still cannot detect:
def __eq__: return NotImplemented
but it's better
New submission from Max:
There's a known issue with `shutil.rmtree` on Windows, in that it fails
intermittently.
The issue is well known
(https://mail.python.org/pipermail/python-dev/2013-September/128353.html), and
the agreement is that it cannot be cleanly solved inside `shutil
Max added the comment:
Actually, never mind, I think one of the paragraphs in the Programming
Guidelines ("Explicitly pass resources to child processes") basically explains
everything already. I just didn't notice it until @noxdafox pointed it out to
me on SO.
Cl
Max Rothman added the comment:
I think that makes sense, but there's still an open question: what should the
correct way be to allow dashes to be present at the beginning of positional
arguments?
--
___
Python tracker <rep...@bugs.python.org>
Max added the comment:
Somewhat related is this statement from Programming Guidelines:
> When using the spawn or forkserver start methods many types from
> multiprocessing need to be picklable so that child processes can use them.
> However, one should generally avoid sending share
Max added the comment:
Yes, this makes sense. My bad, I didn't realize processes might need to wait
until the queue is consumed.
I don't think there's any need to update the docs either, nobody should have
production code that never reads the queue (mine was a test of some other
issue
New submission from Max:
Using multiprocessing.Queue() with several processes writing very fast results
in a deadlock both on Windows and UNIX.
For example, this code:
from multiprocessing import Process, Queue, Manager
import time, sys
def simulate(q, n_results):
for i in range
Max added the comment:
How about inserting this text somewhere:
Note that sharing and synchronization objects (such as `Queue()`, `Pipe()`,
`Manager()`, `Lock()`, `Semaphore()`) should be made available to a new process
by passing them as arguments to the `target` function invoked by the `run
New submission from Max:
It seems both me and many other people (judging from SO questions) are confused
about whether it's ok to write this:
from multiprocessing import Process, Queue
q = Queue()
def f():
q.put([42, None, 'hello'])
def main():
p = Process(target=f)
p.start
Max Rothman added the comment:
Martin: huh, I didn't notice that documentation. The error message definitely
could be improved.
It still seems like an odd choice given that argparse knows about the expected
spec, so it knows whether there are any options or not. Perhaps one could
enable
New submission from Max Rothman:
In the case detailed below, argparse.ArgumentParser improperly parses the
argument string "-_":
```
import argparse
parser = argparse.ArgumentParser()
parser.add_argument('first')
print(parser.parse_args(['-_']))
```
Expected behavior: prints Names
New submission from Max:
According to the
[docs](https://docs.python.org/3/library/pickle.html#pickling-class-instances):
> Note: At unpickling time, some methods like `__getattr__()`,
> `__getattribute__()`, or `__setattr__()` may be called upon the instance. In
> case those met
Max added the comment:
@yselivanov I just wanted to use the handler to avoid storing the callback and
args in my own data structure (I would just store the handlers whenever I may
need to reschedule). Not a big deal, I don't have to use handler as a storage
space, if it's not supported across
New submission from Max:
Is it safe to use the _callback and _args attributes of asyncio.Handle? Is it
possible to officially expose them as public API?
My use case:
handle = event_loop.call_later(delay, callback)
# this function can be triggered by some events
def reschedule
Max added the comment:
Martin - what you suggest is precisely what I had in mind (but didn't phrase it
as well):
> to document the above sort of behaviour as being directly associated with
> operations like as == and !=, and only indirectly associated with the
> NotImplement
New submission from Max:
Currently, there's no clear statement as to what exactly the fallback is in
case `__eq__` returns `NotImplemented`. It would be good to clarify the
behavior of `NotImplemented`; at least for `__eq__`, but perhaps also other
rich comparison methods. For example: "
Max von Tettenborn added the comment:
You are very welcome, glad I could help.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from Max von Tettenborn:
Below code reproduces the problem. The resulting error is a RecursionError and
it is very hard to trace that to the cause of the problem, which is the runner
task and the stop task yielding from each other, forming a deadlock.
I think, an easy to make
Max Khon added the comment:
I reproduced the problem with Python 2.7.5 as shipped with CentOS 7:
root@192.168.0.86 /home/padmin # python -V
Python 2.7.5
root@192.168.0.86 /home/padmin # rpm -q python
python-2.7.5-34.el7.x86_64
root@192.168.0.86 /home/padmin #
(gdb) bt
#0 lookdict_string (mp
New submission from Max Farrell:
Cannot install Python 3.5 64-bit on Windows 10 64-bit Educational Edition.
I have Python 3.4 Installed.
Log include.
--
components: Installation
files: Python 3.5.0 (64-bit)_20151006150920.log
messages: 252423
nosy: Max Farrell
priority: normal
Max Farrell added the comment:
Windows 10 64-Bit Educational Edition.
Python 3.5 64-bit Installation failed. Directory is corrupt.
Log included.
--
title: Windows 10 Installation Fails With Corrupt Directory Error -> Python 3.5
Windows 10 Installation Fails With Corrupt Directory Er
New submission from Max:
PEP8 doesn't verifies last line at all. Also W292 will never be checked.
Reproducible on PEP8 = 1.5.0
--
messages: 216072
nosy: f1ashhimself
priority: normal
severity: normal
status: open
title: PEP8 doesn't verifies last line.
type: behavior
Max Naumov added the comment:
Wouldn't this be more correct?
--- Lib/distutils/msvc9compiler.py 2013-08-03T16:17:08+04:00
+++ Lib/distutils/msvc9compiler.py 2014-03-17T18:36:50.078672+04:00
@@ -411,7 +411,11 @@
'/Z7', '/D_DEBUG
Max Naumov added the comment:
It allows to install numpy on windows python 3.4. Just like the patch in the
original post. Actually my patch is merely the original patch refactored.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
New submission from Max Polk:
In the docs (both Python 2 and 3) for the multiprocessing module, the Proxy
section needs to be explicit about the fact that is does NOT create locks
around access to shared objects.
Why? Because on the same page, we read about
New submission from Max Kaye:
Python 2.7.3 (v2.7.3:70274d53c1dd, Apr 9 2012, 20:52:43)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type help, copyright, credits or license for more information.
print round(1.123456, 3)
1.123
print round(1.123756, 3)
Segmentation fault: 11
Max DeLiso added the comment:
ok I checked in to this more deeply and I was wrong about a few things. first,
my patch is worthless - there are several more instances where the retval of
fileno is passed directly to fstat and that is totally valid (provided the
file* points to a valid file
New submission from Max DeLiso:
hi.
if you cross compile the mercurial native extensions against python 2.7.5 (x64)
on 64 bit windows 7 and then try to clone something, it will crash.
I believe the reason for this is that the c runtime functions in the microsoft
crt will throw a win32
Changes by Max DeLiso maxdel...@gmail.com:
--
hgrepos: -199
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18197
___
___
Python-bugs-list mailing
New submission from Max Cantor:
When you specify a nonexistent encoding at the top of a file, like so for
example:
# -*- coding: fakefakefoobar -*-
The following exception occurs:
SyntaxError: encoding problem: with BOM
This is very unhelpful, especially in cases where you might have made
Changes by Max Mautner max.maut...@gmail.com:
--
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17724
New submission from Max Cantor:
On certain Linux distributions such as Ubuntu, the linker is invoked by default
with --as-needed, which has an undesireable side effect when linking static
libraries: it is bad at detecting required symbols, and the order of libraries
on the command line become
New submission from Max Mautner:
Response handlers are registered with the OpenerDirector class in the
urllib.request module using the add_handler method--it's a convoluted method
that I refactored for legibility's sake.
--
files: urllib_add_handler.patch
keywords: patch
messages
New submission from Max:
http://docs.python.org/dev/glossary.html?highlight=hashable says:
Objects which are instances of user-defined classes are hashable by default;
they all compare unequal, and their hash value is their id().
Since x == x returns True by default, so they all compare
Max added the comment:
I agree about reflected operation, although the wording could be clearer (will
try reflected operation is better worded as will return the result of the
reflected operation called on the swapped arguments.)
But what does it mean or some other fallback? And what
New submission from Max:
In dev/reference/datamodel#object.__hash__, there are two paragraphs that seem
inconsistent. The first paragraph seems to say that a class that overrides
__eq__() *should* explicitly flag itself as unhashable. The next paragraph says
that a class that overrides __eq__
New submission from Max:
Quoting from
http://docs.python.org/reference/datamodel.html#the-standard-type-hierarchy:
NotImplemented
This type has a single value. There is a single object with this value. This
object is accessed through the built-in name NotImplemented. Numeric methods
and rich
Max added the comment:
I propose to close this issue as fixed.
The first two problems in the OP are now resolved through patches to pickle.
The third problem is addressed by issue5370: it is a documented feature of
pickle that anyone who defines __setattr__ / __getattr__ that depend
New submission from Max maxmo...@gmail.com:
Currently -O optimizer flag disables assert statements.
I want to ask that more fine-grained control is offered to users over the
assert statements. In many cases, it would be nice to have the option of
keeping asserts in release code, while still
Max Franks eliqui...@gmail.com added the comment:
Issue 3 is not related to the other 2. See this post
http://bugs.python.org/issue5370. As haypo said, it has to do with unpickling
objects. The post above gives a solution by using the __setstate__ function.
--
nosy: +eliquious
1 - 100 of 124 matches
Mail list logo
