If you reverse the order

fig = plt.figure()
ax1 = plt.subplot()
ax1.plot(range(2), range(2))
ax1.set_ylabel('y label')
ax2 = ax1.twinx()
ax1.yaxis.set_tick_params(which='major', labelsize=12, direction='out')

It works correctly.

@stretch97 You seem to have a talent for finding really odd subtle bugs.

Talent?! I think of it as a curse. =)

Anyways, thanks for the temporary work around.

When debugging this, I noticed that autoscale_view when plot is called causes the problem. I'm on matplotlib 2.x branch and I get the following problem below.

This happens after the below code is called in autoscale_view:

 handle_single_axis(
            scalex, self._autoscaleXon, self._shared_x_axes,
            'intervalx', 'minposx', self.xaxis, self._xmargin,
            margins['left'], margins['right'], self.set_xbound)
        handle_single_axis(
            scaley, self._autoscaleYon, self._shared_y_axes,
            'intervaly', 'minposy', self.yaxis, self._ymargin,
            margins['bottom'], margins['top'], self.set_ybound)

Is this is a new bug that popped up? if so, what would be considered a decent fix for autoscale_view?

I was wondering if auto_scale is actually even needed in plot. I managed to have the below graph just by removing it

I think this is only working with out autoscale_view because the data limits are [0, 1], which also happen to be the default view limits.

Autoscaling the limits (with the margins) is one of the big style changes for 2.0 so that functionality needs to remain.

It also looks like the last image you posted still shows the extra space between the tick labels and the ticks on the left axes.

I'm closing this because the original problem above seems to be gone now. Reopen if I have misunderstood. With

fig = plt.figure()
ax1 = plt.subplot()
ax1.plot(range(2),range(2))
ax1.yaxis.set_tick_params(which = 'major', direction = 'out', \
    labelsize = mpl.rcParams['font.size'], size = mpl.rcParams['ytick.major.size'])
ax2 = ax1.twinx()
fig.savefig('Issue.png')

I get

Yes, the problem does appear to be gone. Thank you to whomever inadvertently solved it!