[IPython-dev] changing working directory from IPython server
ellisonbg at gmail.com
Mon Aug 11 16:20:47 EDT 2014
OK I think I understand, and I don't consider this a bug. If the
notebook you are starting out with is on the same machine, there is no
reason to "upload" that notebook. Just navigate the notebook dashboard
to the directory where that notebook already is and open it. Is there
some reason you can't do that and are instead trying to upload the
On Mon, Aug 11, 2014 at 1:11 PM, Mark Bakker <markbak at gmail.com> wrote:
> Thanks for considering this issue.
> The behavior now:
> I type: ipython notebook to start a notebook.
> At the dashboard, I click on 'To import a notebook, drag the file onto the
> listing below or *click here*. When I click there, a window pops up, I go to
> the directory with my notebook file, click on it, and then it shows up in
> the list of files, with next to it a blue Upload button. When I click on the
> Upload button the notebook is copied to the directory where I started the
> IPython Notebook.
> The problem: The notebook gets copied to the directory where I started
> ipython notebook. That is not very useful, as all associated data files are
> still in the directory where the notebook originated.
> Does that make it clear? Should I file a bug report?
> ps. It seems that the Anaconda guys are also expecting the behavior of the
> Notebook to change. They now have a useful 'start notebook' icon, but that
> starts in 'Documents/IPython Notebooks. And that faces the same problem as I
> described above.
>> From: Brian Granger <ellisonbg at gmail.com>
>> Subject: Re: [IPython-dev] changing working directory from IPython
>> To: IPython developers list <ipython-dev at scipy.org>
>> <CAH4pYpTsm2Vykb27Zaa4kJibmvaN14nSgAg6uq0NBASoQCSXgA at mail.gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>> Oh, I might have understood.
>> Mark can you clarify what exactly you are seeing and what you expect to
>> On Mon, Aug 11, 2014 at 10:03 AM, Thomas Kluyver <takowl at gmail.com> wrote:
>> > On 11 August 2014 07:51, Brian Granger <ellisonbg at gmail.com> wrote:
>> >> I don't remember that we made the decision to have this behavior. It
>> >> is possibly I just don't remember, but today I would consider that to
>> >> be a bug. Mark, could you open a GitHub issue on this to trigger a
>> >> discussion.
>> > I'm pretty sure that what Mark describes is how we expect it to work -
>> > when
>> > you upload a file, the server doesn't know where in your filesystem that
>> > data is coming from, so it can't switch to that directory and use the
>> > original notebook there, which I think is what Mark wants. The
>> > disconnect is
>> > that the UI implicitly encourages uploading, although that doesn't
>> > really
>> > make sense when you're running the server as a local application.
>> > Thomas
>> Brian E. Granger
> IPython-dev mailing list
> IPython-dev at scipy.org
Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger at calpoly.edu and ellisonbg at gmail.com
More information about the IPython-dev