Closed sambuddhabasu closed 9 years ago
@meejah Please have a look at this PR. If the code looks good, I will go ahead and add tests for this
I have added tests for the support of stem.version.Version too
This all looks pretty great, thanks!
I think what I'm going to do is merge all "stem stuff" into the (now horrificially outdated) "stem-integration" branch so we can play with possibly-disruptive changes to see how they feel.
So, I'll rebase stem-integration and merge this into it....
The required changes that were pointed out by @meejah were made. Now, the stem.version
is tried to be imported only when use_stem
is True.
Also, the related tests have been added and all the tests pass successfully.
If everything seems good, I will squash the commits into a single commit
@meejah I have added a new Tox environment with-stem
.
Do let me know if everything looks good so that I can go ahead and squash all the commits into one.
Thanks
Yes, please squash it looks good so far :)
Done squashing the commits and the tests run good too :)
Will this commit be merged with master
or as you mentioned before with the stem-integration
branch?
Looks like the stem-integration
branch is a whole lot of commits behind the master
branch
Yeah, I tred rebasing stem-integration but it has a couple half-baked ideas so instead I'll create a new branch and merge this stuff into it. master is basically stable, and I think it's best to have a place we can try out more of the stem integration ideas together before trying to support a particular public API for it.
merged to optional-stem
We can do integration there.
Note that I took out the class-name check; if it acts like a stem Version object, that's good enough.
This fixes #108