Python currently supports lots of different code pages and other more specific codecs. I was wondering what your thoughts on this are: should we proceed to include an even wider range of codecs or limit the available number to an absolute minimum ? I'm asking this, because Tamito KAJIYAMA wrote a set of codecs for EUC-JP and Shift_JIS which would probably be very useful for Japanese Python users -- I just don't know how many there are and whether inclusion of an extra 650k of source code would hurt or not. Thoughts ? -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
On Fri, Jun 09, 2000 at 01:03:56PM +0200, M.-A. Lemburg wrote:
I'm asking this, because Tamito KAJIYAMA wrote a set of codecs for EUC-JP and Shift_JIS which would probably be very useful for Japanese Python users -- I just don't know how many there are and whether inclusion of an extra 650k of source code would hurt or not.
This seems too much code added that would only be of use to a limited audience, so -1 from me. Japanese packagers of Python would probably include them, of course. -- A.M. Kuchling http://starship.python.net/crew/amk/ I confidently expect it to be a fairly resounding failure. -- John Cleese, on the Monty Python reunion planned for 1999
"Andrew M. Kuchling" wrote:
On Fri, Jun 09, 2000 at 01:03:56PM +0200, M.-A. Lemburg wrote:
I'm asking this, because Tamito KAJIYAMA wrote a set of codecs for EUC-JP and Shift_JIS which would probably be very useful for Japanese Python users -- I just don't know how many there are and whether inclusion of an extra 650k of source code would hurt or not.
This seems too much code added that would only be of use to a limited audience, so -1 from me. Japanese packagers of Python would probably include them, of course.
I just wish that these packagers actually become a reality some day... the concept is good, but there currently seem to be no volunteers or companies jumping in :-( -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
"DA" == David Ascher <DavidA@ActiveState.com> writes:
I just wish that these packagers actually become a reality some day... the concept is good, but there currently seem to be no volunteers or companies jumping in :-(
DA> I can't speak for Japanese packagers, but ActiveState will be DA> packaging Python in various ways. BeOpen also has packaging plans :-). Jeremy
Jeremy Hylton wrote:
"DA" == David Ascher <DavidA@ActiveState.com> writes:
I just wish that these packagers actually become a reality some day... the concept is good, but there currently seem to be no volunteers or companies jumping in :-(
DA> I can't speak for Japanese packagers, but ActiveState will be DA> packaging Python in various ways.
BeOpen also has packaging plans :-).
Sounds cool. I just hope that someone will hint me of the first Python IPO *before* it hits NASDAQ ;-) -- Marc-Andre Lemburg ______________________________________________________________________ Business: http://www.lemburg.com/ Python Pages: http://www.lemburg.com/python/
On Fri, 9 Jun 2000, Fredrik Lundh wrote:
I can't speak for Japanese packagers, but ActiveState will be packaging Python in various ways.
BeOpen also has packaging plans :-).
get in line, guys ;-)
I wonder if next we'll see threads on slashdot about "PythonOne is just trying to get on the Python hype. It has nothing to offer except for a trivial installer anyone can write in 5 minutes in Python" (cf: the LinuxOne fiasco) -- Moshe Zadka <moshez@math.huji.ac.il> http://www.oreilly.com/news/prescod_0300.html http://www.linux.org.il -- we put the penguin in .com
participants (6)
-
Andrew M. Kuchling -
David Ascher -
Fredrik Lundh -
Jeremy Hylton -
M.-A. Lemburg -
Moshe Zadka