The README in cextern says to follow the comments in setup.cfg in order to configure the build to use the system CFITSIO. But at some point those comments were removed (possibly by a tool using ConfigParser).

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2347 ed100bfc-0583-0410-97f2-c26b58777a21
This is necessary to support compiling with older system installs of CFITSIO (older than 3.35 anyways--I don't think any older that 3.28 will work at all)

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2348 ed100bfc-0583-0410-97f2-c26b58777a21
Backported astropy/astropy#968 including updates for Python 2.5.  Will backport this fix to PyFITS 3.1.x and 3.0.x branches

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2351 ed100bfc-0583-0410-97f2-c26b58777a21
Merge pull request #996 from iguananaut/issue-996

Column.null not used when writing FITS table?
Conflicts:

	CHANGES.rst
	astropy/io/fits/column.py
	lib/pyfits/hdu/table.py

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2356 ed100bfc-0583-0410-97f2-c26b58777a21
Ignore warning produced by known issue for now; see https://github.com/spacetelescope/PyFITS/issues/44

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2357 ed100bfc-0583-0410-97f2-c26b58777a21
Fix an obscure issue in one of the tests related to Windows, older versions of Python, and float('nan')

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2358 ed100bfc-0583-0410-97f2-c26b58777a21
Travis doesn't support Python 2.5 anymore; but the 3.3 support should be improved--let's give it a try

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2361 ed100bfc-0583-0410-97f2-c26b58777a21
Re-disable 3.3 for now.  I need to take a closer look at this but I think I may be able to resolve it by using Astropy's wheel of Numpy for Python 3.3

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2364 ed100bfc-0583-0410-97f2-c26b58777a21
Remove the checks for whether the released project is 'pyfits'--these are not necessary since the release hooks are no longer installed as setuptools entry points

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2384 ed100bfc-0583-0410-97f2-c26b58777a21
Update the releaser hooks to tweak how tags are created--this is taken right out of Astropy, and I had forgotten this wasn't the default behavior of zest.releaser...

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2385 ed100bfc-0583-0410-97f2-c26b58777a21
Updated 3.0.12 and 3.1.3 release dates

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2386 ed100bfc-0583-0410-97f2-c26b58777a21
Update to the release instructions for undoing a botched release

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2387 ed100bfc-0583-0410-97f2-c26b58777a21
Add .0 to the tag if the version is just 3.Y (at some point I started an inadvertent convetion that the version number in setup.cfg omits the .0, but the tag name includes it)

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2388 ed100bfc-0583-0410-97f2-c26b58777a21
The MANIFEST.in appeared to exclude all the cextern files

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2389 ed100bfc-0583-0410-97f2-c26b58777a21
Further tweaks to the tag name handling in the release

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2390 ed100bfc-0583-0410-97f2-c26b58777a21
Preparing release 3.2

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2391 ed100bfc-0583-0410-97f2-c26b58777a21
Back to development: 3.3

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2392 ed100bfc-0583-0410-97f2-c26b58777a21
Inserted placeholders for 3.1.4 and 3.0.13

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2393 ed100bfc-0583-0410-97f2-c26b58777a21
Set up 3.2-stable branch for dev of 3.2.1

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2396 ed100bfc-0583-0410-97f2-c26b58777a21
This wasn't supposed to be applied in trunk

git-svn-id: http://svn6.assembla.com/svn/pyfits/trunk@2397 ed100bfc-0583-0410-97f2-c26b58777a21