pygwalker icon indicating copy to clipboard operation
pygwalker copied to clipboard

[BUG] Installation from conda-forge yields No module named 'lib2to3'

Open WillAyd opened this issue 1 year ago • 3 comments

Describe the bug When installing pygwalker via conda, the actual installation works, but subsequent import yields:

----> 1 import pygwalker as pyg

File ~/miniforge3/envs/scratchpad/lib/python3.13/site-packages/pygwalker/__init__.py:16
     13 __version__ = "0.3.17"
     14 __hash__ = __rand_str()
---> 16 from pygwalker.api.walker import walk
     17 from pygwalker.api.gwalker import GWalker
     18 from pygwalker.api.html import to_html

File ~/miniforge3/envs/scratchpad/lib/python3.13/site-packages/pygwalker/api/walker.py:10
      8 from pygwalker.data_parsers.database_parser import Connector
      9 from pygwalker._typing import DataFrame
---> 10 from pygwalker.services.format_invoke_walk_code import get_formated_spec_params_code_from_frame
     11 from pygwalker.services.kaggle import auto_set_kanaries_api_key_on_kaggle, adjust_kaggle_default_font_size
     12 from pygwalker.utils.execute_env_check import check_convert, get_kaggle_run_type, check_kaggle

File ~/miniforge3/envs/scratchpad/lib/python3.13/site-packages/pygwalker/services/format_invoke_walk_code.py:3
      1 from typing import Optional, List, Any
      2 from types import FrameType
----> 3 from lib2to3 import fixer_base, refactor
      4 import logging
      5 import inspect

ModuleNotFoundError: No module named 'lib2to3'

To Reproduce

$ conda install pygwalker
... # open REPL
>>> import pygwalker

Expected behavior Import should work

Versions

  • pygwalker version: 0.3.17
  • python version: 3.13.1
  • browser

Additional context A pip install seems to be successful, and installs a newer version (0.4.9.13) so I'm guessing the conda-forge recipe is just outdated?

WillAyd avatar Dec 19 '24 16:12 WillAyd

have same issue, but it work for me when downgrade to python 3.12 version

hualong1009 avatar Feb 17 '25 02:02 hualong1009

I am getting the same import error as WillAyd with Python 3.13.

dagibbs22 avatar Jun 06 '25 15:06 dagibbs22

Its been a while since I have looked at this, but it may also be the result of Python 3.13 removing the lib2to3 module:

https://docs.python.org/3.13/whatsnew/3.13.html#to3

WillAyd avatar Jun 09 '25 14:06 WillAyd