Peter Kropf <[EMAIL PROTECTED]> wrote:
>> Isn't just the backslash vs forward slash problem? Does it work if you
>> remove it altogether, eg, os.path.join(HOMEPAGE, 'support',
>> '_mountzlib.py') ?
>
> The problem is that the .spec files were generated on Windows and have
> a CRLF line terminator. I checked the .tar.gz distribution and the SVN
> source and they both have it. I'm not certain why the problem exists
> in SVN since it is supposed to take care of the platform text file
> dependencies for you. I'll look at it a bit more to see why but this
> causes a problem for Python on FreeBSD 6.0. I also tried it on a
> Ubuntu Linux system and it worked just fine. Weird.
This is easily fixed by adding svn:eol-style=native to spec files. Committed
in r269.
>> It'd be very helpful if you tried the tests under FreeBSD to check if
they
>> work.
>
> Next problem that I ran into was that the .spec files all create a
> program with a .exe extension. However, the runtests.py program tried
> to run the executable without specifying the .exe extension. And that
> doesn't work all that well on non-Windows platforms ;-) BTW, this is
> also a problem on Linux.
That's right. I believe the output of Makespec could be made
platform-independent somehow. I'm not sure Build.py is smart enough to, eg,
add .exe extensione automatically under Windows. I'll have to check that.
> I'm also seeing a problem with test8 on FreeBSD but haven't looked
> into it yet. Here's the output:
>
>
> ################## EXECUTING TEST test8.py
################################
>
> Traceback (most recent call last):
> File "../Build.py", line 830, in ?
> build(sys.argv[1])
> File "../Build.py", line 76, in build
> exec open(spec, 'r').read()+'\n'
> File "<string>", line 2, in ?
> File "../Build.py", line 102, in __init__
> raise ValueError, "script '%s' not found" % script
> ValueError: script '../support\_mountzlib.py' not found
> disttest8/test8: not found
As I said before, test8.spec and a few others use backslashes in paths
instead of forward slashes. It also contained some absolute paths (eww). I
fixed these issues and committed them as r270.
> Lastly, I tried to submit some bugs to Trac but received:
> Trac detected an internal error:
>
> {'[EMAIL PROTECTED]': (553, "sorry, that domain isn't in my list of
> allowed rcpthosts (#5.5.3 - chkuser)")}
>
> Should I submit them as anonymous? I'd like to receive notification if
> / when the tickets are changed. I can also create a svn diff patch for
> the changes needed for the .exe problem. Should I email that? Or
> attach to a ticket in Trac?
Yes, this is a known problem in our website: ticket email notifications are
broken. I know William was looking into it, but I don't know what's the
current status. AFAICT, only notifications to the mailing list work.
Thanks!
--
Giovanni Bajo
_______________________________________________
PyInstaller mailing list
[email protected]
http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
