# New Features in 3.6.3

**URL:** <https://www.ruby-forum.com/t/new-features-in-3-6-3/229337>\
**Category:** GNU Radio\
**Created:** [January 5, 2013, 12:53am UTC](https://www.ruby-forum.com/t/new-features-in-3-6-3/229337 "2013-01-05T00:53:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![roytruelove](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@roytruelove](https://www.ruby-forum.com/u/roytruelove)\
**Post date:** [January 5, 2013, 12:53am UTC](https://www.ruby-forum.com/t/new-features-in-3-6-3/229337/1 "2013-01-05T00:53:10Z")

</div>

I am starting to play around with 3.6.3rc0 a little bit. I’m excited  
about the new message passing infrastructure and the Python-based  
signal processing blocks. In fact, I would really like to be able to  
create Python-based blocks that use the new message infrastructure.  
However, as best I can tell this is not currently possible since the  
message\_port\_xxx functions are not being exposed to Python. Is that  
accurate? If so, are there any plans to marry them together in the  
future?

Thanks,  
Roy

---

<div class="post-metadata">

**Author:** ![roytruelove](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@roytruelove](https://www.ruby-forum.com/u/roytruelove)\
**Post date:** [January 13, 2013, 5:33pm UTC](https://www.ruby-forum.com/t/new-features-in-3-6-3/229337/2 "2013-01-13T17:33:48Z")

</div>

On Fri, Jan 4, 2013 at 6:52 PM, Roy T. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Roy

That shouldn’t be impossible to support. In general, I’m not a huge fan  
of  
using the Python blocks for efficiency reasons. I always look at them as  
a  
way to prototype an new block or algorithm before converting it into  
C++.  
But I know some people like to use them as framers or frame/packet  
oriented  
workers.

I’ve added this as Issue #508.

Thanks,  
Tom

---

<div class="post-metadata">

**Author:** ![roytruelove](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@roytruelove](https://www.ruby-forum.com/u/roytruelove)\
**Post date:** [January 14, 2013, 12:30am UTC](https://www.ruby-forum.com/t/new-features-in-3-6-3/229337/3 "2013-01-14T00:30:16Z")

</div>

Thanks, I was able to make the modifications to get it working without  
too much trouble. The only thing that was a little tricky was  
registering the messaging handling callback function. I am doing most  
signal processing with C++ blocks but using Python for custom GUI and  
higher layer protocols so it is useful that they can communicate with  
the rest of the blocks via the messaging infrastructure.

Thanks,  
Roy

---

<div class="post-metadata">

**Author:** ![roytruelove](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/3ab097/32.png) [@roytruelove](https://www.ruby-forum.com/u/roytruelove)\
**Post date:** [January 14, 2013, 11:12pm UTC](https://www.ruby-forum.com/t/new-features-in-3-6-3/229337/4 "2013-01-14T23:12:37Z")

</div>

On Sun, Jan 13, 2013 at 6:28 PM, Roy T. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> Thanks, I was able to make the modifications to get it working without  
> too much trouble. The only thing that was a little tricky was  
> registering the messaging handling callback function. I am doing most  
> signal processing with C++ blocks but using Python for custom GUI and  
> higher layer protocols so it is useful that they can communicate with  
> the rest of the blocks via the messaging infrastructure.
> 
> Thanks,  
> Roy

Hey Roy, that’s great!

Any chance you could respond to the Issue I created on the wiki page  
with a  
patch so we could put this into the main code?

Thanks!  
Tom