Re: [Django] #26495: Saving StringIO using custom storage class may result in empty content written to file

2016-04-12 Thread Django
#26495: Saving StringIO using custom storage class may result in empty content written to file -+- Reporter: m-novikov|Owner: nobody Type: Uncategorized|

Re: [Django] #26495: Saving StringIO using custom storage class may result in empty content written to file (was: Storage save method wraps StringIO in File object which is identified as False.)

2016-04-12 Thread Django
#26495: Saving StringIO using custom storage class may result in empty content written to file -+- Reporter: m-novikov|Owner: nobody Type: Uncategorized|

Re: [Django] #26495: Storage save method wraps StringIO in File object which is identified as False.

2016-04-12 Thread Django
#26495: Storage save method wraps StringIO in File object which is identified as False. -+- Reporter: m-novikov|Owner: nobody Type: Uncategorized|

Re: [Django] #26495: Storage save method wraps StringIO in File object which is identified as False.

2016-04-12 Thread Django
#26495: Storage save method wraps StringIO in File object which is identified as False. -+- Reporter: m-novikov|Owner: nobody Type: Uncategorized|

Re: [Django] #17635: Missing ability to cast georaphy to geometry when using GeoDjango and PostgresSQL

2016-04-12 Thread Django
#17635: Missing ability to cast georaphy to geometry when using GeoDjango and PostgresSQL -+- Reporter: corentin.chary@… |Owner: nobody Type: New feature |

Re: [Django] #17635: Missing ability to cast georaphy to geometry when using GeoDjango and PostgresSQL

2016-04-12 Thread Django
#17635: Missing ability to cast georaphy to geometry when using GeoDjango and PostgresSQL -+- Reporter: corentin.chary@… |Owner: nobody Type: New feature |

Re: [Django] #26495: Storage save method wraps StringIO in File object which is identified as False.

2016-04-12 Thread Django
#26495: Storage save method wraps StringIO in File object which is identified as False. -+- Reporter: m-novikov|Owner: nobody Type: Uncategorized|

Re: [Django] #19567: Make javascript i18n view as CBV and more extensible.

2016-04-12 Thread Django
#19567: Make javascript i18n view as CBV and more extensible. -+- Reporter: niwi |Owner: claudep Type: New feature | Status: assigned

[Django] #26495: Storage save method wraps StringIO in File object which is identified as False.

2016-04-12 Thread Django
#26495: Storage save method wraps StringIO in File object which is identified as False. --+ Reporter: m-novikov | Owner: nobody Type: Uncategorized | Status: new Component: File

Re: [Django] #25774: Refactor of datetime expressions and better, official support for right-hand-side date part extraction

2016-04-12 Thread Django
#25774: Refactor of datetime expressions and better, official support for right- hand-side date part extraction -+- Reporter: ryuusenshi |Owner: jarshwah Type: New feature

Re: [Django] #26475: Using functools.partial in model field options causes creation of unnecessary migration on every 'makemigrations' call

2016-04-12 Thread Django
#26475: Using functools.partial in model field options causes creation of unnecessary migration on every 'makemigrations' call + Reporter: un-def |Owner: nobody Type: Bug |

Re: [Django] #26487: Use EHLO after smtplib.SMTP_SSL too.

2016-04-12 Thread Django
#26487: Use EHLO after smtplib.SMTP_SSL too. --+ Reporter: kchmiela |Owner: nobody Type: Cleanup/optimization | Status: new Component: Core (Mail)

Re: [Django] #26494: executable flags lost when using an archive as a project/app template (was: executable flags lost when using an archive as a template)

2016-04-12 Thread Django
#26494: executable flags lost when using an archive as a project/app template ---+ Reporter: misli |Owner: nobody Type: Bug| Status: new Component: Utilities |

Re: [Django] #26484: Add a helpful message in manage.py when Django cannot be imported

2016-04-12 Thread Django
#26484: Add a helpful message in manage.py when Django cannot be imported --+ Reporter: timgraham |Owner: nobody Type: Cleanup/optimization | Status: new

Re: [Django] #22936: Get rid of field.get_db_prep_lookup()

