titleistfour | 16 Jul 21:11 2007
Picon

hook for paramiko


Does anyone have a hook for using paramiko and Crypto?  Paramiko is a
popular package that implements ssh2 in pure python. I'm having
problems building a single binary with that package.  Thanks

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "PyInstaller" group.
To post to this group, send email to PyInstaller@...
To unsubscribe from this group, send email to PyInstaller-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en
-~----------~----~----~----~------~----~------~--~---

titleistfour | 16 Jul 22:45 2007
Picon

Re: hook for paramiko


Found this reference to the same problem.

http://www.mail-archive.com/pyinstaller-/JYPxA39Uh5TLH3MbocFFw <at> public.gmane.org/msg00033.html

Does anyone have a quick fix?

On Jul 16, 2:11 pm, titleistfour <titleistf...@...> wrote:
> Does anyone have a hook for using paramiko and Crypto?  Paramiko is a
> popular package that implements ssh2 in pure python. I'm having
> problems building a single binary with that package.  Thanks

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "PyInstaller" group.
To post to this group, send email to PyInstaller@...
To unsubscribe from this group, send email to PyInstaller-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en
-~----------~----~----~----~------~----~------~--~---

Rishi Khare | 19 Jul 14:18 2007
Picon

problem with different versions of linux


hi all,
      we are facing some problem while running our application on
different versions of linux.
we have an application which uses python-2.4.4 , matplotlib-0.90.0 ,
numpy-1.0.1, and numarray.
we have mainly 2 different types of linux boxes , one older ones with
kernel 2.4.21-47, gcc-3.2.3 (Red Hat Linux 3.2.3-56) and other newer
ones with kernel 2.6.9-42,gcc-3.4.6 (Red Hat 3.4.6-3)

 we need a wide python to support unicode so we install it from source
with ./configure --prefix=$prefix --enable-unicode=ucs4 and then we
install all other modules via python setup.py install

when we create the executable on older machine, it runs fine on older
machine but on newer machine it fails with this message

>> relocation error: /tmp/_MEI21064/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE >> not
defined in file ld-linux.so.2 with link time reference

and if we create the executable on a newer machine then it runs fine
on newer machine but fails on the older machine with this message

>> relocation error: /tmp/_MEI9475/libc.so.6: symbol _rtld_global_ro, version GLIBC_PRIVATE >> not
defined in file ld-linux.so.2 with link time reference

ld-linux.so.2 is at the same place on both machines /lib/ld-linux.so.2

any suggestions/solutions how to solve this?any small hints will also
be of a great help, we need to fix this badly :)
(Continue reading)

Rishi Khare | 19 Jul 14:27 2007
Picon

Re: problem with different versions of linux


just to add we are using pyinstaller-1.3 and creating an elf version
of executable with one file option.

On Jul 19, 5:18 pm, Rishi Khare <khare.ri...@...> wrote:
> hi all,
>       we are facing some problem while running our application on
> different versions of linux.
> we have an application which uses python-2.4.4 , matplotlib-0.90.0 ,
> numpy-1.0.1, and numarray.
> we have mainly 2 different types of linux boxes , one older ones with
> kernel 2.4.21-47, gcc-3.2.3 (Red Hat Linux 3.2.3-56) and other newer
> ones with kernel 2.6.9-42,gcc-3.4.6 (Red Hat 3.4.6-3)
>
>  we need a wide python to support unicode so we install it from source
> with ./configure --prefix=$prefix --enable-unicode=ucs4 and then we
> install all other modules via python setup.py install
>
> when we create the executable on older machine, it runs fine on older
> machine but on newer machine it fails with this message
>
> >> relocation error: /tmp/_MEI21064/libc.so.6: symbol _dl_starting_up, version GLIBC_PRIVATE >>
not defined in file ld-linux.so.2 with link time reference
>
> and if we create the executable on a newer machine then it runs fine
> on newer machine but fails on the older machine with this message
>
> >> relocation error: /tmp/_MEI9475/libc.so.6: symbol _rtld_global_ro, version GLIBC_PRIVATE >> not
defined in file ld-linux.so.2 with link time reference
>
(Continue reading)

Rishi Khare | 20 Jul 22:58 2007
Picon

Re: problem with different versions of linux


finally we are able to solve it,
the solution was to avoid packing the libc.so.6 in the executable so
that it searches for it in the client machine and uses the version it
finds there,
that version would be compatible with ld-linux.so found on that
machine.

to accomplish this there are many approaches , we followed a basic
approach where we banned any lib from paths like /usr/lib , /lib and /
lib/tls
go to pyinstaller-1.3/bindepend.py and there is a default exclusion
list, just add /lib/tls or any other path which you want to block,
then run Configure.py
this will generate a config.dat which will not have any entry
corresponding to those libs, you can choose to modify the config.dat
also but that didnt worked for us.
now use your Build.py as usual.

--Thanks
Rishi Khare

On Jul 19, 5:27 pm, Rishi Khare <khare.ri...@...> wrote:
> just to add we are using pyinstaller-1.3 and creating an elf version
> of executable with one file option.
>
> On Jul 19, 5:18 pm, Rishi Khare <khare.ri...@...> wrote:
>
> > hi all,
> >       we are facing some problem while running our application on
(Continue reading)

Rishi Khare | 20 Jul 23:08 2007
Picon

Re: optparse import problems


