Skip to content

Unsaved file objects may not have an associated URL. #3074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 24, 2015

Conversation

tomchristie
Copy link
Member

If a file object is unsaved it may not have an associated URL.
If we're using FileField(use_url=True) in that case then return None for the field representation.

Superseeds #2759.

@tomchristie tomchristie added this to the 3.1.4 Release milestone Jun 24, 2015
tomchristie added a commit that referenced this pull request Jun 24, 2015
…ize_to_none

Unsaved file objects may not have an associated URL.
@tomchristie tomchristie merged commit cd0c9b7 into master Jun 24, 2015
@tomchristie tomchristie deleted the unsaved_file_objects_serialize_to_none branch June 24, 2015 13:33
@tomchristie tomchristie modified the milestones: 3.1.4 Release, 3.2.0 Release Jul 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant