PyPN can’t find python26.dll

Discussion Forums discussion PyPN can’t find python26.dll

This topic contains 14 replies, has 7 voices, and was last updated by  HDDC 1 month, 1 week ago.

Viewing 15 posts - 1 through 15 (of 15 total)
Author Posts
Author Posts
June 20, 2009 at 5:33 pm #618

kuukkeli
Member

I’m trying to use the latest portable version and while PN itself works fine I can’t get PyPN working. After manually adding pypn.dll to config file I get the following error:

"The program can’t start because python26.dll is missing from your computer. Try installing the program to fix this problem"

Yet I do have Python 2.6.2 installed and the said .dll file is in system32 folder. After I close the error dialog PN starts but PyPN isn’t not listed in extensions. If I copy the .dll file to PN folder there’s no error but PyPN still doesn’t show in extensions. Any ideas how to fix this?

I’m running 64-bit Windows 7 RC build 7100.

June 20, 2009 at 5:43 pm #16536

Midas
Member

Same problem here on 32-bit Windows Vista Home Premium, SP1.

June 25, 2009 at 11:39 am #16537

kuukkeli
Member

I managed to fix my problem by removing 64-bit Python and installing 32-bit version instead. It seems that quite a few libraries are lacking 64-bit support so I would have changed anyway and gladly it fixed PN as well.

March 21, 2011 at 5:25 pm #16538

muradkhan
Member

In an effort to install PyPN, I failed to see that PyPN only appears to be available for Python 2 and I went ahead and installed Python 3.2. Just checking to see if I’m really going to have to uninstall 3.2 and step back to 2.6.

Cheers.

March 21, 2011 at 7:19 pm #16539

muradkhan
Member

Removed Python 3.2, replaced it with Python 2.6, copied over the python26.dll to windowssystem32 and we’re all good to go.

March 22, 2011 at 6:28 pm #16540

stier08
Member

muradkhan,

Though your solution solves the problem it is not generic, and will not do for portable users or those w/o admin rights.

In order to use PyPn in default environment you need to add c:Python26 to your path

Fro portable users: one can install portable pnotepad with PyPn in

<USB DRIVE>/portable-pn2202240

Portable Python to

<USB DRIVE>/Portable-python

and use a script <USB DRIVE>/start.portable.pn.bat with following content

1: set PortablePythonDir=”%~dp0Portable-python”

2: cd /d “%~dp0portable-pn2202240″

3: set PATH=%PortablePythonDir%;%PATH%

4: pn.exe –findexts

5: start pn.exe

May 17, 2011 at 11:02 am #16541

CoDEmanX
Member

I tried your solution (PortablePython 2.6.1 + Portable PN 2.3.2.2300-rc1), but I got application runtime errors and no or not all scripts listed in the dock.

But this works for me:

  • Get latest portable PN (2.3.3.2332-rc2) and PyPN (v1.0.2300)
  • Python 2.6.6 MSI-installer from Python.org
  • Unpack the MSI to pn dir: C:pn_dir> msiexec /a python-2.6.6.msi TARGETDIR=C:pn_dir /qb
  • Add pypn.dll to settingsconfig.xml or run pn.exe –findexts

Tested on WinXP with user-rights, no environment variables involved.

All stock python-scripts appear in scripts-dock and work, so does PyPN in textclips!

May 17, 2011 at 5:30 pm #16542

CoDEmanX
Member

I searched the registry to see if python created any keys, but is doesn’t – thats good.

Also tried if one can put the python files in a subfolder instead of right into pn’s root dir. This requires pypn files to be in that subdir as well. I added an extension entry to pnconfig.xml – with on effect. So i added it to settingsconfig.xml, path: Python26pypn.dll

gave me error, boost python dll not found. Apparently it’s not possible to have extensions in subdirs – thats bad.

May 19, 2011 at 10:55 am #16543

CoDEmanX
Member

I made a self-extracting archive that contains PyPN v1.0.2300 and Python 2.6.6. Select your PN root directory and extract. Run pn.exe --findexts afterwards. For PN v2.3.2.2300-rc1 and v2.3.3.2332-rc2 (should work for both, installed and portable distribution)

PyPN-1.0.2300_Python-2.6.6.exe (~13 MB, hosted at MediaFire.com)

May 19, 2011 at 11:15 am #16544

simon
Key Master

Great! 13mb is pretty heavy though, I wonder if we could cut that down to a sensible subset of Python to include with PN?

I’d like to offer a PN+PyPN download with more stuff done via python, but would like to see the size cut down first.

May 23, 2011 at 8:11 pm #16545

CoDEmanX
Member

Yeah, i’m not sure though if one can delete libs without errors. I gave it a try and ended up with 4mb 7zip archive incl. PyPN, seems to work fine.

removed:

include source header files?

tcl gui lib?

doc python help file

scripts and tools which are basically examples

tests test and exploit scripts?

tkinter library, doesn’t work anyway at the moment cause argv array isn’t set

i could also remove database stuff except sqlite, perhaps multimedia and multithreading too?

May 25, 2011 at 1:05 pm #16546

simon
Key Master

Nice! I think it would be fine to remove more, yes. The idea I guess is to get to the point of a minimal distribution that enables common scenarios in PyPN. Users can then opt to use their own full Python installation (have to work out how to do that).

May 26, 2011 at 3:34 pm #16547

CoDEmanX
Member

okay, i removed the lib dir entirely, but it broke python (couldn’t import traceback…)

But it seems alright to delete files, which belong to a module which is already removed.

So i dropped database support incl. sqlite

hash and encryption stuff (md5, ssl…)

compression stuff (bz2, tar, zip)

audio stuff (we don’t want to edit waves files while coding lol!)

distutils (python distribution)

2to3 (converter python v2 to v3)

msilib (reads Microsoft Installer files)

idlelib (belongs to tcl/tkinter)

pydoc (python help file stuff)

python executables (python.exe / pythonw.exe / w9xpopen.exe – obviously not needed as we still have python DLL)

python-2.6.6.msi (uninstall information?)

I compressed the rest together with PyPN and a ~2 mb self-extracting archive came out. I think this is pretty good already, nonetheless i could remove even more (threading, internet stuff except XML parser…)

May 27, 2011 at 12:54 am #16548

CoDEmanX
Member

After a couple experiments, i found an easy solution to create a lightweight python package:

- Remove all .pyc files

- Run some PyPN scripts in PN and check libs for new .pyc files

- Remove all .py files, which do NOT have a corresponding .pyc

- Remove the new .pyc files as well

Result: Only 22 .py files left (may differ, depends on what modules you use)

Here my UltraLight pack:

PyPN-1.0.2300_Python-2.6.6_UltraLight.exe (1.23 MB, hosted at MediaFire.com)

August 8, 2014 at 10:12 pm #20185

HDDC
Participant

Hello all

I understand that this is about an old version now (and it’s gone from MediaFire anyway) but I wondered if any of you had a similar ultralight portable of the current version of PN2 with PyPN and Python? Getting this working is something which has been giving me a headache, so I’m pleased to have found this thread of people wanting the same thing – who probably have it all sorted already :)

Thanks

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic.