Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rename MPIExecLaunchers to MPILaunchers #1137

Closed
wants to merge 1 commit into from
Closed

Conversation

minrk
Copy link
Member

@minrk minrk commented Dec 10, 2011

MPIExec is unwieldy, and unnecessarily specific when they can be configured to use mpirun, aprun, etc.

This means you can now start an MPI cluster with just:

$> ipcluster start --engines=MPI

old names still work, logging deprecation warnings and pointing to the new names.

@bfroehle
Copy link
Contributor

I haven't tested this, but I think this is semantically a good change.

@minrk
Copy link
Member Author

minrk commented Dec 12, 2011

The code should behave exactly the same for users who replace 'MPIExec' with 'MPI', since all I did was rename the classes. The only new code is the deprecated versions of the old names, which have worked fine in my tests so far, using command-line args and config files with the old names.

MPIExec is unwieldy, and unnecessarily specific when they can be
configured to use mpirun, aprun, etc.

This means you can now start an MPI cluster with just:

    $> ipcluster start --engines=MPI

old names still work, logging deprecation warnings.
@minrk minrk closed this in 22c3df5 Dec 12, 2011
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this pull request Nov 3, 2014
MPIExec is unwieldy, and unnecessarily specific when they can be
configured to use mpirun, aprun, etc.

This means you can now start an MPI cluster with just:

    $> ipcluster start --engines=MPI

old names still work, logging deprecation warnings.

closes ipython#1137
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants