Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Please include a template of in profile_default folder #2974

lsnz opened this Issue · 17 comments

7 participants


I was trying to config the default behavior of my notebook, such as default notebook folder.

I had a lot of trouble until I tried to create a new profile and saw the '' in that profile folder. This is just a workaround.

I suggest IPython includes a template of in profile_default folder. It will be a lot helpful and avoid a lot of search. The configuration file itself is well self-documented.

Note: tested with IPython0.13.1.


profile_default does have a It was not created, probably because you upgraded IPython from a previous version and already have a profile_default folder. Is it the case ?


I recently installed IPython on my raspberryPi with ArchArm Linux. It's a fresh install. I just checked my Profile_default folder, it doesn't have the notebook confiugration file.

BTW, I am the guy who logged this bug with a different ID.

See the following output of ls -al command in profile_default folder.

[oseack@alarmpi profile_default]$ ls -al
total 40
drwxr-xr-x 7 oseack users 4096 Feb 16 22:53 .
drwxr-xr-x 3 oseack users 4096 Jan 21 23:38 ..
drwxr-xr-x 2 oseack users 4096 Feb  3 21:29 db
-rw-r--r-- 1 oseack users 9216 Feb 16 22:53 history.sqlite
drwxr-xr-x 2 oseack users 4096 Jan 21 23:38 log
drwx------ 2 oseack users 4096 Jan 21 23:38 pid
drwx------ 2 oseack users 4096 Jan 21 23:38 security
drwxr-xr-x 2 oseack users 4096 Jan 21 23:38 startup

Hum, ok, weird. Tagging for probably next release.

Thanks !



$> ipython profile create

to generate the default config files. They are not written to the profile dir by default.


Is there a reason of not creating the config files by default ?
I would expect users to try to modify default config files before creating a new profile.

And using ipython profile create to create the default files of an already existing profile dir does not seem obvious to me.

If I had to find one reason it would be that new options could appear between version, and the "default" files would be out of date. What about a default Readme file that state "run ipython profile create to generate the default config files for the directory" ?


What about a default readme file that state "run ipython profile create to generate the default config files for the directory" ?

Probably a good idea.


To follow the convention of OSS, I hope we can include a template config file in the default folder like most others do.

Workaround is Ok after software is released, but for next release, workaround shouldn't be the first thought. And put the template into the the profile_default folder isn't a 'mission impossible'.


Yes, I think this was perhaps a wrong decision - that is, don't write config files until people actually have a reason to use them, so that they won't have stale config files representing an outdated IPython by the time they ultimately do want to do some configuration.

Workaround is Ok after software is released

Except it's not a workaround, it is deliberate, intended practice. It may be that we should change it, but ipython profile create is absolutely not a workaround for a bug, it is how you are supposed to configure IPython.


I understand the concern. I am sorry to call it workaround. But I still hope to have something straighforward.

And here is my suggestion and some other softwares do.

we only need to put the newest into the profile_default. 1.This will not override user's in upgrade installation. 2. for a fresh install, user can copy this to as a start point. I saw a lot of open source softwares doing this especially server software, and notebook is a kind of server software or at least similar.

For both scenarios, the user will have most recent config example file as a reference.


Hi! Seems the docs and the 1.1.0 branch behavior aren't in sync.

I followed the instructions here:

Start by creating a certificate file and a hashed password, as explained above. Then create a custom profile for the notebook, with the following command line, type:

    $ ipython profile create nbserver

In the profile directory just created, edit the file

but in the nbserver directory (or profile_default if i just run ipython profile create) ends up with a only, no as the docs suggest.

I know it's not a huge problem, one can cp and go from there, since the files are pretty much all commented out anyway and such, but it certainly is a bit confusing.



astonishingly it works for me :

└[~/ipython]> git checkout rel-1.1.0
Note: checking out 'rel-1.1.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 7c2ea3a... release 1.1.0
┌[matthiasbussonnier@umr168-curn-2-85-6561] [/dev/ttys002] [7c2ea3a ⚡]
└[~/ipython]> ipython profile create rubrubrub1
[ProfileCreate] Generating default config file: u'/Users/matthiasbussonnier/.ipython/profile_rubrubrub1/'
[ProfileCreate] Generating default config file: u'/Users/matthiasbussonnier/.ipython/profile_rubrubrub1/'
[ProfileCreate] Generating default config file: u'/Users/matthiasbussonnier/.ipython/profile_rubrubrub1/'
[ProfileCreate] Generating default config file: u'/Users/matthiasbussonnier/.ipython/profile_rubrubrub1/

(on master too) How did you install ? Did you have all dependencies ?


Indeed! It's due to deps! when i first ran profile create i didn't have all the deps installed (pyzqm, jinja2) and it didn't create it; once i tried to create the config, then it failed b/c of missing deps, so i installed them, got the server running (then posted the above comment)

Now when i run ipython profile create, as you say, it works as expected! :)

Only difference b/w then and now is that i installed the deps required to get notebook running.

Maybe a simple note somewhere in the docs says, 'didn't create, make sure you have all deps installed' :) for folks like me.

Thanks for the quick assistance!


You shouldn't have to install deps manually, if you pip install ipython[all] it should get everything and "just works".


@Carreau what do you think we should do with this? Close? Is there anything we need to do?


I have a long term plan using json conf for that.
So I think we can close.

@Carreau Carreau closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.