On Sun, Jan 22, 2006 at 12:13:07AM -0500, Nicholas Matsakis wrote:
> So, is it possible there is _no_ standard type code for python source? If
> not, any thoughts on registering one?
Indeed, they're text files. I wouldn't want them to behave any other
way.
The basic problem is that a four-char
Henning Hraban Ramm wrote:
> In this case, 'file' may be right. But I wouldn't trust it if you've to
> handle a lot of file types. ... Mostly I could trust in extensions
> and/or Mac type/creator codes.
I certainly agree with this; applications that create files are in the
best position to kn
Am 2006-01-21 um 08:01 schrieb Nicholas Matsakis:
>
> * The saddest part of this story is that /usr/bin/file has been on
> Mac OS
> X since day one and understands perfectly well what a "a python script
> text executable" is. Yet, when the Finder encounters a file
> without an
> extension or H
On Sat, 21 Jan 2006, Jonathan Wight wrote:
> I'm the author of Python Metadata Importer. There should already be a HFS
> type code for Python source. I can add the type code to Python Metadata
> Importer to wide its search. Getting the importer to work with Spotmeta is
> AFAICT a non-starter -
On Jan 21, 2006, at 2:01 AM, Nicholas Matsakis wrote:
> http://www.apple.com/downloads/macosx/spotlight/
> pythonmetadataimporter.html
>
> I really dig the Spotlight Metadata Importer for python, but it
> only works
> for files ending in ".py" which excludes various shell scripts I have
> writt
http://www.apple.com/downloads/macosx/spotlight/pythonmetadataimporter.html
I really dig the Spotlight Metadata Importer for python, but it only works
for files ending in ".py" which excludes various shell scripts I have
written that have no filename extension. Anyone have a super elegant
sol
