For code/output blocks: Use ``` (aka backtick or grave accent) in a single line before and after the block. See: http://commonmark.org/help/

backtrader2



  • Hi all,

    I would like to ask about the state of backtrader2. Since some pull requests go to backtrader, some go to backtrader2, I would like to ask how to continue. Since @backtrader keeps the code at the current state, new development goes into backtrader2.

    I suppose we don't get a statement from @backtrader about this, also how Daniel intends to continue with backtrader. So how to continue?

    Questions:

    • should new code goes to backtrader2
    • will Daniel give a statement about the future
    • will get backtrader get fragmented
    • how to prevent backtrader from splitting

    my preferred solution would be to @backtrader continue work on backtrader, at least accept pull request, which fixes some stuff.

    On the other side, I follow backtrader2 and am happy to see some growth on the code.

    I really appreciate the work of Daniel, so it would be great to get some statement from him about this whole ongoing process.

    I am also really interested about the opinion of @ab_trader, @vladisld, @vbs, @run-out, @Ed-Bartosh on what to follow and what to expect in the future. Also I would be very happy about some statement about the past process from @backtrader.



  • my intention is just to get a way of future development of bt defined. If @backtrader does not like to continue with further development, since all available stuff works. Maybe from a statement from him we would have a place, where new functionality and fixes goes to. Like having a new maintainer, a defined repository on which we all can work, put issues on, issue pull requests and so on (on which I would really appreciate if @backtrader would have a word on, since his work is awesome)



  • @dasch

    I'm curious that,how many people have read backtrader's source code more than once. How much do you understand the underlying logic of backtrader? I wonder if the underlying logic of backtrader has some problems.



  • @tianjixuetu If the underlying logic code has problems, we need to modify the underlying logic code first, then fix the bug, and develop new functions.anyone understand the backtrader's underlying logic and source code?



  • @dasch said in backtrader2:

    my preferred solution would be to @backtrader continue work on backtrader

    It's my preferred solution as well.

    @dasch said in backtrader2:

    I am also really interested about the opinion of @ab_trader, @vladisld, @vbs, @run-out, @Ed-Bartosh on what to follow and what to expect in the future

    Currently, the backtrader2 repository is open for issues and PRs. There are several devs with PRs approval permissions there.

    All fixes in the backtrader2 are upstreamed as PRs to the original official repository for Daniel (@backtrader) to review, approve, and merge.

    We are not planning to make releases out of backtrader2 (at least not right now) - leaving it to Daniel - and see if it will work.



  • @dasch said in backtrader2:

    I really appreciate the work of Daniel, so it would be great to get some statement from him about this whole ongoing process.

    We have reached out to Daniel and he has not responded.



  • I see to ways:

    1. Daniel expresses his plans how to continue with backtrader and then find a way how either he keeps doing it alone or give others also access to contribute to it
    2. backtrader2 becomes a project independent from original backtrader (including website, forum etc. etc.). This would be big step of course which means alot of effort and dedication.

    No bad feelings but I am personally think in the long run there won't be a vivid collaboration between backtrader2 and backtrader without any form of agreement or approval with Daniel.



  • There's a third way.

    1. We continue to do bug fixes on backtrader keeping the core engine in place.
    2. We can focus on making add-ons/plugins/additional libraries that work on the edges of the engine.

Log in to reply
 

});