search

ergo / pyramid_apispec

Pyramid plugin for openapi spec generation (using ApiSpec)
BSD 3-Clause "New" or "Revised" License
23 stars 10 forks source link

apispec beta tag issue #11

Closed jstevensfit closed 6 years ago

jstevensfit commented 6 years ago

It looks like most versions of pyramid_apispec are pulling the latest build of apispec which is (in this particular case) causing code to break even if bound to a specific version of pyramid_apispec.

Specifically the replacement of spec.definition() to spec.components.schema() and spec.add_path() to spec.path().

In relation to the current documentation and APISpec object.

Could you bind to a specific stable version of apispec to correct the issue?

ergo commented 6 years ago

Hey @jstevensfit I understand your pain, that is why I've made recent 0.3 release. It depends on latest beta, last version was 0.34 and then they suddenly jumped to 1.0 beta releases and made bw. incompatible changes.

My latest release works with latest APISpec, best way would be to pin it in your requirements own to 1.0.0b5 for now. I'm really hoping the API there stabilizes soon - as I don't want to hardcode pre 1.0 versions for now.

jstevensfit commented 6 years ago

Thanks for the response

ergo commented 6 years ago

Yw.

You can either pin 

pyramid_apispec==0.2.1
apispec==1.0.0b1

to keep old behavior or 

pyramid_apispec==0.3.0
apispec==1.0.0b5

Does that help?

jstevensfit commented 6 years ago

Yes it does, I'll use the latter.