Re: GO vs Python
On Mon, Aug 25, Michael Torrie wrote: > No it came through fine here, originally. It must be Google Groups that > messed up the characters in displaying the message and in your reply. Likely not. The header I got with msgid lacks basic headers like "Content-Type:" and "Content-Transfer-Encoding:". Funny that this happend in a thread about encoding... Olaf -- https://mail.python.org/mailman/listinfo/python-list
Re: Python and IDEs [was Re: Python 3 is killing Python]
On Sat, Aug 02, Gregory Ewing wrote: > MacOSX doesn't currently have an automatic dependency > manager, but if it did, things would still be a lot neater > and tidier than they are in Linux or Windows, where what > is conceptually a single object (a package) gets split up > and its parts scattered around several obscure locations. How does "a package" differ? Its "a package" here and there. Just use the correct tools to inspect "a package", like 'rpm -qliv $package' to see what "a package" is all about. Olaf -- https://mail.python.org/mailman/listinfo/python-list
Re: rpath alike feature for python scripts
On Mon, Jul 28, Albert-Jan Roskam wrote: > does this help: https://nixos.org/patchelf.html. It is not specific to > Python, though. No, this does not help because its not about patching the result. The questions is how to obtain the value with should be patched into the result. Looks like I have to dissect setup.py and mimic its behaviour in the Makefile. Olaf -- https://mail.python.org/mailman/listinfo/python-list
Re: rpath alike feature for python scripts
On Sat, Jul 26, dieter wrote: > The "binary" corresponds to a script. The script could have > a function "setup_path" which enhances "sys.path" as appropriate > and ensure that this function is called near its beginning. Yes, but how does it obtain the required values? In other words, at buildtime /some/where is known because its the --prefix= value. How does it know the remainder? +sys.path.insert(0, "/some/where/lib64/python2.6/site-packages") Olaf -- https://mail.python.org/mailman/listinfo/python-list
rpath alike feature for python scripts
Hello, ELF binaries have a concept of RPATH, that means the interpreter looks for libraries first in a list of directories provided by the binary before falling back to default system directories. Since python scripts also do some sort of library loading, but lack an RPATH like feature, I'm asking here how to simulate it. The specific case I'm trying to address is the pygrub script which is included in the xen-tools package. This script makes use of other python libs provided by xen-tools. If xen is configured with --prefix=/some/where the python libs will be installed (in my case) in "/some/where/lib64/python2.6/site-packages". However, there seems to be no way in advance to know that exact location. If it would be known at build time, then something could tweak the pygrub script and insert the searchpath below "/some/where". And is this the right approach anyway? +sys.path.insert(0, "/some/where/lib64/python2.6/site-packages") After browsing the disutils documentation its not clear if setup.py has a way to help with this. Here is a pointer to a discussion I started a while ago, and the sources: http://lists.xenproject.org/archives/html/xen-devel/2014-04/msg02931.html http://xenbits.xen.org/gitweb/?p=xen.git;a=tree;f=tools/pygrub http://xenbits.xen.org/gitweb/?p=xen.git;a=tree;f=tools/python Thanks for any pointers. Olaf -- https://mail.python.org/mailman/listinfo/python-list
