<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to patches</title><link href="https://sourceforge.net/p/python-fam/patches/" rel="alternate"/><link href="https://sourceforge.net/p/python-fam/patches/feed.atom" rel="self"/><id>https://sourceforge.net/p/python-fam/patches/</id><updated>2005-02-27T18:55:56Z</updated><subtitle>Recent changes to patches</subtitle><entry><title>Compilation cleanups</title><link href="https://sourceforge.net/p/python-fam/patches/4/" rel="alternate"/><published>2005-02-27T18:55:56Z</published><updated>2005-02-27T18:55:56Z</updated><author><name>Martin v. Löwis</name><uri>https://sourceforge.net/u/loewis/</uri></author><id>https://sourceforge.net15943996230b1757f837c1954c42755377d2cb41</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This patch cleans up a few warnings that gcc reports.&lt;br /&gt;
In _fam_pending, the complaint is about the assignment&lt;/p&gt;
&lt;p&gt;if (pyval = PyInt_FromLong(1)) {&lt;/p&gt;
&lt;p&gt;While this is C-wise correct, it is not Python-wise: if&lt;br /&gt;
PyInt_FromLong would indeed return NULL, you would have&lt;br /&gt;
to return NULL to the caller. Instead of doing that, I&lt;br /&gt;
rewrote the entire function to return Py_True/Py_False&lt;br /&gt;
(which will return booleans in 2.3 and later).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Yet another setup.py</title><link href="https://sourceforge.net/p/python-fam/patches/3/" rel="alternate"/><published>2005-02-27T18:53:33Z</published><updated>2005-02-27T18:53:33Z</updated><author><name>Martin v. Löwis</name><uri>https://sourceforge.net/u/loewis/</uri></author><id>https://sourceforge.net16ecd5ef893130f61bb888e4f8759a75126d9c7d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This is my take of a setup.py for python-fam. Unlike&lt;br /&gt;
the other patch, this does not create a fam package.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>distutils setup</title><link href="https://sourceforge.net/p/python-fam/patches/2/" rel="alternate"/><published>2003-02-24T10:53:21Z</published><updated>2003-02-24T10:53:21Z</updated><author><name>Terrel Shumway</name><uri>https://sourceforge.net/u/terrelshumway/</uri></author><id>https://sourceforge.net0d6c6a553b37cfc8ee50836df48a8e428de88d16</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I created a distutils setup for python-fam&lt;/p&gt;
&lt;p&gt;This makes it trivial to create an rpm.&lt;/p&gt;
&lt;p&gt;Since this also creates a new package fam to contain&lt;br /&gt;
_fam.so it should probably bump the version number to 1.1&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>crash due to missing hostname</title><link href="https://sourceforge.net/p/python-fam/patches/1/" rel="alternate"/><published>2002-10-23T02:40:50Z</published><updated>2002-10-23T02:40:50Z</updated><author><name>Jason Hildebrand</name><uri>https://sourceforge.net/u/jdhildeb/</uri></author><id>https://sourceforge.net3cf28ab2e46dfcb9f6eff17b038dbef18edfec57</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I compiled python-fam on my system (debian 3.0).  The&lt;br /&gt;
included test.py ran fine, but I encountered a crash&lt;br /&gt;
after making use of it from a different application.&lt;/p&gt;
&lt;p&gt;I traced the problem to the hostname field being NULL&lt;br /&gt;
in _fam_next_event.  The attached patch checks for this&lt;br /&gt;
condition, and sets the python string to the empty&lt;br /&gt;
string in this case.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>