Open fridex opened 4 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
/priority backlog
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/remove-lifecycle rotten /lifecycle forzen
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@sesheta: Closing this issue.
/lifecycle frozen
/triage accept
@codificat: The label(s) triage/accept
cannot be applied, because the repository doesn't have them.
/triage accepted
Is your feature request related to a problem? Please describe.
We recommend TensorFlow based on API symbols used from the library (match user's symbols used with the ones provided by TensorFlow). To support this idea long-term and reduce time spent on maintaining the symbols database, we could create an automatic symbols database update procedure. This procedure can be triggered automatically on new TensorFlow release.
Describe the solution you'd like
Each time there is a new minor TensorFlow release on PyPI, aggregate exposed TensorFlow symbols. A high level procedure description:
Describe alternatives you've considered
Have this procedure as a manual process, which is time-consuming and mundane.
Additional context
See discussion in https://github.com/thoth-station/tensorflow-symbols/pull/6#issuecomment-734718946