On 06/14/2011 04:48 AM, Eric M. Ludlam wrote:
> On 06/09/2011 09:47 AM, Pete Beardmore wrote:
>> Eric M. Ludlam<eric<at> siege-engine.com> writes:
>>
>>>
>>> On 04/23/2011 05:26 PM, qMax wrote:
>>>> Hi.
>>>> I've installed cedet-1.0 and ecb-2.40 on GNU emacs-23
>>>>
>>>> When editing python sources, ECB sucesfully sees all code structure
>>>> like imports, base classes, and all their methods.
>>>> However, neither of completion methods can suggest anything but local
>>>> scope symbols.
>>>>
>>>> Is it possible to tweak semantic or senator to complete symbols from
>>>> imported modules, classes, base classes,
>>>> and recognize 'self' as a ref to current class instance?
>>>
>>> The necessary changes to get 'self' and use of imports was added to
>>> CEDET/bzr repository after the CEDET 1.0 release from last year. Please
>>> try out a bzr checkout to see if it does what you need.
>>>
>>> Eric
>>>
>>
>> Hi,
>>
>> Could i add that the support that was added didn't allow for the possibility of
>> a comma delimited list of modules following the import statement. No biggy on
>> what i look at, but i imagine a lot of includes could be missed for larger
>> projects that just happen to be using that syntax.
>>
>> Cheers,
>> Pete.
>>
>> PS. 'import sys' always persists as an unknown include for some reason too.
>
> Are there any python users on the mailing list interested in taking on
> the project of supporting 'sys' and comma delimited module lists?
>
> Thanks
> Eric
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Cedet-devel mailing list
> Cedet-devel@...
> https://lists.sourceforge.net/lists/listinfo/cedet-devel
I would love to see a little more cedet love for python as well... I am
willing to take on any simple tasks but I don't think I would be able to
easily do this one (I've never worked with LALR (is that even what needs
to be modified to support this?))...
Slightly unrelated, are there any reasons for using emacs' "python"
instead of, say, "pymacs"[1] for lisp<->python communication? I'm using
python3 (which is apparently unsupported by emacs' "python"). However,
dropping in pymacs (see attached patch) does work for me with python3.
-Mitch
[1] http://pymacs.progiciels-bpi.ca/pymacs.html
|