Ben Finney [EMAIL PROTECTED] wrote:
I hereby recommend “pish and tosh” for use by anyone who wants to
counter someone's point. It beats by a country furlong the invective
that has become regrettably common here in recent months.
I second the motion to use pish and tosh for a first level of
2008/12/5 Hendrik van Rooyen [EMAIL PROTECTED]:
I second the motion to use pish and tosh for a first level of disagreement.
I recommend the rather archaic Balderdash as the next step in the
escalation of disagreement...
http://bash.org/?23396
--
Dotan Cohen
http://what-is-what.com
On Dec 5, 12:29 pm, Hendrik van Rooyen [EMAIL PROTECTED] wrote:
Ben Finney [EMAIL PROTECTED] wrote:
I hereby recommend “pish and tosh” for use by anyone who wants to
counter someone's point. It beats by a country furlong the invective
that has become regrettably common here in recent months.
Mensanator wrote:
On Dec 5, 12:29 pm, Hendrik van Rooyen [EMAIL PROTECTED] wrote:
Ben Finney [EMAIL PROTECTED] wrote:
I hereby recommend “pish and tosh” for use by anyone who wants to
counter someone's point. It beats by a country furlong the invective
that has become regrettably common here
On Fri, 05 Dec 2008 12:16:47 -0800, Fernando H. Sanches wrote:
I agree that the tab/space thing should be changed. Would it be too hard
to make the parser see if the indentation is consistent in the whole
file?
*Something* has changed. I had a piece of code where, without realizing
it, I had
Andreas Waldenburger:
Whenever has it been a pythonic ideal to not allow stuff? You get
warnings. Everything else is up to you.
It's a strong source for bugs, especially for newbies, that I have
hoped to see removed from Python3 (my first request of this was years
ago). I was nearly sure to see
On Thu, 4 Dec 2008 15:49:46 -0600 [EMAIL PROTECTED] wrote:
Andreas Whenever has it been a pythonic ideal to not allow
Andreas stuff? You get warnings. Everything else is up to you.
It's more than warnings. With properly crafted combinations of
spaces and tabs you can get code
Andreas Waldenburger:
My point is: If you mix tabs and spaces in a way that breaks code,
you'll find out pretty easily, because your program will not work.
- Most newbies don't know that.
- Sometimes it may produce wrong results.
- And even if you are an expert when you go changing a little a
On Fri, 5 Dec 2008 07:46:02 -0800 (PST) [EMAIL PROTECTED] wrote:
Andreas Waldenburger:
My point is: If you mix tabs and spaces in a way that breaks code,
you'll find out pretty easily, because your program will not work.
- Most newbies don't know that.
- Sometimes it may produce wrong
On Thu, 4 Dec 2008 15:49:46 -0600, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
It's more than warnings. With properly crafted
combinations of spaces and tabs you can get code which
looks like it has a certain indentation to the human
observer but which looks like it has different indentation
[EMAIL PROTECTED] wrote:
Andreas Waldenburger:
Whenever has it been a pythonic ideal to not allow stuff? You get
warnings. Everything else is up to you.
It's a strong source for bugs, especially for newbies, that I have
hoped to see removed from Python3 (my first request of this was years
On Dec 4, 5:45 pm, Andreas Waldenburger [EMAIL PROTECTED] wrote:
On Thu, 4 Dec 2008 11:52:38 -0600 [EMAIL PROTECTED] wrote:
As you have probably guessed: nothing changed here.
Also see:http://www.python.org/dev/peps/pep-0666/
What? Do you mean it's possible to mix tabs
On Fri, 5 Dec 2008 12:16:47 -0800 (PST) Fernando H. Sanches
[EMAIL PROTECTED] wrote:
On Dec 4, 5:45 pm, Andreas Waldenburger [EMAIL PROTECTED] wrote:
On Thu, 4 Dec 2008 11:52:38 -0600 [EMAIL PROTECTED] wrote:
[snip]
Whenever has it been a pythonic ideal to not allow stuff? You get
On Fri, 05 Dec 2008 07:09:27 -0800, bearophileHUGS wrote:
Andreas Waldenburger:
Whenever has it been a pythonic ideal to not allow stuff? You get
warnings. Everything else is up to you.
It's a strong source for bugs, especially for newbies, that I have hoped
to see removed from Python3 (my
On Fri, 05 Dec 2008 22:01:55 +, je.s.te.r wrote:
Fernando H. Sanches [EMAIL PROTECTED] wrote:
And I personally disliked most of the changes (specially the ones on
map and reduce). I hope functional programming doesn't get even more
hindered in future releases, because I believe these
In article [EMAIL PROTECTED],
Ben Finney [EMAIL PROTECTED] wrote:
James Stroud [EMAIL PROTECTED] writes:
comp.lang.python3k ?
The language has undergone an incompatible divide. Hopefully the
community need not do the same.
Pish and tosh. James was clearly making a funny; there's not *that*
[EMAIL PROTECTED] (Aahz) writes:
In article [EMAIL PROTECTED],
Ben Finney [EMAIL PROTECTED] wrote:
James Stroud [EMAIL PROTECTED] writes:
comp.lang.python3k ?
The language has undergone an incompatible divide. Hopefully the
community need not do the same.
Pish and tosh. James was
Steven D'Aprano:
I think you're talking about mixed spaces/tabs in the one module.
Right.
My gut feeling is that you have to have a fairly unusual set of circumstances
before it causes actual bugs.
I don't mix tab and spaces in my code, and my editor is able to
convert them, so after the
On Dec 4, 1:51 am, Barry Warsaw [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Python 3.0 (a.k.a. Python 3000 or Py3k) represents a major
Iain King wrote:
[...] Props. I just looked through the What's New and the change log, but I
couldn't find the answer to something: has any change been made to
how tabs and spaces are used as indentation? Can they still be
(inadvisably) mixed in one file? Or, more extremely, has one or the
Hello,
On Thu, Dec 4, 2008 at 1:51 AM, Barry Warsaw [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
We will continue to
support and develop both Python 3 and Python 2 for the foreseeable future,
and you can safely choose either version (or both) to use in your projects.
Which
Congratulations on a fantastic work!
--
http://mail.python.org/mailman/listinfo/python-list
Hi,
This is great, however, the link to the What's New page appears to be
broken.
http://docs.python.org/dev/3.0/whatsnew/3.1.html
RHH
On Thu, Dec 4, 2008 at 8:37 AM, Istvan Albert [EMAIL PROTECTED]wrote:
Congratulations on a fantastic work!
--
Hi
On Thu, Dec 4, 2008 at 1:54 PM, Roy H. Han
[EMAIL PROTECTED] wrote:
Hi,
This is great, however, the link to the What's New page appears to be
broken.
http://docs.python.org/dev/3.0/whatsnew/3.1.html
replace 3.1 with 3.0 :), so it has to be:
On Dec 3, 7:51 pm, Barry Warsaw [EMAIL PROTECTED] wrote:
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Way to go and congratulations!
--greg
--
http://mail.python.org/mailman/listinfo/python-list
Barry Warsaw [EMAIL PROTECTED] writes:
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Yay!
Thanks for all the great work.
--
http://mail.python.org/mailman/listinfo/python-list
Gerhard Häring:
As you have probably guessed: nothing changed here.
Also see:http://www.python.org/dev/peps/pep-0666/
What? Do you mean it's possible to mix tabs and spaces still? Why?
Bye,
bearophile
--
http://mail.python.org/mailman/listinfo/python-list
As you have probably guessed: nothing changed here.
Also see:http://www.python.org/dev/peps/pep-0666/
What? Do you mean it's possible to mix tabs and spaces still? Why?
Why not?
Cheers,
Daniel
--
Psss, psss, put it down! - http://www.cafepress.com/putitdown
--
As you have probably guessed: nothing changed here.
Also see:http://www.python.org/dev/peps/pep-0666/
What? Do you mean it's possible to mix tabs and spaces still? Why?
Daniel Why not?
Because it has historically been a source of errors in a mixed development
On Thu, 4 Dec 2008 09:30:52 -0800 Daniel Fetchinson
[EMAIL PROTECTED] wrote:
As you have probably guessed: nothing changed here.
Also see:http://www.python.org/dev/peps/pep-0666/
What? Do you mean it's possible to mix tabs and spaces still? Why?
Why not?
+1
--
My real email
On Thu, 4 Dec 2008 11:52:38 -0600 [EMAIL PROTECTED] wrote:
As you have probably guessed: nothing changed here.
Also see:http://www.python.org/dev/peps/pep-0666/
What? Do you mean it's possible to mix tabs and spaces still?
Why?
Daniel Why not?
Because it
Andreas Whenever has it been a pythonic ideal to not allow stuff? You
Andreas get warnings. Everything else is up to you.
It's more than warnings. With properly crafted combinations of spaces and
tabs you can get code which looks like it has a certain indentation to the
human observer
On Dec 4, 4:49 pm, [EMAIL PROTECTED] wrote:
Andreas Whenever has it been a pythonic ideal to not allow stuff? You
Andreas get warnings. Everything else is up to you.
It's more than warnings. With properly crafted combinations of spaces and
tabs you can get code which looks like it
I would like to ask, how long will Python 2 be developed? Just for curiosity.
There won't be a 2.10 release of Python. Whether that means that 2.9
will be the last one, or whether development stops earlier, remains to
be seen.
Regards,
Martin
--
Hi,
Congratulations to the Python 3.0 team!! Great! I was able to
download the Python 3.0
documentation. Looks good. Any hints when the Mac OSX version of
Python 3.0 will
be available?
Cheers, Roger.
--
http://mail.python.org/mailman/listinfo/python-list
Barry Warsaw wrote:
On behalf of the Python development team and the Python community, I am
happy to announce the release of Python 3.0 final.
comp.lang.python3k ?
--
http://mail.python.org/mailman/listinfo/python-list
James Stroud [EMAIL PROTECTED] writes:
comp.lang.python3k ?
The language has undergone an incompatible divide. Hopefully the
community need not do the same.
--
\ “People come up to me and say, ‘Emo, do people really come up |
`\to you?’”
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Python 3.0 (a.k.a. Python 3000 or Py3k) represents a major
milestone in Python's history, and was nearly three years in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Python 3.0 (a.k.a. Python 3000 or Py3k) represents a major
milestone in Python's history, and was nearly three years in
On Dec 4, 11:51 am, Barry Warsaw [EMAIL PROTECTED] wrote:
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Thanks to you and everyone involved for your efforts!
--
http://mail.python.org/mailman/listinfo/python-list
2008/12/4 Barry Warsaw [EMAIL PROTECTED]:
On behalf of the Python development team and the Python community, I am
happy to announce the release of Python 3.0 final.
Congratulations!
I have been learning Python 2.x while paying strict attention to the
3.x [in]compatibility issue. So, I have
On this page:
http://www.python.org/download/releases/3.0/
The text This is a proeuction release should probably read This is
a production release. It would give a better first impression :)
--
Dotan Cohen
http://what-is-what.com
http://gibberish.co.il
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 3, 2008, at 9:13 PM, Dotan Cohen wrote:
On this page:
http://www.python.org/download/releases/3.0/
The text This is a proeuction release should probably read This is
a production release. It would give a better first impression :)
Fixed,
On Thu, Dec 4, 2008 at 11:58 AM, alex23 [EMAIL PROTECTED] wrote:
On Dec 4, 11:51 am, Barry Warsaw [EMAIL PROTECTED] wrote:
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Thanks to you and everyone involved for your
On Dec 3, 2008, at 7:51 PM, Barry Warsaw wrote:
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Props to all the folks whose hard work made this possible! You guys
rock!
-- Ed Leafe
--
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Python 3.0 (a.k.a. Python 3000 or Py3k) represents a major
milestone in Python's history, and was nearly three years in the
making. This is a new version of the
On Wed, Dec 3, 2008 at 7:47 PM, Daniel Fetchinson
[EMAIL PROTECTED] wrote:
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Python 3.0 (a.k.a. Python 3000 or Py3k) represents a major
milestone in Python's history, and
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Python 3.0 (a.k.a. Python 3000 or Py3k) represents a major
milestone in Python's history, and was nearly three years in the
making. This is a new version of the
On Dec 3, 7:51 pm, Barry Warsaw [EMAIL PROTECTED] wrote:
On behalf of the Python development team and the Python community, I
am happy to announce the release of Python 3.0 final.
Congratulations! This is a great day for the Python community.
Carl Banks
--
thankers.append(self)
--
http://mail.python.org/mailman/listinfo/python-list
Carl Banks [EMAIL PROTECTED] writes:
On Dec 3, 7:51 pm, Barry Warsaw [EMAIL PROTECTED] wrote:
On behalf of the Python development team and the Python community,
I am happy to announce the release of Python 3.0 final.
Congratulations! This is a great day for the Python community.
I'm
51 matches
Mail list logo
