<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 1: No MIDI in unit tests</title><link href="https://sourceforge.net/p/pythonmidi/bugs/1/" rel="alternate"/><link href="https://sourceforge.net/p/pythonmidi/bugs/1/feed.atom" rel="self"/><id>https://sourceforge.net/p/pythonmidi/bugs/1/</id><updated>2004-10-27T22:37:59Z</updated><subtitle>Recent changes to 1: No MIDI in unit tests</subtitle><entry><title>No MIDI in unit tests</title><link href="https://sourceforge.net/p/pythonmidi/bugs/1/" rel="alternate"/><published>2004-10-27T22:37:59Z</published><updated>2004-10-27T22:37:59Z</updated><author><name>Lennart Regebro</name><uri>https://sourceforge.net/u/regebro/</uri></author><id>https://sourceforge.net0231271bf7f6b7358098b62c01b2821bd9855b3d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;There are no MIDI in unit tests. Adding tests that open&lt;br /&gt;
a port  would be easy, but what about other tests? Test&lt;br /&gt;
get complicated because of the probable need to put the&lt;br /&gt;
loopback in another thread. Also, how can the MIDI in&lt;br /&gt;
functionality be tested without loopback devices?&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>