The Quick Answer: For the most accurrate time elapsed, use the time module and make 2 time.time() objects.  The difference between these objects is the time elapsed. Do not use time.clock().

The Whole Story

Its pretty basic: I have certain parts of a large python script (that happen to access a MySQL database) that I would like to keep track of how long it took them to execute.

Wrong Answers

Initially, I read on a PLEAC-Python article, Dates and Times (which really is a great overview of Python’s time module), about some ways to use Python’s time module.  That article suggests that all you need to do is:

#-----------------------------
# High Resolution Timers

t1 = time.clock()
# Do Stuff Here
t2 = time.clock()
print t2 - t1

# 2.27236813618
# Accuracy will depend on platform and OS,
# but time.clock() uses the most accurate timer it can

For one of my projects, that worked fine. But then I had a bigger script that used a lot of MySQL via the Python module MySQLdb, and I would look at my script’s run time after leaving, and the times looked short… but not too short. Eventually after running a script that took a 7 hour sleep and then some to run — but the script reported only taking an hour or so — I knew something was wrong.

Only timing the work of Python?

It seemed as if using the time.clock() approach was only timing what Python (as opposed to MySQL?) was doing.  I created this test script

import time

yearstart = time.clock()
print yearstart

for x in range(0, 1000000):
    z = x + 6

yearend = time.clock()
print yearend
elapsed= yearend-yearstart
min = elapsed/60

print elapsed, min

And I didn’t find a problem, but my script still did. I was wanting to time an event of a known length, and so I found out about the time.sleep() function from the aforementioned article. I incorporated the sleep() function:

import time

yearstart = time.clock()
print yearstart

time.sleep(3)

yearend = time.clock()
print yearend
elapsed= yearend-yearstart
min = elapsed/60

print elapsed, min

and ran the script. You would expect to see 3 seconds as a result, or at least something close, but my output was:

0.03
0.03
0.0 0.0

That was funny (although I didn’t laugh) because yearend was not supposed to sample the clock() until after the sleep. I still don’t know why this does this, but it does. I am sure this has its uses, but this was not the use I was wanting.

Use time.time()

Still referencing the PLEAC-Python article, I tried using time.time(), which is supposed to just be the seconds since that day in 1970 and compared it to the time.clock() approach:

import time

yearstart = time.clock()
print yearstart

time.sleep(3)

yearend = time.clock()
print yearend
elapsed= yearend-yearstart
min = elapsed/60

print elapsed, min

yearstart = time.time()
print yearstart

time.sleep(3)

yearend = time.time()
print yearend

elapsed= yearend-yearstart

min = elapsed/60

print elapsed, min

And got the output:

0.03
0.03
0.0 0.0
1211338788.69
1211338791.69
3.00004386902 0.0500007311503

No Fluff Answer:

Read nothing else (on this page). This code will get you going:

import time

start = time.time()

# whatever you want to time, put between these two statements

end = time.time()

elapsed= end - start

#if you want to convert to minutes, just divide
min = elapsed/60

print "Your stuff took", elapsed, "seconds to run, which is the same as", min, "minutes"

So, this works for me.  I supose that time.clock() does not reference absolute time, which was a problem for me. Hope this helps, or at least saves you some head-scratching.

Solution: Not exactly sure, but it seems to have stopped.

There are several WordPress posts that go over an issue of using the

[/sourcecode]

tag to write sourcecode.

Personally, I was very frustrated because while writing in Python, where whitespace matters, my indents would all be lost when switching between the visual and HTML editor in WordPress.

My solution was to wrap my

[sourcecode]

tags in <pre> tags.

Check the plugin?

I originally was using the

[/sourcecode]

tag from <a href="http://code.google.com/p/syntaxhighlighter/">SyntaxHighlighter</a>, then found another one, called SyntaxHilighter Plus.

I don't have time to go over all of this, but I disabled the Plus version, re-enabled the regular SyntaxHighlighter, and made sure to wrap my

[sourcecode]

s in <pre> tags.

Quick Answer: When you want a page break, switch to HTML/Code view and then type <!–nextpage–>.

Whole Story

As simple as this sounds, it took me 20 minutes to get this to work.  My problem was that I thought the usage was like other plugin quicktags, where you can just put it in anywhere.  But if you put in <!–nextpage–> while using the “Visual” or WYSIWYG editor, it will change your greater than and less than sign into the html entities.

The problem with having to switch to the HTML or code view is that I have to scroll down and find where my spot was in the article (if I am putting in page breaks after publishing).  It would be great if WordPress had a button on the writing toolbar, like the “More” tag, that would insert page breaks without having to switch to HTML or Code view, or worrying about whether you are in the right view or not.

This took me so much longer than it should have that this qualifies as a “computer problem that got in my way”.

Quick Answer (for managed attributes only):

class dumb:
    def dummy():
        pass

def attributes(o):
    print "object:", o
    print "Initialized attribute values:"
    step=0
    for var in dir(o):
        vartype=-1
        exec("vartype = type(o."+str(var)+")")
        if not(var in o.__dict__) and not(vartype == type( dumb.dummy)) and not("__" == var[:2]):
            value = -30
            exec("value = o."+str(dir(o)[step]))
            print '%40s' % var  +": "+ str(value)
        step += 1

The whole story

Either I am just really new to python (I am) or it is just really hard when you have an object and you just want to get the public attributes.

The code above uses the dir() function to get everything from the object.  Besides both public and private attributes, this also gets user defined and inherited methods.  Then, i crop out those that are not public attributes.

Code Walkthrough (Get managed attributes only)

Managed attributes are those that are defined in an object’s definition.  Here is an example:

