Imp: Drop support for marshmallow 2 #68
Conversation
|
@SVilgelm Thank you for the review. I'll finalyse this work into the next days. I'm also waiting for a fix on marshmallow itself marshmallow-code/marshmallow#1429 |
|
sure |
lmignon
force-pushed
the
master-marshmallow3
branch
from
f069e30 to
1b55373
Compare
lmignon
force-pushed
the
master-marshmallow3
branch
from
1b55373 to
771aced
Compare
|
@SVilgelm Code fxed but still waiting for marshmallow-code/marshmallow#1429 (testsuite works with this fix on marshmallow...) |
| @@ -1,6 +1,8 @@ | |||
| CHANGES | |||
| ======= | |||
|
|
|||
| * Drop support for marshmallow 2 | |||
There was a problem hiding this comment.
Please remove changes in this file. ChangeLoge will be generated automatically
There was a problem hiding this comment.
^^^ please revert. The bump version script automatically generates the change log file
|
Any progress? I would love to this land soon |
|
@Sytten Unfortunately my PR on marshmallow remains without response... marshmallow-code/marshmallow#1429. Can you review this PR? This may help to move things forward. |
lmignon
changed the title
Since PyYaml 5.2, yaml.UnsafeLoader must be used instead of yaml.FullLoader because deserializing objects is exploitable and can run arbitrary code.
|
@SVilgelm I implemented the propagation of the 'unknow' parameter at loading time as part of the marshmallow-object API to move forward with marshamallow-object... |
| @@ -1,6 +1,8 @@ | |||
| CHANGES | |||
| ======= | |||
|
|
|||
| * Drop support for marshmallow 2 | |||
There was a problem hiding this comment.
^^^ please revert. The bump version script automatically generates the change log file
depends on: marshmallow-code/marshmallow#1429