[Discuss-gnuradio] [announcement] GNU Radio pre-3.8: dependency version bump for Python3 >= 3.6.5

2019-04-21 Thread Marcus Müller
Dear GNU Radio community,

part of the process of keeping GNU Radio future-proof is deciding
minimum versions for dependencies.
One of these dependencies is Python.
As you might have noticed, GNU Radio 3.8 will support both Python2
(2.7) and Python3.
As we want to be able to use newer Python features in releases after
GNU Radio 3.8, we'll start upping our minimum version.

A operating system survey yielded that the oldest sensible Python3
version to support is 3.6.5, so we'll bump the minimum acceptable
Python3 to that version on the `master` branch in a few days.

As usual, I'm open to feedback, questions, and cake.

Best regards,
Marcus


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] gr_zeromq on MS-Windows ?

2019-04-21 Thread Geof Nieboer
I'm not at the machine at the moment, but as I recall pyzmq ends up looking
for one version and gnuradio the other, so maybe I have the name error
backwards.

Either way, I will fix it in the next release, as worst case I just
downgrade to the version of ZMQ that was bundled with 3.7.12.

Geof

On Thu, Apr 18, 2019 at 1:58 PM jmfriedt 
wrote:

> Thank you for your reply which helped me find a (temporary at least)
> solution to my problem: indeed you reminded me that we had been
> streaming data from GNU Radio to a MS-Windows computer running ZeroMQ
> on its GNU Radio flowgraph and that was working well last
> december/january. So downgrading to 3.7.12 solved my short term problem
> of getting GNU Radio+ZMQ running on MS-Windows. Unfortunately I am
> not able to identify the name mismatch you state in your email: I did
> find some name mismatch with vc140 sentences for the boost library but
> not for ZeroMQ.
>
> Thanks for the support,
> Jean-Michel
>
> > There is a problem with the latest installer related to the changes
> > in the way libzmq's build process works.
> > So the libraries are misnamed.
> > Rename the zmq library to libzmq.dll (it'll be something like
> > libzmq_v140_mt_something.dll currently) and see if that resolves the
> > issue.
> >
> > Geof
> >
> > On Wed, Apr 17, 2019 at 12:30 PM Andrej Rode  wrote:
> >
> > > Hi Jean-Michael,
> > >
> > > On Wed, 17 Apr 2019 15:34:21 +
> > > "jean-michel.fri...@femto-st.fr" 
> > > wrote:
> > > > Files\GNURadio-3.7\lib\site-packages\gnuradio\zeromq\zeromq_swig.py",
> > > > line 18, in swig_import_helper return
> > > > importlib.import_module('_zeromq_swig') File "C:\Program
> > > > Files\GNURadio-3.7\gr-python27\lib\importlib\__init__.py", line
> > > > 41, in import_module __import__(name)
> > > > ImportError: DLL load failed: Le module spÚcifiÚ est introuvable.
> > > > ^^^ French for "The specified module cannot be found"
> > >
> > > This usually indicates that `_zeromq_swig.(so|dll)` was found, but
> > > contains unresolvable dynamic linking. Maybe libzmq is missing in
> > > the library_path/dll_path.
> > >
> > > On a Linux host I'd go here: "C:\Program
> > > Files\GNURadio-3.7\lib\site-packages\gnuradio\zeromq\" and look at
> > > the `_zeromq_swig.so` with `ldd`. I don't know what the tool of
> > > choice on a Windows platform is for looking up the dynamic linking
> > > of a library, but certainly that information will help you locate
> > > the missing pieces.
> > >
> > > Cheers
> > > Andrej
> > >
> > >
> > > ___
> > > Discuss-gnuradio mailing list
> > > Discuss-gnuradio@gnu.org
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > >
>
>
>
> --
> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe,
> 25000 Besancon, France
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio