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

Error running dump_pfile_header #6

Open
kyezhang opened this issue Mar 3, 2018 · 5 comments
Open

Error running dump_pfile_header #6

kyezhang opened this issue Mar 3, 2018 · 5 comments

Comments

@kyezhang
Copy link

kyezhang commented Mar 3, 2018

Hi Nathan,

I run into this error when running dump_pfile_header. BTW, I'm looking for the offsets and sizes of daptab and the exam info.

(C:\Anaconda3) c:\Data\ADRC>dump_pfile_header -h
Traceback (most recent call last):
File "C:\Anaconda3\Scripts\dump_pfile_header-script.py", line 11, in
load_entry_point('pfile-tools==0.5.0', 'console_scripts', 'dump_pfile_header
')()
File "C:\Anaconda3\lib\site-packages\pkg_resources_init_.py", line 570, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "C:\Anaconda3\lib\site-packages\pkg_resources_init_.py", line 2755, in
load_entry_point
return ep.load()
File "C:\Anaconda3\lib\site-packages\pkg_resources_init_.py", line 2409, in
load
return self.resolve()
File "C:\Anaconda3\lib\site-packages\pkg_resources_init_.py", line 2415, in
resolve
module = import(self.module_name, fromlist=['name'], level=0)
ImportError: No module named 'pfile_tools.scripts'

Sorry that I can't find how to fix the module name with my poor python knowledge.

Thank you!
Kai

@njvack
Copy link
Owner

njvack commented Mar 5, 2018

Hm... I suspect it's something about python 3 and module importing syntax. I'll try and take a peek.

@curtcorum
Copy link

curtcorum commented Jul 18, 2018

FYI

I could not get dump_pfile_header to run under python 3. I did not try very hard, though.

It does seem to run from 2.7.

Also it seems that 0.5.0 is not the latest (directly from pip). Using sudo pip install --editable ./ from the cloned git tree did work fine.

Nice that it works with 26.002!

@njvack
Copy link
Owner

njvack commented Jul 18, 2018

Hi,

I have basically zero time to maintain this project these days. I'm not gonna say I'll never check into to this but I don't have near-future plans to do it.

Sorry :/

@curtcorum
Copy link

curtcorum commented Jul 22, 2018 via email

@sufkes
Copy link

sufkes commented Jan 27, 2020

I had the same problem as @kyezhang . Using sudo pip install --editable ./ from the cloned git tree (as curtcorum suggested) seemed to fix this problem.

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

4 participants