Hi Andrea,
What about adding an indication that there is custom code?
Noted that when I export setup.py I get a file with mixed line endings.
Werner
P.S.
It works very nicely to generate a setup.py for a http://www.grenouille.com/ in particular pygrenouille which is a performance measuring tool for the internet connection. This project seems to get a bit of momentum here in France to track the performance of the different ADSL suppliers.
Andrea,
Werner F. Bruhin wrote:
Hi Andrea,
What about adding an indication that there is custom code?
Noted that when I export setup.py I get a file with mixed line endings.
One (or one and a half 
) more suggestion.
The generated/exported setup.py does not include something along these lines:
# run it
if __name__ == '__main__':
setup()
So, if I open it e.g. in Boa and try to generate it by clicking on the appropriate toolbar button I get an error.
Also note that the generated file is called "Setup.py" which again with Boa means that it is not recognized as a "setup.py" (lower case).
Werner
Hi Werner,
What about adding an indication that there is custom code?
This is a nice suggestion, although I don't really know *where* to add
a visual indication that custom/post-compilation code is there... I'll
probably add an overlay to the compiler images in the right LabelBook,
something like a "C" on the top right for "Custom code" and a "P" on
the bottom right for "Post-compilation code", if one of them (or both)
are present.
Noted that when I export setup.py I get a file with mixed line endings.
Uhm, I have never noticed it... I'll see which is the cause of it and
I'll try to fix it.
Thank you!
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
On Thu, Oct 9, 2008 at 8:57 AM, Werner F. Bruhin wrote:
Hi Werner,
One (or one and a half
The generated/exported setup.py does not include something along these
lines:# run it
if __name__ == '__main__':
setup()So, if I open it e.g. in Boa and try to generate it by clicking on the
appropriate toolbar button I get an error.
Ok, that's easy to add 
Also note that the generated file is called "Setup.py" which again with Boa
means that it is not recognized as a "setup.py" (lower case).
I thought you could give the name you want when you export the
generated file... isn't it? But anyway, it's just a small change
Thank you for the suggestions and the testing!
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
On Thu, Oct 9, 2008 at 3:26 PM, Werner F. Bruhin wrote:
Andrea Gavana wrote:
Hi Werner,
What about adding an indication that there is custom code?
This is a nice suggestion, although I don't really know *where* to add
a visual indication that custom/post-compilation code is there... I'll
probably add an overlay to the compiler images in the right LabelBook,
something like a "C" on the top right for "Custom code" and a "P" on
the bottom right for "Post-compilation code", if one of them (or both)
are present.Noted that when I export setup.py I get a file with mixed line endings.
Uhm, I have never noticed it... I'll see which is the cause of it and
I'll try to fix it.
It might have to do with custom code. Noticed that I got an additional line(s) in there after I fixed (set all endings to whatever) it with Boa.
Werner
On Thu, Oct 9, 2008 at 8:57 AM, Werner F. Bruhin wrote:
Hi Andrea,
Andrea Gavana wrote:
Hi Werner,
One (or one and a half
The generated/exported setup.py does not include something along these
lines:# run it
if __name__ == '__main__':
setup()So, if I open it e.g. in Boa and try to generate it by clicking on the
appropriate toolbar button I get an error.
Ok, that's easy to addAlso note that the generated file is called "Setup.py" which again with Boa
means that it is not recognized as a "setup.py" (lower case).
I thought you could give the name you want when you export the
generated file... isn't it?
You are right.
But anyway, it's just a small change
But some of us are not capable to see that there is an upper case "S" there :-[
Thank you for the suggestions and the testing!
You are welcome, anyhow it should be me thanking you for the nice tool!
Werner
On Thu, Oct 9, 2008 at 3:26 PM, Werner F. Bruhin wrote:
Hi Werner,
On Thu, Oct 9, 2008 at 3:59 PM, Werner F. Bruhin wrote:
Hi Andrea,
Andrea Gavana wrote:But anyway, it's just a small change
But some of us are not capable to see that there is an upper case "S" there
Sorry, I meant that is a small change to make at the GUI2Exe code... I
am modifying the source to include your suggestions, so that the file
will be saved by default as "setup.py" and *not* as "Setup.py"
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
Andrea Gavana wrote:
Noted that when I export setup.py I get a file with mixed line endings.
Uhm, I have never noticed it... I'll see which is the cause of it and
I'll try to fix it.
I suggest that whenever you open a file for reading, you use the 'U' (Universal) flag -- that will convert whatever the heck line endings it has into '\n'. When you write out, just use the regular native text file.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@noaa.gov