support `-pylab` flag with deprecation warning #540

Closed
wants to merge 1 commit into
from

Projects

None yet

3 participants

@minrk
Member
minrk commented Jun 25, 2011

As requested on the list, the -pylab flag (one -) is allowed once again. If present, the argument is transformed to the current syntax, and a warning is displayed.

@minrk
Member
minrk commented Jun 25, 2011

Pinging @fperez and @bgranger. This specifically supports -pylab only. Flags still require -- prefix. An alternative would be to accept single-- prefix for all flags. This would be more natural for flags like ipython -i for force-interactive. Leaving it as-is gives us a place to add something new in the future.

@fperez
Member
fperez commented Jun 25, 2011

My take on this is to be conservative for now. -pylab is special because it's extremely widely documented, so we don't really want everyone's scripts, aliases and habits to break everywhere. We'll have to fine-tune our handling of command-line args after more extensive field use and feedback, so I'd suggest we stick, for now, to the bare minimum of tweaks until we can collect such information post-0.11.

@minrk
Member
minrk commented Jun 25, 2011

That makes sense. I'll go ahead and merge when I am back at a computer this evening.

@ellisonbg
Member

I am +1 on having this. I also like that this logic only applies to -pylab and not all flags/options.

@minrk minrk added a commit that closed this pull request Jun 26, 2011
@minrk minrk support `-pylab` flag with deprecation warning
closes gh-540
b6abd4d
@minrk minrk closed this in b6abd4d Jun 26, 2011
@mattvonrocketstein mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this pull request Nov 3, 2014
@minrk minrk support `-pylab` flag with deprecation warning
closes gh-540
d1707eb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment