M
Michael Torrie
Very easy to explain: wrong, incorrect, naive unicode
handling.
You should get together with ranging rick so that his python fork can
have unicode done properly then.
Very easy to explain: wrong, incorrect, naive unicode
handling.
Thanks to everyone for all the posts, some friendly some not. I read
all of them with genuine interest.
On 02/23/2013 10:44 AM, jmfauth wrote:
[snip various stupidities]
Peter, jmfauth is one of our resident trolls. Feel free to ignore him.
Error codes under DEC VAX/VMS used odd integers for
"success/information" and even integers for "warning/error" (been too
many years, I think positive integers were success/warning, negative
integers were information/error; I could also be wrong on which set were
even... if 0 were no-info/success then odd were errors and even were
success)).
"end of result set", which isn't exactly an error but you can't fetch0 for warning (or in some cases "status" - an SQLCODE of 100 means
Pardon, but was that deliberate -> FAIL
On 02/23/2013 10:44 AM, jmfauth wrote:
[snip various stupidities]
Peter, jmfauth is one of our resident trolls. Feel free to ignore him.
Sorry, what can say?
More memory and slow down!
If you see a progress, I'm seeing a regression.
I'm using Rapid GUI Programming with Python & Qt (Mark Summerfield ISBN
978-0-13-235418-9) - it fits for me because I needed something that
covered GUI development but also had an intro to the language. The
first 3 chapters are a Python intro at a sensible level for experienced
coders (none of this 'here is the keyboard, there is the screen'
nonsense) so it is enough to get you going with Python. The rest is
about Qt/PyQt, taught via manageable examples and giving a fairly well
thought out dialogue (monologue?) of what each line/function does. It
was useful enough for me to want to carry the hardback version with me
on my 'commute' from the UK to Nigeria where I am currently working.
I've also got two books by Wesley Chun, (Core Python Programming & Core
Python Applications Programming) on my Kindle . I can't give you a
sensible verdict on those two because, while I've finally settled to
reading fiction on the Kindle, I still like to have a real book when it
comes to reference works (on any subject) so they haven't had the usage
that Summerfield has.
Oh, and you're never too old for anything but most things take longer -
gives you more time to enjoy them ;-)
Sounds like IBM DB2 and sqlca.sqlcode - 0 for success, <0 for error,
"end of result set", which isn't exactly an error but you can't fetch
any more from it; it's akin to Python raising StopIteration to
terminate a for loop).
When you learn your first language, you think you're learning to
program, but that's not really accurate. Once you've learned half a
dozen, you begin to understand something of the art of coding as
distinct from any particular language; after that, you can learn any
language fairly easily.
Chris, you are (almost) spot on with the if blocks indentation. This
is what I do, and it has served me well for 15 years.
Very easy to explain: wrong, incorrect, naive unicode
handling.
All apps that return an error code to the operating system return 0 for
success, any other value for error. All command-line utilities work
this way, all shells, etc. Even Windows command-line apps work this way
(errorlevel is what they call it).
On 02/23/2013 10:44 AM, jmfauth wrote:
[snip various stupidities]
jmf
Peter, jmfauth is one of our resident trolls. Feel free to ignore him.
Sorry, what can say?
More memory and slow down!
If you see a progress, I'm seeing a regression.
Potted summary for those who aren't familiar with jmf's trolling:
Python 3.2 had a major bug in its Unicode handling, meaning that
non-BMP characters were mis-handled. Python 3.3 fixes these AND
improves performance on the whole. The complaints are about *very*
specific use-cases, and the overall string-handling benchmarks have
dramatically improved; but more importantly, the bug is fixed.
There, now you too can killfile him without loss.
ChrisA
....although some C functions return a negative error code because aYep, the 0 = success part is pretty much universal (it's been said
that the cause of the downfall of the Roman empire was that, lacking
zero, they were unable to succeed at anything), but the notion of
negative for errors and positive for warnings isn't as clear;
errorlevels and Unix return codes are positive-only.
Yes, it's true that I am trying to write C# code in Python. It is not
going to change any time soon, if at all - I have done too much
C#ing, C++ing before that and C-ing earlier still.
You see, Javascript, for one, behaves the same way as Python (no variable
declaration) but JS has curly braces and you know the variable you have
just used is limited in scope to the code within the { }. With Python, you
have to search the whole file.
Hi all,No biggie. This is easily simulated with:... I have discovered today there is no do...while type loop. [Sigh]
while True:
...
if <exit condition>:
break
Less easily simulated is the lack of a switch/case structure. This has
to be done with a less convenient extended if/elif/.../else structure.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.