-
Notifications
You must be signed in to change notification settings - Fork 1
Add engineering process #4
Comments
Agree. I can not run examples/javascript locally due to the old dependency. |
I’ll schedule it for Tuesday. Also have another engineer who will pick up some work now. |
@lecram you’re familiar with the template already. I’ll try to take a stab this weekend, and will ping you if not. @SilverRainZ let’s start with an empty pytest folder and add unit tests as we go. This PR, I think, should be concerned with putting things into place instead of adding tests? |
Ping @jenstroeger |
Ugh my apologies, it’s been very busy the past few weeks. We’re currently fixing an issue in our Py package template after which we’ll have a good baseline to merge into this repo. Are you ok waiting a week or so? |
No problem, just a reminder. |
@SilverRainZ let’s perhaps do this in several steps:
We can adjust the Makefile as we move forward, and add more flexibility to it (see example). Considering that Sphinx itself requires at least Python 3.6, I think the same should apply here. The metadata classifiers seem outdated Lines 32 to 37 in b9f424b
and the Makefile seems to expect Python 3. This can be fixed as part of step 1. above. |
@jenstroeger That sounds good :D I am quite busy recently so maybe can't help :'( |
Based on the python-package-template repo I think it would make sense to bring over some of the engineering and automation into this repo: pylint and black at least.
Given the number of issues we’re opening we should also replace the examples/javascript folder with proper pytest?
The text was updated successfully, but these errors were encountered: