You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My own code is maybe a day away from being Pyhton3 compatible.
Adding unit tests to the code is maybe a few more days on top of that. One benefit of this entire utility, at least from a technical debt perspective, is that the skeleton files themselves provide an integration test of sorts. That's how we can make surface/aesthetic changes and know whether they are successful. When we get into more complex territory, e.g. signature parsing and output, it gets a little harder. When we come to add Python 3 lets see what we can add by way of unit testing.
Additional questions:
Are there any other languages that would lend themselves well to writing this utility?
What skew was introduced between the standard skeleton generator module and the container module?
Can they be combined and distributed as a sub-module?
What would combining repositories look like?
The text was updated successfully, but these errors were encountered:
Jython has documented that it wants to move toward a Python 3 release, but it's not here yet.
My own code is maybe a day away from being Pyhton3 compatible.
Adding unit tests to the code is maybe a few more days on top of that. One benefit of this entire utility, at least from a technical debt perspective, is that the skeleton files themselves provide an integration test of sorts. That's how we can make surface/aesthetic changes and know whether they are successful. When we get into more complex territory, e.g. signature parsing and output, it gets a little harder. When we come to add Python 3 lets see what we can add by way of unit testing.
Additional questions:
The text was updated successfully, but these errors were encountered: