Package Details: python-panflute 1.12.5-7

Git Clone URL: https://aur.archlinux.org/python-panflute.git (read-only, click to copy)
Package Base: python-panflute
Description: A Pythonic alternative to John MacFarlane’s pandocfilters
Upstream URL: https://github.com/sergiocorreia/panflute
Licenses: BSD
Replaces: pandoc-panflute
Submitter: caleb
Maintainer: caleb (mmtung)
Last Packager: caleb
Votes: 4
Popularity: 0.013372
First Submitted: 2019-03-01 15:16
Last Updated: 2020-10-03 17:11

Pinned Comments

caleb commented on 2020-02-24 05:07

PSA: I've started hosting this as a prebuilt package in my repository for those that want to install it using pacman without messing around with building from the AUR.

Latest Comments

1 2 Next › Last »

caleb commented on 2020-10-03 17:10

@rien333 Apparently the main culprit is tables. I've relaxed the dependency version restrition and added a warning on this package, but I've kept the restriction on python-pantable which is completely out in the cold with Pandoc 2.10.

rien333 commented on 2020-10-03 15:38

I was trying to save anybody else from ending up in the same predicament in production where everything stops working on an update.

Pandoc 2.10 has been in the arch repos for almost 2 months, so I think most have either already found an alternative (e.g. downgrading pandoc) or are unaffected (I use my own panflute filters everyday, and have not noticed any problem). On the other hand, new users might be confused when panflute suddenly doesn't work.

It's your call, but you could also just print a warning for now. I can imagine that users might think that downgrading pandoc is a little too much hassle, especially because it has a lot of dependencies.

caleb commented on 2020-10-03 15:21

@rien333 If it's true that only some filters are problematic I might consider relaxing that restriction (although you can also choose to ignore it at install time if you insist on proceeding). My experience was that all my filter jobs across the board stopped working and the only way I got them back was downgrading Pandoc. I was trying to save anybody else from ending up in the same predicament in production where everything stops working on an update.

rien333 commented on 2020-10-03 11:36

@caleb Ah, I see. Unlike some, I wasn't really hit by any compatibility issues (I guess only specific panflute scripts are affected).

caleb commented on 2020-10-03 09:57

@rien333 Yup, that's kind of the point. You can't upgrade this right now, and this requirement is to block systems that happen to have not ungraded Pandoc yet so that the user knows they have to choose between this and the latest Pandoc. They can't have both.

Until this is resolved upstream with Pandoc 2.10 support the only workaround is to find a Pandoc 2.9.x package on an Arch mirror that keeps old versions around (there are some that have archives) and use that to provide this dependency.

rien333 commented on 2020-10-02 17:59

btw: I get

 -> Could not find all required packages:
    pandoc<2.10.0 (Wanted by: python-panflute)

when trying to upgrade this package to the newest version.

caleb commented on 2020-02-24 05:07

PSA: I've started hosting this as a prebuilt package in my repository for those that want to install it using pacman without messing around with building from the AUR.

caleb commented on 2020-02-20 13:05

@mmtung Yes, my version of the package seems to have been posted after this one. I'm not sure why I didn't find this earlier, possible I was just looking for the wrong name.

That being being said this package is miss-named on at least one, maybe two counts:

  1. It is not packaging the released version, but instead tracking the git HEAD version of the master branch. At the very least it should be named *-git to reflect that.

  2. According to the Arch packaging guidelines as I understand them language specific add-ons like this should be prefixed with the interpreter. Note there is currently a pretty broad mix of pandoc filters using python-<name>, pandoc-<name>, python-pandoc-<name>, pandoc-filter-<name>, etc. I'm not sure I see a precedent. Even the [community] packages are mix and match!

This package should get moved to python-panflute-git (or maybe pandoc-panflute-git if I'm wrong about that second point).

The package I posted does package the release version and is more widely adopted and so should stay (possibly again being renamed into this package's place if I'm wrong about point 2).

mmtung commented on 2020-02-13 13:36

Hi Caleb: indeed, python-panflute (first released 2019-03-01) appears to be a duplicate of pandoc-panflute (first released 2018-08-16).

mmtung commented on 2020-02-13 13:34

Thanks, the format of version.py changed in order to automatically extract the current release/version. Just updated...