`webassets` dependency appears to be abandonware

[phlax]

PRs and issues are ignored in the webassets repo - upstream issue added here miracle2k/webassets#554

questions below: N/A

• I have read the Filing Issues and subsequent “How to Get Help” sections of the documentation.
• I can reproduce this problem with stock/default settings file, theme, and sample content (as described in above “How to Get Help” sections of the documentation).
• I have searched the issues (including closed ones) and believe that this is not a duplicate.

• OS version and name:
• Python version:
• Pelican version:
• Link to theme:
• Links to plugins:
• Link to your site:
• Link to your source:
• Link to a Gist with the contents of your settings file:

Issue

[justinmayer]

Hi @phlax. A few things, in no particular order:

• I can emphasize with how frustrating it can be when projects appear to be abandoned.
• The webassets repository you referenced is not a Pelican “dependency”, but rather a 3rd-party component that is wholly unrelated to this Pelican core repository.
• This Pelican core repository previously contained some plugins, one of which (assets) was eventually moved to the Pelican Plugins repository (now deprecated), and then subsequently moved to its own repository under the Pelican Plugins organization under the name webassets.
• The aforementioned webassets plugin depends on the identically-named component repository you referenced.
• If there is any further discussion warranted, let's do that in the relevant issue I just created for that purpose: Migrate to existing webassets plugin under Pelican Plugins org miracle2k/webassets#555

[phlax]

thanks for the follow up @justinmayer

i wasnt aware that there was an ~official webassets other than the one i am using - not sure how/why i have that setup, but will check and update

mostly i was checking our deps are supported

thanks again

[justinmayer]

I wouldn’t go so far as to call that plugin “official”, but at least it is under an organization with multiple maintainers and is more actively monitored and maintained.

[phlax]

hmm - checking - and it seems that pelican-webassets is pulling in the linked webassets as a dep

https://github.com/pelican-plugins/webassets/blob/17faf0dcf94a165555109b58bd09fabb1decaa61/pyproject.toml#L40

which points back to the webassets repo mentioned - https://pypi.org/project/webassets/

am i misunderstanding something?

[justinmayer]

Please see related discussion at: miracle2k/webassets#553

[justinmayer]

The unmaintained webassets library has been vendored into the identically-named Pelican plugin, which you can get from: https://github.com/pelican-plugins/webassets/releases