>>>>> "Cedric" == Cedric Gustin <[EMAIL PROTECTED]> writes:
Cedric> Actually, I was thinking about simply replacing the
Cedric> current pygtk-2.2.0.win32-py2.3.exe by
Cedric> pygtk-2.2.0-numpy.win32-py2.3.exe, implicitly adding
Cedric> Numeric support from now on. I guess it is better than
Cedric> providing two separate binaries. And I don't think it will
Cedric> break anything for pygtk users who did not install
Cedric> Numeric.
Cedric> What do you think ? Or maybe I should wait for pygtk-2.2.1
Cedric> and provide pygtk-2.2.0-numpy.win32-py2.3.exe in the
Cedric> meantime ? I could also change the version tag to 2.2.0.1
Cedric> but I think it can be misleading.
My policy is to never release 2 different packages under the same
name, no matter how tempting, because it makes it harder down to road
and someone has problems and you say, "what version are you using".
Eg, if they installed the original pygtk-2.2.0.win32-py2.3.exe and get
an error about no Numeric support, it's easier if you can say install
version so an so. I think 2.2.0.1 is sufficiently clear.
JDH
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
