This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description


django-cloneable provides a CloneableMixin class that has a clone() method. It can be mixed into any Django model.

The clone() method must be called on an already saved instance (one that has pk set). It then returns a new instance of the model that has all the same field values as the original instance, but it will be a seperate database row with a distinct primary key.

An example:

from django.db import models
from django_cloneable import CloneableMixin

class Ingredient(CloneableMixin, models.Model):
    name = models.CharField(max_length=50)
    is_spicy = models.BooleanField(default=False)

class Pizza(CloneableMixin, models.Model):
    name = models.CharField(max_length=50)
    price = models.IntegerField()
    ingredients = models.ManyToManyField(Ingredient)

tomatos = Ingredient.objects.create(name='Tomato', is_spicy=False)
cheese = Ingredient.objects.create(name='Cheese', is_spicy=False)
chili = Ingredient.objects.create(name='Chili', is_spicy=True)

margarita = Pizza.objects.create(name='Margarita')

diabolo = margarita.clone(attrs={'name': 'Diabolo'})

# Nothing has changed on the original instance.
assert == 'Margarita'
assert margarita.ingredients.all() == [tomatos, cheese]

# The original m2m values were copied, and the new values were added.
assert == 'Diabolo'
assert diabolo.ingredients.all() == [tomatos, cheese, chili]

As shown in the example, you can provide the attrs that shall be replaced in the cloned object. That lets you change the cloned instance before it gets saved. By default the clone will be saved to the database, so that it has pk when it gets returned.

There are numerous hooks on how you can modify the cloning logic. The best way to learn about them is to have a look at the implementation of CloneableMixin.


Install the dependencies (including the test dependencies) with:

pip install -r requirements.txt

Then you can run all tests with:




  • Initial release.
Release History

Release History


This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
django-cloneable-0.1.0.tar.gz (7.0 kB) Copy SHA256 Checksum SHA256 Source Apr 5, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting