Django-silk

Latest version: v5.1.0

Safety actively analyzes 626604 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 7

2.0.0

Not secure
- Fix migration for request.prof_file field (245)
- Dropped support for Django 1.5
- Dropped support for Django 1.6
- Dropped support for Django 1.7 (247)
- Updated documentation (250)

1.1.0

Not secure
- Support for Django 2 and Python 3.6
- Support garbage collecting old profiling data
- Moved project to jazzband
- Better data visualizations (194)
- Added ability to filter requests by http verb (192)
- Various UI fixes
- Various bug and testing fixes

1.0.0

Not secure
* Improved MySQL support (167 , 38)
* Changes length of Request.path and Request.view_name fields
* Length changes accounts for utf8bm4
* Updates travis matrix and requirements dependencies versions (165)
* Drops Django 1.7 Support & starts Django 1.11 testing
* Fixes scenario where ValueError exception is raised therefore causing no profiling to register (161 , 164)
* Adds configuration for wheels support (168 , 149)
* Adds Code style improvements for readability (166)

**IMPORTANT** As a major version release, expect some unintended quirks over existing installations. smaccona highlighted a couple MySQL scenario's [here](https://github.com/django-silk/silk/pull/167#issuecomment-286179431) . PostgreSQL users should be fine. Upgrade accordingly.

Thanks to ( auvipy, smaccona , PeRDy )

0.7.3

Not secure
- Improves profile storage location (152, 151 )
- ProfileDownloadView now available.
- Stores cProfiler into threaded local storage (153, 155)
- Upgrades testing library.

Thanks to ( r3m0t , Drache91).

0.7.2

Not secure
- Fixes Django 1.10 middleware instantiation issue 148
- Fixes Middleware exception handling to be SQL agnostic 142, 144, 146, 150
- Adds TravisCI testing of various SQL backends 145

Thanks to ( mattjegan , hanleyhansen , lockie )

0.7.1

Not secure
- In the event of an SQL OperationalError while trying to process a request due to a large query, a try catch was introduced to retry the processing (140).

Thanks to hanleyhansen.

Page 4 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.