使用PyInstaller打包含Bokeh与PubSub的Python应用遇新问题

Hey there! Nice work pushing through those initial Jinja2 TemplateNotFound and PubSub import hurdles—those are some of the most frustrating PyInstaller gotchas with these libraries. Since you didn’t share the exact error your .exe is throwing, I’ll break down the most common remaining issues folks hit when packaging Bokeh/PubSub apps, plus actionable fixes:

1. Missing Bokeh Static Assets #

Bokeh depends on a ton of hidden static files (JS, CSS, template fragments) that PyInstaller often overlooks. Here’s how to force it to include them:

• Run PyInstaller with the --collect-data bokeh flag. This tells the tool to pull in all of Bokeh’s required static resources automatically.
• If that doesn’t cut it, manually add the static folder path to your .spec file under the datas section:

  import os
  from bokeh import __file__ as bokeh_install_path
  bokeh_static_folder = (os.path.join(os.path.dirname(bokeh_install_path), 'static'), 'bokeh/static')
  datas = [bokeh_static_folder]
  

2. Undetected Hidden Imports #

Even after fixing the initial PubSub import, PyInstaller’s auto-scanner might miss nested submodules for Bokeh or PubSub:

• Add these hidden imports via command line or your spec file:

  --hidden-import bokeh.io --hidden-import bokeh.models --hidden-import bokeh.plotting --hidden-import pubsub.pub
  

  Tailor the list to match exactly which parts of Bokeh/PubSub your app uses.

3. Runtime Path Mismatch #

Sometimes the exe can’t locate bundled assets when it runs. Add this snippet at the very top of your main script to explicitly point Bokeh to the right resources:

import sys
import os
from bokeh.resources import Resources

# Check if we're running from a bundled exe
if hasattr(sys, '_MEIPASS'):
    # Use bundled static files
    resources = Resources(mode='relative', root_dir=os.path.join(sys._MEIPASS, 'bokeh', 'static'))
else:
    # Fallback to CDN for development
    resources = Resources(mode='cdn')

4. Debug with Console Mode #

If you’re using the --windowed flag (no console window), you’re missing out on critical error logs. Run your exe directly from a command prompt first—this will spit out the full traceback and tell you exactly what’s failing (e.g., a missing module, a missing data file).

5. Custom Template Residuals #

If your app uses custom Jinja2 templates, PyInstaller won’t pick them up by default. Add your template folder to the datas list in your spec file:

datas = [('path/to/your/app/templates', 'templates')]

If you can share the exact error message from the console run, I can help you zero in on the exact fix even faster!

内容的提问来源于stack exchange，提问作者neo