[kdev-python] [Bug 373640] kdev-python continues to parse after "Stop All" and even "Close Project"

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=373640

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 373640] kdev-python continues to parse after "Stop All" and even "Close Project"

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=373640

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 373640] kdev-python continues to parse after "Stop All" and even "Close Project"

[Justin Zobel]

https://bugs.kde.org/show_bug.cgi?id=373640

Justin Zobel  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #3 from Justin Zobel  ---
Thank you for reporting this bug in KDE software. As it has been a while since
this issue was reported, can we please ask you to see if you can reproduce the
issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when
replying. Thank you!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 373640] kdev-python continues to parse after "Stop All" and even "Close Project"

[Sven Brauch]

https://bugs.kde.org/show_bug.cgi?id=373640

Sven Brauch  changed:

   What|Removed |Added

   Priority|NOR |LO

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 373640] kdev-python continues to parse after "Stop All" and even "Close Project"

[RJVB]

https://bugs.kde.org/show_bug.cgi?id=373640

--- Comment #2 from RJVB  ---
If jobs show up under the "Stop" button, they should react to the "Stop All"
button to, as far as I'm concerned. And as far as I can tell, C (C++ etc)
parsing jobs do this.

I've never tried closing a C++ project as a last resort to stopping the parser
because I never had to, but I would expect that the clang plugin doesn't keep
on parsing a project that's no longer part of the session.

Why would I try stopping the parser? When it eats unwarranted CPU cycles and
spews tons of output to the calling terminal. Kdev-python is very good at that
2nd thing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdev-python] [Bug 373640] kdev-python continues to parse after "Stop All" and even "Close Project"

[Francis Herne]

https://bugs.kde.org/show_bug.cgi?id=373640

Francis Herne  changed:

   What|Removed |Added

 CC||m...@flherne.uk

--- Comment #1 from Francis Herne  ---
AFAIK, "Stop All" isn't intended to have that effect - it stops
build/debug/exec/test jobs of the project that are launched from KDevelop, not
internal parsing.

Parsing data and jobs belong to the session, not the project - you might notice
that when creating a new session kdev-python has to start parsing
/usr/lib/python3.?/ from scratch.

Why are you trying to do this at all?

-- 
You are receiving this mail because:
You are watching all bug changes.