By-polls: PTI leaders in Timergara oppose alliance with JI

Say party should field its own candidate for PK-95, Lower Dir-II seat.


Amjad Ali Shah March 27, 2015
Since JI is a key coalition partner in the provincial government, it has the right to field its own candidate to retain the seat. The party is likely to receive support from the ruling PTI. PHOTO: STOCK IMAGE

TIMERGARA: Pakistan Tehreek-e-Insaf leaders have urged their party’s leadership to field its own candidate for the upcoming by-elections for the vacant PK-95 Lower Dir-II assembly seat.

Insiders familiar with the matter told The Express Tribune on Friday that PTI leaders from the region are opposed to forming an alliance with the Jamaat-e-Islami for the by-polls, which was vacated by JI chief Sirajul Haq following his victory in the Senate polls. As a result, his party is likely to face a closely fought battle in the by-polls for the vacant slot. The elections will be held on May 7.

Since JI is a key coalition partner in the provincial government, it has the right to field its own candidate to retain the seat. The party is likely to receive support from the ruling PTI.

However, PTI leaders from the constituency insist the party is in a much stronger position in the area and should field its own candidate for the seat.

They have vehemently opposed the alliance and have even approached the PTI chief Imran Khan to have their grievances addressed.

Resistance from PTI leaders in the constituency has created hardships for JI leaders. Even though the JI enjoys considerable popularity in Lower Dir, the party is plagued by internal rifts which are likely to create setbacks for its nominees in the upcoming by-elections.

However, analysts believe rifts between PTI and JI before the by-elections could also encourage opposition parties to chalk out a strategy to jointly field a candidate.

Published in The Express Tribune, March 28th, 2015.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