|
|
# Passlib Roadmap
|
|
# :railroad_track: Passlib Roadmap
|
|
|
|
|
|
|
|
## Overview
|
|
## Overview
|
|
|
|
|
|
|
|
Passlib is slowly moving towards 2.0, and with it, there are plans to cleanup (and attempt to simplify) a lot of the internal code. Release 1.7 made some major cleanups to the API, while trying to maintain backwards compatibility. 1.8 will shed some low-impact features, and add some slated new ones.
|
|
Passlib is slowly moving towards 2.0, and with it, there are plans to cleanup (and attempt to simplify) a lot of the internal code. Release 1.7 made some major cleanups to the API, while trying to maintain backwards compatibility. 1.8 will drop python 2 support, shed some low-impact features, and add some slated new ones.
|
|
|
|
|
|
|
|
If something here would impact your application, please post a question / feedback on the [mailing list](https://groups.google.com/group/passlib-users)!
|
|
If something here would impact your application, please post a question / feedback on the [mailing list](https://groups.google.com/group/passlib-users)!
|
|
|
|
|
|
| ... | @@ -21,7 +21,7 @@ planned for future releases: |
... | @@ -21,7 +21,7 @@ planned for future releases: |
|
|
|
|
|
|
|
### v1.9
|
|
### v1.9
|
|
|
|
|
|
|
|
* Depending on v2.0 development changes, there *may* be a v1.9 a transitional release: applications using non-deprecated parts of 1.9 should be able to drop in 2.0 without much pain.
|
|
* Depending on how v2.0 development pans out, there *may* be a v1.9 transitional release leading up to it; which would contain deprecation warnings for anything that needs fixing in your application before upgrading to v2.0. In all likelyhood, these warnings will just get rolled into v1.8.
|
|
|
|
|
|
|
|
### v2.0
|
|
### v2.0
|
|
|
|
|
|
| ... | | ... | |
