No. They're both "reserved" loop-back addresses, but 127.0.0.1 has more cultural/conventional weight for this explicit purpose and also avoids any possible semantic overloads with dotted-quad zero and/or null values.
Since I have a local web server running that will respond on 127.0.0.1 I'd just as soon avoid the overhead of the wasted hit and rendering of the local page, unless there was some notable value to using that address over all nulls.