From: Hermann H. <her...@we...> - 2016-09-23 07:18:36
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi, <div><br/> <u>To install or to not install, that is the question.</u></div> <div><br/> I was recently bitten by some lethal errors using pyusb. These were not in the pyusb code but came from lower layers as a consequence of misusing them.<br/> The following correspondence with the maintenance crew was unsuccessful because the service aspect was not realized.<br/> It turned out that the errors were a consequence of different installation requirements of the different services.</div> <div>I confess guilty of having too long ignored the features of the winusb service.</div> <div>I have learned that DLLs need not be installed with winusb.</div> <div>I have learned too that DLLs must be installed with the libusb0 service and the installed library must be used.<br/> And it was the hard way to learn (using an apparently widely unknown technique called testing).</div> <div>And that installation requirement is what you still have to learn!</div> <div>I have enough logfiles to prove that.</div> <div>This has consequences for the structure of pyusb, the features that can safely be provided, and the necessary restrictions that must be documented.</div> <div>The good news is that for winusb served devices no changes are required.</div> <div>Well, to proceed with my work on the installation guide, I need a formal agreement of the service thesis because that will dominate the bugfix procedure.</div> <div>Who ever objects to this thesis should talk now or be silent for ever.</div> <div>I agree [ ] I disagree [ ]</div> <div> </div> </div></div></body></html> |