2016-04-12 Thread Django
#22936: Get rid of field.get_db_prep_lookup() -+- Reporter: akaariai |Owner: nobody Type: | Status: new Cleanup/optimization

Re: [Django] #26491: Duplicated queries with nested prefetch

2016-04-12 Thread Django
#26491: Duplicated queries with nested prefetch -+- Reporter: duduklein|Owner: nobody Type: | Status: closed Cleanup/optimization

Re: [Django] #26432: Bug: X/Y inverted when using numpy.reshape() on a GDALRaster's GDALBand

2016-04-12 Thread Django
#26432: Bug: X/Y inverted when using numpy.reshape() on a GDALRaster's GDALBand -+- Reporter: Opa- |Owner: Opa- Type: Bug | Status:

Re: [Django] #26493: Document that built-in signals use send()

2016-04-12 Thread Django
#26493: Document that built-in signals use send() --+ Reporter: marfire |Owner: nobody Type: Cleanup/optimization | Status: new Component:

Re: [Django] #17635: Missing ability to cast georaphy to geometry when using GeoDjango and PostgresSQL

2016-04-12 Thread Django
#17635: Missing ability to cast georaphy to geometry when using GeoDjango and PostgresSQL -+- Reporter: corentin.chary@… |Owner: nobody Type: New feature |

Re: [Django] #26492: "./manage.py migrate" causes "maximum recursion depth exceeded" error

2016-04-12 Thread Django
#26492: "./manage.py migrate" causes "maximum recursion depth exceeded" error -+- Reporter: berkerpeksag |Owner: | berkerpeksag Type: Bug

Re: [Django] #26351: Recommend enabling MySQL's STRICT_TRANS_TABLES to prevent silent truncation

2016-04-12 Thread Django
#26351: Recommend enabling MySQL's STRICT_TRANS_TABLES to prevent silent truncation -+- Reporter: zhebrak |Owner: nobody Type: | Status:

Re: [Django] #26492: "./manage.py migrate" causes "maximum recursion depth exceeded" error

2016-04-12 Thread Django
#26492: "./manage.py migrate" causes "maximum recursion depth exceeded" error -+- Reporter: berkerpeksag |Owner: | berkerpeksag Type: Bug

Re: [Django] #18867: Restoring YAML fixtures with DateTimeField causes timezone warnings

2016-04-12 Thread Django
#18867: Restoring YAML fixtures with DateTimeField causes timezone warnings -+- Reporter: aigarius@… |Owner: aaugustin Type: | Status:

Re: [Django] #18867: Restoring YAML fixtures with DateTimeField causes timezone warnings

2016-04-12 Thread Django
#18867: Restoring YAML fixtures with DateTimeField causes timezone warnings -+- Reporter: aigarius@… |Owner: aaugustin Type: | Status:

[Django] #26494: executable flags lost when using an archive as a template

2016-04-12 Thread Django
#26494: executable flags lost when using an archive as a template + Reporter: misli | Owner: nobody Type: Bug | Status: new Component: Utilities |Version: 1.9 Severity: Normal |

Re: [Django] #16327: "save as new" redirects to list view instead of newly-created item

2016-04-12 Thread Django
#16327: "save as new" redirects to list view instead of newly-created item ---+--- Reporter: candlerb |Owner: giuliettamasina Type: Bug| Status: assigned

Re: [Django] #26489: Should reusable django apps use `zip_safe=False` in setup.py?

2016-04-12 Thread Django
#26489: Should reusable django apps use `zip_safe=False` in setup.py? -+- Reporter: guettli |Owner: nobody Type: | Status: closed

Re: [Django] #26489: Should reusable django apps use `zip_safe=False` in setup.py?

2016-04-12 Thread Django
#26489: Should reusable django apps use `zip_safe=False` in setup.py? -+- Reporter: guettli |Owner: nobody Type: | Status: new

Re: [Django] #26492: "./manage.py migrate" causes "maximum recursion depth exceeded" error

2016-04-12 Thread Django
#26492: "./manage.py migrate" causes "maximum recursion depth exceeded" error -+ Reporter: berkerpeksag |Owner: berkerpeksag Type: Bug | Status: assigned