[Django]-Django RelatedManager's .create() usage?

I don’t see how is your first example supposed to be a bug? This behavior is completely intuitive. Your p is a play with an id of 2383, and you’re calling the create method on its related set. You’re also specifying an extra field, called player_id, and giving it a value of 2383. It’s only logical that both play id will be 2383 (because that’s the id of the play containing this related set) and that player id will also be 2383 (because you explicitly passed that value in).

Your second example would seem to indicate a bug, but I cannot reproduce it. Here are my models:

class Player(models.Model):
    name = models.CharField(max_length=100)

class Play(models.Model):
    title = models.CharField(max_length=100)

class PlayParticipant(models.Model):
    player = models.ForeignKey('Player')
    play = models.ForeignKey('Play')
    note = models.CharField(max_length=100, blank=True)

Here’s the shell output:

>>> player1 = Player.objects.create()
>>> player2 = Player.objects.create()
>>> player1.id
2
>>> player2.id
3
>>> play1 = Play.objects.create()
>>> play2 = Play.objects.create()
>>> play1.id
3
>>> play2.id
4
>>> pp1 = play1.playparticipant_set.create(player_id=2)
>>> pp1.play.id
3
>>> pp1.player.id
2

In any case, why are you posting this to SO? Django has a bugtracker, a couple of active official mailing lists and a couple of IRC channels.