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

Backtrader's Future



  • Thanks @vladisld !

    I would limit number of admins and number of people able to change the master (at least). I've seen number of times when reported issues or bugs were just results of lack of understanding of the bt. We might have a lot of errors later.

    Also strict rules on how bugs/issues should be presented (script sample, data sample, error message, what expected) need to get set and followed.

    I would start with PRs on main repo, also couple interesting issues related to stop and limit orders were posted here recently.



  • @vladisld my github is https://github.com/tianjixuetu ,thank you very much.



  • Hi guys, nice work getting the ball rolling. I'd love to be a part of this. Whether it's as an admin or contributor. My github id is benmercerdev.



  • Great to see people stepping up.



  • Thanks @vladisld, really nice! Looking forward to this!
    Regarding the name: Might backtrader2 lead people into thinking that it is v2 of the official project? Maybe the name should indicate more that is is a fork of the official backtrader? Some people seem to already expect some sort of a version 2 of the offical project, e.g. https://community.backtrader.com/topic/2210/backtrader-2-0



  • @vbs said in Backtrader's Future:

    Thanks @vladisld, really nice! Looking forward to this!
    Regarding the name: Might backtrader2 lead people into thinking that it is v2 of the official project? Maybe the name should indicate more that is is a fork of the official backtrader? Some people seem to already expect some sort of a version 2 of the offical project, e.g. https://community.backtrader.com/topic/2210/backtrader-2-0

    Thanks for the comment. I hope I'm not speaking out of turn for the tam. There won't be a version two coming from the original creator of backtrader. Perhaps someday there might be a version 2 but the first steps to getting to a that would be to have the platform controlled by the users and have at a minimum bugs worked out of the system and some admins with an excellent level of knowledge of the platform.

    Once we are comfortable with that the platform is organized and under control, then maybe other items for a version 2 can be discussed.

    Baby steps for now.



  • @vbs said in Backtrader's Future:

    Might backtrader2 lead people into thinking that it is v2 of the official project

    backtrader2 is just a name of the org. Repository name is still backtrader. So I'm personally less concerned here. The question remains about the release scheme - this is something that still need to be discussed of cause.

    IMHO the main issue right now is to organize the environment/policies to ensure the highest quality of the incoming changes and stability of the project. I'm thinking about utilizing the existing tests so that they could be run on each change as a prerequisite for PR approval ( probably in automated fashion) as well as requesting each PR to include the tests covering the proposed change.

    Both of the above has its own problems:

    1. Most of the existing tests seems to be developed for manual run and inspection. 2. Some parts of the code is hard to automatically test since interactions with external API could be required and there is no any mock interfaces or simulators available yet


  • I have set up Travis CI on my fork to automatically run tests upon commit. Maybe it will help you:
    https://travis-ci.com/github/verybadsoldier/backtrader

    Both of the above has its own problems:

    1. Most of the existing tests seems to be developed for manual run and inspection.

    Hm, not sure. Which ones do you mean?
    The ones that I am aware of can be run automatically, e.g.:
    https://travis-ci.com/github/verybadsoldier/backtrader/jobs/295673688

    1. Some parts of the code is hard to automatically test since interactions with external API could be required and there is no any mock interfaces or simulators available yet

    Python's unittest package has quite good mocking features. So writing tests for external APIs shouldn't be hard. I think that is the standard way.



  • @vbs said in Backtrader's Future:

    I have set up Travis CI on my fork to automatically run tests upon commit. Maybe it will help you

    The ones that I am aware of can be run automatically

    Gr8, very useful. Thanks a lot.

    @vbs said in Backtrader's Future:

    Python's unittest package has quite good mocking features. So writing tests for external APIs shouldn't be hard

    I have a bunch of bugs opened in my fork, mainly related to IB store - was thinking about writing mocks for IbPy interfaces and include it in automation. I guess we'll need similar mocks for others as well.

    Thanks @vbs.



  • @vladisld Looking forward to contributing on this (not admin though). Github user: mik-s



  • pablonosh as contributor



  • It seems creating the 'contributors' team was unnecessary. Right now anyone may just submit the PRs and open Bugs directly - the repository is public.

    Sorry for confusion - my bad - we are figuring all the details slowly, hope we'll manage.

    In any case, any feedback about managing the repository is very welcome.
    Thanks a lot.



  • hey guys, I very much appreciate your effort. I really hope, this will give baxktrader a push for more contributions. So a lot of cudos to @run-out and all you other guys.

    We will find a way for the future of backtrader.



  • This PR (https://github.com/mementum/backtrader/pull/401) seems like a nice bugfix to get the ball rolling with backtrader2. It's not mine but I'll steal it if the original author takes too long :P


  • administrators

    Dear @vladisld,

    I have just read this tread and you statement

    @vladisld said in Backtrader's Future:

    Since no one I guess has a full understanding of the platform yet, we probably should limit ourselves to bug fixing only, at least initially - and see how it goes.

    This is probably spot on and something I have failed to realize. Since your fork doesn't yet contain any changes, I am adding a few bug fixes to the main repository and release a new version with them.



  • @backtrader since you're in the thread, is it possible to modify the official backtrader repo to give some more people write access (probably just the admins of backtrader2 for now)?



  • (I'm assuming that continuing the official backtrader repo with a new team of maintainers is preferable to forking it but I could be wrong about that)


  • administrators



  • Very nice. Someday I'd like to meet Daniel R. in person and buy him a beverage.

    Vlad, I'm limited in time and scope but would like to try to contribute as an admin where I can: https://github.com/bigdavediode



  • @backtrader said in Backtrader's Future:

    I am adding a few bug fixes to the main repository and release a new version with them.

    God bless you Daniel, you are back. Thanks a lot. So what do you say about the initiative to continue the maintenance for bug fixing ?

    Should we continue with the fork, or there is a way to continue on the official repo?


Log in to reply
 

});