class Widget(object):
    """The Widget represents an object of work.  it can be processed by a worker. it is assigned to a worker by an organization."""
        self.__id=id
        self.test=35

    ### MANAGED ATTRIBUTES ###

    #id
    def id():
        """id is readonly"""
            return self.__id
        return locals()
    id = property(**id())
    #END id

    ### END MANAGED ATTRIBUTES ###

    def spoil_step(self):
        """Increases the steps that this widget has been spoiling"""
        old = self.__time_spoiling
        self.__time_spoiling += 1
        #check for sure
        if old + 1 == self.__time_spoiling:
            return self.__time_spoiling
        else:
            return False

    ####END Widget OBJECT ####

The Following list references the code at the top of the page

1. I created a dumb object with a dummy function.  This will be used to identify “instance methods”. The pass instruction is just a filler.

   class dumb:
       def dummy():
           pass
   
   

2. I created a function that takes an object, o, as input.  It then just prints out the object and lets the user know that it is about to go through it:

   def attributes(o):
       print "object:", o
       print "Initialized attribute values:"
   
   

3. I created a variable to keep track of which thing we are looking at, starting at the 0-index:

        step=0
   
   

4. Then I go through each member of the object:

        for var in dir(o):
   
   

5. I then create a variable, and assign the type of the object to this variable:

             vartype=-1
             exec("vartype = type(o."+str(var)+")")
   
   

6. Next comes the key conditional statement:

             if not(var in o.__dict__) and not(vartype == type( dumb.dummy)) and not("__" == var[:2]):
   
   

   The first part says exclude if you find it in o.__dict__, which contains the private attributes from the __init__() function. The second part excludes things that are of the same type as an instance method; so this gets rid of the object’s methods. The last part looks at the first to characters of the thing, and if it is equal to __, it is excluded.

7. Within the conditional, we just name and value of that thing, which should be only managed attributes:

                  value = -30
                  exec("value = o."+str(dir(o)[step]))
                  print '%40s' % var  +": "+ str(value)
   
   

The next page goes over how to get both the managed and public (not just the managed) attributes from an object

What I wanted was for a user to put in http://www.olddomain.com/a_file.html and be redirected to http://newdomain.com/a_file.html. I wanted it to do that for each file, and I didn’t want to specify a redirect for each file. I didn’t want to use mod_rewrite because I wanted to give the 301 redirect for Search Engine Optimization (SEO) reasons.

Quick Answer: use RedirectMatch permanent ^(.*)$ http://www.newdomain.com$1 in a .htaccess file in your old domain.

Initially, I read that this line

RedirectMatch permanent ^(.*)$ http://www.newdomain.com

would redirect all files from the old domain to files on the new domain of the same name when placed in the .htaccess file in the /www/ directory of the old domain. However, when I tried this, all of my redirects simply redirected to the index file of the new domain. For example,

http://www.olddomain.com/file_a.html

http://www.olddomain.com/file_b.html

would both redirect to

http://www.newdomain.com/index.html

Then I modified the apache directive to

RedirectMatch permanent ^(.*)$ http://www.newdomain.com$1

and this worked for me. Even when I put in a bad filename, I got my new domain’s 404 error document.

Not sure why I found RedirectMatch permanent ^(.*)$ http://www.newdomain.com in several sources and it didn’t work…

Quick Solution: Use Disk Utility to Restore your old drive to your new drive, then tell Time Machine that you want to use a different disk

The Whole Story

When I got the 1TB drive, it was formatted as FAT32. I had been using Time Machine (I am running Mac OS 10.5.2) and I wanted to use my new drive for Time Machine, but I wanted to keep my current Time Machine history. My vision was to have the exact same data, but now my external drive can hold more. I ran into a few issues while trying to do this, so here is how I solved them.

Note: The sections “Formatting the new hard drive”, “Transfer the files”, and “Transfer Problems” narrate the problems I had while trying to just copy files… see the following section, “Use Disk Utility Instead”, for enumerated instructions on how I actually solved the problem.

Formatting the new hard drive

When I first plugged in the drive, Leopard recognized it. I thought that I might just be able to dump the files from my old external hard drive (formatted in HFS+) onto the new one (FAT32). When I selected the files to move and dragged them to the new folder, I heard the “pang” sound that Finder makes when you copy files, but nothing actually happened.

Since I will only use this new drive on a Mac, I thought maybe I should reformat to HFS+ (I also thought that Time Machine might require it). Using Disk Utility, I ran into a few vague errors and the disk would never be successfully formatted. I found the solution on the Apple Discussion Forums .

This basically says that you must select the highest parent of the drive you want to format

and select the “Partition” page.

Then go to “Options…” and select the top option: “GUID”.

The formatting should only take a few seconds.

The next page goes over transferring your files.

The quick answer: export your data and reinstall WordPress.

The whole story:

So I used the cPanel interface of the web hoster and created a subdomain, blog, and set the document root to /www/blog/. When I would try to pull up www.blog.thewebsite.com , the browser would just redirect to www.thewebsite.com/, and no blog would appear.

I was going to go through all of the things that I did to try to hack-up WordPress so that I would not have to reinstall, but then I realized that none of that actually worked. I could get far enough that the page would show up and about half of the links would work, but there ended up being an issue with the permalinks.

What I had to do was use the Manage->Export feature of the WordPress admin area to save my categories, posts, etc. Then, to uninstall WordPress, I deleted all of the tables in my WordPress database, then ran the install.php script again. I probably could have kept the users table, and perhaps a few other tables with the plugin settings, but I didn’t. So I had to reactivate my plugins and all of the other options that I had changed from the default values.

If you have a better fix for this, please leave a comment!