[wingide-users] epydoc!

Gene Campbell campbell.gene at gmail.com
Tue Oct 4 09:35:05 MDT 2011


Hi,

How would epydoc be used to implement better source analysis, and thus
auto-completion?

Is the idea that we would document methods, and the epydoc comments
will tell Wing about the argument types?

def plant(seed, *tools, **options):
    """
    @param seed: The seed that should be planted.
    @type seed: Seed
    """

Thanks
Gene

On Tue, Oct 4, 2011 at 7:36 AM, Stephan Deibel <sdeibel at wingware.com> wrote:
> On 10/4/11 10:32 AM, Linos wrote:
>>
>> Yeah i spoke about Python3 native annotations in the first post but many
>> people
>> will be attached to Python2 for a long time, other than this epydoc lets
>> you
>> annotate variables in code not only function parameters so it seems like a
>> better solution.
>>
>> Maybe Wing IDE could add support for epydoc right now and in the future
>> add
>> support for Python3 native annotations when Python3 have been adopted by
>> more
>> developers?.
>
> Sorry, I missed that you mentioned annotations earlier.  In any case, I
> agree epydoc support has more value.
>
> Thanks,
>
> - Stephan
>
> _________________________________________________
> Wing IDE users list
> http://wingware.com/lists/wingide
>


More information about the wingide-users mailing list