On Jun 24, 2008, at 11:32 AM, Kyle VanderBeek wrote:
I just noticed the same thing happened in the 0.9.5 release of Beaker as well:[EMAIL PROTECTED] devel]$ tar tzf Beaker-0.9.5.tar.gz | grep \\._ Beaker-0.9.5/beaker/.___init__.py Beaker-0.9.5/beaker/._cache.py Beaker-0.9.5/beaker/._container.py Beaker-0.9.5/beaker/ext/.___init__.py Beaker-0.9.5/beaker/ext/._database.py Beaker-0.9.5/beaker/ext/._google.py Beaker-0.9.5/beaker/ext/._memcached.py Beaker-0.9.5/beaker/._middleware.py Beaker-0.9.5/beaker/._session.py Beaker-0.9.5/beaker/._util.py Beaker-0.9.5/._CHANGELOG Beaker-0.9.5/._LICENSE Beaker-0.9.5/._setup.py Beaker-0.9.5/tests/._test_cache.py Beaker-0.9.5/tests/._test_database.py Beaker-0.9.5/tests/._test_memcached.py This looks like some sort of mercurial artifact. How are packages being rolled for release? "python setup.py sdist" should roll these cleanly without this sort of problem
It's actually a Leopard issue. There's a known issue with these _files being packaged in tars on OSX, prior to OSX 10.5, there was an environment flag that fixed the problem by forcing the OSX tar to not include them. It appears that since moving to OSX 10.5, this environment variables no longer works, and these damn files are back again. I'll likely need to move my packaging off to a separate linux host to avoid having these files included in the future.
If you're packaging these packages for an OS distro, please feel free to remove them from the package.
Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature
