[chirp_devel] Here we go...

[Tony Fuller]

Dan,

How are you generating your python3 wheel? I'm getting an error from pip when it tries to auto generate the wheel.

Here's what I'm seeing when snapcraft tries to install CHIRP:
+ pip install -U .
...
Building wheels for collected packages: chirp, future, yattag
...
 WARNING: Built wheel for chirp is invalid: Metadata 1.2 mandates PEP 440 version, but 'daily-20221229' is not
...
Failed to build chirp
...
 DEPRECATION: chirp was installed using the legacy 'setup.py install' method, because a wheel could not be built for it. pip 23.1 will enforce this behaviour change. A possible replacement is to fix the wheel build issue reported above. Discussion can be found at https://github.com/pypa/pip/issues/8368


Tony



December 27, 2022 at 2:59 PM, "Dan Smith via chirp_devel" <chirp_devel at intrepid.danplanet.com> wrote:


> 
> Just a heads up, the master branch is now python3 (what was the py3 branch), the legacy branch is now python2 (what was the master branch). I'll be reconfiguring the build system for the -next builds to use master going forward. No turning back now.
> 
> I'm also planning to rebase this on master and apply soon:
> 
> https://github.com/kk7ds/chirp/pull/310
> 
> Dropping more py2 tox targets, gtk, etc stuff from -next. I need to do that at least a couple days before I announce to users so we can make sure that doesn't break any build stuff (although I think it's okay).
> 
> --Dan
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20221229/0421f774/attachment-0001.html