1.Try adding the following to your spec file, sometimes the imports
added to spec file resolves all the issues of missing modules and it
forces their inclusion
    import optparse

2.check for your PYTHONPATH first,and make sure it is not being
imported as a sub module earlier before it is being imported as a
complete module.
3.use Pyinstaller-1.3/ArchiveViewer.py to find out the contents of
your executable created , and make sure that optparse is being
included there.
let us know if that helped.

it might be working fine on one machine because it might be able to
import it from the default path there which is absent on another
machine.
--Thanks
Rishi Khare
Louai Al-Khanji wrote:
> Hi all,
> I'm having some trouble with imports. The weird thing is that it works
> fine on one machine, but not on another one, and I cannot figure out
> why.
>
> Specifically importing optparse seems to be broken somehow. I tested
> some other modules like sys and os and they work ok, but the
> following:
>
> import optparse
(Continue reading)

Rishi Khare | 20 Jul 23:19 2007
Picon

Re: sys.getfilesystemencoding() always return None

encodings are usually missed in pyinstaller created exectables.
in your spec file import them explicitely and probably that should do
the trick.

On Jun 14, 3:28 pm, 人言落日是天涯,望极天涯不见家 <kelvin.... <at> gmail.com> wrote:
> On 6月14日, 下午6时19分, 人言落日是天涯,望极天涯不见家
<kelvin.... <at> gmail.com> wrote:
>
> > When I packaged my program with pyinstaller, the
> > sys.getfilesystemencoding()  always return None. My system is
> > Fedora5.  If I run the origion file directly, it work fine.
> > Any suggestion will be appreciated.
>
> In addition, my python version is 2.5.1

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "PyInstaller" group.
To post to this group, send email to PyInstaller <at> googlegroups.com
To unsubscribe from this group, send email to PyInstaller-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en
-~----------~----~----~----~------~----~------~--~---

Rishi Khare | 20 Jul 23:23 2007
Picon

Re: Adding folder


instead of tree try PKG , it will archive your data into a .pkg file
and
in your installation script you can unarchive it.

On May 27, 4:46 pm, Tobbe <tobbeswe...@...> wrote:
> This is the spec file I'm using. As you can see I have tried to use
> the Tree class to include the data directory, but it doesn't seem to
> work...
>
> a = Analysis([os.path.join(HOMEPATH,'support\\_mountzlib.py'),
> os.path.join(HOMEPATH,'support\\useUnicode.py'), 'c:\\Tobbe\
> \DevProjects\\Python\\Slide\\slide.py'],
>              pathex=['C:\\Tobbe\\Download\\pyinst'])
> pyz = PYZ(a.pure)
> tree = Tree('c:\\Tobbe\\DevProjects\\Python\\Slide\\data')
> exe = EXE( pyz,
>           a.scripts,
>           a.binaries,
>           tree,
>           name='slide.exe',
>           debug=False,
>           strip=False,
>           upx=False,
>           console=False )
>
> On May 27, 4:27 am, Tobbe <tobbeswe...@...> wrote:
>
> > Hi
>
(Continue reading)

Rishi Khare | 20 Jul 23:30 2007
Picon

Re: msvcr71.dll could not be extracted


common problem, and using matplotlib gives lot of problems in
pyinstaller,
actually not only matplotlib but also you would need to copy numpy/
numaray whatver you are using in your program
because matplotlib will need that.
explicit imports to your matplotlib and numpy in your spec file will
ensure it being picked up
add it to your spec file and make sure your pythonpath can find them

import matplotlib
import matplotlib.xxx (whatever all other packages u use)
import pylab  (if u use pylab interface)
import numpy
import numpy.xxx (whatever all other package u use..)

the way i do it is to pack matplotlib in a single pkg file and numpy
in a single pkg file and include them in executable,
in my init script i just unpack them and use.

On May 27, 5:07 pm, Massi <massi_...@...> wrote:
> Yes, I did the same and the problem was solved, but I couldn't build
> the executable anyway. well, in fact the executable is built, but it
> can't be run....It seems that pyinstaller can't import matplotlib
> packages. Did anyone have the same problem?
>
> On 27 Mag, 12:14, Tobbe <tobbeswe...@...> wrote:
>
> > I had that problem as well. All I had to do to fix it was to grab the
> > latest version of PyInstaller from svn
(Continue reading)

CheesyGuy | 23 Jul 16:49 2007
Picon

Problems with pyGTK and PyInstaller.


I have a small python application with UI designed in glade. This app
runs properly as a script. I needed to convert it to a distributable
exe.

1) I am using pyinstaller version 1.3. This version still does not
appear to have a corrected hooks\hook-gtk.py. Following some other
posts, I have edited my local copy to include all the required hidden
imports.
2) I have copied the .glade file to the exe directory.
3) I have generated a new pango.modules file using pango-querymodules.

My current problem is:

When I run my executable, pango complains that it is unable to find
any built-in or dynamically loadable modules. It suggests that I build
my pango.modules file using pango-querymodules, which I have already
done.
This results in the application showing all my buttons and labels and
other text as simple squares.I am a new python user and on both linux
and windows. Some help would be greatly appreciated.

Thanks in advance.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "PyInstaller" group.
To post to this group, send email to PyInstaller@...
To unsubscribe from this group, send email to PyInstaller-unsubscribe@...
For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en
-~----------~----~----~----~------~----~------~--~---
(Continue reading)


Gmane