non-deterministic DeprecationWarning (not sure how to reproduce)

Bug #505717 reported by David Wagner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Exaile
Fix Released
Low
Unassigned

Bug Description

When running Exaile, I occasionally get the following message in my ~/.xsession-errors:

/usr/local/lib/exaile/xl/trax/track.py:89: DeprecationWarning: integer argument expected, got float
  self.__cleanup)

It doesn't happen every time, and I can't figure out what circumstances trigger it or how to reproduce it reliably. It happens perhaps only to 1 in 3 times I execute Exaile, and I have no clue what causes the difference.

I don't know whether this warning matters. It might be nothing and ignorable. I'm reporting it in case it reflects some underlying issue in the code that you'd want to know about.

This is with the bzr head (bzr 2803), on Fedora 12 x86_64.

Revision history for this message
reacocard (reacocard) wrote :

warning is harmless, but it should be fixed in trunk/2804 anyway.

Changed in exaile:
importance: Undecided → Low
milestone: none → 0.3.1
status: New → Fix Committed
reacocard (reacocard)
Changed in exaile:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.