Skip to content

Give Table a _repr_latex_ method? #3972

Closed

Description

@Cadair

Having a _repr_latex_ method on the Table object would be really useful for me when using PythonTeX.

Are there any reasons why this has not / should not be done?

Activity

  1. embray commented on Jul 17, 2015

    @embray
    Member

    I guess the only question here (and the problem I have with all _repr_..._ methods, is what the default formatting options should be. If we add this we might also want a way to control, via an instance attribute, what the default LaTeX formatting options are for a table (if it doesn't already exist).

  2. taldcroft commented on Jul 17, 2015

    @taldcroft
    Member

    It's not a totally robust or future-proof idea, but the latexdict args (http://astropy.readthedocs.org/en/latest/api/astropy.io.ascii.Latex.html#astropy.io.ascii.Latex) that control how a table is formatted into latex could be just stored in the table via meta['latexdict'], and _repr_latex_ would know to look for that to supply defaults.

  3. embray commented on Jul 17, 2015

    @embray
    Member

    Seems good enough to me for starters.

  4. taldcroft commented on Jul 17, 2015

    @taldcroft
    Member

    OK @Cadair you are clear to code! 😄

  5. taldcroft commented on Jul 17, 2015

    @taldcroft
    Member

    (And find a way to feel like you are writing your thesis without actually writing it.)

  6. Suyog7130 commented on Apr 2, 2021

    @Suyog7130
    Contributor

    Hey, @aaryapatil and @hamogu, has this issue been worked on before?
    There are many open issues marked Package-novice etc. but have had a Pull Request or two.

  7. hamogu commented on Apr 2, 2021

    @hamogu
    Member

    @Suyog7130 As long as an issue is open, you can work on it. Often, someone tried their hand (e.g. for GSOC applications!) but it did not work out. You can go to the linked pull requests and see what worked, what did not and why it was not finished. However, in this particular case, I don't think anyone has worked on exactly this issue.

  8. added a commit that references this issue on Apr 18, 2021
  9. added a commit that references this issue on May 10, 2021
  10. added a commit that references this issue on May 12, 2021
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