Weekly Edition
Return to the Development page
| |||||||||||||
Ruby 2.0.0 released
Version
2.0.0 of the Ruby language is now available. "Ruby 2.0.0 is the
first stable release of the Ruby 2.0 series, with many new features and
improvements in response to the increasingly diverse and expanding demands
for Ruby." Changes include keyword arguments, UTF-8 encoding by
default, a number of new libraries, some performance improvements, and
more. See this
article for more information about the changes in this release.
(Log in to post comments)
Ruby 2.0.0 released Posted Feb 24, 2013 15:43 UTC (Sun) by tnoo (subscriber, #20427) [Link]
After seeing in what clunky way keyword arguments are implemented I am glad we also/still have Python.
P.S. Just my first thought, I don't intend to start a language flamewar here.
Ruby 2.0.0 released Posted Feb 24, 2013 16:11 UTC (Sun) by marduk (subscriber, #3831) [Link]
I too like Python but, unless I'm missing something horribly obvious here, it doesn't appear that much different than how Python does it.. they use ":" instead of "=". The "**" syntax is identical to Python AFAICT.
Ruby 2.0.0 released Posted Feb 24, 2013 16:47 UTC (Sun) by tnoo (subscriber, #20427) [Link] Rubydef cycle(first_value, *values) options = values.extract_options! name = options.fetch(:name, 'default') Python def cycle(first_value, name=default): or alternatively def cycle(first_value, **values): name = values.get('name', 'default') Both Python versions looks much simpler to me.
Ruby 2.0.0 released Posted Feb 24, 2013 16:56 UTC (Sun) by imgx64 (guest, #78590) [Link] That's the old way of using keyword arguments. The new way, as the article points out:
Ruby 2.0.0 released Posted Feb 25, 2013 7:47 UTC (Mon) by tnoo (subscriber, #20427) [Link]
Ooops, you're correct, I read that article too hastily. In this case I'm glad to see sane syntax being used consistently.
Just curious Posted Feb 25, 2013 22:30 UTC (Mon) by man_ls (subscriber, #15091) [Link] I am glad we also/still have Python.What series, Python 2.x or Python 3.x? Speaking of which, I have heard that Ruby is even worse in that respect than Python, breaking backwards compatibility in point releases (1.7 vs 1.8). Does this Ruby 2.0 break too many things, or has sanity prevailed?
Just curious Posted Feb 25, 2013 23:04 UTC (Mon) by sml (subscriber, #75391) [Link]
I've worked quite a bit with python 2/3 and ruby 1.8/1.9 and python is certainly far worse with regards to maintaining backwards compatibility.
While there are some incompatible changes in ruby 2, the majority are added features and optimisations, and unlikely to cause major breakage.
Just curious Posted Feb 25, 2013 23:20 UTC (Mon) by cortana (subscriber, #24596) [Link]
> python is certainly far worse with regards to maintaining backwards compatibility
The language, the standard library, or third party modules?
Not that it matters if Python sucks for what you're doing--I would just like a little more detail.
Just curious Posted Feb 25, 2013 23:28 UTC (Mon) by mathstuf (subscriber, #69389) [Link]
I'd be more interested in what it takes to support all the major versions with one code base. For example, the only way to get exceptions which works from Python 2.4 (RHEL 5) to Python 3.3 (Fedora 18) is to use sys.exc_info(); "except X as e" doesn't work in 2.4 and "except X, e" is no longer accepted in 3.x. I have no real experience with Ruby to know how hard such support is in it.
I'd be happier if one of Python 2.x and 3.x just went away, but that's not going to happen any time soon and short of splitting the codebase, supporting both can be a pain. Plus, 3.3 now supports namespace modules (which is emulated by straight.plugin[1] for now), so there's another version break I have to be aware of.
Just curious Posted Feb 26, 2013 0:27 UTC (Tue) by cjwatson (subscriber, #7322) [Link]
OTOH, if you can afford not to care about pre-2.6 (Debian squeeze; Ubuntu 9.04) then supporting both 2 and 3 is rather easy in most new code provided all your library dependencies are available - you can mostly write in Python 3 style with a bit of extra boilerplate - and for old code the main difficulty is getting bytes vs. text straight which is no bad thing anyway. I've written a few thousand lines of bilingual 2/3 code in the last week alone.
Just curious Posted Feb 27, 2013 3:29 UTC (Wed) by HelloWorld (guest, #56129) [Link]
Can't you just bundle Python 3 with your application and be done with it? I find it unbearable to support a version as old as 2.4. And shame on Red Hat for not adding a Py3 package to RHEL 5.
Just curious Posted Feb 27, 2013 3:44 UTC (Wed) by mathstuf (subscriber, #69389) [Link]
The project has Python bindings, not an embedded Python, so shipping our own isn't really an option[1]. To be fair, there is a 2.6 package for RHEL5, so that is a possible path. Also, the chance of the RHEL5-targeting project using the Python support is low, but I'd rather keep compatibility incrementally than as an all-at-once change. The test suite is where most of the code which hits this problem lives, and it's nice for code that doesn't ship to raise a lower version bound on something. Doesn't make it less painful.
[1]I suppose, technically, it is, but we also try to play nice with Python world by converting between NumPy and C++ data structures instead of forcing Python to use a C-like API. Losing that by trying to get an embedded Python to work with a non-embedded Python isn't worth it (or we ship NumPy too...). Unless I've missed some docs on that...
Ruby 2.0.0 released Posted Mar 14, 2013 1:11 UTC (Thu) by Baylink (subscriber, #755) [Link]
When did languages start having *version numbers*...?
(Yes, yes; I know; it's just... it's stupid. It's a *tool*; if you rev it out from underneath people who've written scads of code, especially if you stop supporting it, you've just wasted their energy. I note that C was created in 197mumble, and has changed maybe 3 times. Nearly every line of code ever written in ANSI C will still compile.)
|
|||||||||||||