views:

1371

answers:

5

I would like to emulate the pass-by-value behaviour in python. In other words, I would like to make absolutely sure that the function I write do not modify user supplied data.

One possible way is to use deep copy:

from copy import deepcopy
def f(data):
    data = deepcopy(data)
    #do stuff

is there more efficient or more pythonic way to achieve this goal, making as few assumptions as possible about the object being passed (such as .clone() method)

Edit

I'm aware that technically everything in python is passed by value. I was interested in emulating the behaviour, i.e. making sure I don't mess with the data that was passed to the function. I guess the most general way is to clone the object in question either with its own clone mechanism or with deepcopy.

+1  A: 

I can't figure out any other pythonic option. But personally I'd prefer the more OO way.

class TheData(object):
  def clone(self):  """return the cloned"""

def f(data):
  #do stuff

def caller():
  d = TheData()
  f(d.clone())
Sake
Thank you. However, clone implies a customized and maybe more efficient way to do deep copy. I personally saw libraries where the cloned objects were not as deep as one expected :) . Not to mention classes with no clone method at all. So, basically deepcopy is more portable.
bgbg
(see my clarification to the question)
bgbg
deepcopy is simply another way to clone the data. The real point in my code is that "inside the caller" is indeed the better place to decide on how to pass the argument, not inside the function
Sake
Also deepcopy is absolutely not "more efficient". When the decision to clone the data is within the caller where you know exactly the kind of data you are passing, then you can use the most efficient method to do that; (like list[:], dict(dic)).. If you are not really sure what data will be passed, then keeping the decision for efficient-cloning-method to the data object itself will always yield better performance.
Sake
+10  A: 

You can make a decorator and put the cloning behaviour in that.

>>> def passbyval(func):
def new(*args):
 cargs = [deepcopy(arg) for arg in args]
 return func(*cargs)
return new

>>> @passbyval
def myfunc(a):
    print a

>>> myfunc(20)
20

This is not the most robust way, and doesn't handle key-value arguments or class methods (lack of self argument), but you get the picture.

Note that the following statements are equal:

@somedecorator
def func1(): pass
# ... same as ...
def func2(): pass
func2 = somedecorator(func2)

You could even have the decorator take some kind of function that does the cloning and thus allowing the user of the decorator to decide the cloning strategy. In that case the decorator is probably best implemented as a class with __call__ overridden.

Skurmedel
I think a decorator is a really elegant approach to solving this problem. I'm sure you could come up with something that could cope with keyword args too without much trouble.
jkp
Yep, it's more or less a matter of giving the new method a **kwargs argument too, and copying them.
Skurmedel
+4  A: 

There is no pythonic way of doing this.

Python provides very few facilities for enforcing things such as private or read-only data. The pythonic philosophy is that "we're all consenting adults": in this case this means that "the function shouldn't change the data" is part of the spec but not enforced in the code.


If you want to make a copy of the data, the closest you can get is your solution. But copy.deepcopy, besides being inefficient, also has caveats such as:

Because deep copy copies everything it may copy too much, e.g., administrative data structures that should be shared even between copies.

[...]

This module does not copy types like module, method, stack trace, stack frame, file, socket, window, array, or any similar types.

So i'd only recommend it if you know that you're dealing with built-in Python types or your own objects (where you can customize copying behavior by defining the __copy__ / __deepcopy__ special methods, there's no need to define your own clone() method).

dF
A: 

usually when passing data to an external API, you can assure the integrity of your data by passing it as an immutable object, for example wrap your data into a tuple. This cannot be modified, if that is what you tried to prevent by your code.

Tom
+1  A: 

Though i'm sure there's no really pythonic way to do this, i expect the pickle module will give you copies of everything you have any business treating as a value.

import pickle

def f(data):
    data = pickle.loads(pickle.dumps((data)))
    #do stuff
TokenMacGuy