Ryan Fox added the comment:
If you change the class member 'x' to a different name like 'y', then cv
doesn't include 'x', but does include an unbound 'y'.
In both cases, the function isn't referring to a global variable, just the
class member of that name. Besides the function itself
Change by Ryan May :
--
nosy: +Ryan May
___
Python tracker
<https://bugs.python.org/issue44556>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ryan Mast (nightlark) added the comment:
> How is manually dispatched workflows different from just opening a PR to your
> own fork? I do that from time to time in order to run the CI before opening a
> PR against the CPython repo.
Here are a few thoughts on how it is different:
-
Ryan Mast (nightlark) added the comment:
I haven't gotten a chance to narrow it down much yet, it might be that it is
occurs more often on systems with a low core count/higher load -- a bit hard to
tell with it being intermittent though
Ryan Mast (nightlark) added the comment:
> On the main request, provided the workflow_dispatch is only triggerable by
> non-contributors in their own fork (without any of our tokens/etc.) then it's
> fine by me. If it allows anyone to trigger CI builds against the main repo,
>
Ryan Mast (nightlark) added the comment:
Another observation, first-time contributors need a maintainer to approve the
workflows for their PRs -- from the looks of it that isn't an instant process
and could take a few days, so this also gives first-time contributors a way to
check
Change by Ryan Mast (nightlark) :
--
nosy: +brett.cannon
___
Python tracker
<https://bugs.python.org/issue44972>
___
___
Python-bugs-list mailing list
Unsub
Change by Ryan Mast (nightlark) :
--
nosy: +steve.dower
___
Python tracker
<https://bugs.python.org/issue44972>
___
___
Python-bugs-list mailing list
Unsub
Change by Ryan Mast (nightlark) :
--
keywords: +patch
pull_requests: +26328
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/27873
___
Python tracker
<https://bugs.python.org/issu
Change by Ryan Mast (nightlark) :
--
nosy: +FFY00
___
Python tracker
<https://bugs.python.org/issue44972>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ryan Mast (nightlark) added the comment:
* The main constraint is that the the `workflow_dispatch` trigger must be in
the GHA workflow yaml files for the branch to be selectable as a target on the
Actions tab when manually triggering a workflow. Having the change made to the
main branch
New submission from Ryan Mast (nightlark) :
Adding a workflow_dispatch trigger for the GitHub Actions jobs makes it
possible to run the GHA CI jobs for commits to branches in a fork without
opening a "draft/WIP" PR to one of the main release branches. It also runs the
SSL t
Ryan Mast (nightlark) added the comment:
The new issue for the failing test is bpo-44968
--
___
Python tracker
<https://bugs.python.org/issue41322>
___
___
Pytho
New submission from Ryan Mast (nightlark) :
A deprecation made in bpo-41322 uncovered issues with
test_subprocess_wait_no_same_group in test_asyncio that seems to have been
broken for some time.
Reverting to a similar structure prior to the refactoring in
https://github.com/python/cpython
Ryan Mast (nightlark) added the comment:
Sure, I'll open a new issue.
--
___
Python tracker
<https://bugs.python.org/issue41322>
___
___
Python-bugs-list mailin
Ryan Mast (nightlark) added the comment:
Would rewriting the test so that it doesn't yield be the right fix?
```
def test_subprocess_wait_no_same_group(self):
# start the new process in a new session
connect = self.loop.subprocess_shell
Ryan Mast (nightlark) added the comment:
It looks like since GH-27748 got merged, `test_subprocess_wait_no_same_group`
in `test_asyncio` has been failing for the Ubuntu SSL tests.
--
nosy: +rmast
___
Python tracker
<https://bugs.python.
Change by Ryan Mast (nightlark) :
--
nosy: +rmast
___
Python tracker
<https://bugs.python.org/issue20041>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ryan Mast (nightlark) :
--
nosy: +rmast
___
Python tracker
<https://bugs.python.org/issue26545>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ryan Mast (nightlark) :
--
nosy: +rmast
___
Python tracker
<https://bugs.python.org/issue15373>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ryan Mast (nightlark) added the comment:
I'm new to this system, if I'm understanding
https://devguide.python.org/triaging/#nosy-list then it looks like the people
listed for `tkinter` should be added to the Nosy List?
--
nosy: +gpolo, serhiy.storchaka
New submission from Ryan Mast (nightlark) :
Tk the number pad enter and main enter keys separately. The number pad enter
button should be bound to `self.ok` in simpleDialog's `Dialog` class so that
both enter buttons have the same behavior.
A PR for this change has been submitted on GitHub
Ryan Mast (nightlark) added the comment:
It looks like this has a PR that just needs rebasing, then it will be ready for
another review.
--
nosy: +rmast
___
Python tracker
<https://bugs.python.org/issue24
Ryan Mast (nightlark) added the comment:
If this function were to be implemented on Windows would the preferred
approach be the one described in the initial message for this issue of creating
a Windows `os.set_owner` function that uses the appropriate Windows API calls
to change owner
Ryan Mast added the comment:
Should this be closed? It looks like the PR is only changing a file in
distutils, and according to https://bugs.python.org/issue30925#msg386350
distutils is deprecated and only release blocking issues will be considered.
--
nosy: +rmast
Ryan Pecor added the comment:
Wow, that was quick and the code looks clean too! Thanks for fixing that up!
--
___
Python tracker
<https://bugs.python.org/issue44
Ryan Pecor added the comment:
Actually, hasattr() specifically states that it uses getattr() so that behavior
is expected from getattr() so I will not be creating a separate issue for that.
Now that I see hasattr() uses getattr(), it looks like the tab completion issue
might not stem from
Ryan Pecor added the comment:
It looks to me like the issue is caused by the eval() in line 155 of the
rlcompleter.py file
(https://github.com/python/cpython/blob/bb3e0c240bc60fe08d332ff5955d54197f79751c/Lib/rlcompleter.py#L155)
which runs the function in order to see if it runs or raises
Ryan Pecor added the comment:
I forgot to mention that I also added "~~~" to either side of the printed
string every time it printed to help differentiate the printed string from
commands that I typed into the interpreter.
--
___
Pyth
New submission from Ryan Pecor :
After making a class using the @property decorator to implement a getter, using
tab completion that matches the getter function name executes the function.
See below for example (line numbers added, indicates when the user
presses the tab key):
1
Change by Ryan Ozawa :
--
pull_requests: +25912
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/27376
___
Python tracker
<https://bugs.python.org/issu
Ryan Ozawa added the comment:
Hi all,
This is my first issue so feedback is welcome.
Following @vstinner 's suggestions:
> * os.rename() can fail if source and destination are on two different
file systems
> * Use shutil.move() to support move to a different directory
And from @e
Change by Ryan Rudes :
--
components: +Library (Lib) -Tkinter
___
Python tracker
<https://bugs.python.org/issue44437>
___
___
Python-bugs-list mailing list
Unsub
Change by Ryan Rudes :
--
keywords: +patch
pull_requests: +25347
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26762
___
Python tracker
<https://bugs.python.org/issu
Change by Ryan Rudes :
--
components: Tkinter
nosy: Ryan-Rudes
priority: normal
severity: normal
status: open
title: Add multimap() function similar to map(), but with multiprocessing
functionality to the multiprocessing module
type: enhancement
versions: Python 3.10, Python 3.11
Ryan Hileman added the comment:
> Do you think that pytime.c has the bug? I don't think so.
No, a misaligned stack would be an issue in the caller or compiler, not
pytime.c. I have hit misaligned stack in practice, but it should be rare enough
to check on init only.
> In theo
Ryan Hileman added the comment:
> It shouldn't behave drastically different just because the user closed the
> laptop lid for an hour
I talked to someone who's been helping with the Go time APIs and it seems like
that holds pretty well for interactive timeouts, but makes no
Ryan Hileman added the comment:
Perhaps the simplest initial fix would be to move that check down to
PyThread__init_thread() in the same file. I'm not sure what the cpython
convention for that kind of init error is, would it just be the same
Py_FatalError block or is there a better pattern
Ryan Hileman added the comment:
I agree with not throwing fatal errors, but that check is unlikely to actually
be hit, and you removed the startup checks covering the underlying clocks here:
https://github.com/python/cpython/commit/ae6cd7cfdab0599139002c526953d907696d9eef
I think
Ryan Hileman added the comment:
> The monotonic clock should thus be based on QueryUnbiasedInterruptTime
My primary complaint here is that Windows is the only major platform with a low
resolution monotonic clock. Using QueryUnbiasedInterruptTime() on older OS
versions wouldn't entirely h
Ryan Hileman added the comment:
I think a lot of that is based on very outdated information. It's worth reading
this article:
https://docs.microsoft.com/en-us/windows/win32/sysinfo/acquiring-high-resolution-time-stamps
I will repeat Microsoft's current recommendation (from that article
Ryan Hileman added the comment:
Great information, thanks!
> Windows 10 also provides QueryInterruptTimePrecise(), which is a hybrid
> solution. It uses the performance counter to interpolate a timestamp between
> interrupts. I'd prefer to use this for time.monotonic() inste
Ryan Hileman added the comment:
I found these two references:
-
https://stackoverflow.com/questions/35601880/windows-timing-drift-of-performancecounter-c
- https://bugs.python.org/issue10278#msg143209
Which suggest QueryPerformanceCounter() may be bad because it can drift.
However
Ryan Hileman added the comment:
Ok, I filed a PR for this. I used pytime's interface to avoid duplicating the
QueryPerformanceFrequency() code.
I found a StackOverflow answer that says QueryPerformance functions will only
fail if you pass in an unaligned pointer: https://stackoverflow.com
Change by Ryan Hileman :
--
keywords: +patch
pull_requests: +25157
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26568
___
Python tracker
<https://bugs.python.org/issu
New submission from Ryan Hileman :
Related to https://bugs.python.org/issue41299#msg395220
Presumably `time.monotonic()` on Windows historically used GetTickCount64()
because QueryPerformanceCounter() could fail. However, that hasn't been the
case since Windows XP:
https
Change by Ryan Hileman :
--
versions: +Python 3.10, Python 3.11, Python 3.9
___
Python tracker
<https://bugs.python.org/issue41299>
___
___
Python-bugs-list m
Ryan Hileman added the comment:
I just ran into this. GetTickCount64() is a bad choice even without improving
the Windows timer resolution, as every mutex wait will have 16ms of jitter.
Here are some lock.acquire(timeout=0.001) times measured with
time.perf_counter():
elapsed=21.215ms
New submission from Ryan Tarpine :
Functions registered with unittest.addModuleCleanup are not called unless the
user defines tearDownModule in their test module.
This behavior is unexpected because functions registered with
TestCase.addClassCleanup are called even the user doesn't define
New submission from Ryan McCampbell :
Until 3.8 the curses window class was not directly available in code, but now
it is available as `_curses.window`. This is not explicitly stated in the
documentation (although it is consistent with how the method signatures are
written). It is useful
Change by Ryan Hiebert :
--
nosy: +ryanhiebert
___
Python tracker
<https://bugs.python.org/issue43532>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ryan Hiebert added the comment:
Thank you, Christian. It sounds like you believe that we should view the
`_get_socket` method as a public interface? That at least makes it possible to
use a proxy socket through an appropriate mechanism, which solves my use-case
Change by Ryan Hiebert :
--
nosy: +ryanhiebert
___
Python tracker
<https://bugs.python.org/issue29687>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ryan Hileman added the comment:
> Sounds good to me. We can deprecate RESTRICTED with no intention to
remove it, since it's documented.
> Do you want to prepare a PR for this?
In case you missed it, the attached PR 24182 as of commit d3e998b is based on
the steps I listed - I mov
Ryan Hileman added the comment:
Just updated the PR with another much simpler attempt, using a new READ_AUDIT
flag (aliased to READ_RESTRICTED, and newtypes documentation updated).
I re-ran timings for the new build, and in all cases they match or slightly
beat my previous reported timings
Ryan Hileman added the comment:
I agree that READ_RESTRICTED would work, and I'm strongly in support of
refactoring my patch around that kind of flag, as it simplifies it quite a bit
and the if statement is already there.
However, using the seemingly legacy RESTRICTED flag names for audit
Ryan Hileman added the comment:
How's this for maintainable?
https://github.com/lunixbochs/cpython/commit/2bf1cc93d19a49cbed09b45f7dbb00212229f0a1
--
___
Python tracker
<https://bugs.python.org/issue42
Ryan Hileman added the comment:
My understanding as per the outline in PEP 551 as well as PEP 578, is that the
audit system is meant primarily to observe the behavior of code rather than to
have good sandbox coverage / directly prevent behavior.
I am using audit hooks to observe
Ryan Hileman added the comment:
My personal motivation is not to unilaterally prevent access to globals, but to
close a simpler gap in the audit system that affects a currently deployed high
performance production system (which is not trying to be a sandbox). I am also
already using a C
Ryan Hileman added the comment:
I just found out that generator object variants have their own code attributes.
I investigated the stdlib usage and it seems to be for debug / dis only, so
adding these attributes shouldn't impact performance.
I updated the PR to now cover the following
Ryan Heisler added the comment:
Perfect, thanks for your quick response. I was passing a bound method of obj as
the func to `weakref.finalize(obj, func, /, *args, **kwargs)`. It slipped my
mind that an instance variable like self.name and a bound method like
self.clean_up, though they both
New submission from Ryan Heisler :
In the documentation for `weakref.finalize`
(https://docs.python.org/3.9/library/weakref.html#weakref.finalize), it says:
"Note It is important to ensure that func, args and kwargs do not own any
references to obj, either directly or indirectly,
Ryan Hileman added the comment:
PR submitted, waiting on CLA process.
I added documentation at the field sites, but the audit event table generation
does not handle attributes or object.__getattr__ very well at all, so I'm not
updating the audit table for now.
The `.. audit-event:: object
Change by Ryan Hileman :
--
keywords: +patch
pull_requests: +23010
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/24182
___
Python tracker
<https://bugs.python.org/issu
Ryan Hileman added the comment:
Oops, by tb_code I meant traceback.tb_frame.f_code. So you can get to a frame
from traceback.tb_frame (without triggering audit) or sys._getframe (which has
an audit hook already), and you can get to __code__ from a frame via
frame.f_code (without triggering
Ryan Hileman added the comment:
I'm definitely not proposing to hook all of object.__getattr__, as my intuition
says that would be very slow. I simply refer to "object.__getattr__" as the
event name used by a couple of rare event audit hooks. This is how getting
__code__ is emitt
Ryan Hileman added the comment:
traceback's `tb_code` attribute also allows you to bypass the
`object.__getattr__` audit event for `__code__`.
Perhaps accessing a traceback object's `tb_code` and `tb_frame` should both
raise an `object.__getattr__` event?
--
nosy: +lunixbochs2
New submission from Ryan Govostes :
The documentation for weakref.proxy() does not describe how the proxy object
behaves when the object it references is gone.
The apparent behavior is that it raises a ReferenceError when an attribute of
the proxy object is accessed.
It would probably
Ryan Sobol added the comment:
Also, I'm a bit puzzled about something from the previously mentioned Integer
class and its use of __future__.annotations.
Why is it possible to declare an Integer return type for the add() method, but
only possible to declare an "Integer" forward
Ryan Sobol added the comment:
Does anyone know why the treatment of unresolved references was changed in 3.9?
--
___
Python tracker
<https://bugs.python.org/issue41
john ryan added the comment:
Thanks. That is understandable. I reported it in case it was helpful.
--
___
Python tracker
<https://bugs.python.org/issue42
New submission from john ryan :
My test environment runs Ubuntu 18.04 in a virtualbox hosted on Windows 8.1 and
Python executes within a venv running Python 3.9.0 (Python 3.9.0 (default, Oct
26 2020, 09:02:51)
[GCC 7.5.0] on linux
Running a test with unittest.IsolatedAsyncioTestCase my code
Ryan Sobol added the comment:
It's worth pointing out that a similar error is produced for a
forward-referenced return type of a registered method, but only for python3.9.
For example:
from __future__ import annotations
from functools import singledispatchmethod
class Integer:
def
New submission from john ryan :
I am building an application that is made up of several separate processes,
where each process is a python program. They are all started by the supervisord
utility and execute within a venv running Python 3.8.5 (default, Aug 13 2020,
15:42:06) [GCC 7.5.0
Change by Ryan Hiebert :
--
nosy: +ryanhiebert
___
Python tracker
<https://bugs.python.org/issue33129>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ryan Westlund added the comment:
Sorry, I forgot the pydoc docs don't have as much information as the online
docs.
On Mon, Jun 22, 2020 at 1:54 PM Ezio Melotti wrote:
>
> Ezio Melotti added the comment:
>
> This behavior was changed in 3.7: "Empty matches for the patte
New submission from Ryan Westlund :
```
>>> re.sub('a*', '-', 'a')
'--'
>>> re.sub('a*', '-', 'aa')
'--'
>>> re.sub('a*', '-', 'aaa')
'--'
```
Shouldn't it be returning one dash, not two, since the greedy quantifier will
match all the a's? I understand why
Ryan Schmidt added the comment:
Christian, thanks for the pointer. I think you're right, I probably am actually
wanting this to be fixed in setuptools, not distutils, since setuptools is what
people are using today. Since setuptools is an offshoot of distutils, I had
assumed
Ryan Schmidt added the comment:
What needs to happen to get this 15 year old bug fixed? It prevents C++ Python
modules from being compiled in situations where the user needs to supply
CXXFLAGS.
--
nosy: +ryandesign
___
Python tracker
<ht
New submission from Ryan C. Gordon :
(Forgive any obvious mistakes in this report, I'm almost illiterate with
Python, doubly so with Python internals.)
In trying to get buildbot-worker running on Haiku ( https://haiku-os.org/ ), it
runs into a situation where it tries to connect a non
Ryan Tu added the comment:
#Maybe not a good solution
I do not know the should we delete the code in cgitb.py or adjust the
configration of apache httpd. My solution is deleting some code as follows:
```
return '''
-->
--> -->
'''
```
Then it works
Ryan Gonzalez added the comment:
Oh my god this was still open? I think you can just use the CC variable, not
sure what 6-years-younger-and-more-stupid me was thinking here. Sorry about the
noise.
--
stage: patch review -> resolved
status: open ->
Ryan McCampbell added the comment:
This seems like a pretty straightforward fix. What's holding it up?
--
nosy: +rmccampbell7
___
Python tracker
<https://bugs.python.org/issue34
Change by Ryan Ware :
--
nosy: +ware
___
Python tracker
<https://bugs.python.org/issue39503>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Change by Ryan Ware :
--
nosy: +ware
___
Python tracker
<https://bugs.python.org/issue38576>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
Ryan Petrello added the comment:
I believe I'm also encountering some version of this bug while importing code
from the kombu library within a multi-threaded context.
For what it's worth, I'm able to reproduce the reported deadlock
(https://bugs.python.org/file48737/issue38884.zip) using
New submission from Ryan McCampbell :
In Python 3.6 the following works:
class HexInt(int):
def __repr__(self):
return hex(self)
class MyEnum(HexInt, enum.Enum):
A = 1
B = 2
C = 3
>>> MyEnum.A
However in Python 3.7/8 it instead prints
>>> MyE
Ryan Govostes added the comment:
This absolutely should be documented. If adding an earlier event is not
supported then it should raise an exception. Appearing the enqueue the event
but not triggering the callback is especially confusing. It may be obvious
behavior to someone who has spent
Change by Ryan Batchelder :
--
keywords: +patch
pull_requests: +17398
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/17995
___
Python tracker
<https://bugs.python.org/issu
New submission from Ryan Batchelder :
I would like to propose that the mimetype for markdown files ending in .md to
text/markdown is included in the mimetypes library. This is registered here:
https://www.iana.org/assignments/media-types/text/markdown
--
messages: 359931
nosy: Ryan
Ryan added the comment:
Thank you, this looks good. I'm pinned to 3.6 so while it won't work for me
currently, maybe it will in a few years.
For clarity and because I can't edit my original message, the RFC is 5424 (I
had mistakenly said 5454 but you got it right
New submission from Ryan :
When using the SysLogHandler
(https://docs.python.org/3/library/logging.handlers.html#logging.handlers.SysLogHandler)
the supported facilities appear to be lagging the RFC (5454 ?), or at least
what is being supported in other mainstream languages. I Specifically
New submission from Ryan McCampbell :
The email.contentmanager.set_bytes_content function which handles bytes content
for raw_data_manager fails when passed cte="7bit" with an AttributeError:
'bytes' object has no attribute 'encode'. This is probably not a major use case
s
New submission from Ryan Thornton :
## Expected Behavior
pip install should download dependencies matching the architecture of the
python executable being used.
## Actual Behavior
When calling pip install from a Visual Studio command prompt configured to
cross compile from x64 to x86, pip
Ryan Govostes added the comment:
The origin of this warning involves interleaving read and write operations, and
was added here: https://bugs.python.org/issue12213
I'm not sure if it applies to sockets, pipes, etc. though.
The pySerial documentation advises using io.BufferedRWPair(x, x
New submission from Ryan Govostes :
The documentation for the io.BufferedRWPair class gives this warning:
> BufferedRWPair does not attempt to synchronize accesses to its underlying raw
> streams. You should not pass it the same object as reader and writer; use
> BufferedRandom in
Change by Ryan May :
--
nosy: +Ryan May
___
Python tracker
<https://bugs.python.org/issue33725>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ryan Govostes :
argparse supports consuming multiple command-line arguments with nargs=2, etc.
It converts them to the type given in the argument's type parameter.
argparse does not provide a good solution when the input arguments should be
different data types
Change by Ryan Hiebert :
--
nosy: +ryanhiebert
___
Python tracker
<https://bugs.python.org/issue30491>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ryan Hiebert :
--
nosy: +ryanhiebert
___
Python tracker
<https://bugs.python.org/issue31387>
___
___
Python-bugs-list mailing list
Unsubscribe:
1 - 100 of 425 matches
Mail list logo
