Burak Arslan
Burak Arslan
> All existing with no type annos This should work as before > Support existing peoples code where they have full type annotations The logic to support this will be...
> Ok, this next release won't be backward compatible for anyone who had type annotations in their functions? Is this a thing? People have type annotations in their functions decorated...
OK, this is a good point. hmmm. First, mypy's type annotators are not compatible with spyne's type annotators. So users will have to choose one or the other. Maybe instead...
> Or, we could make sure Spyne's annotators are compatible with mypy's, though I imagine this would open a huge can of worms so I'm not entirely willing to go...
Sorry, yes, I think we should parse annotations like we originally wanted. If backwards compatibility becomes a problem, we can turn off reading annotations with eg by a new ``spyne.const.READ_ANNOTATIONS``...
Besides the PEP8 violations, this looks good to me. If you could make sure lines don't exceed 80 characters, I can merge this
> Ran through black, but looks like it changed quite a bit to align with PEP8 Huh, this is a mess. Can't you simply break lines manually?
> Might be good to add some doccos too, not sure where the best place to add them is, or what your plan is going forward with doccos - latest...
Here's the link to the latest jenkins run: https://jenkins.arskom.com.tr/job/spyne/job/origin-stable/214/
Huh, for some reason I stopped getting github notifications. Found these by chance. I'll start by getting jenkins back up. Stable release issue is still: #705