On 2024-01-17 3:01 AM, Greg Ewing via Python-list wrote:
On 17/01/24 1:01 am, Frank Millman wrote:
I sometimes need to keep a reference from a transient object to a more
permanent structure in my app. To save myself the extra step of
removing all these references when the transient object is
On 17/01/24 1:01 am, Frank Millman wrote:
I sometimes need to keep a reference from a
transient object to a more permanent structure in my app. To save myself
the extra step of removing all these references when the transient
object is deleted, I make them weak references.
I don't see how
On 17/01/24 4:00 am, Chris Angelico wrote:
class Form:
def __init__(self):
self.elements = []
class Element:
def __init__(self, form):
self.form = form
form.elements.append(self)
If you make the reference from Element to Form a weak reference,
it won't
> On 16 Jan 2024, at 17:11, Sibylle Koczian via Python-list
> wrote:
>
> while the new Windows 11 machine finds the Microsoft stub
You can turn off the stub in windows settings. The magic windows jargon is
“App Execution Aliases”. Once you find it in settings you can turn off
the python and
> On 16 Jan 2024, at 12:10, Frank Millman via Python-list
> wrote:
>
> My problem is that my app is quite complex, and it is easy to leave a
> reference dangling somewhere which prevents an object from being gc'd.
What I do to track these problems down is use gc.get_objects() then
> On 16 Jan 2024, at 13:17, Thomas Passin via Python-list
> wrote:
>
> The usual advice is to call deleteLater() on objects derived from PyQt
> classes. I don't know enough about PyQt to know if this takes care of all
> dangling reference problems, though.
It works well and robustly.
Am 15.01.2024 um 23:55 schrieb Mats Wichmann via Python-list:
On 1/15/24 12:01, Thomas Passin via Python-list wrote:
On 1/15/2024 1:26 PM, Mats Wichmann via Python-list wrote:
Python from the App Store is not the same as Python from python.org:
yes. this question is about the python.org
On Wed, 17 Jan 2024 at 01:45, Frank Millman via Python-list
wrote:
>
> On 2024-01-16 2:15 PM, Chris Angelico via Python-list wrote:
> >
> > Where do you tend to "leave a reference dangling somewhere"? How is
> > this occurring? Is it a result of an incomplete transaction (like an
> > HTTP request
On 2024-01-16 2:15 PM, Chris Angelico via Python-list wrote:
Where do you tend to "leave a reference dangling somewhere"? How is
this occurring? Is it a result of an incomplete transaction (like an
HTTP request that never finishes), or a regular part of the operation
of the server?
I have a
On 1/16/2024 4:17 AM, Barry wrote:
On 16 Jan 2024, at 03:49, Thomas Passin via Python-list
wrote:
This kind of thing can happen with PyQt, also. There are ways to minimize it
but I don't know if you can ever be sure all Qt C++ objects will get deleted.
It depends on the type of object
On Tue, 16 Jan 2024 at 23:08, Frank Millman via Python-list
wrote:
>
> On 2024-01-15 3:51 PM, Frank Millman via Python-list wrote:
> > Hi all
> >
> > I have read that one should not have to worry about garbage collection
> > in modern versions of Python - it 'just works'.
> >
> > I don't want to
On 2024-01-15 3:51 PM, Frank Millman via Python-list wrote:
Hi all
I have read that one should not have to worry about garbage collection
in modern versions of Python - it 'just works'.
I don't want to rely on that. My app is a long-running server, with
multiple clients logging on, doing
> On 16 Jan 2024, at 03:49, Thomas Passin via Python-list
> wrote:
>
> This kind of thing can happen with PyQt, also. There are ways to minimize it
> but I don't know if you can ever be sure all Qt C++ objects will get deleted.
> It depends on the type of object and the circumstances.
13 matches
Mail list logo
