[gps-users] Has anyone run into a problem with pep8 dependency causing a big failure in GPS?

[Micahwelf Waddoups]

Thank you for your help, I managed to get everything working again by
stripping every environment variable except the GUI and critical path
elements, destroying the hidden user directory .gps,  and using a fresh
/opt/gps2016 instalation. Now I am starting to use my own little compiled
Ada program to automatically set up the environment I need to maintain this
arrangement. Apparently, I didn't notice the early bits of dysfunction in
time to know exactly what was wrong until a cascade of problems collapsed
on me.  Thank you all for your support. I may finally get some of my mini
projects completed enough to share on github: micahwelf

On Nov 14, 2016 01:41, "Emmanuel Briot" <briot at adacore.com> wrote:

> > Since pep8 has been renamed to pycodestyle (for valid, but not critical
> reasons), I have not been able to run GPS and get any of my word and study
> in Ada done in my machine. I am considering doing a backward hack, building
> a private directory where I can build python with pep8 and everything GPS
> expects, then mount-binding both the development work directories and the
> important system directories so that GPS will run.  Or just run a virtual
> machine, but that is slower and requires special considerations for
> maintenance and accessing the file-system...  Right now these seem my only
> fast solutions I see to running the older versions and the current version
> of GPS (GPL), but future versions should should be adapted to work with the
> new python modules or remove the dependency on pep8 all together.  Anyhow,
> I am very eager to see GPL working again.
>
>
> Hello,
>
> We are not aware of such an issue. On the other hand, GPS GPL comes with
> its own python
> installation, so removing pep8 in your system's python should have no
> impact unless you also
> modify GPS's own python install ... which we don't recommend.
>
> Most likely you can simply disable the pep8_integration plugin for now
> (via the /Tools menu in
> GPL 2016), and that should be it. That plug-in will eventually need to be
> adapted or removed
> when we change the version of python.
>
> I did not follow python development, but I am surprised they would be
> removing pep8 from
> python2. Are you trying to use python3 ? (in which case I certainly except
> much more failures
> than just pep8 indeed)
>
> regards
> Emmanuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/gps-users/attachments/20161114/3e43b7c8/attachment.html>