<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 1: No MIDI in unit tests</title><link>https://sourceforge.net/p/pythonmidi/bugs/1/</link><description>Recent changes to 1: No MIDI in unit tests</description><atom:link href="https://sourceforge.net/p/pythonmidi/bugs/1/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 27 Oct 2004 22:37:59 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/pythonmidi/bugs/1/feed.rss" rel="self" type="application/rss+xml"/><item><title>No MIDI in unit tests</title><link>https://sourceforge.net/p/pythonmidi/bugs/1/</link><description>&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;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lennart Regebro</dc:creator><pubDate>Wed, 27 Oct 2004 22:37:59 -0000</pubDate><guid>https://sourceforge.net0231271bf7f6b7358098b62c01b2821bd9855b3d</guid></item></channel></rss>