enabling github issues
-
there are many links to the github issues in the documentation and the blog post, but the issues on github are disabled.
is it possible to enable the issues again? If you aren't working with the github issues where and how do you track the issues (features, bugs, pushes ...) ? -
The platform is deemed mature since a long while, the GitHub issues are abused for things which are not-issues and the ' README' states:
For feedback/questions/issues use the Community
See also: Community - EoDevelopment 1.x
-
Hi,
I would like to check whether backtrader is the right framework for me (compared to other backtesting frameworks like e.g. zipline). To determine this, I usually also look at the amount of open issues in github and how fast they are closed/commented etc.
For quite a time, this was not possible (but seems to be possible again recently, as I can see at least one open issue at github now (https://github.com/backtrader/backtrader/issues).
Question:
where can I see the overall amount of open topics / issues in the community?Or do I have to assume that the one open issue is the only one?
Thanks in advance!
-
@newesttrader said in enabling github issues:
Or do I have to assume that the one open issue is the only one?
The
open
issue in GitHub is not an issue and it will be closed. The issues were closed because they were abused for posting questions and questions ... and issues where actually around 1% of the things.@newesttrader said in enabling github issues:
To determine this, I usually also look at the amount of open issues in github and how fast they are closed/commented etc.
So far this is a best effort project.
@newesttrader said in enabling github issues:
where can I see the overall amount of open topics / issues in the community?
There isn't such a thing.
-
Hi @backtrader,
thanks for your reply.
I understand your point. Perhaps tagging the threads that represent(ed) a bug with the tag issue could be a solution.
Bye!
-
So far people have reported things and things have been sorted out or discussed to clarify why the reported behavior is not a bug. I would bet that the major topic is order execution, where people expect immediate execution, without taking into account that such behavior is cheating
-
thanks @backtrader !