run time error anlysis of python source code
To All, It appears that one possibility of investigation into the development of a safety-critical variant of the python language would be to conduct run time error analysis of the source code that is responsible for producing the python language. Therefore, I will now conduct these run time error analysis of the python source code as if the python environment itself was to be utilized as a FADEC controller within an aircraft engine. I have already conducted some analysis already and it appears to be some concern with memory management within Python. I will redouble my efforts and determine if I am correct and as a promise. I will give my findings to everyone to enjoy if they so want it. I will also give the correct source if anyone would want it for their own purposes. The source code that I will be evaluating is the one responsible for the newer variants of Python 3.0. I believe that I will name this new variant of the python language as Apocalypse Python !! I will also develop a web-page for the development and evolution of Apocalypse Python. If anyone has any questions, please let me know !!! Thank You, David Blubaugh
omega_force2003@yahoo.com wrote:
It appears that one possibility of investigation into the development of a safety-critical variant of the python language would be to conduct run time error analysis of the source code that is responsible for producing the python language. Therefore, I will now conduct these run time error analysis of the python source code as if the python environment itself was to be utilized as a FADEC controller within an aircraft engine. I have already conducted some analysis already and it appears to be some concern with memory management within Python. I will redouble my efforts and determine if I am correct and as a promise. I will give my findings to everyone to enjoy if they so want it. I will also give the correct source if anyone would want it for their own purposes. The source code that I will be evaluating is the one responsible for the newer variants of Python 3.0.
I hope you mean 3.1 ;-) 3.0 was basically a trial version of Py3.
Hi David, <omega_force2003@yahoo.com> wrote:
It appears that one possibility of investigation into the development of a safety-critical variant of the python language
There is some interesting work related to a safety-critical variant of Python.
would be to conduct run time error analysis of the source code that is responsible for producing the python language.
There's been some effort into this too, and the Coverity and Klocwork based fixes could also be of interest to you.
Therefore, I will now conduct these run time error analysis of the python source code as if the python environment itself was to be utilized as a FADEC controller within an aircraft engine.
Nice, what tools do you have available for this? Any papers that would be a good start on the topic?
I have already conducted some analysis already and it appears to be some concern with memory management within Python. I will redouble my efforts and determine if I am correct and as a promise. I will give my findings to everyone to enjoy if they so want it. I will also give the correct source if anyone would want it for their own purposes. The source code that I will be evaluating is the one responsible for the newer variants of Python 3.0.
You want the py3k branch. BTW, take a look at Brett Cannon's work on Python security, as well as tav's.
I believe that I will name this new variant of the python language as
Apocalypse Python !!
Oh. Apocalypse Python !!, you say? Maybe something that conveys a security message or anything that doesn't relate to the end of the world could work better.
I will also develop a web-page for the development and evolution of Apocalypse Python.
Ah. Hm. David? Don't. I mean, read the mailing lists, take a look at open bug reports, read the community blogs. You'll get to know how things flow, you'll figure a nice way to relate your ideas to what people are discussing and past experiences. Make small contributions that bring us closer to... Apocalypse Python !!, then you'll have an easier time to push the idea of going the whole way towards it. Or just do it, dunno, if it makes you feel better go for it, we all have our own issues. That's why we have an issue tracker, it's soooo nice, wanna see it???
If anyone has any questions, please let me know !!!
OK, I promise. Daniel
On Sun, Jun 21, 2009 at 5:05 PM, Daniel Diniz<ajaksu@gmail.com> wrote:
Hi David,
<omega_force2003@yahoo.com> wrote:
It appears that one possibility of investigation into the development of a safety-critical variant of the python language
There is some interesting work related to a safety-critical variant of Python.
would be to conduct run time error analysis of the source code that is responsible for producing the python language.
There's been some effort into this too, and the Coverity and Klocwork based fixes could also be of interest to you.
Therefore, I will now conduct these run time error analysis of the python source code as if the python environment itself was to be utilized as a FADEC controller within an aircraft engine.
Nice, what tools do you have available for this? Any papers that would be a good start on the topic?
I have already conducted some analysis already and it appears to be some concern with memory management within Python. I will redouble my efforts and determine if I am correct and as a promise. I will give my findings to everyone to enjoy if they so want it. I will also give the correct source if anyone would want it for their own purposes. The source code that I will be evaluating is the one responsible for the newer variants of Python 3.0.
You want the py3k branch. BTW, take a look at Brett Cannon's work on Python security, as well as tav's.
Is py3k branch even passing all tests on all buildbots all the time? I don't think svn head is the right thing to look at. Also, it's worth noting that most big libraries are 2.x compatible only.
Maciej Fijalkowski <fijall <at> gmail.com> writes:
Is py3k branch even passing all tests on all buildbots all the time?
As much as other branches do (that is, not much, due to the flakiness of some of the tests and the lack of buildbot maintenance).
I don't think svn head is the right thing to look at. Also, it's worth noting that most big libraries are 2.x compatible only.
For projects difficult enough that they won't be finished before a couple of years, I think it makes sense to target 3.x. Big libraries will hopefully migrate gradually. SQLAlchemy recently announced that their current development version is 100% py3k-compatible (http://www.sqlalchemy.org/news.html#item_1).
Daniel Diniz wrote:
Apocalypse Python !!, you say? Maybe something that conveys a security message or anything that doesn't relate to the end of the world could work better.
I guess the idea is meant to be that it's safe enough to use for something that would result in the end of the world if it failed !! Although personally, if something might cause the end of the world if it failed, I'd prefer not to attempt it in the first place !! -- Apocalypse Python !! - If you ever need to use it, you're in deep trouble... !! Greg !!
participants (6)
-
Antoine Pitrou -
Daniel Diniz -
Greg Ewing -
Maciej Fijalkowski -
omega_force2003＠yahoo.com -
Terry Reedy