tag:blogger.com,1999:blog-7888156866269720289.post4082502529043386160..comments2023-11-05T11:15:45.570+01:00Comments on Linux, Games, Programming, and some other random stuff: kdev-python: GHNS support for documentation datascummoshttp://www.blogger.com/profile/12133795109922287229noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7888156866269720289.post-79543467541735149322021-11-27T08:26:07.242+01:002021-11-27T08:26:07.242+01:00az 104 exam questions
scrum master exam questions
...<a href="https://k21academy.com/microsoft-azure/az-104/interview-questions-for-azure-admin/" rel="nofollow">az 104 exam questions</a><br /><a href="https://k21academy.com/scrum-master/scrum-master-certification-exam-questions-answers/" rel="nofollow">scrum master exam questions</a><br /><a href="https://k21academy.com/microsoft-azure/dp-900/azure-data-fundamentals-exam-questions/" rel="nofollow">dp 900 exam questions</a><br />pragyanhttps://www.blogger.com/profile/05518178967609801062noreply@blogger.comtag:blogger.com,1999:blog-7888156866269720289.post-8539386274361574852013-03-18T13:50:47.718+01:002013-03-18T13:50:47.718+01:00This is about all sorts of data used by kdev-pytho...This is about all sorts of data used by kdev-python, such as docstrings, but also "which attributes does this class have", or "how many arguments does this function take".<br /><br />Usually, this information is extracted from your python code automatically by kdev-python. However there's two reasons why you might still want this:<br />1) You're using a python module which is written in C, and only exists as a .so file on your hard disks. Well-known examples for this include numpy, or the built-in sys. In this case, the static language analyzer of kdev-python can't do anything, since it can only analyze python code. Here what you can do is run my introspect script on the module, to generate "pseudo"-python files from the binary module (using the run-time information python gives you when you import the module). Those files will not contain the actual code for the module, but only declarations such as def fft(in: cvec): return cvec(). You can then place those files into a special directory, and kdev-python will read them when you use the module in your code.<br />2) The second case occurs when you have something difficult in your (or a library's code) which kdev-python's analyzer can't figure out. An example for this is modifying the __builtin__ dict in a loop, adding functions. In such a case, you don't want to modify the real python file (since it's what's going to be used by your program), but you could copy that file to said special directoy, and modify it there (and for example list all the functions added in the loop explicitly). That way you'll get good support for the module in kdevelop, but you'll not have to touch your program at all.<br /><br />You could do all this before manually, but this change proivdes you with an easy-to-use UI to automate most things, and also with the GHNS widget to e.g. share an adjusted version of one of django's modules which has been modified slightly to be better understood by kdev-python's analyzer.<br /><br />Greetings,<br />Svenscummoshttps://www.blogger.com/profile/12133795109922287229noreply@blogger.comtag:blogger.com,1999:blog-7888156866269720289.post-53826087020881044252013-03-18T13:37:33.426+01:002013-03-18T13:37:33.426+01:00I'm sorry but I am not clear what this is for....I'm sorry but I am not clear what this is for. What sort of documentation are you referring to? Is this supposed to be just docstrings, or the same sort of data used by something like, say, Sphinx, or some subset/superset of this, or something entirely different? Is this something that has to be distributed by GHNS or can it also be parsed out of the files themselves?toddrme2178https://www.blogger.com/profile/03684472911091668339noreply@blogger.com