To be clear, and repeat what's been said many, many times --
"unstable" in this context means "the API might change a bit in future
releases", not "the library has bugs that will make it crash".
Indeed. In fact, at this point I would say that overall 2.9 is less buggy
than 2.8.
If anybody has ideas for better terminology to use rather than
stable/unstable that doesn't imply that one series is better than the other,
then please suggest it. There have been a couple suggestions already but
none have really grabbed my attention yet.
How about something like:
Static (fixed API, only getting bug fixes)
vs.
Dynamic (possibly changeable API, new features, etc.)
I think those two terms give a better immediate indication of the
status of the version with no baggage about bugginess or instability.
I don't know if those were among the earlier choices.
My $0.02.
Cheers,
Scott.
···
On Thu, Dec 13, 2012 at 6:09 PM, Robin Dunn <robin@alldunn.com> wrote:
On 12/13/12 8:40 AM, Chris Barker - NOAA Federal wrote:
How about:
Ironclad v Unfettered
Foss(il) v Evo(lution)
···
On 13/12/12 23:24, grunculus wrote:
Hi Robin and All,
On Thu, Dec 13, 2012 at 6:09 PM, Robin Dunn <robin@alldunn.com> wrote:
On 12/13/12 8:40 AM, Chris Barker - NOAA Federal wrote:
[...]
To be clear, and repeat what's been said many, many times --
"unstable" in this context means "the API might change a bit in future
releases", not "the library has bugs that will make it crash".
Indeed. In fact, at this point I would say that overall 2.9 is less buggy
than 2.8.
If anybody has ideas for better terminology to use rather than
stable/unstable that doesn't imply that one series is better than the other,
then please suggest it. There have been a couple suggestions already but
none have really grabbed my attention yet.
How about something like:
Static (fixed API, only getting bug fixes)
vs.
Dynamic (possibly changeable API, new features, etc.)
I think those two terms give a better immediate indication of the
status of the version with no baggage about bugginess or instability.
I don't know if those were among the earlier choices.
I think we are chasing shadows here. One person’s “stable” is another person’s “unstable”. In other words we are talking software here and it does not really matter how you label something because it is ultimately an arbitrary choice. You simply can’t please everybody, so I recommend we keep it as it is and hope that the passage of time will make it obvious to all.
One last point: a “stable” version of anything is probably only one use-case away from becoming unstable
Those names are accurate, but unfortunately they are already commonly used in programming circles to mean how an executable is linked, among other things. So it could lead to confusion about how wxPython is built, for example whether wxWidgets is statically or dynamically linked to the wxPython extension modules, or whether the wxPython extension modules are statically linked with a Python executable or are dynamically loaded like usual.
···
On 12/13/12 3:24 PM, grunculus wrote:
Hi Robin and All,
On Thu, Dec 13, 2012 at 6:09 PM, Robin Dunn <robin@alldunn.com> wrote:
On 12/13/12 8:40 AM, Chris Barker - NOAA Federal wrote:
[...]
To be clear, and repeat what's been said many, many times --
"unstable" in this context means "the API might change a bit in future
releases", not "the library has bugs that will make it crash".
Indeed. In fact, at this point I would say that overall 2.9 is less buggy
than 2.8.
If anybody has ideas for better terminology to use rather than
stable/unstable that doesn't imply that one series is better than the other,
then please suggest it. There have been a couple suggestions already but
none have really grabbed my attention yet.
How about something like:
Static (fixed API, only getting bug fixes)
vs.
Dynamic (possibly changeable API, new features, etc.)
I think those two terms give a better immediate indication of the
status of the version with no baggage about bugginess or instability.
Hi to all. My name is Demir Ajvazi. I want to learn programming in Python, but I can't find any good book for beginners. Can someone help me? If someone has such kind of books, please send me. Thank you in advance! Demir Ajvazi.
On Friday, December 14, 2012 9:49:45 AM UTC-8, Robin Dunn wrote:
On 12/13/12 3:24 PM, grunculus wrote:
Hi Robin and All,
On Thu, Dec 13, 2012 at 6:09 PM, Robin Dunn ro...@alldunn.com wrote:
On 12/13/12 8:40 AM, Chris Barker - NOAA Federal wrote:
[…]
To be clear, and repeat what’s been said many, many times –
“unstable” in this context means "the API might change a bit in future
releases", not “the library has bugs that will make it crash”.
Indeed. In fact, at this point I would say that overall 2.9 is less buggy
than 2.8.
If anybody has ideas for better terminology to use rather than
stable/unstable that doesn’t imply that one series is better than the other,
then please suggest it. There have been a couple suggestions already but
none have really grabbed my attention yet.
How about something like:
Static (fixed API, only getting bug fixes)
vs.
Dynamic (possibly changeable API, new features, etc.)
I think those two terms give a better immediate indication of the
status of the version with no baggage about bugginess or instability.
Those names are accurate, but unfortunately they are already commonly
used in programming circles to mean how an executable is linked, among
other things. So it could lead to confusion about how wxPython is
built, for example whether wxWidgets is statically or dynamically linked
to the wxPython extension modules, or whether the wxPython extension
modules are statically linked with a Python executable or are
dynamically loaded like usual.
Hi to all. My name is Demir Ajvazi. I want to learn programming in
Python, but I can't find any good book for beginners. Can someone help
me? If someone has such kind of books, please send me. Thank you in
advance! Demir Ajvazi.
Hi to all. My name is Demir Ajvazi. I want to learn programming in Python, but I can't find any good book for beginners.
1) it's a good idea to learn the basics of python before diving into
wx--which it sounds like you want to do-- good plan?
Are you new to programming or just to python?
If new to programming , I suggest:
"Thinking in python"
"learn python the hard way"
And maybe
"core python programming"
If you have a background in other languages:
Core python programming
Dive into python( this one is a bit out of date, and some are critical
of it, but give it a try and see what you think)
"learning python" was good back in the day, but I don't know if it's
been updated recently.
- Chris
···
On Dec 14, 2012, at 1:20 PM, Demir Ajvazi <demir.beocin@gmail.com> wrote:
Can someone help me? If someone has such kind of books, please send me. Thank you in advance! Demir Ajvazi.
--
To unsubscribe, send email to wxPython-users+unsubscribe@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en
Thank you very much.
With best regards
Demir Ajvazi
···
----- Original Message ----- From: "Robin Dunn" <robin@alldunn.com>
To: <wxpython-users@googlegroups.com>
Sent: Saturday, December 15, 2012 4:10 AM
Subject: Re: [wxPython-users] Learning Python
On 12/14/12 1:05 PM, Demir Ajvazi wrote:
Hi to all. My name is Demir Ajvazi. I want to learn programming in
Python, but I can't find any good book for beginners. Can someone help
me? If someone has such kind of books, please send me. Thank you in
advance! Demir Ajvazi.
