On May 27, 2005, at 01:39, Ronald Oussoren wrote:
> On 26-mei-2005, at 16:54, Jonathan Wight wrote:
>
>> After adding Gideon's suggestion for CRLF ending file. My importer is
>> failing on only 8 files out of 3084 files.
>>
>> All the failures are with Python files that try to generate the
>> __ve
On 26-mei-2005, at 16:54, Jonathan Wight wrote:
After adding Gideon's suggestion for CRLF ending file. My importer is
failing on only 8 files out of 3084 files.
All the failures are with Python files that try to generate the
__version__ attribute with code instead, e.g.:
__version__ = string.
Yep, right at the line break - sorry I didn't notice that (so I guess
you could say the client and user in this case :~)
Like others, I've been using tinyURLs on another list that has
excessively long message URL references, but as you and others have
pointed out they have longevity (?) issu
No, the URL was what I meant, but Mail.app has a tendency to inject
extra spaces (show up as %20) into long URLs. Another client may be
less stupid about it.
-bob
On May 26, 2005, at 4:57 PM, Lee Cullens wrote:
> Bob's URL didn't work for me, but I think he meant:
> http://bob.pythonmac.org
Also, for my own projects I place *.pth files in ~/Library/Python/2.4/
site-packages/ (after I woke up with a little help ;')
Where they would be placed otherwise, I'll leave to the experts to
answer.
On May 26, 2005, at 7:57 PM, Lee Cullens wrote:
> Bob's URL didn't work for me, but I thi
Bob's URL didn't work for me, but I think he meant:
http://bob.pythonmac.org/archives/2005/02/06/
On May 26, 2005, at 4:16 PM, Kenneth McDonald wrote:
> According to my (slightly dated) Python In a Nutshell book, I can
> specify python search paths by putting them in a .python.pth file in
> t
On May 26, 2005, at 2:17 PM, has wrote:
> Bob wrote:
>
>
>>> ImportError: Failure linking new module: /usr/lib/libmx.A.dylib:
>>> dyld: /Library/Frameworks/Python.framework/Versions/2.3/Resources/
>>> Python.app/Contents/MacOS/Python can't open library: /usr/lib/
>>> libmx.A.dylib (No such f
On May 26, 2005, at 2:11 PM, has wrote:
> Glenn Andreas wrote:
>
>
>>> ImportError: Failure linking new module: /usr/lib/libmx.A.dylib:
>>> dyld: /Library/Frameworks/Python.framework/Versions/2.3/Resources/
>>> Python.app/Contents/MacOS/Python can't open library: /usr/lib/
>>> libmx.A.dylib
Bob wrote:
>>ImportError: Failure linking new module: /usr/lib/libmx.A.dylib: dyld:
>>/Library/Frameworks/Python.framework/Versions/2.3/Resources/Python.app/Contents/MacOS/Python
>> can't open library: /usr/lib/libmx.A.dylib (No such file or directory,
>>errno = 2)
>>
>>Any ideas? (Source and b
Glenn Andreas wrote:
>>ImportError: Failure linking new module: /usr/lib/libmx.A.dylib: dyld:
>>/Library/Frameworks/Python.framework/Versions/2.3/Resources/Python.app/Contents/MacOS/Python
>> can't open library: /usr/lib/libmx.A.dylib (No such file or directory,
>>errno = 2)
>
>[...] Switching
On May 26, 2005, at 1:16 PM, Kenneth McDonald wrote:
> According to my (slightly dated) Python In a Nutshell book, I can
> specify python search paths by putting them in a .python.pth file in
> the PYTHONHOME directory. However, my environment doesn't have a
> PYTHONHOM variable. Do I need to def
On May 26, 2005, at 11:56 AM, has wrote:
> Nicholas Riley wrote:
>
>
>>> Obviously the extension needs to be built on Tiger to provide sdef
>>> support, but what should I do to ensure that, say, applications
>>> containing that binary extension will still work OK when run on
>>> earlier OSes?
>>>
According to my (slightly dated) Python In a Nutshell book, I can
specify python search paths by putting them in a .python.pth file in
the PYTHONHOME directory. However, my environment doesn't have a
PYTHONHOM variable. Do I need to define it explicitly, or is there
another location I can put the p
On May 26, 2005, at 1:56 PM, has wrote:
> Nicholas Riley wrote:
>
>
>>> Obviously the extension needs to be built on Tiger to provide sdef
>>> support, but what should I do to ensure that, say, applications
>>> containing that binary extension will still work OK when run on
>>> earlier OSes?
>>>
Nicholas Riley wrote:
> > Obviously the extension needs to be built on Tiger to provide sdef
>> support, but what should I do to ensure that, say, applications
>> containing that binary extension will still work OK when run on
> > earlier OSes?
>
>You can use weak linking if you don't need to supp
> Not many people do the CVS thing these days, and that number is going
> to get smaller and smaller since people are replacing CVS with
> Subversion and others.
svn propset svn:keywords 'id' filename (which is a default, I think,
anyway - I don't think switching to subversion will make it *a
On Thu, May 26, 2005 at 10:52:05AM -0700, Bob Ippolito wrote:
> There are still other places where you'll have version expressions.
>
> PyOpenGL's is the most braindead, it reads the version from *A FILE*.
>
> Many extensions bring in the version from some extension (i.e. PyObjC).
>
> I'd go ahe
On May 26, 2005, at 8:05 AM, Nicholas Riley wrote:
> On Thu, May 26, 2005 at 10:54:59AM -0400, Jonathan Wight wrote:
>
>> After adding Gideon's suggestion for CRLF ending file. My importer is
>> failing on only 8 files out of 3084 files.
>>
>> All the failures are with Python files that try to ge
On May 26, 2005, at 8:03 AM, Kent Quirk wrote:
> Thanks for the hint. This helped us a lot, but we don't quite have the
> complete answer.
>
> We were never linking to Python 2.3, but otool shows us that we have
> references to /Library/Frameworks/Python.framework in our extensions
> (and in the
On Thu, May 26, 2005 at 10:54:59AM -0400, Jonathan Wight wrote:
> After adding Gideon's suggestion for CRLF ending file. My importer is
> failing on only 8 files out of 3084 files.
>
> All the failures are with Python files that try to generate the
> __version__ attribute with code instead, e.
Thanks for the hint. This helped us a lot, but we don't quite have the
complete answer.
We were never linking to Python 2.3, but otool shows us that we have
references to /Library/Frameworks/Python.framework in our extensions
(and in the embedded Python executable) rather than to
@executable_path/
After adding Gideon's suggestion for CRLF ending file. My importer is
failing on only 8 files out of 3084 files.
All the failures are with Python files that try to generate the
__version__ attribute with code instead, e.g.:
__version__ = string.split('$Revision: 1.8 $')[1]
__version__ = '$Rev
Jon, I have a number of python files with dos line ending (\r\n), which
can't be parsed with the parser module. If you change the open call
in importer.py in :
theSource = file(inPath,'U').read()
the line ending is translated into newline and the script is able to
read them :)
Cheers,
Yeah I screwed up with the code that scans functions.
There's a new version online now that fixes that.
Jon.
On May 26, 2005, at 09:37, Nicholas Riley wrote:
> On Thu, May 26, 2005 at 12:13:02AM -0400, Jonathan Wight wrote:
>
>
>
>> Just to let everyone know that my Python Metadata Impor
On Thu, May 26, 2005 at 02:28:59PM +0100, has wrote:
> Obviously the extension needs to be built on Tiger to provide sdef
> support, but what should I do to ensure that, say, applications
> containing that binary extension will still work OK when run on
> earlier OSes? For example, should I include
On Thu, May 26, 2005 at 12:13:02AM -0400, Jonathan Wight wrote:
> Just to let everyone know that my Python Metadata Importer plug-in
> was released the other day.
>
> http://toxicsoftware.com/blog/index.php/weblog/
> python_metadata_importer_101_released/
Since I installed this I got a co
Hi all, please forgive my crappy knowledge of C, etc. in advance... ;)
In updating my osaterminology package to support Tiger, I've added a new
function, OSAGetSdef(), to its OSATerminology.so extension [1]. To allow the
extension to build on older OSes, I've inserted an #ifdef as shown:
static
On May 26, 2005, at 00:38, Bob Ippolito wrote:
> On May 25, 2005, at 9:13 PM, Jonathan Wight wrote:
>
>
>> Just to let everyone know that my Python Metadata Importer plug-in
>> was released the other day.
>>
>> http://toxicsoftware.com/blog/index.php/weblog/
>> python_metadata_importer_101_r
28 matches
Mail list logo
