Re: [PATCH] Added the libudev python bindings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok, so then I can remove the whole method, and we have no problem with the naming :)

--

  Martin Gracik

----- "Hans de Goede" <hdegoede@xxxxxxxxxx> wrote:

> Hi,
> 
> On 11/11/2009 09:24 AM, Martin Gracik wrote:
> > Hello,
> >
> >> Can we instead only call pyudev.Udev() once and stash an instance
> to
> >> the
> >> object as a global in baseudev.py?  I'm concerned that we're going
> to
> >> be
> >> introducing another big slowdown here in device discovery on very
> >> large
> >> configurations.
> >
> > Propably you're right, I have no idea how many times this get's
> called.
> > What I wanted to do first was rewrite the whole baseudev.py to
> something "better".
> > But Hans stopped me, to rewrite just needed parts, not to break
> anything.
> > So I was just trying to make as little changes as possible to the
> original code.
> >
> > My concern is, where will we call the "teardown" method?
> >
> 
> We would not, we would do one call to libudev_new_udev on import of
> pyudev.py,
> and then never release it, its memory will then get returned to the
> OS
> when python exits.
> 
> Regards,
> 
> Hans
> 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux