[Discuss-gnuradio] DMARC related changes starting this week for FSF hosted Mailman lists

2019-06-17 Thread Ian Kelling
Over the next few days, the Free Software Foundation will be making changes to our GNU Mailman systems, including lists.gnu.org, lists.nongnu.org, lists.libreplanet.org, lists.fsf.org, and lists.endsoftwarepatents.org, in order to address mailing list deliverability issues reported by many users.

Re: [Discuss-gnuradio] [EXT] Re: Python3 or still Python 2.7?

2019-06-17 Thread Marc Kaufman
I suppose Windows will always be a poor relation. The current version of MSVC is "19". It's a real pain to downgrade the build environment. Marc On 6/17/2019 10:32 AM, Geof Nieboer wrote: All, Once 3.8 is ready, I'll first release a version that is built on 2.7, primarily because that's what

Re: [Discuss-gnuradio] [EXT] Re: Python3 or still Python 2.7?

2019-06-17 Thread Marc Kaufman
I suppose Windows will always be a poor relation. The current version of MSVC is "19". It's a real pain to downgrade the build environment. Marc On 6/17/2019 10:32 AM, Geof Nieboer wrote: All, Once 3.8 is ready, I'll first release a version that is built on 2.7, primarily because that's what

Re: [Discuss-gnuradio] [EXT] Re: Python3 or still Python 2.7?

2019-06-17 Thread Geof Nieboer
All, Once 3.8 is ready, I'll first release a version that is built on 2.7, primarily because that's what the scripts are built around at the moment, and to split the upgrade into two steps. That version should support those who are looking for max compatibility. Then I'll shift the scripts to

Re: [Discuss-gnuradio] [EXT] Re: Python3 or still Python 2.7?

2019-06-17 Thread Chesir, Aaron M.
Philip, Geof (et al.), When will a Windows version of GR that supports Python 3 (and complete with one-click installers, much like that advertised for Release 3.7.13.5, below) be available? The reason I prefer to operate within Windows (as opposed to the various versions of Linux) is that I

Re: [Discuss-gnuradio] Python3 or still Python 2.7?

2019-06-17 Thread Philip Balister
On 06/17/2019 10:49 AM, Chesir, Aaron M. wrote: > Will GNUradio migrate to Python3.X, or will it remain with Python 2.7? > > The reason I ask is that (for reasons that unclear), there are syntax > differences between the two, and Python 3 is *not* backward compatible for > some of them. The

[Discuss-gnuradio] Python3 or still Python 2.7?

2019-06-17 Thread Chesir, Aaron M.
Will GNUradio migrate to Python3.X, or will it remain with Python 2.7? The reason I ask is that (for reasons that unclear), there are syntax differences between the two, and Python 3 is *not* backward compatible for some of them. Aaron -Original Message- From: Discuss-gnuradio On

Re: [Discuss-gnuradio] extract value of signal

2019-06-17 Thread Kyeong Su Shin
Hello Jafar, If what you are asking for is a way to access data which are being generated (and outputted) by your pre-existing GNU Radio flowgraphs, the best way would be NOT extracting them. You can embed your own Python code to your GNU Radio flowgraph by writing Embedded Python Blocks (ex:

Re: [Discuss-gnuradio] extract value of signal

2019-06-17 Thread Sebastian Sahlin
Hi Jafar, You need to be more specific. What type of value are you talking about, frequency, phase, magnitude..? Regards Den mån 17 juni 2019 kl 12:11 skrev jafar jafari : > hi > how can i extract value of signal in gnuradio companion and use them in my > python code > >

[Discuss-gnuradio] Saving PMT messages to file.

2019-06-17 Thread SG
Hello all! I have been trying to save the messages generated after the demodulation and decode of the WiFi received signal to a file but file sink is not compatible with message types. Is there a replacement for the deprecated message sink? Could anyone point me to the right direction.

[Discuss-gnuradio] extract value of signal

2019-06-17 Thread jafar jafari
hi how can i extract value of signal in gnuradio companion and use them in my python code ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio