{"id":91,"date":"2016-06-08T15:31:40","date_gmt":"2016-06-08T19:31:40","guid":{"rendered":"http:\/\/williamkennerly.com\/blog\/?p=91"},"modified":"2016-06-17T16:07:32","modified_gmt":"2016-06-17T20:07:32","slug":"python-single-point-geometry-energy-script-update","status":"publish","type":"post","link":"http:\/\/williamkennerly.com\/blog\/python-single-point-geometry-energy-script-update\/","title":{"rendered":"Python Single-Point Geometry Energy Script Update"},"content":{"rendered":"

Continued from a previous post<\/a>.<\/p>\n

As I created my first completed version of the python script, I learned several things about python.<\/p>\n

One thing I learned was how file handles work. With the function:<\/p>\n

def find_parameters(file_handle):
\n    for l in file_handle:
\n         if l.startswith(\" #\"):
\n             return l.rstrip()<\/code><\/p>\n

I was running into an error in which I received the message, Nonetype has no attribute…, meaning that my code was trying to use nothing as its input for functions that were looking for strings. That was after I looped through the file handle for a find function. I learned that looping through a file handle leaves the “cursor” at the end of the file handle, so that the very next use\u00a0of the file handle would start at the end of the file handle. To reset the “cursor” at the beginning of the file handle, I need to call file_handle.seek(0)<\/code> after each iteration, as follows:<\/p>\n

def find_parameters(file_handle):
\n    file_handle.seek(0)
\n    for l in file_handle:
\n         if l.startswith(\" #\"):
\n             return l.rstrip()<\/code><\/p>\n

Here is a Stack Overflow thread<\/a> with an explanation.<\/p>\n

Another thing I learned had to do with the difference between the .append()<\/code> and .extend()<\/code> functions. After some searching and consultation with Prof. Kennerly, I realized that that was because I called .extend()<\/code> rather than .append()<\/code>. I was trying to add a string as an item to an empty list, and the .extend()<\/code> function treated the string itself as some sort of list. Using the .append()<\/code> function instead kept the string as a string and simply added it as a value to the list. Here is a Stack Overflow thread<\/a> with more discussion of the difference between .append()<\/code> and .extend()<\/code>.<\/p>\n

One more error that I do not understand but have since overcome has to do with Unicode. I had an interesting hour or so in which I got long text files of Sanskrit and other unexpected languages instead of my output data, when I opened my results text file in Wordpad. Other text editors, such as Microsoft Word, had no trouble reading the text files. I think that this error had something to do with the .extend()<\/code> function, but I’m not sure. I recall that the error went away after I corrected my code to use .append()<\/code> instead of .extend()<\/code>, but that may not have been the direct source of the error. Further investigation of the Unicode issue is needed for a better understanding of it.<\/p>\n

Often error messages may not describe the cause of the problem, but give clues of where the problem is. That is why many different error messages popped up when I had a more fundamental issue somewhere else in the script. In addition, as Prof. Kennerly says, computers always do what you tell them. So, the Sanskrit output made sense, given the code I wrote. To fix problems with the script, I needed more understanding of what certain functions did and how python and Wordpad read files.<\/p>\n

I used IDLE on a Windows computer to edit and run my script.<\/p>\n

P.S. WordPress is not good at allowing indentations or extra spaces. I have to use a keyword &+nbsp; (without the +) to create spaces in the text editor, and all instances of it disappear if I switch to the visual editor. I think this is an issue with HTML, and I read that I would have to use CSS to allow indents in WordPress. This is an annoying problem, and I am trying to get around it for future posts where I show snippets of code.<\/p>\n","protected":false},"excerpt":{"rendered":"

Continued from a previous post. As I created my first completed version of the python script, I learned several things about python. One thing I learned was how file handles work. With the function: def find_parameters(file_handle):     for l in file_handle: … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[14],"class_list":["post-91","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-python"],"_links":{"self":[{"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/posts\/91","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/comments?post=91"}],"version-history":[{"count":8,"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/posts\/91\/revisions"}],"predecessor-version":[{"id":112,"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/posts\/91\/revisions\/112"}],"wp:attachment":[{"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/media?parent=91"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/categories?post=91"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/williamkennerly.com\/blog\/wp-json\/wp\/v2\/tags?post=91"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}