Package Details: python-panflute 2.1.3-2

Git Clone URL: (read-only, click to copy)
Package Base: python-panflute
Description: A Pythonic alternative to John MacFarlane’s pandocfilters
Upstream URL:
Licenses: BSD
Conflicts: pandoc-panflute
Provides: pandoc-panflute
Replaces: pandoc-panflute
Submitter: alerque
Maintainer: alerque (mmtung)
Last Packager: alerque
Votes: 4
Popularity: 0.000000
First Submitted: 2019-03-01 15:16 (UTC)
Last Updated: 2022-04-12 12:33 (UTC)

Pinned Comments

alerque commented on 2020-02-24 05:07 (UTC)

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

mmtung commented on 2022-05-23 07:52 (UTC)

Last version 2.1.3 upon compilation and testing gives following error:

/usr/lib/python3.10/site-packages/pytest_asyncio/ DeprecationWarning: The 'asyncio_mode' default value will change to 'strict' in future, please explicitly use 'asyncio_mode=strict' or 'asyncio_mode=auto' in pytest configuration file. config.issue_config_time_warning(LEGACY_MODE, stacklevel=2)

panflute/ /home/user/.cache/yay/python-panflute/src/panflute-2.1.3/panflute/ DeprecationWarning: invalid escape sequence '*' """

-- Docs: =========================== short test summary info ============================ FAILED tests/ - AssertionError: assert ['/... =========== 1 failed, 29 passed, 1 deselected, 2 warnings in 13.71s ============ ==> ERROR: A failure occurred in check(). Aborting... -> error making: python-panflute

This indicates that panflute-2.1.3/panflute/ probably needs to be patched, erasing an illegal character.

alerque commented on 2021-01-07 13:48 (UTC)

@tzok I would have loved to, but the AUR guidelines explicitly discourage bumping packages for rebuilds like that (even though it's by far the easiest and cleanest way to make sure it gets done and rolls out to everybody). I realize a lot of folks do it anyway, but I'd rather play by the rules (and lobby to get them changed). For now please rebuild yourself (if using yay for example, try yay --rebuild -S python-panflute).

tzok commented on 2020-12-29 14:27 (UTC)

Please bump the pkgrel, because with Python 3.9 in extra, this package needs a rebuild.

alerque commented on 2020-10-03 17:10 (UTC)

@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 (UTC)

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.

alerque commented on 2020-10-03 15:21 (UTC)

@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 (UTC)

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

alerque commented on 2020-10-03 09:57 (UTC)

@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 (UTC)

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.

alerque commented on 2020-02-24 05:07 (UTC)

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.

alerque commented on 2020-02-20 13:05 (UTC) (edited on 2020-02-20 13:24 (UTC) by alerque)

@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 (UTC)

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 (UTC)

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

rien333 commented on 2020-02-12 09:36 (UTC) (edited on 2020-02-12 09:40 (UTC) by rien333)

Thanks for the update, but you forgot to define the variable $_name (to e.g. $_pipname). build() now fails on line 24 because $_name is undefined.

rien333 commented on 2020-02-12 09:31 (UTC)

Duplicate, and also fails in pkgver():

==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphensor whitespace.
==> ERROR: pkgver() generated an invalid version: """
Panflute version

alerque commented on 2020-02-12 08:11 (UTC)

Possible duplicate with python-panflute?

alerque commented on 2019-12-02 11:18 (UTC)

@golinski Done.

alerque commented on 2019-12-02 10:41 (UTC)

@golinski Yes I will look into that packaging method as I would prefer it myself. If anybody wants to contribute that change I'd be happy to see code too ;-)

golinski commented on 2019-03-07 13:36 (UTC) (edited on 2019-03-07 13:38 (UTC) by golinski)

I was a user of the pandoc-panflute package, by accident I have stumbled on this one. I have just one remark: the Arch guidelines suggest to use distutils/setuptools instead of pip for installation. I have many python-* packages installed (including several from AUR), none of them use pip. I can see that some python packages in community use pip, but still a marginal amount. Would it be possible to convert this package to use the suggested way?

By the way, python-future is not used in any way (this is only for python2), so this dependency can be dropped.