Skip to content

Add dev docs explaining PLY integration #4318

Closed

Description

@eteq

As mentioned in #4300, there are some pieces of units and coordinates that use PLY (and lex/yacc) to parse various strings. However, there is no developer documentation describing how this works and how it should be maintained. It would be valuable if @mdboom (or perhaps @embray ?) could write a short developer docs page describing how these fit together, so that other contributors can understand how they might be able to help maintain or expand these pieces.

Activity

  1. changed the title [-]Add dev docs explaining [/-] [+]Add dev docs explaining PLY integration[/+] on Nov 17, 2015
  2. embray commented on Nov 17, 2015

    @embray
    Member

    I think the documentation for PLY itself would be a start...
    These modules are just using PLY in a way that is not unusual.

  3. eteq commented on Nov 18, 2015

    @eteq
    MemberAuthor

    @embray - the point is why they are used and specifically where, and how/when to invoke it. Even if it's standard, the point is that most people who may need to fiddle with these things don't have the time/inclination to master PLY so there should be some information about why they should care and how to get started learning what they need to o know.

  4. reopened this on Nov 18, 2015
  5. embray commented on Nov 18, 2015

    @embray
    Member

    In the relatively remote chance any has to, they should start here:

    http://www.dabeaz.com/ply/ply.html

    There's not much point in reiterating what the PLY docs already say. It's pretty succinct already, and anybody who's going to mess with a parser should understand how that works. Those docs tell you everything you need to know. I don't think there's anything too special to know about its use in astropy beyond what you already added in those comments.

  6. AMAN3003 commented on Feb 7, 2016

    @AMAN3003

    @eteq could I work on this

  7. AMAN3003 commented on Feb 7, 2016

    @AMAN3003

    @eteq @embray please guide me what should i do to write the dev ply docs

  8. astrofrog commented on Feb 7, 2016

    @astrofrog
    Member

    @AMAN3003 - this issue is labelled as package-expert, which means that it requires a lot of knowledge about how we've set up the package, etc. So this issue is more intended as an issue for a core developer. I would suggest sticking to package-novice issues for now while you familiarize yourself with the project.

  9. AMAN3003 commented on Feb 7, 2016

    @AMAN3003

    @astrofrog thank you for you advice.But could you give me a favour ..please include me in development team by assigning little task .I would do my best .I want to develop with your teams.Developing little function of the scripts will also be a golden chance for me.Give me a chance Sir

  10. eteq commented on Feb 9, 2018

    @eteq
    MemberAuthor

    Closed by #7174

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions