Re: [jupyter] How to run forked version of notebook when testing contributions?

That worked. For documentation's sake, I had to `pip uninstall notebook` and then `conda uninstall notebook` before I could install notebook from my forked and cloned notebook repository using `pip install -e .`. On Thursday, April 20, 2017 at 1:18:58 AM UTC-7, Min RK wrote: > > You are doing

Re: [jupyter] How to run forked version of notebook when testing contributions?

I just tried switching back to master, making changes, and rerunning 'pip install -e .' and 'npm run build' and my changes are still not showing up. I also uninstalled any version of jupyter notebook I had using "pip uninstall notebook" in case there was a conflict with the version I had

Re: [jupyter] How to run forked version of notebook when testing contributions?

Could it be something with my branches? For example, I have a development branch I'm working on, but could "pip install -e ." be pulling from master? On Wednesday, April 19, 2017 at 3:00:07 PM UTC-7, Adam Rule wrote: > > I am attempting to change actions.js and notebook.js so that the three >

Re: [jupyter] How to run forked version of notebook when testing contributions?

I am attempting to change actions.js and notebook.js so that the three paste items in the Edit menubar call a paste action rather than the paste function directly (issue #2415 ). I have run "pip install -e ." in the folder containing the forked

Re: [jupyter] How to run forked version of notebook when testing contributions?

Hi Adam, Do you have the necessary Javascript tools set up to rebuild Javascript and CSS if you're changing those pieces? http://jupyter-notebook.readthedocs.io/en/latest/contributing.html Changes to frontend stuff are also sometimes hidden by the browser cache. Usually pressing Ctrl-F5 a few

Re: [jupyter] How to run forked version of notebook when testing contributions?

It depends on what codebase you are changing, but normally you have to install your changes into your working environment before they take effect. The README from your clone should have instructions. Commonly it would be "pip install -e ." If you can say more about what you have done (what did you