fixtures

One of the things that bugs me about Django fixtures is that you've got to specify every model's primary key. Is there any way to create fixtures without having to specify a primary key for each row? Use "pk: null" instead of "pk: 1" (or whatever), which will result in the PK being set to None, and when the object is saved a primary key will be assigned. This works for YAML at least, I'm guessing you're using that if you are creating by hand. You should have a look at Natural Keys if you're wiling to add relation without using pk's https://docs.djangoproject.com/en/dev/ref/django-admin/

This question already has an answer here: Generating natural schedule for a sports league 2 answers I would like to write a League Fixture generator in python, but I can't. Here is the details: There is a dynamic list of teams like teams = ["Team1", "Team2", "Team3", "Team4"] . How can I generate a fixture_weekx list from the teams list? For example: fixture_week1 = ["Team1", "Team2", "Team3", "Team4"] fixture_week2 = ["Team1", "Team3", "Team2", "Team4"] fixture_week2 = ["Team1", "Team4", "Team2", "Team3"] #Return matches: fixture_week1 = ["Team2", "Team1", "Team4", "Team3"] fixture_week2 = [

I'm working with a Rails 2.2 project working to update it. I'm replacing existing fixtures with factories (using factory_girl) and have had some issues. The problem is with models that represent tables with lookup data. When I create a Cart with two products that have the same product type, each created product is re-creating the same product type. This errors from a unique validation on the ProductType model. Problem Demonstration This is from a unit test where I create a Cart and put it together in pieces. I had to do this to get around the problem. This still demonstrates the problem though

Say I have a User model with the following code in User.rb: before_create :create_dependencies after_create :build_inbox And I also have a users.yml file with a bunch of user fixtures defined in it. When I run rake db:fixtures:load, it doesn't appear to trigger the callbacks. Is this how it is expected to work? If so, why did they design it this way? Is there a way to force the triggering of the callbacks when loading fixtures? Is this how it is expected to work? If so, why did they design it this way? Yes, fixtures do not use callbacks. I'm assuming this is for performance reasons. It is

I am using py.test to test some DLL code wrapped in a python class MyTester. For validating purpose I need to log some test data during the tests and do more processing afterwards. As I have many test_... files I want to reuse the tester object creation (instance of MyTester) for most of my tests. As the tester object is the one which got the references to the DLL's variables and functions I need to pass a list of the DLL's variables to the tester object for each of the test files (variables to be logged are the same for a test_... file). The content of the list is shall be used to log the