[docs] [issue15542] Documentation incorrectly suggests __init__ called after direct __new__ call