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

Pdoc commandline script name conflict #52

Closed
karimbahgat opened this issue May 29, 2015 · 2 comments

Comments

Projects
None yet
3 participants
@karimbahgat
Copy link

commented May 29, 2015

When using pdoc for the first time I encountered an error with the commandline script that got placed into Python27/Scripts. First off, the file did not have the .py extension, so I had to add it. Secondly, when the commandline script tried importing pdoc from site-packages it just ended up importing itself (because the commandline script had the same name as the site-packages pdoc), resulting in a nameerror when trying to run the import_module() function. Changing the name of the commandline script fixed this error.

I am surprised noone else have gotten this error? Should be a quick fix anyway. I am on Windows 8, 32 bit Py27.

@marcos-alfredo

This comment has been minimized.

Copy link

commented Jul 27, 2016

Had the same issue where after installing pdoc, it created a script without extension.
Using Python 2.7 and Windows 7.

@sjpb sjpb referenced this issue Nov 6, 2017

Merged

Fix windows install #138

@cortesi

This comment has been minimized.

Copy link
Member

commented Jun 3, 2018

Pdoc now targets Python 3.6 and later. Please let us know if you still see this issue there. Thanks!

@cortesi cortesi closed this Jun 3, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.