Thread: [Pyobjc-dev] breakage in CVS?
Brought to you by:
ronaldoussoren
Menu
▾
▴
pyobjc-dev
|
From: Michael H. <mw...@py...> - 2003-08-28 14:55:37
|
I managed to trick SF into letting me update via anon CVS and this
happened:
Python 2.3+ (#1, Aug 28 2003, 14:14:54)
[GCC 3.1 20020420 (prerelease)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
->> import AppKit
Traceback (most recent call last):
File "<input>", line 2, in ?
File "/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/PyObjC/AppKit/__init__.py", line 32, in ?
NSMakePoint = Foundation.NSMakePoint
AttributeError: 'module' object has no attribute 'NSMakePoint'
Is it just me?
Cheers,
mwh
--
LINTILLA: You could take some evening classes.
ARTHUR: What, here?
LINTILLA: Yes, I've got a bottle of them. Little pink ones.
-- The Hitch-Hikers Guide to the Galaxy, Episode 12
|
|
From: Just v. R. <ju...@le...> - 2003-08-28 15:16:16
|
Michael Hudson wrote: > I managed to trick SF into letting me update via anon CVS and this > happened: > > Python 2.3+ (#1, Aug 28 2003, 14:14:54) > [GCC 3.1 20020420 (prerelease)] on darwin > Type "help", "copyright", "credits" or "license" for more information. > ->> import AppKit > Traceback (most recent call last): > File "<input>", line 2, in ? > File > "/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site- packages/PyObjC/AppKit/ > __init__.py", line 32, in ? > NSMakePoint = Foundation.NSMakePoint > AttributeError: 'module' object has no attribute 'NSMakePoint' It's AppKit.NSMakePoint()... But: why use it to begin with? NSPoints are represented as 2-tuples. Just |
|
From: Michael H. <mw...@py...> - 2003-08-28 15:20:27
|
Just van Rossum <ju...@le...> writes:
> Michael Hudson wrote:
>
>> I managed to trick SF into letting me update via anon CVS and this
>> happened:
>>
>> Python 2.3+ (#1, Aug 28 2003, 14:14:54)
>> [GCC 3.1 20020420 (prerelease)] on darwin
>> Type "help", "copyright", "credits" or "license" for more information.
>> ->> import AppKit
>> Traceback (most recent call last):
>> File "<input>", line 2, in ?
>> File
>>
> "/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-
> packages/PyObjC/AppKit/
>> __init__.py", line 32, in ?
>> NSMakePoint = Foundation.NSMakePoint
>> AttributeError: 'module' object has no attribute 'NSMakePoint'
>
> It's AppKit.NSMakePoint()... But: why use it to begin with? NSPoints are
> represented as 2-tuples.
I can see that... I don't even want to use NSMakePoint, but being able
to import AppKit would be a bonus!
Cheers,
mwh
--
#ifndef P_tmpdir
printf( "Go buy a better computer" );
exit( ETHESKYISFALLINGANDIWANTMYMAMA );
-- Dimitri Maziuk on writing secure code, asr
|
|
From: Just v. R. <ju...@le...> - 2003-08-28 16:11:37
|
Michael Hudson wrote: > I can see that... I don't even want to use NSMakePoint, but being able > to import AppKit would be a bonus! *blush* <hides-under-desk> Just |
|
From: Zeph C. <ze...@ho...> - 2003-08-28 16:29:26
|
> Just van Rossum <ju...@le...> writes: > >> Michael Hudson wrote: >> >> It's AppKit.NSMakePoint()... But: why use it to begin with? NSPoints >> are >> represented as 2-tuples. > > I can see that... I don't even want to use NSMakePoint, but being able > to import AppKit would be a bonus! As a noob to PyObjC, I had to find out the hard way what was and was not included, and I guess the rule of thumb is that if it can be expressed as a tuple, there's no reason to have a function just to spit out the equivelent struct. BTW, the global function NSMakeRect wasn't included - sure it was trivial to re-implement, but still... I guess that's why it's beta :-) - Zeph |
|
From: Michael H. <mw...@py...> - 2003-08-28 16:45:28
|
Zeph Campbell <ze...@ho...> writes:
>> Just van Rossum <ju...@le...> writes:
>>
>>> Michael Hudson wrote:
>>>
>>> It's AppKit.NSMakePoint()... But: why use it to begin with?
>>> NSPoints are
>>> represented as 2-tuples.
>>
>> I can see that... I don't even want to use NSMakePoint, but being able
>> to import AppKit would be a bonus!
>
> As a noob to PyObjC, I had to find out the hard way what was and was
> not included, and I guess the rule of thumb is that if it can be
> expressed as a tuple, there's no reason to have a function just to
> spit out the equivelent struct.
I seem to be causing some confusion here.
I do not care a jot whether NSMakePoint is defined in Foundation,
AppKit or not at all.
However, in the version of PyObjC I checked out today, when you import
AppKit, *AppKit/__init__.py* tries to import NSMakePoint and friends
from Foundation -- and fails.
I'm not asking for someone to help, I'm asking for someone to fix it!
Maybe Ronald missed a file in a check in? That's what it looks like
to me.
Cheers,
mwh
--
SPIDER: 'Scuse me. [scuttles off]
ZAPHOD: One huge spider.
FORD: Polite though.
-- The Hitch-Hikers Guide to the Galaxy, Episode 11
|
|
From: Ronald O. <ous...@ci...> - 2003-08-29 10:26:40
|
On Thursday, 28 August 2003, at 18:45, Michael Hudson wrote: > I seem to be causing some confusion here. > > I do not care a jot whether NSMakePoint is defined in Foundation, > AppKit or not at all. That was quite obvious to me, maybe your mail got garbled on its way to the others :-) > > However, in the version of PyObjC I checked out today, when you import > AppKit, *AppKit/__init__.py* tries to import NSMakePoint and friends > from Foundation -- and fails. > > I'm not asking for someone to help, I'm asking for someone to fix it! > Maybe Ronald missed a file in a check in? That's what it looks like > to me. That's not it, the wrappers for those functions are generated when you build PyObjC (that's what 's happening after setup.py prints 'Performing task: Generating wrappers & stubs'). Ronald |
|
From: Just v. R. <ju...@le...> - 2003-08-29 11:00:43
|
Ronald Oussoren wrote: > > I do not care a jot whether NSMakePoint is defined in Foundation, > > AppKit or not at all. > > That was quite obvious to me, maybe your mail got garbled on its way > to the others :-) Yes, it had indeed absolutely NOTHING to do with the fact that I usually don't actually read the posts I reply to ;-) Just |
|
From: Ronald O. <ous...@ci...> - 2003-08-29 10:07:37
|
On Thursday, 28 August 2003, at 18:24, Zeph Campbell wrote: > >> Just van Rossum <ju...@le...> writes: >> >>> Michael Hudson wrote: >>> >>> It's AppKit.NSMakePoint()... But: why use it to begin with? NSPoints >>> are >>> represented as 2-tuples. >> >> I can see that... I don't even want to use NSMakePoint, but being able >> to import AppKit would be a bonus! > > As a noob to PyObjC, I had to find out the hard way what was and was > not included, and I guess the rule of thumb is that if it can be > expressed as a tuple, there's no reason to have a function just to > spit out the equivelent struct. > > BTW, the global function NSMakeRect wasn't included - sure it was > trivial to re-implement, but still... NSMakeRect is included, it is in the current CVS tree (if you manage to get to that :-), and probably also in 1.0rc1. Ronald |
|
From: Ronald O. <ous...@ci...> - 2003-08-29 10:05:37
|
Could you try installing after removing the existing PyObjC installation in site-packages. For some reason distutils sometimes doesn't install the new version of files. Ronald |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X