Relation to existing unittest2pytest project

[The-Compiler]

There is already an existing unittest2pytest project under the pytest-dev umbrella by @htgoebel, which has the same name and works via lib2to3 as well.

Unfortunately, that's quite confusing - and I'm wondering, what's the reason Dropbox started their own converter rather than using the existing one? :wink:

[auvipy]

same question fro me too. I'm gonna convert django unit tests to pytest tests. which should I use then?

[nipunn1313]

Hey guys. Thanks for bringing this up. Honest truth is that we didn't know it was there when we wrote it. Was actually written around the same time (~Oct 2015). We came up with the name after the fact (turns out at least 2 people independently thought it was a good name :)) and it happens to collide with an existing project. Took a brief look at both projects and they are similar, but subtly different in how/where they work.

Perhaps we can try to merge the functionality of the projects. Or just have two implementations of similar things. Will have to look into it more. Happy to take any suggestions.

[The-Compiler]

Thanks for replying! IMHO, if @htgoebel agrees, it'd be best to merge them. I think having two projects with the same goal, each with their own subtle benefits/drawbacks, doesn't benefit anyone here.

But all of that is of course up to @htgoebel and you - I'm afraid I won't have the time to help getting those merged. I just thought it was a good idea of bringing it up. :smile:

[htgoebel]

but subtly different in how/where they work.

Well, they are simply fixing different cases :-)

You are warmly welcome to contribute your fixes to unittest2pytest project under the pytest-dev umbrella. I suggest merging there, since this is where people will look for it.

[nipunn1313]

For now I just went ahead and renamed this project and merged in @adamchainz's readme clarification. I'll continue redirecting people to the pytest-dev project which looks like it's going to get more love.