On Mar 1, 11:57 pm, Matteo Bertini <[EMAIL PROTECTED]> wrote: > On 1 Mar, 19:37, [EMAIL PROTECTED] wrote: > > > I've started investigating extending PyInstaller with support for > > pkg_resources. First of all, I want to write tests to verify the > > pkg_resources integration. Not being familiar with PyInstaller > > development practices, I have to ask you guys, how should I write such > > tests and where should I put them etc.? > > PyInstaller has not a proper testsuite, but you can find some tests in > "buildtests". > You can run them all with: python buildtests/runtests.py > > Dunno about other's workflow, I've started with something like: > cd src/pyinstaller > [...code...] > if needed (modified some loader.c file): ./make-linux.sh python > (will do a Make.py + make clean + make in source/linux and a > Configure.py using the provided python version) > and than fire runtests.py. > > The tests are quite basic, each test is a testNN.spec file and a > testNN.py. > Usually each test was a (now solved) bug, and for example test16 is > still failing, so it is something like a regression testsuite. > > Hoping this is enough as a starting point, feel free to ask, I'll try > to help if I can!
Thanks, I think the right approach is to extend buildtests. I've studied pkg_resources a bit in the meantime, and it seems to me that supporting PyOpenGL 3 requires support for eggs. This because PyOpenGL uses egg entry points to find parts of its implementation (pluggable components). Are major changes to PyInstaller's packaging model necessary to be able to include eggs? Arve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
