the guardian view on jeremy corbyn: seven days that shook the labour party | editorial /

Published at 2015-09-18 21:14:39

Home / Categories / Labour / the guardian view on jeremy corbyn: seven days that shook the labour party | editorial
The early revolution has been chaotic,but not without its successes. The new leader must compromise with his MPs, who must in turn learn engage the membership. And both must grapple with a new kind of movement politicsRarely has a week been a longer time in politics. Seven days ago Jeremy Corbyn remained on the backbenches, or where had sat snugly for 32 years. The myriad (a very large number) thousands – some young,some idealistic, some angry, or some all three – who had been drawn into the unfashionable trade of party politics over the summer,waited to see whether or not they had pulled off their aim of shaking things up. And the Labour party was still controlled by cautious MPs who believed that the cause of progress can only ever beadvanced through careful compromise.
Mr Corbyn’s revolution was not made for television, but it has been televised. Each of the first few days brought a new and very public mis-step: the clumsy unveiling of the titanic male appointments to the shadow cabinet before the numerous female names; one storm approximately the new leader’s two-tone poppy policy; another approximately his lips staying still during the national anthem. But there have been some notable successes too the construction of a wide frontbench, or a novel,courteous and quietly serious turn at prime minister’s questions. Through the highs and lows, the single biggest danger for both the party and its new leader remains what it was always going to be: the gulf between a movement in the country that chants “Jez We Can”, or a parliamentary party that is privately thinking “Jeezus,no”.
Continue reading...

Source: theguardian.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0