Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Path to markitdown #204

Open
soccken opened this issue Dec 23, 2024 · 11 comments
Open

Path to markitdown #204

soccken opened this issue Dec 23, 2024 · 11 comments

Comments

@soccken
Copy link

soccken commented Dec 23, 2024

I installed it by running [pip install markitdown] in Windows PowerShell.

After that, I ran [markitdown path-to-file.pdf -o document.md], but I got a problem where "markitdown" was not recognized as an operable program.
Is this a problem with the Path?

@l-lumin
Copy link
Contributor

l-lumin commented Dec 23, 2024

hi, can you share your Path environment variable? I think you should run it in venv or use pipx, rather than installing it directly with pip

@mrbarua
Copy link

mrbarua commented Dec 23, 2024

Even I have the same issue "markitdown command not found"

@boredchilada
Copy link

boredchilada commented Dec 24, 2024

You can use my webgui if you'd like while you get this fixed. We do not save any information.

we also added batch mode.

mitdown.ca

Image

@mrbarua
Copy link

mrbarua commented Dec 26, 2024

Hello @soccken
I solved it after reinstalling Python.

@Walterfraser
Copy link

Walterfraser commented Dec 30, 2024

I installed it by running [pip install markitdown] in Windows PowerShell.

After that, I ran [markitdown path-to-file.pdf -o document.md], but I got a problem where "markitdown" was not recognized as an operable program. Is this a problem with the Path?

It installs it into your python script directory, for me this was:

C:\Users\Username\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\Scripts\

You can install a virtual environment in a folder by typing:

python3 -m venv venv

Then use the following to activate it: venv\scripts\activate

Once it's active install it in the location you've created (for me I created a folder in c:\Dev) using the "pip install markdown" while in that directory

This is relative to Windows, colleagues on mac had no issue with this

@tiansiyuan
Copy link

Same on Ubuntu 20.04.

@KiryUp
Copy link

KiryUp commented Jan 23, 2025

Can anyone please explain, or at least point to a documentation that shows how to make this work globally ? i tried this on ubuntu too and i get the same message "markitdown command not found"". From the doc it simply says that after a "pip install" it should be possible to call it from a cmd line interface just like a tool, but it's not the case. Thanks for the help

@KiryUp
Copy link

KiryUp commented Jan 23, 2025

just a follow up on how I fixed the issue on my hand.
I was using an old version of python (3.8 on ubuntu WSL), which seemed to install an "incomplete" vresion folder inside ~/.local/lib/python3.8/site-packages that's why I was confused.
Eventually I used "pyenv" to install a new version and installed a 3.12 version and made it my "global" version, then did the install again via "pip install markitdown" and it worked.
Hope this help !

@tiansiyuan
Copy link

Yes, it does not work with Python 3.8 (the default Python3 version on Ubuntu 2004.

It works with 3.12.

I tried with a 3.12 docker image, python:3.12.

Thanks

@dantetemplar
Copy link

You can use my webgui if you'd like while you get this fixed. We do not save any information.

we also added batch mode.

mitdown.ca

Image

+respect for this demo bro, I will include it at https://github.com/dantetemplar/pdf-extraction-agenda/tree/main?tab=readme-ov-file#marker

@pchuri
Copy link

pchuri commented Mar 4, 2025

I also experienced the "markitdown command not found" issue and solved it with these steps:

  1. I ran pip show markitdown to find the actual installation path.
  2. In my case, it was installed at C:\Users\USER\AppData\Roaming\Python\Python312\Scripts.
  3. I added this path to the Windows PATH environment variable (Control Panel > System > Advanced System Settings > Environment Variables > Edit Path).
  4. After opening a new command prompt, the markitdown command worked correctly.

The script installation location may vary depending on your Python installation method and environment, so it's important to check the exact path with pip show markitdown and then add that to your PATH.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants