Build Issue - pygments~=2.11.2 distribution was not found about hammerspoon HOT 11 CLOSED

Oh, and I'm still on Monterey v12.6.3 - could that be related? Did you update code to only work with Xcode on Ventura?

from hammerspoon.

Not building the documentation (i.e. removing ./scripts/build.sh docs) builds for me. Not sure why I can't build the documentation anymore though? Any ideas @asmagill ?

from hammerspoon.

Where is the pip executable that you're calling? (which pip)

This could be one of the tedious things that happens when you have multiple Python installs and paths get messy.

from hammerspoon.

/Library/Frameworks/Python.framework/Versions/3.11/bin/pip

That weird part is that I've build fine previously, and as far as I can see, nothing has changed in the build scripts since I last built, and I haven't updated Xcode, because I'm still on Monterey.

from hammerspoon.

In my Catalina build attempts, I've run into an issue with the Sparkle Pod not honoring the limitation to build for 10.15, so I haven't tested the doc building yet. Checking the docs for Sparkle I found one line in the release notes that talks about bumping the required Xcode version to something after the one I can run on Catalina, but no details. Still trying to learn how the pods work, maybe I could tell it to use an earlier version?

I'm thinking about stripping out Sparkle completely since we won't be using it anyways, but I was trying to keep the core files as close to the original as possible to simplify future merges. I'll poke at it some more next week.

from hammerspoon.

As far as I can tell, it's something in here going funky:

function assert_docs_requirements() {
    # FIXME: This is overly broad - if all that's happening is linting or JSON generation, these requirements are not required
  echo "Checking Python requirements.txt is satisfied..."
  echo "import sys
import pkg_resources
from pkg_resources import DistributionNotFound, VersionConflict
dependencies = open('${HAMMERSPOON_HOME}/requirements.txt', 'r').readlines()
pkg_resources.require(dependencies)" | /usr/bin/python3
}

...any ideas @cmsj ?

from hammerspoon.

Yep, your pip is from a different Python than the one being used during the build (3.11 vs 3.9).

Have you run the build.sh installdeps?

from hammerspoon.

Will try again now.

from hammerspoon.

Ok, so I ran build.sh installdeps but now I get..

Building docs Markdown...
Traceback (most recent call last):
  File "/Users/chrishocking/Documents/GitHub/CommandPost-App/scripts/docs/bin/build_docs.py", line 835, in <module>
    main()
  File "/Users/chrishocking/Documents/GitHub/CommandPost-App/scripts/docs/bin/build_docs.py", line 829, in main
    write_markdown(arguments.output_dir + "/markdown/",
  File "/Users/chrishocking/Documents/GitHub/CommandPost-App/scripts/docs/bin/build_docs.py", line 735, in write_markdown
    write_templated_output(output_dir, template_dir, title, source_url_base, data, "md")
  File "/Users/chrishocking/Documents/GitHub/CommandPost-App/scripts/docs/bin/build_docs.py", line 662, in write_templated_output
    import markdown
ModuleNotFoundError: No module named 'markdown'

from hammerspoon.

Ah, actually, maybe this is my fault:

	########################################################
	## ADDED BY CHRIS FOR COMMANDPOST:
	########################################################
    import jinja2
    import markdown

    md = markdown.Markdown(extensions=['meta'])

    jinja = jinja2.Environment()
    jinja.filters['markdown'] = lambda text: jinja2.Markup(md.convert(text))
    jinja.trim_blocks = True
    jinja.lstrip_blocks = True
	########################################################

from hammerspoon.

Adding markdown to requirements.txt solved for me!

Thanks team! Apologies for the noise.

from hammerspoon.