nParse - Yet another parser.

[Gumbo]

Originally Posted by Mirox [You must be logged in to view images. Log in or Register.]

1. Get nParse master source (https://github.com/nomns/nparse/archive/master.zip or if you have git installed, "git clone https://github.com/nomns/nparse" in command prompt.
2. Install Python 3 (https://www.python.org/downloads/) -- ensure add python to path is selected during install.
3. Open up a command prompt, run "pip install pyqt5"
4. In the command prompt and within the source directory, "python nparse.py"

I checked with Python and the last version that supports Windows XP is 2.77 so I downloaded and install that version.

I downloaded the nParse master source and unzipped it into a folder and copied it to the Python27 directory.

I opened a command prompt and typed 'pip install pyqt5' and it told me that I was using an outdated version and to downloaded the latest version. It did so from the command prompt but now if I type 'pip install pyqt5', I get told that 'pip' is not recognized as an internal or external command.

I change the directory to c:\python27\nparse and type in the command prompt, python nparse.py, I get the following error:

File "nparse.py", line 207
sys.exit(APP.exec())

SyntaxError: invalid syntax

Did I do something wrong or does it sound like it just doesn't work?

[Mirox]

Originally Posted by Gumbo [You must be logged in to view images. Log in or Register.]

I checked with Python and the last version that supports Windows XP is 2.77 so I downloaded and install that version.

I downloaded the nParse master source and unzipped it into a folder and copied it to the Python27 directory.

I opened a command prompt and typed 'pip install pyqt5' and it told me that I was using an outdated version and to downloaded the latest version. It did so from the command prompt but now if I type 'pip install pyqt5', I get told that 'pip' is not recognized as an internal or external command.

I change the directory to c:\python27\nparse and type in the command prompt, python nparse.py, I get the following error:

File "nparse.py", line 207
sys.exit(APP.exec())

SyntaxError: invalid syntax

Did I do something wrong or does it sound like it just doesn't work?

For sure Python 2 will not work. I am sure I used some stuff that is only compatible with Python 3.

That is weird about the pip issue. The last version of python 3 that supports Windows XP is https://www.python.org/downloads/release/python-345/. You can uninstall Python 2.7, then install Python 3 from that link. Make sure you tell it to put the python executables in the path. Make sure Python 2.7 is removed before doing this.

'pip install pyqt5' should indicate that pyqt5 is installed. If pyqt5 does install, and it warns you about pip being out of date, you can ignore that.

You do not have to put the nparse source in the python directory. As long as Python is put in your system path.. (meaning you can run it from any directory which is an option when you install python -- make sure to look for it, it maybe be out of the way), you should be able to type "python nparse.py" in command prompt. Meaning, you can place the nParse master source in your My Documents folder or something. You can open a command prompt using file explorer by holding shift and right clicking the window then selecting open a command prompt here from the context menu.

I am sorry.. Windows XP -- too bad you can't update it to at least 7 :O

I hope the above works for you.

[Gumbo]

Originally Posted by Mirox [You must be logged in to view images. Log in or Register.]

For sure Python 2 will not work. I am sure I used some stuff that is only compatible with Python 3.

That is weird about the pip issue. The last version of python 3 that supports Windows XP is https://www.python.org/downloads/release/python-345/. You can uninstall Python 2.7, then install Python 3 from that link. Make sure you tell it to put the python executables in the path. Make sure Python 2.7 is removed before doing this.

'pip install pyqt5' should indicate that pyqt5 is installed. If pyqt5 does install, and it warns you about pip being out of date, you can ignore that.

You do not have to put the nparse source in the python directory. As long as Python is put in your system path.. (meaning you can run it from any directory which is an option when you install python -- make sure to look for it, it maybe be out of the way), you should be able to type "python nparse.py" in command prompt. Meaning, you can place the nParse master source in your My Documents folder or something. You can open a command prompt using file explorer by holding shift and right clicking the window then selecting open a command prompt here from the context menu.

I am sorry.. Windows XP -- too bad you can't update it to at least 7 :O

I hope the above works for you.

Looks like I'm out of luck because the link you sent me states the following:

Python 3.4.5 has only been released in source code form; no more official binary installers will be produced.

I checked all the versions close to 3.4.5 and all of them keep saying it has expired and just has me update to the latest version.

No worries and thanks for your help...

[magicfest2]

Ah yeah, thinking about it again and it's obvious that you're correct. The range that the game displays damage messages is super low for some reason. I had to be practically in melee range today trying to see how much damage my pet was doing. So, I guess there really isn't any way to have an accurate parser for this in EQ, unless you're a melee class that's always right next to the mobs.... And even then, you don't see damage for spells you didn't cast, right? Bleh. Guess my pipe dream is dead already.

[magicfest2]

Hey, following up on a different issue -- I was going to start working on a different feature, and figured I should probably base off the `dev` branch, since it looks like it is newer and contains some more modern stuff (like more valid pep8, and a requirements.txt) but it seems to be missing some stuff?

There are references to "widgets" which don't seem to exist, and no obvious standard package provides that. I am assuming during your refactoring you made a widgets directory and forgot to add it to the commit, so that code is only available locally for you?

I see it referenced here (and a few other places): https://github.com/nomns/nparse/blob...s/window.py#L6

[Mirox]

Originally Posted by magicfest2 [You must be logged in to view images. Log in or Register.]

Hey, following up on a different issue -- I was going to start working on a different feature, and figured I should probably base off the `dev` branch, since it looks like it is newer and contains some more modern stuff (like more valid pep8, and a requirements.txt) but it seems to be missing some stuff?

There are references to "widgets" which don't seem to exist, and no obvious standard package provides that. I am assuming during your refactoring you made a widgets directory and forgot to add it to the commit, so that code is only available locally for you?

I see it referenced here (and a few other places): https://github.com/nomns/nparse/blob...s/window.py#L6

I will take a look. I haven't had any time to work on nParse. I am positive I have local changes that haven't been synced since I was in the middle of working on features the last time I was able to work on it.

[Mirox]

Originally Posted by Mirox [You must be logged in to view images. Log in or Register.]

I will take a look. I haven't had any time to work on nParse. I am positive I have local changes that haven't been synced since I was in the middle of working on features the last time I was able to work on it.

I've updated the dev branch -- widgets directory was missing as you surmised. It should be usable, but I can't ensure there are no bugs in it. There are major changes in the dev branch that are not complete, so there are some wonky things like a blank trigger window.

[magicfest2]

Originally Posted by Mirox [You must be logged in to view images. Log in or Register.]

I've updated the dev branch -- widgets directory was missing as you surmised. It should be usable, but I can't ensure there are no bugs in it. There are major changes in the dev branch that are not complete, so there are some wonky things like a blank trigger window.

Thanks! I'll continue polishing stuff on the master branch then, and port over to the dev branch once I'm done so I know any new bugs aren't something I've introduced. [You must be logged in to view images. Log in or Register.]

[magicfest2]

Cool, thanks! I've based my changes on master for now but should be easy to rebase them later.

One more question: what is your build process for releases? I'm *guessing* you are using PyInstaller, and I've been playing around with it, but I'm new to it and can't get it to work exactly the way I want. What is the exact command you use to generate a release?

[Mirox]

I use PyInstaller and use the spec file within the main directory -- "nparse_py.spec". So, I just run ".\pyinstaller nparse_py.spec". It's been so long since I've built it. I may use the --onefile flag or something to ensure the output is a single exe file. Then, everything that isn't imported into the executable needs to be copied into the dist directory where the executable is created. I believe I copy generic settings and most of the data directory.