openplotter-pypilot 3.x.x beta released

[Sailoog]

Hello Sailoog!

I still don't see a way to install pypilot in the "latest" version of Openplotter that is available on the link.

Am I that stupid, or is there something wrong with the Openplotter Headless, still after all the complaints and "fixes"?

Thanks for reply,

Gennady

In OpenPlotter 3 just click "Get candidates" in settings app, then select pypilot and click install:

https://openplotter.readthedocs.io/en/3....candidates

[Gennady]

It is my intention that pypilot only access serial ports assigned to it.  
I made a small update to https://github.com/pypilot/openplotter-pypilot just now, and hopefully it will fix.

I see you made many changes...     I will try to merge.

Hi,

Can you inform us how to install a file from github?

And which version of Openplotter has a possibility of installing the pypilot in it?

Thanks,

Gennady

---

Hello Sailoog!

I still don't see a way to install pypilot in the "latest" version of Openplotter that is available on the link.

Am I that stupid, or is there something wrong with the Openplotter Headless, still after all the complaints and "fixes"?

Thanks for reply,

Gennady

In OpenPlotter 3 just click "Get candidates" in settings app, then select pypilot and click install:

https://openplotter.readthedocs.io/en/3....candidates

Hi Sailoog! Thank you! It actually worked for me! Now I can open pypilot straight from Openplotter.

Thank you again,

Gennady

[Sailoog]

Hi,

Can you inform us how to install a file from github?

And which version of Openplotter has a possibility of installing the pypilot in it?

Thanks,

Gennady

Every time you re-install openplotter-pypilot app, the last stable pypilot version is installed even if there is no new version of openplotter-pypilot. We should wait for Sean news to test these fixes.

[seandepagnier]

I am trying a bit harder now to make only essential bug fixes to the master branch. My ongoing work is in an unstable branch which is likely to throw exceptions.

[Sailoog]

OK, let me know when changes are in master branch and I will publish a new openplotter-pypilot version to force a pypilot update.

[ironman]

I ran the whole procedure from scratch this week and it resulted in Pypilot 3.2.4 app with pypilot 0.35 in it. No comments from me anymore, very happy with it.

I am trying a bit harder now to make only essential bug fixes to the master branch.   My ongoing work is in an unstable branch which is likely to throw exceptions.

Can we then speak of pypilot releases? Maybe number each of these master commits with a new (major, minor) version number? Some release notes for each master commit would then also be handy? Or tagging those releases with a github tag, so it's be easier to revert back to a certain commit?

OK, let me know when changes are in master branch and I will publish a new openplotter-pypilot version to force a pypilot update.

Please only do this after the master commit has been tested. I'd be happy to be a tester!

[Sailoog]

OK, let me know when changes are in master branch and I will publish a new openplotter-pypilot version to force a pypilot update.

Please only do this after the master commit has been tested. I'd be happy to be a tester!

Thanks for testing and reporting.

Once the changes has been committed to the master branch in pypilot, they will be available for fresh installations and re-installations of openplotter-pypilot app, so testing has to be done in the dev branch before merging in master.

[ironman]

Ok I understand. Would you consider a fork of the master to update the openplotter pypilot from?

[Sailoog]

That is how openplotter-pypilot worked in OP 2 and it turned out a not very agile way. I have a better idea, I can add a "hidden" setting in /home/pi/.openplotter/openplotter.conf to set the pypilot branch target. If this setting does not exists or it is "master", the stable branch will be compiled when reinstalling. If this setting is for example "dev", "beta" or whatever, that branch will be compiled.

[seandepagnier]

I am trying hard to keep master branch stable for now though.. Only adding bugfixes. I will merge unstable changes in only after extensive testing. I hope this is good enough.