Replies: 1 comment
-
|
When doing some talking with other people it does appear that having all python instances be setup in the same repository with a different branch. So that is what will be done here as well |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Overview
Should a separate branch be created for a Python implementation of the code (Like how it is planned to be done) or should it be in a new repository all together?
I'm quite torn on the matter as having a Python version is something that I believe would be beneficial to have on hand as there's been some teams that have already moved over to Python as their main code base. In order to help them out and be able to give them advice with things like swerve drive that is coded in Python. Having a Python implementation would be a huge help. Although there is C++ as well, I have not seen a whole lot of teams use it for their code.
Branch
The benefit that I see from using a branch is that the current year's code is contained in just a single repository, instead of 2 of them. The downside to that is that if there's any updates to that branch with Python, you would need a pull request that is just Python and make sure it gets pulled into the right branch. That could make it a little bit more of a hassle to deal with.
Repository
The benefit that I see from using a separate repository on the other hand is organization. All issues, and pull requests would be just with that single code base, nothing from Java mixed in as well. The downside is for the future, as if there is 2 repositories, 1 for Python, 1, for Java, down the line, each project would need to have multiple repositories unless we switched fully from Java to Python. But even then, having multiple languages isn't a bad thing to have.
The main thing that I see here is organization, it could go either way. We can organize based on tags and branch names, or would do so for the repository as a whole. I think the branch idea is what I would choose, what is everyone else's thought in this?
Beta Was this translation helpful? Give feedback.
All reactions