pybluez inquiry bug on win7,it just use win7 stack's info,but doesn't do a inquiry

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. win7 inquiry a new device 
2. unplug the device found in the  last step
3. make a inquiry use bluetooth.discover_devices(lookup_names = True),you will 
find the device  unplugged in the last step.

What is the expected output? What do you see instead?
The unplugged device must not appear in the inquiry result list.
but it still appears.

What version of the product are you using? On what operating system?
pybluez0.18 win7 home standard

Please provide any additional information below.

Original issue reported on code.google.com by wushuan...@gmail.com on 12 Sep 2010 at 2:40

Merged into: #24

GoogleCodeExporter commented 8 years ago

the detail version:PyBluez-0.18.win32-py2.5.exe on win7

Original comment by wushuan...@gmail.com on 12 Sep 2010 at 2:44

GoogleCodeExporter commented 8 years ago

Original comment by karu...@wp.pl on 16 Jan 2014 at 10:44

Changed state: Duplicate

pvdao / pybluez

pybluez inquiry bug on win7,it just use win7 stack's info,but doesn't do a inquiry #35