Any plans to migrate to API v3?

[jwcollins]

Joe,

I've been using your octopart.py code as the low level interface from some of my scripts to Octopart. Basically, I'm trying to create and maintain some company component libraries at my current gig. Your code is the lowest level piece of that puzzle. Thanks for publishing it. It let me get started with a good bit less pain than otherwise would have been the case.

However, I just got an e-mail from Octopart earlier today saying that they are phasing out v2 of their API (the one that you use!) as of March 15th, 2014.

Have you had a chance to experiment with porting your code to v3 of Octopart's API?

Please advise. Thank you. --jwc

[guyzmo]

I'm doing a fork of this library to improve it, switching to python 3 (no plan to keep it compatible with py2), simplifying it and eventually moving to the v3 api.

Once it's stable, I might do a PR if jbaker is ok with my changes

cf https://github.com/guyzmo/Python-Octopart-API

Any help is welcome :-)

N.B.: I hope that @jbaker0428, you don't mind me changing the name to pyoctopart, as ultimately I plan on pushing it to pypi ( if you don't mind ;-)

[jbaker0428]

Go for it, I don't really have time to work on it right now. I'm just mad I didn't think of that name myself.

[guyzmo]

Go for it,

Well, I don't really have time, but I wanted to be able to easily/fastly get datasheets and specs for my projects' components, or for components we're talking about. This is why I took over your lib, to make it available on pypi, with a proper build setup (I'm not much into virtualenv, I much prefer zc.buildout).

That tool, is https://github.com/guyzmo/pyparts and you can install it using pip install pyparts.

So to get back on the current issue topic, I've updated three methods for /parts endpoints to support the new API with full show/hide/include parameters and with strong type checking on parameters. i.e. if you give show_foobar=True, you'll get insulted! I did not update the tests and I did not update the Models…

I don't really have time to work on it right now.

…because I neither have got a lot of time to focus on that, but I wanted to do that tool for a while, so now here it is. I'll keep on working on it at a slower pace, and don't hesitate to contribute back.

I'm not considering the fork stable at all at the time being!

I'm just mad I didn't think of that name myself.

Well, if you look at my github repositories, you'll find that it's more a scheme I apply to all my projects, than really having good ideas :-)