From 56d566293fdc2859ef392163cbbcd65ae9f93705 Mon Sep 17 00:00:00 2001 From: "C.A.M. Gerlach" Date: Sat, 14 Sep 2024 20:46:47 -0500 Subject: [PATCH 1/2] Remove obselete po messages & drop legacy conf.py setting --- doc/conf.py | 1 - noxfile.py | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/conf.py b/doc/conf.py index 3bcbe547..aa6f7eb1 100644 --- a/doc/conf.py +++ b/doc/conf.py @@ -59,7 +59,6 @@ # You can specify multiple suffix as a list of string: # # source_suffix = ['.rst', '.md'] -source_suffix = ".rst" # The encoding of source files. source_encoding = "utf-8" diff --git a/noxfile.py b/noxfile.py index 2028b4a8..a5823c2f 100644 --- a/noxfile.py +++ b/noxfile.py @@ -478,6 +478,7 @@ def _update_po(session): POT_DIR, "--line-width", str(PO_LINE_WIDTH), + "--no-obsolete", *lang_args, *posargs, ) From c5ae9b97a6b3da22518777df514a3b364555f962 Mon Sep 17 00:00:00 2001 From: "C.A.M. Gerlach" Date: Sat, 14 Sep 2024 20:58:25 -0500 Subject: [PATCH 2/2] Regenerate pot and po files with modern Sphinx, theme & i18n infra --- doc/locales/en/LC_MESSAGES/faq.po | 480 ++- doc/locales/en/LC_MESSAGES/index.po | 117 +- doc/locales/en/LC_MESSAGES/installation.po | 493 +-- doc/locales/en/LC_MESSAGES/panes.po | 1770 +++++------ doc/locales/en/LC_MESSAGES/plugins.po | 252 +- doc/locales/en/LC_MESSAGES/quickstart.po | 15 +- doc/locales/en/LC_MESSAGES/troubleshooting.po | 729 ++--- doc/locales/en/LC_MESSAGES/videos.po | 477 +-- doc/locales/en/LC_MESSAGES/workshops.po | 2751 +++++----------- doc/locales/pot/faq.pot | 485 ++- doc/locales/pot/index.pot | 120 +- doc/locales/pot/installation.pot | 496 +-- doc/locales/pot/panes.pot | 1856 +++++------ doc/locales/pot/plugins.pot | 259 +- doc/locales/pot/quickstart.pot | 18 +- doc/locales/pot/troubleshooting.pot | 732 ++--- doc/locales/pot/videos.pot | 481 +-- doc/locales/pot/workshops.pot | 2783 +++++------------ 18 files changed, 4698 insertions(+), 9616 deletions(-) diff --git a/doc/locales/en/LC_MESSAGES/faq.po b/doc/locales/en/LC_MESSAGES/faq.po index 9b45e51e..c7ac4ede 100644 --- a/doc/locales/en/LC_MESSAGES/faq.po +++ b/doc/locales/en/LC_MESSAGES/faq.po @@ -8,16 +8,16 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" #: ../../faq.rst:3 msgid "Frequently Asked Questions" @@ -27,39 +27,32 @@ msgstr "" msgid "Installing and updating" msgstr "" +#: ../../faq.rst +msgid "Q: How do I install Spyder?" +msgstr "" + #: ../../faq.rst:12 -msgid "" -"The easiest way to install Spyder is with the Anaconda Python " -"distribution, which comes with everything you need to get started in an " -"all-in-one package. Download it from its `webpage`_." +msgid "The easiest way to install Spyder is with the Anaconda Python distribution, which comes with everything you need to get started in an all-in-one package. Download it from its `webpage`_." msgstr "" #: ../../faq.rst:17 msgid "For more information, visit our :doc:`/installation`." msgstr "" +#: ../../faq.rst +msgid "Q: How do I install Spyder on Windows Subsystem for Linux 2 (WSL2)?" +msgstr "" + #: ../../faq.rst:23 -msgid "" -"If you already installed Spyder on your Windows machine, you do not need " -"to reinstall it on a WSL2-based Linux environment if your code must run " -"there." +msgid "If you already installed Spyder on your Windows machine, you do not need to reinstall it on a WSL2-based Linux environment if your code must run there." msgstr "" #: ../../faq.rst:25 -msgid "" -"Instead, just install `Miniconda`_ inside WSL2 and create a new conda " -"environment (or use an existing conda- or virtualenv), then install " -"Spyder-Kernels into that environment with e.g. ``conda install spyder-" -"kernels``. You must manually install ``ipython_genutils`` with e.g. " -"``conda install ipython_genutils``." +msgid "Instead, just install `Miniconda`_ inside WSL2 and create a new conda environment (or use an existing conda- or virtualenv), then install Spyder-Kernels into that environment with e.g. ``conda install spyder-kernels``. You must manually install ``ipython_genutils`` with e.g. ``conda install ipython_genutils``." msgstr "" #: ../../faq.rst:30 -msgid "" -"Windows creates a network path located at ``\\\\wsl$`` that points to the" -" partitions of your WSL2 machines, e.g. ``\\\\wsl$\\Ubuntu-20.04``. You " -"**must** map a network drive letter to your machine path, e.g. ``W:``, " -"for Spyder to correctly see its files and folders." +msgid "Windows creates a network path located at ``\\\\wsl$`` that points to the partitions of your WSL2 machines, e.g. ``\\\\wsl$\\Ubuntu-20.04``. You **must** map a network drive letter to your machine path, e.g. ``W:``, for Spyder to correctly see its files and folders." msgstr "" #: ../../faq.rst:33 @@ -67,22 +60,15 @@ msgid "To start a Spyder kernel, from your Linux terminal run" msgstr "" #: ../../faq.rst:39 -msgid "" -"It will run the kernel as a subprocess and create a file named " -":file:`remotemachine.json` in your WSL home folder." +msgid "It will run the kernel as a subprocess and create a file named :file:`remotemachine.json` in your WSL home folder." msgstr "" #: ../../faq.rst:41 -msgid "" -"Finally, under the options menu of Spyder's :doc:`panes/ipythonconsole`, " -"select :guilabel:`Connect to an existing kernel` as described in :ref" -":`connecting-external-kernel`. Insert the absolute path of " -":file:`remotemachine.json` into the :guilabel:`Connection file` field. If" -" you mapped ``W:`` as mentioned in above note, the path should be " -":file:`W:/home/{username}/remotemachine.json`. A new console will open in" -" Spyder, running in the Linux environment. Try running ``os.system('ls " -"-la')`` and see if it lists your WSL home folder. If you run ``exit()`` " -"from Spyder, the kernel running on Linux will be stopped." +msgid "Finally, under the options menu of Spyder's :doc:`panes/ipythonconsole`, select :guilabel:`Connect to an existing kernel` as described in :ref:`connecting-external-kernel`. Insert the absolute path of :file:`remotemachine.json` into the :guilabel:`Connection file` field. If you mapped ``W:`` as mentioned in above note, the path should be :file:`W:/home/{username}/remotemachine.json`. A new console will open in Spyder, running in the Linux environment. Try running ``os.system('ls -la')`` and see if it lists your WSL home folder. If you run ``exit()`` from Spyder, the kernel running on Linux will be stopped." +msgstr "" + +#: ../../faq.rst +msgid "Q: How do I update Spyder using conda?" msgstr "" #: ../../faq.rst:52 @@ -90,62 +76,67 @@ msgid "From the command line (or Anaconda prompt on Windows), run:" msgstr "" #: ../../faq.rst:59 -msgid "" -"If this results in an error or does not update Spyder to the latest " -"version, try:" +msgid "If this results in an error or does not update Spyder to the latest version, try:" +msgstr "" + +#: ../../faq.rst +msgid "Q: How do update I Spyder using Anaconda Navigator?" msgstr "" #: ../../faq.rst:69 -msgid "" -"Open the \"gear\" menu in Spyder's section under :guilabel:`Home` in " -"Navigator. Go to :guilabel:`Install specific version` and select the " -"version of Spyder you want to use. We strongly recommend the latest " -"available, to benefit from new features, bug fixes, performance " -"improvements and usability enhancements." +msgid "Open the \"gear\" menu in Spyder's section under :guilabel:`Home` in Navigator. Go to :guilabel:`Install specific version` and select the version of Spyder you want to use. We strongly recommend the latest available, to benefit from new features, bug fixes, performance improvements and usability enhancements." +msgstr "" + +#: ../../faq.rst:73 +msgid "Navigator showing installing specific version of Spyder" msgstr "" #: ../../faq.rst:80 msgid "Running Spyder" msgstr "" +#: ../../faq.rst +msgid "Q: How do I run Spyder?" +msgstr "" + #: ../../faq.rst:85 msgid "You can launch it in any of the following ways:" msgstr "" #: ../../faq.rst:87 -msgid "" -"**From the command line**: Type ``spyder`` in your terminal (or Anaconda " -"prompt on Windows)." +msgid "**From the command line**: Type ``spyder`` in your terminal (or Anaconda prompt on Windows)." msgstr "" #: ../../faq.rst:89 -msgid "" -"**From Anaconda Navigator**: Scroll to :guilabel:`Spyder` under " -":guilabel:`Home`, and click :guilabel:`Launch`." +msgid "**From Anaconda Navigator**: Scroll to :guilabel:`Spyder` under :guilabel:`Home`, and click :guilabel:`Launch`." +msgstr "" + +#: ../../faq.rst:91 +msgid "Navigator showing running a specific version of Spyder" msgstr "" #: ../../faq.rst:94 msgid "***Windows Only***: Launch it via the Start menu shortcut." msgstr "" +#: ../../faq.rst:96 +msgid "Spyder shortcut in the Windows Start menu" +msgstr "" + +#: ../../faq.rst +msgid "Q: Can I try Spyder without installing it?" +msgstr "" + #: ../../faq.rst:103 -msgid "" -"Yes! With `Binder`_, you can work with a fully functional copy of Spyder " -"that runs right in your web browser. Try it `here`_." +msgid "Yes! With `Binder`_, you can work with a fully functional copy of Spyder that runs right in your web browser. Try it `here`_." +msgstr "" + +#: ../../faq.rst +msgid "Q: What are the system requirements for Spyder? How resource-intensive is it?" msgstr "" #: ../../faq.rst:114 -msgid "" -"Spyder works on modern versions of Windows, macOS and Linux (see the " -"table below for recommended versions) via Anaconda, as well as other " -"methods. It typically uses relatively minimal CPU when idle, and 0.5 GB -" -" 1 GB of RAM, depending on how long you've been using it and how many " -"files, projects, panes and consoles you have open. It should work on any " -"system with a dual-core or better x64 processor and at least 4 GB of RAM," -" although 8 GB is *strongly* recommended for best performance when " -"running other applications. However, the code you run, such as scientific" -" computation and deep learning models, may require additional resources " -"beyond this baseline for Spyder itself." +msgid "Spyder works on modern versions of Windows, macOS and Linux (see the table below for recommended versions) via Anaconda, as well as other methods. It typically uses relatively minimal CPU when idle, and 0.5 GB - 1 GB of RAM, depending on how long you've been using it and how many files, projects, panes and consoles you have open. It should work on any system with a dual-core or better x64 processor and at least 4 GB of RAM, although 8 GB is *strongly* recommended for best performance when running other applications. However, the code you run, such as scientific computation and deep learning models, may require additional resources beyond this baseline for Spyder itself." msgstr "" #: ../../faq.rst:122 @@ -180,18 +171,24 @@ msgstr "" msgid "Ubuntu 16.04" msgstr "" +#: ../../faq.rst +msgid "Q: How do I run Spyder installed in a conda environment using Anaconda Navigator?" +msgstr "" + #: ../../faq.rst:133 -msgid "" -"Select the environment you want to launch Spyder from under " -":guilabel:`Applications on`. If Spyder is installed in this environment, " -"you will see it in Navigator's :guilabel:`Home` window. Click " -":guilabel:`Launch` to start Spyder in your selected environment." +msgid "Select the environment you want to launch Spyder from under :guilabel:`Applications on`. If Spyder is installed in this environment, you will see it in Navigator's :guilabel:`Home` window. Click :guilabel:`Launch` to start Spyder in your selected environment." +msgstr "" + +#: ../../faq.rst:137 +msgid "Navigator showing running Spyder in a specific environment" +msgstr "" + +#: ../../faq.rst +msgid "Q: How do I run Spyder installed in a conda environment using the command line?" msgstr "" #: ../../faq.rst:144 -msgid "" -"Activate your conda environment by typing the following in your terminal " -"(or Anaconda Prompt on Windows):" +msgid "Activate your conda environment by typing the following in your terminal (or Anaconda Prompt on Windows):" msgstr "" #: ../../faq.rst:150 @@ -202,279 +199,238 @@ msgstr "" msgid "Using Spyder" msgstr "" +#: ../../faq.rst +msgid "Q: How do I install Python packages to use within Spyder if I installed Spyder with conda?" +msgstr "" + #: ../../faq.rst:163 -msgid "" -"The first approach for installing a package should be using conda. In " -"your system terminal (or Anaconda Prompt on Windows), type:" +msgid "The first approach for installing a package should be using conda. In your system terminal (or Anaconda Prompt on Windows), type:" msgstr "" #: ../../faq.rst:170 -msgid "" -"If your installation is not successful, follow steps 3 through 5 of Part " -"2 in our video on solving and avoiding problems with pip, Conda and " -"Conda-Forge." +msgid "If your installation is not successful, follow steps 3 through 5 of Part 2 in our video on solving and avoiding problems with pip, Conda and Conda-Forge." +msgstr "" + +#: ../../faq.rst +msgid "Q: How do I get Spyder to work with my existing Python packages/environment?" +msgstr "" + +#: ../../faq.rst:182 +msgid "To work with an existing environment in Spyder, change the default Python interpreter for new :doc:`/panes/ipythonconsole`\\s to point to this environment." msgstr "" #: ../../faq.rst:184 -msgid "" -"To work with an existing environment in Spyder, change the default Python" -" interpreter for new :doc:`/panes/ipythonconsole`\\s to point to this " -"environment." +msgid "To do so, open the :guilabel:`Python interpreter` section of Spyder's preferences (:menuselection:`Tools --> Preferences`, or :menuselection:`Spyder --> Preferences` on macOS). Here, select the option :guilabel:`Use the following Python interpreter`, and use the dropdown below to select your preferred environment. If it's not listed, see :ref:`the note below `." msgstr "" -#: ../../faq.rst:186 -msgid "" -"To do so, open the :guilabel:`Python interpreter` section of Spyder's " -"preferences (:menuselection:`Tools --> Preferences`, or " -":menuselection:`Spyder --> Preferences` on macOS). Here, select the " -"option :guilabel:`Use the following Python interpreter`, and use the " -"dropdown below to select your preferred environment. If it's not listed, " -"see :ref:`the note below `." +#: ../../faq.rst:188 +msgid "Preferences showing changing Python interpreter" +msgstr "" + +#: ../../faq.rst:195 +msgid "If you installed Miniconda (or another Conda-based distribution) to a non-default path, or are using a virtual environment managed by a tool other than ``pyenv``, your environments likely won't be listed." msgstr "" #: ../../faq.rst:197 -msgid "" -"If you installed Miniconda (or another Conda-based distribution) to a " -"non-default path, or are using a virtual environment managed by a tool " -"other than ``pyenv``, your environments likely won't be listed." +msgid "Instead, use the text box or the :guilabel:`Select file` button to enter the path to the Python interpreter you want to use. You can find this path by activating the venv or Conda env you want to use in your terminal (Anaconda Prompt on Windows), and running the command:" msgstr "" -#: ../../faq.rst:199 -msgid "" -"Instead, use the text box or the :guilabel:`Select file` button to enter " -"the path to the Python interpreter you want to use. You can find this " -"path by activating the venv or Conda env you want to use in your terminal" -" (Anaconda Prompt on Windows), and running the command:" +#: ../../faq.rst:204 +msgid "Finally, click :guilabel:`Restart kernel` in the :guilabel:`Consoles` menu for this change to take effect. If ``spyder-kernels`` is not already installed, the :doc:`/panes/ipythonconsole` will display instructions on how to install the right version. Execute the given command in your terminal (the Anaconda Prompt on Windows) with the environment activated, and finally restart the kernel once more." msgstr "" -#: ../../faq.rst:206 -msgid "" -"Finally, click :guilabel:`Restart kernel` in the :guilabel:`Consoles` " -"menu for this change to take effect. If ``spyder-kernels`` is not already" -" installed, the :doc:`/panes/ipythonconsole` will display instructions on" -" how to install the right version. Execute the given command in your " -"terminal (the Anaconda Prompt on Windows) with the environment activated," -" and finally restart the kernel once more." +#: ../../faq.rst +msgid "Q: How do I install Python packages to use within Spyder if I downloaded Spyder from the standalone installers?" msgstr "" -#: ../../faq.rst:216 -msgid "" -"Watch our video on using additional packages or follow the instructions " -"below." +#: ../../faq.rst:212 +msgid "Watch our video on using additional packages or follow the instructions below." msgstr "" -#: ../../faq.rst:224 -msgid "" -"If you want to use other packages in Spyder that don't come with our " -"installer, you need to have your own Python distribution installed; we " -"recommend `Miniconda`_ or another Conda-based option. For Spyder to " -"recognize it automatically, you should use a Conda-based distribution " -"with its default install path." +#: ../../faq.rst:220 +msgid "If you want to use other packages in Spyder that don't come with our installer, you need to have your own Python distribution installed; we recommend `Miniconda`_ or another Conda-based option. For Spyder to recognize it automatically, you should use a Conda-based distribution with its default install path." msgstr "" -#: ../../faq.rst:229 -msgid "" -"Create a new conda environment containing ``spyder-kernels`` and the " -"packages that you want to use. For example, if you want to use ``scikit-" -"learn``, open your terminal (or Anaconda prompt on Windows) and run the " -"following command:" +#: ../../faq.rst:225 +msgid "Create a new conda environment containing ``spyder-kernels`` and the packages that you want to use. For example, if you want to use ``scikit-learn``, open your terminal (or Anaconda prompt on Windows) and run the following command:" msgstr "" -#: ../../faq.rst:236 -msgid "" -"Finally, connect Spyder to this ``my-env`` environment by changing " -"Spyder's default Python interpreter, following the instructions in " -":ref:`the above answer `." +#: ../../faq.rst:232 +msgid "Finally, connect Spyder to this ``my-env`` environment by changing Spyder's default Python interpreter, following the instructions in :ref:`the above answer `." msgstr "" -#: ../../faq.rst:242 -msgid "" -"Either use the :guilabel:`Reset Spyder to factory defaults` under " -":guilabel:`Tools` in Spyder's menu bar, the :guilabel:`Reset Spyder " -"settings` Start menu shortcut (Windows), or run ``spyder --reset`` in " -"your system terminal (Anaconda prompt on Windows)." +#: ../../faq.rst +msgid "Q: How do I reset Spyder's preferences to the defaults?" msgstr "" -#: ../../faq.rst:251 -msgid "" -"Under :guilabel:`General` in Spyder's :guilabel:`Preferences`, go to the " -":guilabel:`Advanced settings` tab and select your language from the " -"options displayed under :guilabel:`Language`." +#: ../../faq.rst:238 +msgid "Either use the :guilabel:`Reset Spyder to factory defaults` under :guilabel:`Tools` in Spyder's menu bar, the :guilabel:`Reset Spyder settings` Start menu shortcut (Windows), or run ``spyder --reset`` in your system terminal (Anaconda prompt on Windows)." +msgstr "" + +#: ../../faq.rst:240 +msgid "Spyder reset button in tools" +msgstr "" + +#: ../../faq.rst +msgid "Q: How do I change Spyder's language?" +msgstr "" + +#: ../../faq.rst:247 +msgid "Under :guilabel:`General` in Spyder's :guilabel:`Preferences`, go to the :guilabel:`Advanced settings` tab and select your language from the options displayed under :guilabel:`Language`." msgstr "" -#: ../../faq.rst:260 +#: ../../faq.rst:249 +msgid "Spyder change language in preferences." +msgstr "" + +#: ../../faq.rst +msgid "Q: How do I use code cells in Spyder?" +msgstr "" + +#: ../../faq.rst:256 #, python-format -msgid "" -"To create a cell in Spyder's :doc:`/panes/editor`, type ``#%%`` in your " -"script. Each ``#%%`` will make a new cell. To run a cell, press :kbd" -":`Shift-Enter` (while your cursor is focused on it) or use the " -":guilabel:`Run current cell` button in Spyder's toolbar." +msgid "To create a cell in Spyder's :doc:`/panes/editor`, type ``#%%`` in your script. Each ``#%%`` will make a new cell. To run a cell, press :kbd:`Shift-Enter` (while your cursor is focused on it) or use the :guilabel:`Run current cell` button in Spyder's toolbar." msgstr "" -#: ../../faq.rst:271 -msgid "" -"Spyder plugins are available in the ``conda-forge`` conda channel. To " -"install one, type on the command line (or Anaconda Prompt on Windows):" +#: ../../faq.rst:260 ../../faq.rst:295 ../../faq.rst:304 ../../faq.rst:313 +msgid "Spyder showing cell generation." msgstr "" -#: ../../faq.rst:278 -msgid "" -"Replace ```` with the name of the plugin you want to use. For " -"more information on a specific plugin, go to the its repository:" +#: ../../faq.rst +msgid "Q: How do I use plugins with Spyder (e.g. Spyder-Notebook, Spyder-Terminal, Spyder-Unittest)?" msgstr "" -#: ../../faq.rst:281 +#: ../../faq.rst:267 +msgid "Spyder plugins are available in the ``conda-forge`` conda channel. To install one, type on the command line (or Anaconda Prompt on Windows):" +msgstr "" + +#: ../../faq.rst:274 +msgid "Replace ```` with the name of the plugin you want to use. For more information on a specific plugin, go to the its repository:" +msgstr "" + +#: ../../faq.rst:277 msgid "`spyder-unittest`_" msgstr "" -#: ../../faq.rst:282 +#: ../../faq.rst:278 msgid "`spyder-terminal`_" msgstr "" -#: ../../faq.rst:283 +#: ../../faq.rst:279 msgid "`spyder-notebook`_" msgstr "" -#: ../../faq.rst:284 +#: ../../faq.rst:280 msgid "`spyder-memory-profiler`_" msgstr "" -#: ../../faq.rst:285 +#: ../../faq.rst:281 msgid "`spyder-line-profiler`_" msgstr "" -#: ../../faq.rst:297 -msgid "" -"Check the option :guilabel:`Remove all variables before execution` in the" -" :guilabel:`Configuration per file...` dialog under the :guilabel:`Run` " -"menu." +#: ../../faq.rst +msgid "Q: How do I clear all variables before executing my code?" msgstr "" -#: ../../faq.rst:306 -msgid "" -"Select the appropriate option in the :guilabel:`Configuration per " -"file...` dialog under the :guilabel:`Run` menu." +#: ../../faq.rst:293 +msgid "Check the option :guilabel:`Remove all variables before execution` in the :guilabel:`Configuration per file...` dialog under the :guilabel:`Run` menu." msgstr "" -#: ../../faq.rst:315 -msgid "" -"Go to :guilabel:`Preferences` and select the theme you want under " -":guilabel:`Syntax highlighting theme` in the :guilabel:`Appearance` " -"section." +#: ../../faq.rst +msgid "Q: How do I run my code in a dedicated console or an external system terminal?" +msgstr "" + +#: ../../faq.rst:302 +msgid "Select the appropriate option in the :guilabel:`Configuration per file...` dialog under the :guilabel:`Run` menu." +msgstr "" + +#: ../../faq.rst +msgid "Q: How do I change the syntax highlighting theme in the Editor?" msgstr "" -#: ../../faq.rst:324 +#: ../../faq.rst:311 +msgid "Go to :guilabel:`Preferences` and select the theme you want under :guilabel:`Syntax highlighting theme` in the :guilabel:`Appearance` section." +msgstr "" + +#: ../../faq.rst:320 msgid "Troubleshooting" msgstr "" -#: ../../faq.rst:329 -msgid "" -"You should first follow the steps in our :doc:`troubleshooting " -"guide`. If you can't solve your problem, " -"open an issue by following the instructions in our " -":doc:`/troubleshooting/submit-a-report` section." +#: ../../faq.rst +msgid "Q: I've found a bug or issue with Spyder. What do I do?" msgstr "" -#: ../../faq.rst:336 -msgid "" -"First, make sure the error you are seeing is not a bug in your code. To " -"confirm this, try running it in any standard Python interpreter. If the " -"error still occurs, the problem is likely with your code and a site like " -"`Stack Overflow`_ might be the best place to start. Otherwise, start at " -"the :doc:`/troubleshooting/basic-first-aid` section of our " -"troubleshooting guide." +#: ../../faq.rst:325 +msgid "You should first follow the steps in our :doc:`troubleshooting guide`. If you can't solve your problem, open an issue by following the instructions in our :doc:`/troubleshooting/submit-a-report` section." msgstr "" -#: ../../faq.rst:347 -msgid "" -"If nothing is displayed in the calltip, hover hint or :doc:`/panes/help` " -"pane, make sure the object you are inspecting has a docstring, and try " -"executing your code in the :doc:`/panes/ipythonconsole` to get help and " -"completions there. If this doesn't work, try restarting PyLS by right-" -"clicking the :guilabel:`LSP Python` label item in the statusbar at the " -"bottom of Spyder's main window, and selecting the :guilabel:`Restart " -"Python Language Server` option." +#: ../../faq.rst +msgid "Q: I get an error in the IPython console running my code! Help!" msgstr "" -#: ../../faq.rst:350 -msgid "" -"For more information, go to the :ref:`code-completion-problems-ref` " -"section in the :doc:`/troubleshooting/common-illnesses` page of our " -"troubleshooting guide." +#: ../../faq.rst:332 +msgid "First, make sure the error you are seeing is not a bug in your code. To confirm this, try running it in any standard Python interpreter. If the error still occurs, the problem is likely with your code and a site like `Stack Overflow`_ might be the best place to start. Otherwise, start at the :doc:`/troubleshooting/basic-first-aid` section of our troubleshooting guide." msgstr "" -#: ../../faq.rst:356 -msgid "" -"First, make sure your version of Spyder-Kernels is compatible with that " -"of Spyder. See the table in the :ref:`spyder-kernels-version-ref` section" -" of the troubleshooting guide to check." +#: ../../faq.rst +msgid "Q: Code completion/help doesn't work; what can I do?" msgstr "" -#: ../../faq.rst:359 -msgid "" -"To install the right version, type the following on the command line (or " -"Anaconda Prompt on Windows)" +#: ../../faq.rst:343 +msgid "If nothing is displayed in the calltip, hover hint or :doc:`/panes/help` pane, make sure the object you are inspecting has a docstring, and try executing your code in the :doc:`/panes/ipythonconsole` to get help and completions there. If this doesn't work, try restarting PyLS by right-clicking the :guilabel:`LSP Python` label item in the statusbar at the bottom of Spyder's main window, and selecting the :guilabel:`Restart Python Language Server` option." msgstr "" -#: ../../faq.rst:365 -msgid "" -"For more information, go to the :ref:`starting-kernel-problems-ref` " -"section in the :doc:`/troubleshooting/common-illnesses` page of our " -"troubleshooting guide." +#: ../../faq.rst:346 +msgid "For more information, go to the :ref:`code-completion-problems-ref` section in the :doc:`/troubleshooting/common-illnesses` page of our troubleshooting guide." msgstr "" -#: ../../faq.rst:371 -msgid "" -"Spyder is in the final stages of being updated for full compatibility " -"with macOS 11 Big Sur, which will be released by the end of 2020 as part " -"of version 4.2.1. However, you can get it working right now with the " -"workaround below. Make sure you have the Anaconda or Miniconda " -"distribution installed, and run the following commands in the Terminal to" -" install Spyder from Conda-Forge in a clean environment:" +#: ../../faq.rst +msgid "Q: I get the message \"An error occurred while starting the kernel\". How do I fix this?" msgstr "" -#: ../../faq.rst:381 -msgid "" -"Then, whenever you want to start Spyder, run the following from the " -"Terminal:" +#: ../../faq.rst:352 +msgid "First, make sure your version of Spyder-Kernels is compatible with that of Spyder. See the table in the :ref:`spyder-kernels-version-ref` section of the troubleshooting guide to check." +msgstr "" + +#: ../../faq.rst:355 +msgid "To install the right version, type the following on the command line (or Anaconda Prompt on Windows)" +msgstr "" + +#: ../../faq.rst:361 +msgid "For more information, go to the :ref:`starting-kernel-problems-ref` section in the :doc:`/troubleshooting/common-illnesses` page of our troubleshooting guide." msgstr "" -#: ../../faq.rst:393 +#: ../../faq.rst +msgid "Q: Spyder doesn't launch or is slow on macOS Big Sur. How can I get it working?" +msgstr "" + +#: ../../faq.rst:367 +msgid "Spyder is in the final stages of being updated for full compatibility with macOS 11 Big Sur, which will be released by the end of 2020 as part of version 4.2.1. However, you can get it working right now with the workaround below. Make sure you have the Anaconda or Miniconda distribution installed, and run the following commands in the Terminal to install Spyder from Conda-Forge in a clean environment:" +msgstr "" + +#: ../../faq.rst:377 +msgid "Then, whenever you want to start Spyder, run the following from the Terminal:" +msgstr "" + +#: ../../faq.rst:389 msgid "About Spyder" msgstr "" -#: ../../faq.rst:398 +#: ../../faq.rst +msgid "Q: What's Spyder's licensing situation? Is commercial use allowed?" +msgstr "" + +#: ../../faq.rst:394 #, python-format -msgid "" -"Spyder is 100% free and open source; there is no paid version or " -"prohibition on commercial use. It is developed by its international user " -"community, and supported by its users through `OpenCollective`_ and by " -"its generous sponsoring organizations, including `Quansight`_ and " -"`NumFOCUS`_. Our source code, standalone installers and most of our " -"distribution methods (Pip/PyPI, Linux distros, MacPorts, WinPython, etc) " -"can be freely redistributed, used and modified by anyone, for any " -"purpose, including commercial use. For more details about the situation " -"with Anaconda, see `that question`_." -msgstr "" - -#: ../../faq.rst:412 +msgid "Spyder is 100% free and open source; there is no paid version or prohibition on commercial use. It is developed by its international user community, and supported by its users through `OpenCollective`_ and by its generous sponsoring organizations, including `Quansight`_ and `NumFOCUS`_. Our source code, standalone installers and most of our distribution methods (Pip/PyPI, Linux distros, MacPorts, WinPython, etc) can be freely redistributed, used and modified by anyone, for any purpose, including commercial use. For more details about the situation with Anaconda, see `that question`_." +msgstr "" + +#: ../../faq.rst +msgid "Q: What do the Anaconda licensing changes mean for Spyder?" +msgstr "" + +#: ../../faq.rst:408 #, python-format -msgid "" -"If you use Spyder with the Anaconda distribution, they `recently " -"changed`_ their `Terms of Service`_ to add restrictions on large (> 200 " -"employee) for-profit companies using Anaconda on a large scale. However, " -"these terms only apply to the package infrastructure (the full Anaconda " -"distribution and the ``defaults`` conda channel). Instead, you can simply" -" download the similar `Miniforge distribution`_, which is 100% open " -"source and identical to full Anaconda (aside from not bundling the Python" -" packages installed by default in the Anaconda ``base`` environment, " -"which we recommend you avoid using anyway given any problems here can " -"break your whole installation). Then, simply install the packages you " -"need (including Spyder, if you aren't using our recommended :ref" -":`install-standalone`) with ``conda`` as you usually do. Miniforge will " -"automatically use the community-maintained Conda-Forge repository, which " -"has a much wider variety of packages and is generally more up to date " -"than the Anaconda equivalent, in addition to being free of any commercial" -" restrictions. For more, see our :doc:`/installation`." +msgid "If you use Spyder with the Anaconda distribution, they `recently changed`_ their `Terms of Service`_ to add restrictions on large (> 200 employee) for-profit companies using Anaconda on a large scale. However, these terms only apply to the package infrastructure (the full Anaconda distribution and the ``defaults`` conda channel). Instead, you can simply download the similar `Miniforge distribution`_, which is 100% open source and identical to full Anaconda (aside from not bundling the Python packages installed by default in the Anaconda ``base`` environment, which we recommend you avoid using anyway given any problems here can break your whole installation). Then, simply install the packages you need (including Spyder, if you aren't using our recommended :ref:`install-standalone`) with ``conda`` as you usually do. Miniforge will automatically use the community-maintained Conda-Forge repository, which has a much wider variety of packages and is generally more up to date than the Anaconda equivalent, in addition to being free of any commercial restrictions. For more, see our :doc:`/installation`." msgstr "" diff --git a/doc/locales/en/LC_MESSAGES/index.po b/doc/locales/en/LC_MESSAGES/index.po index e72e5efd..a671f341 100644 --- a/doc/locales/en/LC_MESSAGES/index.po +++ b/doc/locales/en/LC_MESSAGES/index.po @@ -8,22 +8,18 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" -#: ../../index.rst:137 -msgid "Welcome" -msgstr "" - -#: ../../index.rst:137 +#: ../../index.rst:153 msgid "FAQ" msgstr "" @@ -31,14 +27,12 @@ msgstr "" msgid "Welcome to Spyder's Documentation" msgstr "" +#: ../../index.rst:5 +msgid "Screenshot of the Spyder main window, with the default panel layout" +msgstr "" + #: ../../index.rst:9 -msgid "" -"Spyder is a powerful scientific environment written in Python, for " -"Python, and designed by and for scientists, engineers and data analysts. " -"It features a unique combination of the advanced editing, analysis, " -"debugging, and profiling functionality of a comprehensive development " -"tool with the data exploration, interactive execution, deep inspection, " -"and beautiful visualization capabilities of a scientific package." +msgid "Spyder is a powerful scientific environment written in Python, for Python, and designed by and for scientists, engineers and data analysts. It features a unique combination of the advanced editing, analysis, debugging, and profiling functionality of a comprehensive development tool with the data exploration, interactive execution, deep inspection, and beautiful visualization capabilities of a scientific package." msgstr "" #: ../../index.rst:18 @@ -46,109 +40,74 @@ msgid "Where to go now?" msgstr "" #: ../../index.rst:20 -msgid "" -"Spyder's documentation provides a variety of resources that will help you" -" learn how to use the application and explore each one of its panes. " -"These include video tutorials, in-depth descriptions and how-to guides " -"covering a wide range of needs and experience levels with Spyder." +msgid "Spyder's documentation provides a variety of resources that will help you learn how to use the application and explore each one of its panes. These include video tutorials, in-depth descriptions and how-to guides covering a wide range of needs and experience levels with Spyder." msgstr "" -#: ../../index.rst:33 -msgid "" -"If you are looking for a summary of its features and interface, check out" -" the :doc:`quickstart`." +#: ../../index.rst:34 +msgid "If you are looking for a summary of its features and interface, check out the :doc:`quickstart`." msgstr "" -#: ../../index.rst:41 -msgid "" -"If you don't have Spyder installed and want to get started, follow the " -":doc:`/installation`." +#: ../../index.rst:45 +msgid "If you don't have Spyder installed and want to get started, follow the :doc:`/installation`." msgstr "" -#: ../../index.rst:49 -msgid "" -"If you are completely new to Spyder, watch our basic tutorial series, " -":doc:`videos/first-steps-with-spyder`." +#: ../../index.rst:56 +msgid "If you are completely new to Spyder, watch our basic tutorial series, :doc:`videos/first-steps-with-spyder`." msgstr "" -#: ../../index.rst:57 -msgid "" -"If you are familiar with Spyder and want to explore the functionality of " -"its panes in more detail, go to :doc:`panes/index`." +#: ../../index.rst:67 +msgid "If you are familiar with Spyder and want to explore the functionality of its panes in more detail, go to :doc:`panes/index`." msgstr "" -#: ../../index.rst:65 -msgid "" -"If you've run into a Spyder problem and need help solving it, take a look" -" at our :doc:`troubleshooting guide`." +#: ../../index.rst:78 +msgid "If you've run into a Spyder problem and need help solving it, take a look at our :doc:`troubleshooting guide`." msgstr "" -#: ../../index.rst:73 +#: ../../index.rst:89 msgid "If you have a question about Spyder, visit the :doc:`faq` section." msgstr "" -#: ../../index.rst:81 +#: ../../index.rst:97 msgid "Join our community" msgstr "" -#: ../../index.rst:83 -msgid "" -"Spyder is open source software, which means that is free for everyone to " -"use and anyone can contribute to it. We encourage everyone to become a " -"part of our community and help develop Spyder!" +#: ../../index.rst:99 +msgid "Spyder is open source software, which means that is free for everyone to use and anyone can contribute to it. We encourage everyone to become a part of our community and help develop Spyder!" msgstr "" -#: ../../index.rst:90 +#: ../../index.rst:106 msgid "Looking to contribute your code?" msgstr "" -#: ../../index.rst:92 -msgid "" -"Spyder is written in the same Python language that you use it to develop," -" so its easy to get started contributing to it. You can follow our " -"`contributing guide`_ to set up a development environment, and you can " -"get involved with the project through our `Github repository`_. The " -"easiest way to get started is helping us resolve items on our `issue " -"tracker`_, either by fixing bugs in Spyder, or helping users troubleshoot" -" their problems (which doesn't require writing any code)." +#: ../../index.rst:108 +msgid "Spyder is written in the same Python language that you use it to develop, so its easy to get started contributing to it. You can follow our `contributing guide`_ to set up a development environment, and you can get involved with the project through our `Github repository`_. The easiest way to get started is helping us resolve items on our `issue tracker`_, either by fixing bugs in Spyder, or helping users troubleshoot their problems (which doesn't require writing any code)." msgstr "" -#: ../../index.rst:106 +#: ../../index.rst:122 msgid "Want to help writing docs?" msgstr "" -#: ../../index.rst:108 -msgid "" -"We welcome your contributions of corrections, additions and enhancements " -"to these docs. Check out the `docs contributing guide`_ to learn how to " -"submit a PR with your changes on our `docs repo`_." +#: ../../index.rst:124 +msgid "We welcome your contributions of corrections, additions and enhancements to these docs. Check out the `docs contributing guide`_ to learn how to submit a PR with your changes on our `docs repo`_." msgstr "" -#: ../../index.rst:119 +#: ../../index.rst:135 msgid "Interested in translating Spyder?" msgstr "" -#: ../../index.rst:121 -msgid "" -"In order to reach more users around the world in need of a powerful " -"scientific Python environment, we welcome your help translating the " -"documentation and the interface into different languages." +#: ../../index.rst:137 +msgid "In order to reach more users around the world in need of a powerful scientific Python environment, we welcome your help translating the documentation and the interface into different languages." msgstr "" -#: ../../index.rst:123 -msgid "" -"For this purpose we use `Crowdin`_, which provides a simple web based " -"interface for translators, proofreaders and managers, so everyone can " -"help us translate Spyder into any language." +#: ../../index.rst:139 +msgid "For this purpose we use `Crowdin`_, which provides a simple web based interface for translators, proofreaders and managers, so everyone can help us translate Spyder into any language." msgstr "" -#: ../../index.rst:131 +#: ../../index.rst:147 msgid "Want to be part of our social media?" msgstr "" -#: ../../index.rst:133 -msgid "" -"Connect with Spyder through our social media channels to stay up to date " -"with our current developments!" +#: ../../index.rst:149 +msgid "Connect with Spyder through our social media channels to stay up to date with our current developments!" msgstr "" diff --git a/doc/locales/en/LC_MESSAGES/installation.po b/doc/locales/en/LC_MESSAGES/installation.po index d1937f37..5fe8230d 100644 --- a/doc/locales/en/LC_MESSAGES/installation.po +++ b/doc/locales/en/LC_MESSAGES/installation.po @@ -8,46 +8,31 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" #: ../../installation.rst:5 -msgid "Installation Guide" +msgid "Install Guide" msgstr "" #: ../../installation.rst:7 -msgid "" -"Spyder is relatively easy to install on Windows, Linux and macOS. Just " -"make sure to read and follow these instructions with care." +msgid "Spyder is relatively easy to install on Windows, Linux and macOS. Just make sure to read and follow these instructions with care." msgstr "" #: ../../installation.rst:10 -msgid "" -"If you run into problems, before posting a report, *please* consult our " -"comprehensive :doc:`troubleshooting guide` " -"and search the `issue tracker`_ for your error message and problem " -"description. These methods generally fix or isolate the great majority of" -" install-related difficulties. Thanks!" +msgid "If you run into problems, before posting a report, *please* consult our comprehensive :doc:`troubleshooting guide` and search the `issue tracker`_ for your error message and problem description. These methods generally fix or isolate the great majority of install-related difficulties. Thanks!" msgstr "" #: ../../installation.rst:18 -msgid "" -"For most users on Windows and macOS, we recommend our :ref:`install-" -"standalone` as the most straightforward and robust option to obtain " -"Spyder. For users needing Linux support, third-party Spyder plugins or " -"Variable Explorer compatibility with custom-installed packages—all " -"capabilities which the standalone installers currently do not yet " -"provide—we advise using a :ref:`install-conda`. Linux, plugin and " -"package/environment management support in the standalone installers are " -"currently under active development for future Spyder versions." +msgid "For most users on Windows and macOS, we recommend our :ref:`install-standalone` as the most straightforward and robust option to obtain Spyder. For users needing Linux support, third-party Spyder plugins or Variable Explorer compatibility with custom-installed packages—all capabilities which the standalone installers currently do not yet provide—we advise using a :ref:`install-conda`. Linux, plugin and package/environment management support in the standalone installers are currently under active development for future Spyder versions." msgstr "" #: ../../installation.rst:27 @@ -55,11 +40,11 @@ msgid "Try Spyder online" msgstr "" #: ../../installation.rst:29 -msgid "" -"Want to try out Spyder without installing it? With `Binder`_ you can work" -" with a fully functional copy of Spyder online that runs right in your " -"web browser, no installation needed. Visit the `Spyder Binder`_ to get " -"started using Spyder." +msgid "Want to try out Spyder without installing it? With `Binder`_ you can work with a fully functional copy of Spyder online that runs right in your web browser, no installation needed. Visit the `Spyder Binder`_ to get started using Spyder." +msgstr "" + +#: ../../installation.rst:36 +msgid "Spyder running on Binder" msgstr "" #: ../../installation.rst:45 @@ -67,34 +52,15 @@ msgid "Standalone installers" msgstr "" #: ../../installation.rst:47 -msgid "" -"The standalone installers are our recommended method for most users on " -"Windows and macOS, with experimental Linux support under active " -"development. They work like any other IDE, where Spyder can be installed " -"and updated independently of the Python environments you use to run your " -"code. This avoids the problems with incompatible packages and broken " -"installations users often face when mixing Spyder with the (Conda, etc) " -"environments they use to run their code." +msgid "The standalone installers are our recommended method for most users on Windows and macOS, with experimental Linux support under active development. They work like any other IDE, where Spyder can be installed and updated independently of the Python environments you use to run your code. This avoids the problems with incompatible packages and broken installations users often face when mixing Spyder with the (Conda, etc) environments they use to run their code." msgstr "" #: ../../installation.rst:51 -msgid "" -"The installers include a built-in Python environment with the most common" -" scientific libraries (e.g. NumPy, Pandas, Matpotlib, etc), which can be " -"used out of the box for basic data analysis tasks. However, to manage " -"your own packages and environments, you'll currently need to connect an " -"external Python distribution (such as `Anaconda`_, `Miniconda`_, " -"`Miniforge/Mambaforge`_, `WinPython`_ or `Python.org `__) to " -"your standalone copy of Spyder. For more information on this, see our " -":ref:`FAQ entry on the subject `." +msgid "The installers include a built-in Python environment with the most common scientific libraries (e.g. NumPy, Pandas, Matpotlib, etc), which can be used out of the box for basic data analysis tasks. However, to manage your own packages and environments, you'll currently need to connect an external Python distribution (such as `Anaconda`_, `Miniconda`_, `Miniforge/Mambaforge`_, `WinPython`_ or `Python.org `__) to your standalone copy of Spyder. For more information on this, see our :ref:`FAQ entry on the subject `." msgstr "" #: ../../installation.rst:57 -msgid "" -"The standalone installers do not yet support installing third-party " -"Spyder plugins not already bundled with them, though this feature is " -"currently under development. For now, if you need this capability, we " -"recommend a :ref:`install-conda`." +msgid "The standalone installers do not yet support installing third-party Spyder plugins not already bundled with them, though this feature is currently under development. For now, if you need this capability, we recommend a :ref:`install-conda`." msgstr "" #: ../../installation.rst:64 @@ -102,495 +68,354 @@ msgid "Downloading and installing" msgstr "" #: ../../installation.rst:66 -msgid "" -"To download the supported Spyder installer for your platform, simply " -"click the appropriate link below (for Linux, see the :ref:`install-conda`" -" section). Then, double-click the downloaded file to open the installer. " -"If a security warning pops up, you may need to click :guilabel:`Yes`, " -":guilabel:`OK`, :guilabel:`Open`, :guilabel:`Allow` or similar." +msgid "To download the supported Spyder installer for your platform, simply click the appropriate link below (for Linux, see the :ref:`install-conda` section). Then, double-click the downloaded file to open the installer. If a security warning pops up, you may need to click :guilabel:`Yes`, :guilabel:`OK`, :guilabel:`Open`, :guilabel:`Allow` or similar." msgstr "" #: ../../installation.rst:70 -msgid "" -"On Windows, if a \"SmartScreen\" dialog appears, click :guilabel:`More " -"info` followed by :guilabel:`Run anyway`, and then proceed through the " -"steps in the installer." +msgid "On Windows, if a \"SmartScreen\" dialog appears, click :guilabel:`More info` followed by :guilabel:`Run anyway`, and then proceed through the steps in the installer." msgstr "" #: ../../installation.rst:72 -msgid "" -"On macOS, open the disk image and drag Spyder to your " -":guilabel:`Applications` folder." +msgid "On macOS, open the disk image and drag Spyder to your :guilabel:`Applications` folder." msgstr "" #: ../../installation.rst:79 -msgid "`Windows Installer`_" +msgid "`Windows`_" msgstr "" #: ../../installation.rst:79 -msgid "`macOS Installer`_" +msgid "`macOS M1`_" msgstr "" -#: ../../installation.rst:87 -msgid "" -"\"Lite\" versions of both installers are also available from the " -"`releases page`_, which are somewhat smaller than the full installers. " -"These lack a number of optional but recommended dependencies, such as " -"NumPy, SciPy and Pandas, meaning that a few " -":doc:`/panes/variableexplorer` features, including graphical data import " -"wizards and support for rich display and editing of NumPy arrays and " -"Pandas DataFrames, will not be available. Given this only saves a modest " -"amount of space while missing out on significant features, we recommend " -"using the full installers unless minimizing download/install size and " -"memory usage is a priority." -msgstr "" - -#: ../../installation.rst:97 -msgid "Running from a standalone install" +#: ../../installation.rst:79 +msgid "`macOS Intel`_" +msgstr "" + +#: ../../installation.rst:79 +msgid "`Linux`_" +msgstr "" + +#: ../../installation.rst:89 +msgid "\"Lite\" versions of both installers are also available from the `releases page`_, which are somewhat smaller than the full installers. These lack a number of optional but recommended dependencies, such as NumPy, SciPy and Pandas, meaning that a few :doc:`/panes/variableexplorer` features, including graphical data import wizards and support for rich display and editing of NumPy arrays and Pandas DataFrames, will not be available. Given this only saves a modest amount of space while missing out on significant features, we recommend using the full installers unless minimizing download/install size and memory usage is a priority." msgstr "" #: ../../installation.rst:99 -msgid "" -"To run Spyder when installed standalone, you can simply use your " -"operating system's typical method of launching applications, such as " -"opening it from the :guilabel:`Start` menu on Windows (or the Taskbar, if" -" you've pinned it there), or from Launchpad, Spotlight or the " -":guilabel:`Applications` folder on macOS (or the Dock, if you've added it" -" there)." +msgid "Running from a standalone install" msgstr "" -#: ../../installation.rst:105 -msgid "Updating a standalone install" +#: ../../installation.rst:101 +msgid "To run Spyder when installed standalone, you can simply use your operating system's typical method of launching applications, such as opening it from the :guilabel:`Start` menu on Windows (or the Taskbar, if you've pinned it there), or from Launchpad, Spotlight or the :guilabel:`Applications` folder on macOS (or the Dock, if you've added it there)." msgstr "" #: ../../installation.rst:107 -msgid "" -"By default, Spyder checks for updates automatically on startup, and you " -"can also check manually with :menuselection:`Help --> Check for updates`." -" The standalone installers for Spyder 5.4.0+ include update functionality" -" built right into Spyder, which after checking for updates will display a" -" prompt to automatically download and install the current version. On " -"earlier versions, you'll need to manually download and install the latest" -" release (if on Windows, make sure to remove the old version first from " -"Control Panel/System Settings)." +msgid "Updating a standalone install" msgstr "" -#: ../../installation.rst:117 -msgid "Conda-based distributions" +#: ../../installation.rst:109 +msgid "By default, Spyder checks for updates automatically on startup, and you can also check manually with :menuselection:`Help --> Check for updates`. The standalone installers for Spyder 5.4.0+ include update functionality built right into Spyder, which after checking for updates will display a prompt to automatically download and install the current version. On earlier versions, you'll need to manually download and install the latest release (if on Windows, make sure to remove the old version first from Control Panel/System Settings)." msgstr "" #: ../../installation.rst:119 -msgid "" -"Spyder is included by default in the `Anaconda`_ Python distribution, " -"which comes with everything you need to get started in an all-in-one " -"package. It can also be easily installed in the much lighter-weight " -"`Miniconda`_ and `Miniforge/Mambaforge`_, which include just Python and " -"the Conda/Mamba package and environment manager by default (with " -"Miniforge defaulting to the Conda-Forge channel, and Mambaforge using " -"Mamba, a much faster alternative to Conda). This is our recommended " -"installation method on Linux and for users with third-party Spyder " -"plugins, as support for both of these in our standalone installers is " -"still under active development." -msgstr "" - -#: ../../installation.rst:131 -msgid "Conda environment" +msgid "Conda-based distributions" +msgstr "" + +#: ../../installation.rst:121 +msgid "Spyder is included by default in the `Anaconda`_ Python distribution, which comes with everything you need to get started in an all-in-one package. It can also be easily installed in the much lighter-weight `Miniconda`_ and `Miniforge/Mambaforge`_, which include just Python and the Conda/Mamba package and environment manager by default (with Miniforge defaulting to the Conda-Forge channel, and Mambaforge using Mamba, a much faster alternative to Conda). This is our recommended installation method on Linux and for users with third-party Spyder plugins, as support for both of these in our standalone installers is still under active development." msgstr "" #: ../../installation.rst:133 -msgid "" -"With Miniconda/Miniforge/Mambaforge, or to get a more reliable and up-to-" -"date Spyder version with Anaconda, we strongly recommend installing " -"Spyder into its own dedicated Conda environment." +msgid "Conda environment" msgstr "" -#: ../../installation.rst:137 -msgid "" -"If using Mamba/Mambaforge, substitute ``mamba`` for ``conda`` in the " -"following commands." +#: ../../installation.rst:135 +msgid "With Miniconda/Miniforge/Mambaforge, or to get a more reliable and up-to-date Spyder version with Anaconda, we strongly recommend installing Spyder into its own dedicated Conda environment." msgstr "" -#: ../../installation.rst:143 -msgid "Installing with Conda" +#: ../../installation.rst:139 +msgid "If using Mamba/Mambaforge, substitute ``mamba`` for ``conda`` in the following commands." msgstr "" #: ../../installation.rst:145 -msgid "" -"For a full install of Spyder and all optional dependencies, run the " -"following command in your Anaconda Prompt (Windows) or terminal:" +msgid "Installing with Conda" msgstr "" -#: ../../installation.rst:151 -msgid "" -"For a minimal install without the optional functionality and integration " -"with the above packages, you can instead run:" +#: ../../installation.rst:147 +msgid "For a full install of Spyder and all optional dependencies, run the following command in your Anaconda Prompt (Windows) or terminal:" msgstr "" -#: ../../installation.rst:157 -msgid "" -"This installs Spyder into a new environment called ``spyder-env``, using " -"the more up-to-date, community-run Conda-Forge channel. To make sure " -"future installs/updates in this environment also use Conda-Forge and are " -"faster and more reliable, make sure to set it as your environment's " -"default channel with strict channel priority enabled, if this isn't the " -"case already (as it is with Miniforge/Mambaforge or if you've manually " -"configured it):" +#: ../../installation.rst:153 +msgid "For a minimal install without the optional functionality and integration with the above packages, you can instead run:" +msgstr "" + +#: ../../installation.rst:159 +msgid "This installs Spyder into a new environment called ``spyder-env``, using the more up-to-date, community-run Conda-Forge channel. To make sure future installs/updates in this environment also use Conda-Forge and are faster and more reliable, make sure to set it as your environment's default channel with strict channel priority enabled, if this isn't the case already (as it is with Miniforge/Mambaforge or if you've manually configured it):" msgstr "" -#: ../../installation.rst:166 +#: ../../installation.rst:168 msgid "Here's a summary of the main steps." msgstr "" -#: ../../installation.rst:175 -msgid "Running with Conda" +#: ../../installation.rst:170 +msgid "Running Spyder installation with conda" msgstr "" #: ../../installation.rst:177 -msgid "" -"You can then run Spyder by the same methods :ref:`as with Anaconda " -"`, except that you need to make sure to launch " -"the Start menu shortcut with ``(spyder-env)`` in the name, select the " -"``spyder-env`` environment on the left before launching it with " -"Navigator, or type ``conda activate spyder-env`` before launching it on " -"the command line." +msgid "Running with Conda" msgstr "" #: ../../installation.rst:179 -msgid "" -"See :ref:`our FAQ question ` for more " -"information about how to use Spyder with your existing Conda " -"environments." +msgid "You can then run Spyder by the same methods :ref:`as with Anaconda `, except that you need to make sure to launch the Start menu shortcut with ``(spyder-env)`` in the name, select the ``spyder-env`` environment on the left before launching it with Navigator, or type ``conda activate spyder-env`` before launching it on the command line." msgstr "" -#: ../../installation.rst:185 -msgid "Updating with Conda" +#: ../../installation.rst:181 +msgid "See :ref:`our FAQ question ` for more information about how to use Spyder with your existing Conda environments." msgstr "" #: ../../installation.rst:187 -msgid "" -"With any Conda-based distribution and Spyder installed in its own " -"environment (recommended), update Conda itself, active the environment, " -"and finally update Spyder. In your system terminal (or Anaconda Prompt if" -" on Windows), run:" +msgid "Updating with Conda" msgstr "" -#: ../../installation.rst:196 -msgid "" -"In case you get an error trying to update, just remove the existing " -"environment (if using one other than ``base``):" +#: ../../installation.rst:189 +msgid "With any Conda-based distribution and Spyder installed in its own environment (recommended), update Conda itself, active the environment, and finally update Spyder. In your system terminal (or Anaconda Prompt if on Windows), run:" +msgstr "" + +#: ../../installation.rst:198 +msgid "In case you get an error trying to update, just remove the existing environment (if using one other than ``base``):" msgstr "" -#: ../../installation.rst:202 +#: ../../installation.rst:204 msgid "And then :ref:`recreate a fresh one `." msgstr "" -#: ../../installation.rst:208 +#: ../../installation.rst:210 msgid "Anaconda base" msgstr "" -#: ../../installation.rst:210 -msgid "" -"While we recommend always using a dedicated environment, with Anaconda " -"you can also run the bundled copy of Spyder from the built-in ``base`` " -"environment." +#: ../../installation.rst:212 +msgid "While we recommend always using a dedicated environment, with Anaconda you can also run the bundled copy of Spyder from the built-in ``base`` environment." msgstr "" -#: ../../installation.rst:214 -msgid "" -"The bundled Spyder version can often be quite out of date, missing new " -"features and bug fixes from the latest version, and if you install, " -"change or remove other packages, there is a significant chance of " -"dependency conflicts or a broken Spyder installation. Therefore, we " -"recommend :ref:`installing Spyder into a new Conda environment ` to avoid all these issues." +#: ../../installation.rst:216 +msgid "The bundled Spyder version can often be quite out of date, missing new features and bug fixes from the latest version, and if you install, change or remove other packages, there is a significant chance of dependency conflicts or a broken Spyder installation. Therefore, we recommend :ref:`installing Spyder into a new Conda environment ` to avoid all these issues." msgstr "" -#: ../../installation.rst:221 +#: ../../installation.rst:223 msgid "Running with Anaconda" msgstr "" -#: ../../installation.rst:223 -msgid "" -"To run the bundled version of Spyder after installing it with Anaconda, " -"the recommended method on Windows is to launch it via the Start menu " -"shortcut. On other platforms, open Anaconda Navigator, scroll to Spyder " -"under :guilabel:`Home` and click :guilabel:`Launch`." +#: ../../installation.rst:225 +msgid "To run the bundled version of Spyder after installing it with Anaconda, the recommended method on Windows is to launch it via the Start menu shortcut. On other platforms, open Anaconda Navigator, scroll to Spyder under :guilabel:`Home` and click :guilabel:`Launch`." msgstr "" -#: ../../installation.rst:229 -msgid "" -"If Spyder does not start via this method or you prefer to use the command" -" line, open Anaconda Prompt (Windows) or your terminal (other platforms)," -" type ``conda activate base`` then ``spyder``." +#: ../../installation.rst:228 +msgid "Anaconda Navigator showing Spyder" msgstr "" -#: ../../installation.rst:235 -msgid "Updating with Anaconda" +#: ../../installation.rst:231 +msgid "If Spyder does not start via this method or you prefer to use the command line, open Anaconda Prompt (Windows) or your terminal (other platforms), type ``conda activate base`` then ``spyder``." msgstr "" #: ../../installation.rst:237 -msgid "" -"With Spyder installed in Anaconda's ``base`` environment, first update " -"the ``anaconda`` meta-package, and then Spyder itself (in case there is a" -" newer version than that pinned to the ``anaconda`` metapackage). In your" -" system terminal (or Anaconda Prompt if on Windows), run:" +msgid "Updating with Anaconda" msgstr "" -#: ../../installation.rst:247 -msgid "" -"These commands also update all your other packages, which is one reason " -"we strongly recommend you use an isolated conda environment to avoid any " -"potential unintended effects on other installed packages." +#: ../../installation.rst:239 +msgid "With Spyder installed in Anaconda's ``base`` environment, first update the ``anaconda`` meta-package, and then Spyder itself (in case there is a newer version than that pinned to the ``anaconda`` metapackage). In your system terminal (or Anaconda Prompt if on Windows), run:" msgstr "" #: ../../installation.rst:249 -msgid "" -"In case you get an error resolving dependencies, try uninstalling Spyder " -"and re-installing it:" +msgid "These commands also update all your other packages, which is one reason we strongly recommend you use an isolated conda environment to avoid any potential unintended effects on other installed packages." msgstr "" -#: ../../installation.rst:262 -msgid "Using pip" +#: ../../installation.rst:251 +msgid "In case you get an error resolving dependencies, try uninstalling Spyder and re-installing it:" msgstr "" -#: ../../installation.rst:266 -msgid "" -"While this installation method is a viable option for experienced users, " -"installing Spyder (and other PyData-stack packages) with pip can " -"sometimes lead to tricky issues, particularly on Windows and macOS. While" -" you are welcome to try it on your own, we are typically not able to " -"provide individual support for installation problems with pip, except to " -"recommend our :ref:`install-standalone` (Windows and macOS) or a :ref" -":`install-conda`." +#: ../../installation.rst:264 +msgid "Using pip" msgstr "" -#: ../../installation.rst:269 -msgid "" -"You can install Spyder with the pip package manager, which is included by" -" default with most Python installations. Before installing Spyder itself " -"by this method, you need to download the `Python`_ programming language." +#: ../../installation.rst:268 +msgid "While this installation method is a viable option for experienced users, installing Spyder (and other PyData-stack packages) with pip can sometimes lead to tricky issues, particularly on Windows and macOS. While you are welcome to try it on your own, we are typically not able to provide individual support for installation problems with pip, except to recommend our :ref:`install-standalone` (Windows and macOS) or a :ref:`install-conda`." msgstr "" -#: ../../installation.rst:276 -msgid "" -"Due to a known issue with some DEB-based Linux distributions (Debian, " -"Ubuntu, Mint), you might also need to install the ``pyqt5-dev-tools`` " -"package first, with ``sudo apt install pyqt5-dev-tools``." +#: ../../installation.rst:271 +msgid "You can install Spyder with the pip package manager, which is included by default with most Python installations. Before installing Spyder itself by this method, you need to download the `Python`_ programming language." msgstr "" #: ../../installation.rst:278 -msgid "" -"You'll first want to create and activate a virtual environment in which " -"to install Spyder, via one of the following methods." +msgid "Due to a known issue with some DEB-based Linux distributions (Debian, Ubuntu, Mint), you might also need to install the ``pyqt5-dev-tools`` package first, with ``sudo apt install pyqt5-dev-tools``." msgstr "" #: ../../installation.rst:280 +msgid "You'll first want to create and activate a virtual environment in which to install Spyder, via one of the following methods." +msgstr "" + +#: ../../installation.rst:282 msgid "With ``virtualenvwrapper``:" msgstr "" -#: ../../installation.rst:287 +#: ../../installation.rst:289 msgid "Otherwise, on macOS/Linux/Unix:" msgstr "" -#: ../../installation.rst:294 +#: ../../installation.rst:296 msgid "or on Windows:" msgstr "" -#: ../../installation.rst:301 -msgid "" -"After activating your environment, to install Spyder and its optional " -"dependencies, run:" +#: ../../installation.rst:303 +msgid "After activating your environment, to install Spyder and its optional dependencies, run:" msgstr "" -#: ../../installation.rst:307 +#: ../../installation.rst:309 msgid "Or for a minimal installation, run:" msgstr "" -#: ../../installation.rst:316 -msgid "" -"To launch Spyder after installing it, ensure your environment is " -"activated and run the ``spyder`` or ``spyder3`` command." +#: ../../installation.rst:315 +msgid "Running Spyder installation with pip" msgstr "" #: ../../installation.rst:318 -msgid "And to update Spyder, with your Spyder environment activated, run:" +msgid "To launch Spyder after installing it, ensure your environment is activated and run the ``spyder`` or ``spyder3`` command." msgstr "" -#: ../../installation.rst:330 -msgid "Alternative methods" +#: ../../installation.rst:320 +msgid "And to update Spyder, with your Spyder environment activated, run:" msgstr "" -#: ../../installation.rst:334 -msgid "" -"While we describe alternative Spyder installation options for users who " -"prefer them, as these are third-party distributions that we have no " -"direct involvement in, we are usually not able to offer useful individual" -" assistance for problems specific to installing via these alternative " -"methods." +#: ../../installation.rst:332 +msgid "Alternative methods" msgstr "" #: ../../installation.rst:336 -msgid "" -"Also, the Spyder versions they install may be out of date relative to the" -" current release, and thus be missing the latest features and bug fixes." +msgid "While we describe alternative Spyder installation options for users who prefer them, as these are third-party distributions that we have no direct involvement in, we are usually not able to offer useful individual assistance for problems specific to installing via these alternative methods." msgstr "" #: ../../installation.rst:338 -msgid "" -"Therefore, we recommend you switch to our :ref:`install-standalone` " -"(Windows and macOS) or a :ref:`install-conda` if you encounter " -"installation issues you are unable to solve on your own." +msgid "Also, the Spyder versions they install may be out of date relative to the current release, and thus be missing the latest features and bug fixes." msgstr "" -#: ../../installation.rst:344 -msgid "Windows" +#: ../../installation.rst:340 +msgid "Therefore, we recommend you switch to our :ref:`install-standalone` (Windows and macOS) or a :ref:`install-conda` if you encounter installation issues you are unable to solve on your own." msgstr "" #: ../../installation.rst:346 -msgid "" -"Spyder is included in the `WinPython`_ scientific Python distribution, " -"along with many other common numerical computing and data analysis " -"packages. You can use Spyder immediately after installing, similar to " -"Anaconda." +msgid "Windows" msgstr "" -#: ../../installation.rst:355 -msgid "macOS" +#: ../../installation.rst:348 +msgid "Spyder is included in the `WinPython`_ scientific Python distribution, along with many other common numerical computing and data analysis packages. You can use Spyder immediately after installing, similar to Anaconda." msgstr "" #: ../../installation.rst:357 +msgid "macOS" +msgstr "" + +#: ../../installation.rst:359 msgid "Spyder is available as `a cask`_ through `Homebrew`_." msgstr "" -#: ../../installation.rst:362 +#: ../../installation.rst:364 msgid "To install it using the ``brew`` package manager, run:" msgstr "" -#: ../../installation.rst:368 +#: ../../installation.rst:370 msgid "It is also available as a `a port`_ through `MacPorts`_." msgstr "" -#: ../../installation.rst:373 +#: ../../installation.rst:375 msgid "To install it using the ``port`` package manager, run:" msgstr "" -#: ../../installation.rst:383 +#: ../../installation.rst:385 msgid "Linux" msgstr "" -#: ../../installation.rst:385 -msgid "" -"Spyder can be installed via third-party distro packages on most common " -"Linux distributions." +#: ../../installation.rst:387 +msgid "Spyder can be installed via third-party distro packages on most common Linux distributions." msgstr "" -#: ../../installation.rst:387 -msgid "" -"Running Spyder installed this way will generally be the same as any other" -" distro-installed application. Alternatively, it can be launched from the" -" terminal with ``spyder`` (or ``spyder3``, on older versions of some " -"distros)." +#: ../../installation.rst:389 +msgid "Running Spyder installed this way will generally be the same as any other distro-installed application. Alternatively, it can be launched from the terminal with ``spyder`` (or ``spyder3``, on older versions of some distros)." msgstr "" -#: ../../installation.rst:394 +#: ../../installation.rst:396 msgid "Ubuntu/Debian" msgstr "" -#: ../../installation.rst:396 +#: ../../installation.rst:398 msgid "Spyder is available as `a Ubuntu package`_ and `a Debian package`_." msgstr "" -#: ../../installation.rst:401 +#: ../../installation.rst:403 msgid "To install it using the ``apt`` package manager, run:" msgstr "" -#: ../../installation.rst:411 +#: ../../installation.rst:413 msgid "Other distributions" msgstr "" -#: ../../installation.rst:413 +#: ../../installation.rst:415 msgid "Spyder is also available in other GNU/Linux distributions, including:" msgstr "" -#: ../../installation.rst:415 +#: ../../installation.rst:417 msgid "`Arch Linux`_" msgstr "" -#: ../../installation.rst:416 +#: ../../installation.rst:418 msgid "`Fedora`_" msgstr "" -#: ../../installation.rst:417 +#: ../../installation.rst:419 msgid "`Gentoo`_" msgstr "" -#: ../../installation.rst:418 +#: ../../installation.rst:420 msgid "`openSUSE`_" msgstr "" -#: ../../installation.rst:425 -msgid "" -"Please refer to the links or your distribution's documentation for how to" -" install Spyder." +#: ../../installation.rst:427 +msgid "Please refer to the links or your distribution's documentation for how to install Spyder." msgstr "" -#: ../../installation.rst:433 +#: ../../installation.rst:435 msgid "Development builds" msgstr "" -#: ../../installation.rst:435 -msgid "" -"If you want to try the next Spyder version before it is released, you " -"can! You may want to do this for fixing bugs in Spyder, adding new " -"features, learning how Spyder works or just getting a taste of what the " -"IDE can do. For more information, please see the `Contributing Guide`_ " -"included with the Spyder source or on Github, and for further detail " -"consult the `Spyder development wiki`_." +#: ../../installation.rst:437 +msgid "If you want to try the next Spyder version before it is released, you can! You may want to do this for fixing bugs in Spyder, adding new features, learning how Spyder works or just getting a taste of what the IDE can do. For more information, please see the `Contributing Guide`_ included with the Spyder source or on Github, and for further detail consult the `Spyder development wiki`_." msgstr "" -#: ../../installation.rst:450 +#: ../../installation.rst:452 msgid "Additional help" msgstr "" -#: ../../installation.rst:454 -msgid "" -"*Run in to a problem installing or running Spyder?* Read our " -"`Troubleshooting Guide and FAQ`_." +#: ../../installation.rst:456 +msgid "*Run in to a problem installing or running Spyder?* Read our :ref:`Troubleshooting Guide `." msgstr "" -#: ../../installation.rst:458 -msgid "" -"*Looking for general information about Spyder and its ecosystem?* See our" -" `main website`_." +#: ../../installation.rst:460 +msgid "*Looking for general information about Spyder and its ecosystem?* See our `main website`_." msgstr "" -#: ../../installation.rst:462 -msgid "" -"*Need to submit a bug report or feature request?* Check out our `Github " -"repository`_." +#: ../../installation.rst:464 +msgid "*Need to submit a bug report or feature request?* Check out our `Github repository`_." msgstr "" -#: ../../installation.rst:466 -msgid "" -"*Want development-oriented help and information?* Consult our `Github " -"wiki`_." +#: ../../installation.rst:468 +msgid "*Want development-oriented help and information?* Consult our `Github wiki`_." msgstr "" -#: ../../installation.rst:470 -msgid "" -"*Have a help request or discussion topic?* Subscribe to our `Google " -"Group`_." +#: ../../installation.rst:472 +msgid "*Have a help request or discussion topic?* Subscribe to our `Google Group`_." msgstr "" -#: ../../installation.rst:474 -msgid "" -"*Asking a quick question or want to chat with the dev team?* Stop by our " -"`Gitter chatroom`_." +#: ../../installation.rst:476 +msgid "*Asking a quick question or want to chat with the dev team?* Stop by our `Gitter chatroom`_." msgstr "" -#: ../../installation.rst:478 -msgid "" -"*Seeking personalized help from expert Spyder consultants?* Visit " -"`OpenTeams`_." +#: ../../installation.rst:480 +msgid "*Seeking personalized help from expert Spyder consultants?* Visit `OpenTeams`_." msgstr "" diff --git a/doc/locales/en/LC_MESSAGES/panes.po b/doc/locales/en/LC_MESSAGES/panes.po index 50872d36..a3c456cc 100644 --- a/doc/locales/en/LC_MESSAGES/panes.po +++ b/doc/locales/en/LC_MESSAGES/panes.po @@ -8,28 +8,27 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" #: ../../panes/debugging.rst:3 msgid "Debugger" msgstr "" #: ../../panes/debugging.rst:5 -msgid "" -"**Debugging** in Spyder is supported through integration with the " -"enhanced ``ipdb`` debugger in the :doc:`ipythonconsole`. This allows " -"breakpoints and the execution flow to be viewed and controlled right from" -" the Spyder GUI, as well as with all the familiar IPython console " -"commands." +msgid "**Debugging** in Spyder is supported through integration with the enhanced ``ipdb`` debugger in the :doc:`ipythonconsole`. This allows breakpoints and the execution flow to be viewed and controlled right from the Spyder GUI, as well as with all the familiar IPython console commands." +msgstr "" + +#: ../../panes/debugging.rst:8 +msgid "A Spyder IPython console window, showing the ipdb debugger in action" msgstr "" #: ../../panes/debugging.rst:15 @@ -37,45 +36,48 @@ msgid "Debugging with ipdb" msgstr "" #: ../../panes/debugging.rst:17 -msgid "" -"You can fully control debugger execution from the :guilabel:`Debug` menu," -" :guilabel:`Debug toolbar` and via configurable keyboard shortcuts, along" -" with the standard ``ipdb`` `console commands`_." +msgid "You can fully control debugger execution from the :guilabel:`Debug` menu, :guilabel:`Debug toolbar` and via configurable keyboard shortcuts, along with the standard ``ipdb`` `console commands`_." +msgstr "" + +#: ../../panes/debugging.rst:19 +msgid "A Spyder IPython console window, showing debugging from toolbar" msgstr "" #: ../../panes/debugging.rst:22 -msgid "" -"Additionally, the :doc:`editor` shows the line of code the debugger is " -"currently stopped on with an arrow." +msgid "Additionally, the :doc:`editor` shows the line of code the debugger is currently stopped on with an arrow." +msgstr "" + +#: ../../panes/debugging.rst:26 +msgid "Spyder Editor showing the debugging panel" msgstr "" #: ../../panes/debugging.rst:29 -msgid "" -"Spyder's debugger offers syntax highlighting, code completion and command" -" history, which work exactly like they do in the normal interactive " -"interpreter." +msgid "Spyder's debugger offers syntax highlighting, code completion and command history, which work exactly like they do in the normal interactive interpreter." msgstr "" #: ../../panes/debugging.rst:31 -msgid "" -"Use the up and down arrows to recall previous commands, and press " -":kbd:`Tab` to trigger autocomplete suggestions." +msgid "Use the up and down arrows to recall previous commands, and press :kbd:`Tab` to trigger autocomplete suggestions." +msgstr "" + +#: ../../panes/debugging.rst:33 +msgid "A Spyder IPython console window, showing autocompletion when debugging" msgstr "" #: ../../panes/debugging.rst:36 #, python-format -msgid "" -"Furthermore, IPython's `magic functions`_ are available in debugging " -"mode. You can, for example, run ``%ls`` to list the contents of your " -"current working directory or ``%timeit`` to check how fast a given " -"snippet of code is." +msgid "Furthermore, IPython's `magic functions`_ are available in debugging mode. You can, for example, run ``%ls`` to list the contents of your current working directory or ``%timeit`` to check how fast a given snippet of code is." +msgstr "" + +#: ../../panes/debugging.rst:41 +msgid "Ipython console in debug mode showing timeit magic" msgstr "" #: ../../panes/debugging.rst:44 -msgid "" -"Finally, you can enter and execute multiline statements in Spyder's " -"debugger just like with the regular IPython prompt, to easily run complex" -" code." +msgid "Finally, you can enter and execute multiline statements in Spyder's debugger just like with the regular IPython prompt, to easily run complex code." +msgstr "" + +#: ../../panes/debugging.rst:46 +msgid "Debugger showing multiline debugger" msgstr "" #: ../../panes/debugging.rst:54 @@ -83,11 +85,11 @@ msgid "Breakpoints" msgstr "" #: ../../panes/debugging.rst:56 -msgid "" -"Spyder's debugger is integrated with the :guilabel:`Breakpoints` pane, " -"which lists the file, line, and condition (if any) of every breakpoint " -"defined. To open it, select :menuselection:`Debug --> List breakpoints`, " -"or press :kbd:`Ctrl-Shift-B` (:kbd:`Cmd-Shift-B` on macOS)." +msgid "Spyder's debugger is integrated with the :guilabel:`Breakpoints` pane, which lists the file, line, and condition (if any) of every breakpoint defined. To open it, select :menuselection:`Debug --> List breakpoints`, or press :kbd:`Ctrl-Shift-B` (:kbd:`Cmd-Shift-B` on macOS)." +msgstr "" + +#: ../../panes/debugging.rst:59 +msgid "Spyder's Breakpoints panel, with a number of examples showing file, line number and an optional condition" msgstr "" #: ../../panes/debugging.rst:62 @@ -99,15 +101,11 @@ msgid "With the :guilabel:`Set/clear breakpoint` option in the Debug menu." msgstr "" #: ../../panes/debugging.rst:65 -msgid "" -"Through pressing the configurable keyboard shortcut (:kbd:`F12` for " -"normal, or :kbd:`Shift-F12` for conditional breakpoints by default)." +msgid "Through pressing the configurable keyboard shortcut (:kbd:`F12` for normal, or :kbd:`Shift-F12` for conditional breakpoints by default)." msgstr "" #: ../../panes/debugging.rst:66 -msgid "" -"By clicking to the left of the line number in an open file in the Editor " -"(adding :kbd:`Shift` for a conditional breakpoint)." +msgid "By clicking to the left of the line number in an open file in the Editor (adding :kbd:`Shift` for a conditional breakpoint)." msgstr "" #: ../../panes/debugging.rst:67 @@ -118,10 +116,16 @@ msgstr "" msgid "Interactively, using the ``b`` command in a debugging session." msgstr "" +#: ../../panes/debugging.rst:70 +msgid "Spyder showing setting conditional breakpoint" +msgstr "" + #: ../../panes/debugging.rst:73 -msgid "" -"You can access and edit local and global variables at each breakpoint " -"through the :doc:`variableexplorer`." +msgid "You can access and edit local and global variables at each breakpoint through the :doc:`variableexplorer`." +msgstr "" + +#: ../../panes/debugging.rst:75 +msgid "Spyder's console and variable explorer showing local and global variables when debugging" msgstr "" #: ../../panes/debugging.rst:82 @@ -129,30 +133,27 @@ msgid "Advanced features" msgstr "" #: ../../panes/debugging.rst:84 -msgid "" -"You can avoid stepping through other Python packages while debugging by " -"enabling the new :guilabel:`Ignore Python libraries while debugging` " -"option in Spyder's preferences, under :menuselection:`IPython Console -->" -" Debugger --> Debug`. This will skip all the built-in and third-party " -"Python modules you have installed." +msgid "You can avoid stepping through other Python packages while debugging by enabling the new :guilabel:`Ignore Python libraries while debugging` option in Spyder's preferences, under :menuselection:`IPython Console --> Debugger --> Debug`. This will skip all the built-in and third-party Python modules you have installed." +msgstr "" + +#: ../../panes/debugging.rst:87 +msgid "Spyder's preferences showing Ignore Python libraries while debugging options" msgstr "" #: ../../panes/debugging.rst:90 -msgid "" -"If your code has variables with the same names as Pdb commands (e.g. " -"``b`` or ``step``), you can still refer to them as normal while " -"debugging. To call the respective Pdb command, just add an exclamation " -"point before it (e.g. ``!b`` or ``!step``)." +msgid "If your code has variables with the same names as Pdb commands (e.g. ``b`` or ``step``), you can still refer to them as normal while debugging. To call the respective Pdb command, just add an exclamation point before it (e.g. ``!b`` or ``!step``)." +msgstr "" + +#: ../../panes/debugging.rst:93 +msgid "Spyder's IPython console showing Pdb commands" msgstr "" #: ../../panes/debugging.rst:96 -msgid "" -"You can have Spyder automatically execute a custom snippet of code every " -"time the debugger stops. For example, you can use this to set specific " -"variables, or import commonly-used modules so they are always available " -"while debugging. To set this up, go to :menuselection:`Preferences --> " -"IPython Console --> Debugger --> Run code while debugging`, and enter the" -" code that you want to be executed with each step." +msgid "You can have Spyder automatically execute a custom snippet of code every time the debugger stops. For example, you can use this to set specific variables, or import commonly-used modules so they are always available while debugging. To set this up, go to :menuselection:`Preferences --> IPython Console --> Debugger --> Run code while debugging`, and enter the code that you want to be executed with each step." +msgstr "" + +#: ../../panes/debugging.rst:100 +msgid "Spyder's preferenes with debugging snippet" msgstr "" #: ../../panes/debugging.rst:107 @@ -160,20 +161,15 @@ msgid "Matplotlib support" msgstr "" #: ../../panes/debugging.rst:109 -msgid "" -"Generating Matplotlib figures is fully supported while the debugger is " -"active, including all the different graphics backends. Use the " -"``%matplotlib`` magic to change to an interactive backend (e.g. " -"``%matplotlib qt5``) to pan, zoom and adjust your plots in a separate " -"window, or switch back to the default ``inline`` (``%matplotlib inline``)" -" to see them displayed right in the :doc:`plots` pane." +msgid "Generating Matplotlib figures is fully supported while the debugger is active, including all the different graphics backends. Use the ``%matplotlib`` magic to change to an interactive backend (e.g. ``%matplotlib qt5``) to pan, zoom and adjust your plots in a separate window, or switch back to the default ``inline`` (``%matplotlib inline``) to see them displayed right in the :doc:`plots` pane." +msgstr "" + +#: ../../panes/debugging.rst:112 +msgid "Debugger showing matplotlib interactive backend" msgstr "" #: ../../panes/debugging.rst:116 -msgid "" -"To avoid showing plots while debugging, deactivate the :guilabel:`Process" -" execute events while debugging` option in :menuselection:`Preferences " -"--> IPython console --> Debugger`." +msgid "To avoid showing plots while debugging, deactivate the :guilabel:`Process execute events while debugging` option in :menuselection:`Preferences --> IPython console --> Debugger`." msgstr "" #: ../../panes/debugging.rst:122 ../../panes/editor.rst:313 @@ -210,13 +206,11 @@ msgid "Editor" msgstr "" #: ../../panes/editor.rst:5 -msgid "" -"Spyder's multi-language **Editor** pane is the key element of the IDE, " -"where you can create, open, and modify source files. The Editor offers a " -"variety of core features, such as autocompletion, real-time analysis, " -"syntax highlighting, horizontal and vertical splitting, and much more. In" -" addition, it integrates a number of powerful tools for an easy to use, " -"efficient editing experience." +msgid "Spyder's multi-language **Editor** pane is the key element of the IDE, where you can create, open, and modify source files. The Editor offers a variety of core features, such as autocompletion, real-time analysis, syntax highlighting, horizontal and vertical splitting, and much more. In addition, it integrates a number of powerful tools for an easy to use, efficient editing experience." +msgstr "" + +#: ../../panes/editor.rst:9 +msgid "Spyder's Editor pane, split horizontally and with style analysis" msgstr "" #: ../../panes/editor.rst:16 @@ -227,12 +221,12 @@ msgstr "" msgid "The Editor pane consists of the following areas:" msgstr "" +#: ../../panes/editor.rst:20 +msgid "Spyder's Editor pane, showing its different areas (described below)" +msgstr "" + #: ../../panes/editor.rst:23 -msgid "" -"The left sidebar shows line numbers and displays any code analysis " -"warnings that exist in the current file. Clicking a line number selects " -"the text on that line, and clicking to the right of it sets a " -":ref:`breakpoint `." +msgid "The left sidebar shows line numbers and displays any code analysis warnings that exist in the current file. Clicking a line number selects the text on that line, and clicking to the right of it sets a :ref:`breakpoint `." msgstr "" #: ../../panes/editor.rst:25 @@ -240,28 +234,19 @@ msgid "The scrollbars allow vertical and horizontal navigation in a file." msgstr "" #: ../../panes/editor.rst:26 -msgid "" -"The context (right-click) menu displays actions relevant to whatever was " -"clicked." +msgid "The context (right-click) menu displays actions relevant to whatever was clicked." msgstr "" #: ../../panes/editor.rst:27 -msgid "" -"The options menu (\"Hamburger\" icon at top right) includes useful " -"settings and actions relevant to the Editor." +msgid "The options menu (\"Hamburger\" icon at top right) includes useful settings and actions relevant to the Editor." msgstr "" #: ../../panes/editor.rst:28 -msgid "" -"The location bar at the top of the Editor pane shows the full path of the" -" current file." +msgid "The location bar at the top of the Editor pane shows the full path of the current file." msgstr "" #: ../../panes/editor.rst:29 -msgid "" -"The tab bar displays the names of all opened files. It also has a " -":guilabel:`Browse tabs` button (at left) to show every open tab and " -"switch between them—which comes in handy if many are open." +msgid "The tab bar displays the names of all opened files. It also has a :guilabel:`Browse tabs` button (at left) to show every open tab and switch between them—which comes in handy if many are open." msgstr "" #: ../../panes/editor.rst:36 @@ -273,17 +258,19 @@ msgid "Tabs" msgstr "" #: ../../panes/editor.rst:41 -msgid "" -"You can browse and navigate between open files in the Editor with tabs. " -"Click the :guilabel:`Browse tabs` button on the left of the tab bar to " -"display a list of open files, with the active tab checked." +msgid "You can browse and navigate between open files in the Editor with tabs. Click the :guilabel:`Browse tabs` button on the left of the tab bar to display a list of open files, with the active tab checked." +msgstr "" + +#: ../../panes/editor.rst:44 +msgid "Spyder's Editor pane, showing the tabs browser" msgstr "" #: ../../panes/editor.rst:47 -msgid "" -"Reorder files by dragging and dropping, or with :guilabel:`Sort tabs " -"alphabetically` in the options menu, which also allows closing all tabs " -"to the right of, or all tabs but the active one." +msgid "Reorder files by dragging and dropping, or with :guilabel:`Sort tabs alphabetically` in the options menu, which also allows closing all tabs to the right of, or all tabs but the active one." +msgstr "" + +#: ../../panes/editor.rst:49 +msgid "Spyder's Editor pane, showing how to browse and sort open tabs alphabetically" msgstr "" #: ../../panes/editor.rst:54 @@ -291,18 +278,19 @@ msgid "File switcher" msgstr "" #: ../../panes/editor.rst:56 -msgid "" -"The Editor features a file switcher, which enables you to navigate and " -"switch between multiple open files. The file switcher is helpful for " -"locating any file when there are several files opened." +msgid "The Editor features a file switcher, which enables you to navigate and switch between multiple open files. The file switcher is helpful for locating any file when there are several files opened." +msgstr "" + +#: ../../panes/editor.rst:59 +msgid "Spyder's Editor pane, showing the file switcher" msgstr "" #: ../../panes/editor.rst:62 -msgid "" -"It can be accessed from the :menuselection:`File --> File Switcher` menu " -"or :kbd:`Ctrl-P`, and includes a search function. You can type in any " -"part of an open file's name and—if exists—it can be switched to by " -"pressing :kbd:`Enter`." +msgid "It can be accessed from the :menuselection:`File --> File Switcher` menu or :kbd:`Ctrl-P`, and includes a search function. You can type in any part of an open file's name and—if exists—it can be switched to by pressing :kbd:`Enter`." +msgstr "" + +#: ../../panes/editor.rst:65 +msgid "Spyder's Editor pane, showing searching and switching to an existing file" msgstr "" #: ../../panes/editor.rst:70 @@ -310,25 +298,19 @@ msgid "Split panels" msgstr "" #: ../../panes/editor.rst:72 -msgid "" -"The Editor can be split horizontally and vertically into as many distinct" -" panels as desired. This allows viewing and editing the contents of " -"several files (or different parts of the same file) at the same time." +msgid "The Editor can be split horizontally and vertically into as many distinct panels as desired. This allows viewing and editing the contents of several files (or different parts of the same file) at the same time." +msgstr "" + +#: ../../panes/editor.rst:75 +msgid "Spyder's Editor pane, showing how to split panels" msgstr "" #: ../../panes/editor.rst:78 -msgid "" -"Split the Editor with the :guilabel:`Split vertically` (:kbd:`Ctrl-" -"Shift-{`) and :guilabel:`Split horizontally` (:kbd:`Ctrl-Shift--`) " -"commands in the options menu, and use :guilabel:`Close this panel` (:kbd" -":`Alt-Shift-W`) to close the selected split panel." +msgid "Split the Editor with the :guilabel:`Split vertically` (:kbd:`Ctrl-Shift-{`) and :guilabel:`Split horizontally` (:kbd:`Ctrl-Shift--`) commands in the options menu, and use :guilabel:`Close this panel` (:kbd:`Alt-Shift-W`) to close the selected split panel." msgstr "" #: ../../panes/editor.rst:80 -msgid "" -":menuselection:`Close this panel` closes a split panel, while " -":menuselection:`Close` hides the entire Editor *pane* (including all " -"splits, which are restored when the Editor is re-opened)." +msgid ":menuselection:`Close this panel` closes a split panel, while :menuselection:`Close` hides the entire Editor *pane* (including all splits, which are restored when the Editor is re-opened)." msgstr "" #: ../../panes/editor.rst:86 @@ -340,27 +322,19 @@ msgid "Syntax highlighting" msgstr "" #: ../../panes/editor.rst:91 -msgid "" -"To improve the readability of your code, Spyder has a syntax highlighting" -" feature that determines the color and style of text in the Editor, as " -"well as in the :doc:`ipythonconsole`." +msgid "To improve the readability of your code, Spyder has a syntax highlighting feature that determines the color and style of text in the Editor, as well as in the :doc:`ipythonconsole`." msgstr "" #: ../../panes/editor.rst:93 -msgid "" -"You can configure and preview syntax highlighting themes and fonts under " -":menuselection:`Preferences --> Appearance`. The :guilabel:`Syntax " -"highlighting theme` section allows you to change the color and style of " -"the syntax elements and background to match your preferences. You can " -"switch between available themes in the drop-down menu, modify the " -"selected theme, create a new theme, and more. The :guilabel:`Fonts` " -"section lets you change the text font and size." +msgid "You can configure and preview syntax highlighting themes and fonts under :menuselection:`Preferences --> Appearance`. The :guilabel:`Syntax highlighting theme` section allows you to change the color and style of the syntax elements and background to match your preferences. You can switch between available themes in the drop-down menu, modify the selected theme, create a new theme, and more. The :guilabel:`Fonts` section lets you change the text font and size." +msgstr "" + +#: ../../panes/editor.rst:98 +msgid "Spyder's Editor pane, showing how to switch between syntax highlighting themes" msgstr "" #: ../../panes/editor.rst:101 -msgid "" -"Changes made to the syntax highlighting theme and font settings are " -"common to all source files, regardless of their language." +msgid "Changes made to the syntax highlighting theme and font settings are common to all source files, regardless of their language." msgstr "" #: ../../panes/editor.rst:105 @@ -368,12 +342,11 @@ msgid "Code cells" msgstr "" #: ../../panes/editor.rst:107 -msgid "" -"A \"code cell\" in Spyder is a block of lines, typically in a script, " -"that can be easily executed all at once in the current " -":doc:`ipythonconsole`. This is similar to \"cell\" behavior in Jupyter " -"Notebook and MATLAB. You can divide your scripts into as many cells as " -"needed, or none at all—the choice is yours." +msgid "A \"code cell\" in Spyder is a block of lines, typically in a script, that can be easily executed all at once in the current :doc:`ipythonconsole`. This is similar to \"cell\" behavior in Jupyter Notebook and MATLAB. You can divide your scripts into as many cells as needed, or none at all—the choice is yours." +msgstr "" + +#: ../../panes/editor.rst:111 +msgid "Spyder's Editor pane, showing an example of a code cell" msgstr "" #: ../../panes/editor.rst:114 @@ -391,28 +364,19 @@ msgstr "" #: ../../panes/editor.rst:119 #, python-format -msgid "" -"Providing a description to the right of the separator will give that cell" -" its own name in the :doc:`outline`. You can also create \"subsections\" " -"by adding more ``%`` signs to the cell separator, e.g. ``# %%%`` to " -"create a level 2 subsection, ``# %%%%`` for level 3, etc. This displays " -"multiple levels in the :doc:`outline` pane." +msgid "Providing a description to the right of the separator will give that cell its own name in the :doc:`outline`. You can also create \"subsections\" by adding more ``%`` signs to the cell separator, e.g. ``# %%%`` to create a level 2 subsection, ``# %%%%`` for level 3, etc. This displays multiple levels in the :doc:`outline` pane." +msgstr "" + +#: ../../panes/editor.rst:123 +msgid "Spyder outline pane, showing an example of sub sections" msgstr "" #: ../../panes/editor.rst:126 -msgid "" -"This only affects how the cell is displayed in the :doc:`outline`, and " -"doesn't affect running it in the Editor." +msgid "This only affects how the cell is displayed in the :doc:`outline`, and doesn't affect running it in the Editor." msgstr "" #: ../../panes/editor.rst:128 -msgid "" -"To run the code in a cell, use :menuselection:`Run --> Run cell`, the " -":guilabel:`Run cell` button in the toolbar or the keyboard shortcut (:kbd" -":`Ctrl-Enter`/:kbd:`Cmd-Return` by default). You can also run a cell and " -"then jump to the next one, letting you quickly step through multiple " -"cells, using :menuselection:`Run --> Run cell and advance` (:kbd:`Shift-" -"Enter` by default)." +msgid "To run the code in a cell, use :menuselection:`Run --> Run cell`, the :guilabel:`Run cell` button in the toolbar or the keyboard shortcut (:kbd:`Ctrl-Enter`/:kbd:`Cmd-Return` by default). You can also run a cell and then jump to the next one, letting you quickly step through multiple cells, using :menuselection:`Run --> Run cell and advance` (:kbd:`Shift-Enter` by default)." msgstr "" #: ../../panes/editor.rst:133 @@ -420,22 +384,19 @@ msgid "Automatic formatting" msgstr "" #: ../../panes/editor.rst:135 -msgid "" -"The Editor has built-in support for automatically formatting your code " -"using several popular tools, including `Autopep8 " -"`_ and `Black " -"`_. The :guilabel:`Format file " -"or selection with {tool}` command in the :guilabel:`Source` or context " -"menu will format either the selected fragment (if text is selected) or " -"the entire active file." +msgid "The Editor has built-in support for automatically formatting your code using several popular tools, including `Autopep8 `_ and `Black `_. The :guilabel:`Format file or selection with {tool}` command in the :guilabel:`Source` or context menu will format either the selected fragment (if text is selected) or the entire active file." +msgstr "" + +#: ../../panes/editor.rst:138 +msgid "Spyder Editor pane, showing an example of code selection formatting" msgstr "" #: ../../panes/editor.rst:141 -msgid "" -"You can have the Editor automatically autoformat a file every time you " -"save your work. To set this up, go to :menuselection:`Preferences --> " -"Completion and linting --> Code style and formatting --> Code formatting`" -" and check the :guilabel:`Autoformat files on save` option." +msgid "You can have the Editor automatically autoformat a file every time you save your work. To set this up, go to :menuselection:`Preferences --> Completion and linting --> Code style and formatting --> Code formatting` and check the :guilabel:`Autoformat files on save` option." +msgstr "" + +#: ../../panes/editor.rst:144 +msgid "Spyder's preferences dialog, showing checking the autoformat files on save setting" msgstr "" #: ../../panes/editor.rst:151 @@ -443,9 +404,7 @@ msgid "Running code" msgstr "" #: ../../panes/editor.rst:153 -msgid "" -"The Editor lets you run an entire file as well as specific lines, " -"selections or cells." +msgid "The Editor lets you run an entire file as well as specific lines, selections or cells." msgstr "" #: ../../panes/editor.rst:155 @@ -457,9 +416,7 @@ msgid "The :doc:`ipythonconsole` will display output and errors." msgstr "" #: ../../panes/editor.rst:158 -msgid "" -"The :doc:`variableexplorer` allows you to browse and interact with the " -"objects generated." +msgid "The :doc:`variableexplorer` allows you to browse and interact with the objects generated." msgstr "" #: ../../panes/editor.rst:159 @@ -471,11 +428,7 @@ msgid "Run file" msgstr "" #: ../../panes/editor.rst:165 -msgid "" -"Run an entire Editor file using the :menuselection:`Run --> Run` menu " -"item, the :guilabel:`Run file` toolbar button or the :kbd:`F5` key. Use " -":menuselection:`Run --> Re-Run last script` to re-run the most recent " -"file executed with the above." +msgid "Run an entire Editor file using the :menuselection:`Run --> Run` menu item, the :guilabel:`Run file` toolbar button or the :kbd:`F5` key. Use :menuselection:`Run --> Re-Run last script` to re-run the most recent file executed with the above." msgstr "" #: ../../panes/editor.rst:170 @@ -483,14 +436,7 @@ msgid "Run line/selection" msgstr "" #: ../../panes/editor.rst:172 -msgid "" -"You can execute the current line—or multiple selected lines—using the " -":guilabel:`Run selection or current line` option from the toolbar or the " -":menuselection:`Run` menu, as well as with the :kbd:`F9` key. After " -"running the current line, the cursor automatically advances to the next " -"one, so you can step through your code line by line. Unlike " -":guilabel:`Run file`, the executed lines are shown in the " -":doc:`ipythonconsole`." +msgid "You can execute the current line—or multiple selected lines—using the :guilabel:`Run selection or current line` option from the toolbar or the :menuselection:`Run` menu, as well as with the :kbd:`F9` key. After running the current line, the cursor automatically advances to the next one, so you can step through your code line by line. Unlike :guilabel:`Run file`, the executed lines are shown in the :doc:`ipythonconsole`." msgstr "" #: ../../panes/editor.rst:178 @@ -498,13 +444,7 @@ msgid "Run cell" msgstr "" #: ../../panes/editor.rst:180 -msgid "" -"To run a cell, place your cursor inside it and use the " -":menuselection:`Run --> Run cell` menu item, the :guilabel:`Run current " -"cell` toolbar button or the :kbd:`Ctrl-Enter` / :kbd:`Cmd-Return` " -"keyboard shortcut. Use :guilabel:`Run cell and advance` in the " -":guilabel:`Run` menu/toolbar or :kbd:`Shift-Enter` to jump to the next " -"cell after running, useful for stepping through cells quickly." +msgid "To run a cell, place your cursor inside it and use the :menuselection:`Run --> Run cell` menu item, the :guilabel:`Run current cell` toolbar button or the :kbd:`Ctrl-Enter` / :kbd:`Cmd-Return` keyboard shortcut. Use :guilabel:`Run cell and advance` in the :guilabel:`Run` menu/toolbar or :kbd:`Shift-Enter` to jump to the next cell after running, useful for stepping through cells quickly." msgstr "" #: ../../panes/editor.rst:185 @@ -512,17 +452,15 @@ msgid "Run configuration" msgstr "" #: ../../panes/editor.rst:187 -msgid "" -"You can use the :guilabel:`Run configuration per file` dialog to set each" -" file's working directory, console mode (current, dedicated or external)," -" command line arguments, execution options (clear all variables, run in " -"an existing/empty namespace, debug on error), and more." +msgid "You can use the :guilabel:`Run configuration per file` dialog to set each file's working directory, console mode (current, dedicated or external), command line arguments, execution options (clear all variables, run in an existing/empty namespace, debug on error), and more." +msgstr "" + +#: ../../panes/editor.rst:189 +msgid "Spyder's Editor pane, showing the Run Configuration dialog" msgstr "" #: ../../panes/editor.rst:192 -msgid "" -"To access it, click :menuselection:`Run --> Configuration per file...` or" -" press :kbd:`Ctrl-F6` / :kbd:`Cmd-F6`." +msgid "To access it, click :menuselection:`Run --> Configuration per file...` or press :kbd:`Ctrl-F6` / :kbd:`Cmd-F6`." msgstr "" #: ../../panes/editor.rst:198 @@ -534,19 +472,11 @@ msgid "Find and replace" msgstr "" #: ../../panes/editor.rst:203 -msgid "" -"To search for text in the current file, use :menuselection:`Search --> " -"Find text` or :kbd:`Ctrl-F` / :kbd:`Cmd-F`, and to replace it, use " -":menuselection:`Search --> Replace text` or :kbd:`Ctrl-R` / :kbd:`Cmd-R`." -" Typing your search string in the resulting panel below the Editor " -"highlights each result and counts the total. Navigate between matches " -"with the :guilabel:`Find Previous` and :guilabel:`Find Next` buttons in " -"the find/replace panel, their corresponding entries in the " -":guilabel:`Search` menu, or use the :kbd:`F2` and :kbd:`F3` keys. Use the" -" :guilabel:`.*` button to process search text as a `regular expression " -"`_, :guilabel:`Aa` to treat it" -" as case-sensitive and :guilabel:`[–]` to only match whole words (e.g. " -"for ``data``, match ``data()`` but not ``dataframe``)." +msgid "To search for text in the current file, use :menuselection:`Search --> Find text` or :kbd:`Ctrl-F` / :kbd:`Cmd-F`, and to replace it, use :menuselection:`Search --> Replace text` or :kbd:`Ctrl-R` / :kbd:`Cmd-R`. Typing your search string in the resulting panel below the Editor highlights each result and counts the total. Navigate between matches with the :guilabel:`Find Previous` and :guilabel:`Find Next` buttons in the find/replace panel, their corresponding entries in the :guilabel:`Search` menu, or use the :kbd:`F2` and :kbd:`F3` keys. Use the :guilabel:`.*` button to process search text as a `regular expression `_, :guilabel:`Aa` to treat it as case-sensitive and :guilabel:`[–]` to only match whole words (e.g. for ``data``, match ``data()`` but not ``dataframe``)." +msgstr "" + +#: ../../panes/editor.rst:208 +msgid "Spyder's Editor pane, showing the find and replace panel" msgstr "" #: ../../panes/editor.rst:213 @@ -554,11 +484,11 @@ msgid "Go to line" msgstr "" #: ../../panes/editor.rst:215 -msgid "" -"The :guilabel:`Go to line` dialog allows jumping to a specific line in " -"the active file. Open it with :menuselection:`Search --> Go to line` or " -":kbd:`Ctrl-L` / :kbd:`Cmd-L`, type the line number you want to scroll to " -"and press :kbd:`Enter` (or click :guilabel:`OK`)." +msgid "The :guilabel:`Go to line` dialog allows jumping to a specific line in the active file. Open it with :menuselection:`Search --> Go to line` or :kbd:`Ctrl-L` / :kbd:`Cmd-L`, type the line number you want to scroll to and press :kbd:`Enter` (or click :guilabel:`OK`)." +msgstr "" + +#: ../../panes/editor.rst:218 +msgid "Spyder's Editor pane, showing the go to line feature" msgstr "" #: ../../panes/editor.rst:221 @@ -570,12 +500,11 @@ msgid "Class/function selector" msgstr "" #: ../../panes/editor.rst:227 -msgid "" -"This panel, activated under :menuselection:`Source --> Show selector for " -"classes and functions`, displays (as applicable) the name of the cell, " -"function/method and class the Editor cursor is located inside. Use its " -"dropdowns to view and jump to the functions, methods and classes in the " -"current file." +msgid "This panel, activated under :menuselection:`Source --> Show selector for classes and functions`, displays (as applicable) the name of the cell, function/method and class the Editor cursor is located inside. Use its dropdowns to view and jump to the functions, methods and classes in the current file." +msgstr "" + +#: ../../panes/editor.rst:230 +msgid "Spyder's Editor pane, showing the class and function selector panel" msgstr "" #: ../../panes/editor.rst:237 @@ -583,27 +512,15 @@ msgid "Code analysis and completions" msgstr "" #: ../../panes/editor.rst:239 -msgid "" -"Spyder uses the `Language Server Protocol `_ (LSP) to provide code completion and " -"linting for the Editor, similar to VSCode, Neovim, and other popular " -"editors/IDEs." +msgid "Spyder uses the `Language Server Protocol `_ (LSP) to provide code completion and linting for the Editor, similar to VSCode, Neovim, and other popular editors/IDEs." msgstr "" #: ../../panes/editor.rst:243 -msgid "" -"Many issues with completion and linting are outside of Spyder's control, " -"and are either limitations with the LSP or the code that is being " -"introspected, but some can be worked around. See :ref:`code-completion-" -"problems-ref` for troubleshooting steps." +msgid "Many issues with completion and linting are outside of Spyder's control, and are either limitations with the LSP or the code that is being introspected, but some can be worked around. See :ref:`code-completion-problems-ref` for troubleshooting steps." msgstr "" #: ../../panes/editor.rst:246 -msgid "" -"Python is supported out of the box, and advanced users can add completion" -" and linting support for other languages by setting up LSP servers for " -"them under :menuselection:`Preferences --> Completion and Linting --> " -"Other languages`." +msgid "Python is supported out of the box, and advanced users can add completion and linting support for other languages by setting up LSP servers for them under :menuselection:`Preferences --> Completion and Linting --> Other languages`." msgstr "" #: ../../panes/editor.rst:250 @@ -611,24 +528,15 @@ msgid "Code completion" msgstr "" #: ../../panes/editor.rst:252 -msgid "" -"Automatic code completion as you type is enabled by default in the " -"Editor, and can also be triggered manually with :kbd:`Ctrl-Space`/:kbd" -":`Cmd-Space`, showing you possible completions (with pop-up help for " -"each) and available code snippets. For example, typing ``cla`` will " -"display the keyword ``class``, the decorator ``classmethod`` and two " -"built-in snippets with class templates. Select the desired completion " -"with the arrow keys and :kbd:`Enter`, or by double clicking." +msgid "Automatic code completion as you type is enabled by default in the Editor, and can also be triggered manually with :kbd:`Ctrl-Space`/:kbd:`Cmd-Space`, showing you possible completions (with pop-up help for each) and available code snippets. For example, typing ``cla`` will display the keyword ``class``, the decorator ``classmethod`` and two built-in snippets with class templates. Select the desired completion with the arrow keys and :kbd:`Enter`, or by double clicking." +msgstr "" + +#: ../../panes/editor.rst:256 +msgid "Spyder's Editor pane, showing a code completion example" msgstr "" #: ../../panes/editor.rst:259 -msgid "" -"You can enable or disable on-the-fly code completion, as well as modify " -"when it is triggered and what results are shown, under " -":menuselection:`Preferences --> Completion and Linting --> General --> " -"Completions`. Spyder also allows you to define custom completion snippets" -" to use, in addition to the ones offered by the LSP, under " -":menuselection:`Preferences --> Completion and Linting --> Advanced`." +msgid "You can enable or disable on-the-fly code completion, as well as modify when it is triggered and what results are shown, under :menuselection:`Preferences --> Completion and Linting --> General --> Completions`. Spyder also allows you to define custom completion snippets to use, in addition to the ones offered by the LSP, under :menuselection:`Preferences --> Completion and Linting --> Advanced`." msgstr "" #: ../../panes/editor.rst:264 @@ -636,30 +544,27 @@ msgid "Linting and code style" msgstr "" #: ../../panes/editor.rst:266 -msgid "" -"Spyder can optionally highlight syntax errors, style issues, and other " -"potential problems with your code in the Editor, which can help you spot " -"bugs quickly and make your code easier to read and understand." +msgid "Spyder can optionally highlight syntax errors, style issues, and other potential problems with your code in the Editor, which can help you spot bugs quickly and make your code easier to read and understand." +msgstr "" + +#: ../../panes/editor.rst:268 +msgid "Spyder's Editor pane, showing an example of a highlighted code error" msgstr "" #: ../../panes/editor.rst:271 -msgid "" -"The Editor's basic linting, powered by `Pyflakes " -"`_, warns of syntax errors and likely " -"bugs in your code. It is on by default, and can be disabled or customized" -" under :menuselection:`Preferences --> Completion and Linting --> " -"Linting`." +msgid "The Editor's basic linting, powered by `Pyflakes `_, warns of syntax errors and likely bugs in your code. It is on by default, and can be disabled or customized under :menuselection:`Preferences --> Completion and Linting --> Linting`." +msgstr "" + +#: ../../panes/editor.rst:274 +msgid "Spyder's preferences dialog, showing linting settings" msgstr "" #: ../../panes/editor.rst:277 -msgid "" -"Code style analysis, powered by `Pycodestyle " -"`_, flags deviations from the " -"style conventions in :pep:`8`. It is not active by default, but you can " -"enable it and customize the `Pycodestyle error codes " -"`_ shown " -"with the options under :menuselection:`Preferences --> Completion and " -"Linting --> Code style and formatting --> Code Style`." +msgid "Code style analysis, powered by `Pycodestyle `_, flags deviations from the style conventions in :pep:`8`. It is not active by default, but you can enable it and customize the `Pycodestyle error codes `_ shown with the options under :menuselection:`Preferences --> Completion and Linting --> Code style and formatting --> Code Style`." +msgstr "" + +#: ../../panes/editor.rst:280 +msgid "Spyder's preferences dialog, showing code style and formatting settings" msgstr "" #: ../../panes/editor.rst:285 @@ -667,27 +572,23 @@ msgid "Introspection features" msgstr "" #: ../../panes/editor.rst:287 -msgid "" -"If there's a function, class or variable for which you would like to " -"check its definition, you need to :kbd:`Ctrl`/:kbd:`Cmd`-click its name " -"in the Editor (or click its name and press :kbd:`Ctrl-G` / :kbd:`Cmd-G` " -"to jump to the file and line where it is declared." +msgid "If there's a function, class or variable for which you would like to check its definition, you need to :kbd:`Ctrl`/:kbd:`Cmd`-click its name in the Editor (or click its name and press :kbd:`Ctrl-G` / :kbd:`Cmd-G` to jump to the file and line where it is declared." +msgstr "" + +#: ../../panes/editor.rst:289 +msgid "Spyder's Editor pane, showing the go to definition feature" msgstr "" #: ../../panes/editor.rst:292 -msgid "" -"You can hover over the name of an object for pop-up help, as " -":ref:`described in the Help pane docs `." +msgid "You can hover over the name of an object for pop-up help, as :ref:`described in the Help pane docs `." +msgstr "" + +#: ../../panes/editor.rst:294 +msgid "Spyder's Editor pane, showing an example of a hover hint" msgstr "" #: ../../panes/editor.rst:297 -msgid "" -"Finally, if you type the name of a function, method or class constructor " -"and then an open parenthesis, a calltip will pop up which shows the " -"function's parameters as you type them, as well as a summary of its " -"documentation. These features can be enabled and customized under " -":menuselection:`Preferences --> Completion and Linting --> " -"Introspection`." +msgid "Finally, if you type the name of a function, method or class constructor and then an open parenthesis, a calltip will pop up which shows the function's parameters as you type them, as well as a summary of its documentation. These features can be enabled and customized under :menuselection:`Preferences --> Completion and Linting --> Introspection`." msgstr "" #: ../../panes/editor.rst:304 @@ -695,11 +596,7 @@ msgid "Keyboard shortcuts" msgstr "" #: ../../panes/editor.rst:306 -msgid "" -"To view the Editor's primary keyboard shortcuts, consult its section " -"under :menuselection:`Help --> Shortcuts Summary`. The full list can be " -"browsed, searched and customized (on double-click) in " -":menuselection:`Preferences --> Keyboard shortcuts`." +msgid "To view the Editor's primary keyboard shortcuts, consult its section under :menuselection:`Help --> Shortcuts Summary`. The full list can be browsed, searched and customized (on double-click) in :menuselection:`Preferences --> Keyboard shortcuts`." msgstr "" #: ../../panes/editor.rst:315 ../../panes/findinfiles.rst:68 @@ -725,11 +622,11 @@ msgid "Files" msgstr "" #: ../../panes/fileexplorer.rst:5 -msgid "" -"The **Files** pane is a filesystem and directory browser built right into" -" Spyder. You can view and filter files according to their type and " -"extension, open them with the :doc:`editor` or an external tool, and " -"perform many common operations." +msgid "The **Files** pane is a filesystem and directory browser built right into Spyder. You can view and filter files according to their type and extension, open them with the :doc:`editor` or an external tool, and perform many common operations." +msgstr "" + +#: ../../panes/fileexplorer.rst:8 +msgid "Spyder Files pane, showing a tree view of files and metadata" msgstr "" #: ../../panes/fileexplorer.rst:17 @@ -737,28 +634,27 @@ msgid "File operations" msgstr "" #: ../../panes/fileexplorer.rst:19 -msgid "" -"To browse the files on your system, use the arrows at the top of the " -"pane. You can expand/collapse the folders in the pane to display the " -"files and subdirectories hierarchically. Double-clicking a folder will " -"open it, showing the files inside and making it your working directory." +msgid "To browse the files on your system, use the arrows at the top of the pane. You can expand/collapse the folders in the pane to display the files and subdirectories hierarchically. Double-clicking a folder will open it, showing the files inside and making it your working directory." +msgstr "" + +#: ../../panes/fileexplorer.rst:23 +msgid "Spyder Files pane showing browsing directories" msgstr "" #: ../../panes/fileexplorer.rst:26 -msgid "" -"To open a file in the :guilabel:`Editor` from the :guilabel:`Files` pane," -" double-click its name. If you right-click over it, you will see a " -"context menu that allows you to access a number of functions, including " -"running scripts; creating, renaming, moving, deleting files; and opening " -"them in your computer's file manager." +msgid "To open a file in the :guilabel:`Editor` from the :guilabel:`Files` pane, double-click its name. If you right-click over it, you will see a context menu that allows you to access a number of functions, including running scripts; creating, renaming, moving, deleting files; and opening them in your computer's file manager." +msgstr "" + +#: ../../panes/fileexplorer.rst:29 +msgid "Spyder Files pane showing context menu" msgstr "" #: ../../panes/fileexplorer.rst:32 -msgid "" -"You can copy and paste one or several files to and from the pane, and " -"copy their absolute or relative paths to the clipboard as text. If " -"copying the paths for multiple files, they will be automatically " -"formatted so you can paste them directly into a Python list." +msgid "You can copy and paste one or several files to and from the pane, and copy their absolute or relative paths to the clipboard as text. If copying the paths for multiple files, they will be automatically formatted so you can paste them directly into a Python list." +msgstr "" + +#: ../../panes/fileexplorer.rst:35 +msgid "Spyder Files pane showing copying absolute path to Editor" msgstr "" #: ../../panes/fileexplorer.rst:44 @@ -766,12 +662,11 @@ msgid "Version control support" msgstr "" #: ../../panes/fileexplorer.rst:46 -msgid "" -"The :guilabel:`Files` pane allows you to perform basic operations with " -"the `Git`_ distributed version control system, like committing your " -"changes and browsing the repository a given file or folder is part of. " -"This is :ref:`particularly useful` when you're working in " -"Spyder :doc:`projects`." +msgid "The :guilabel:`Files` pane allows you to perform basic operations with the `Git`_ distributed version control system, like committing your changes and browsing the repository a given file or folder is part of. This is :ref:`particularly useful` when you're working in Spyder :doc:`projects`." +msgstr "" + +#: ../../panes/fileexplorer.rst:51 +msgid "Spyder Files pane showing committing change of file" msgstr "" #: ../../panes/fileexplorer.rst:58 ../../panes/ipythonconsole.rst:65 @@ -781,38 +676,31 @@ msgid "Options menu" msgstr "" #: ../../panes/fileexplorer.rst:60 -msgid "" -"The options menu in the top right of the :guilabel:`Files` pane offers " -"several ways to customize how your files are displayed." +msgid "The options menu in the top right of the :guilabel:`Files` pane offers several ways to customize how your files are displayed." msgstr "" #: ../../panes/fileexplorer.rst:62 -msgid "" -"By default, the pane displays the contents of your working directory " -"without filtering. However, it can filter the list to show only files " -"matching the patterns set under :guilabel:`Show filenames with these " -"extensions...`, if you toggle the :guilabel:`Filter filenames` button in " -"the pane toolbar." +msgid "By default, the pane displays the contents of your working directory without filtering. However, it can filter the list to show only files matching the patterns set under :guilabel:`Show filenames with these extensions...`, if you toggle the :guilabel:`Filter filenames` button in the pane toolbar." +msgstr "" + +#: ../../panes/fileexplorer.rst:65 +msgid "Spyder Files pane showing filtering files" msgstr "" #: ../../panes/fileexplorer.rst:68 -msgid "" -"You can also activate the :guilabel:`Show hidden files` option, which " -"will display files that are invisible by default in your operating " -"system." +msgid "You can also activate the :guilabel:`Show hidden files` option, which will display files that are invisible by default in your operating system." msgstr "" #: ../../panes/fileexplorer.rst:70 -msgid "" -"Additionally, you can change which file attributes you want to see by " -"hiding or displaying the :guilabel:`Type`, :guilabel:`Size` and " -":guilabel:`Date Modified` columns using the corresponding menu options." +msgid "Additionally, you can change which file attributes you want to see by hiding or displaying the :guilabel:`Type`, :guilabel:`Size` and :guilabel:`Date Modified` columns using the corresponding menu options." +msgstr "" + +#: ../../panes/fileexplorer.rst:72 +msgid "Spyder Files pane showing columns checked and shown" msgstr "" #: ../../panes/fileexplorer.rst:75 -msgid "" -"The menu also gives you the option to open files and directories with a " -"single instead of a double click, to suit your preferences." +msgid "The menu also gives you the option to open files and directories with a single instead of a double click, to suit your preferences." msgstr "" #: ../../panes/fileexplorer.rst:81 @@ -820,21 +708,19 @@ msgid "File associations" msgstr "" #: ../../panes/fileexplorer.rst:83 -msgid "" -":guilabel:`Files` allows you to associate different external applications" -" with specific file extensions they can open. Under the :guilabel:`File " -"associations` tab of the :guilabel:`Files` preferences pane, you can add " -"file types and set the external program used to open each of them by " -"default." +msgid ":guilabel:`Files` allows you to associate different external applications with specific file extensions they can open. Under the :guilabel:`File associations` tab of the :guilabel:`Files` preferences pane, you can add file types and set the external program used to open each of them by default." +msgstr "" + +#: ../../panes/fileexplorer.rst:86 +msgid "Spyder Files pane showing files associations" msgstr "" #: ../../panes/fileexplorer.rst:89 -msgid "" -"Once you've set this up, files will automatically launch in the " -"associated application when opened from Spyder's :guilabel:`Files` pane. " -"Additionally, when you right-click a file, you will find an " -":guilabel:`Open with...` option that will allow you to select from the " -"applications associated with this extension." +msgid "Once you've set this up, files will automatically launch in the associated application when opened from Spyder's :guilabel:`Files` pane. Additionally, when you right-click a file, you will find an :guilabel:`Open with...` option that will allow you to select from the applications associated with this extension." +msgstr "" + +#: ../../panes/fileexplorer.rst:92 +msgid "Spyder Files pane showing opening file with associated program" msgstr "" #: ../../panes/findinfiles.rst:3 @@ -842,9 +728,11 @@ msgid "Find" msgstr "" #: ../../panes/findinfiles.rst:5 -msgid "" -"The **Find** pane allows you to search the content of text files in a " -"user-defined location, with advanced features to filter your results." +msgid "The **Find** pane allows you to search the content of text files in a user-defined location, with advanced features to filter your results." +msgstr "" + +#: ../../panes/findinfiles.rst:7 +msgid "Spyder Find in Files panel, with search results shown per-file" msgstr "" #: ../../panes/findinfiles.rst:14 @@ -852,23 +740,19 @@ msgid "Using the Find pane" msgstr "" #: ../../panes/findinfiles.rst:16 -msgid "" -"To search for text in the Find pane, enter it in the field in the top " -"left and press the search button. This will allow you to view and " -"navigate through all the occurrences of your search text in your working " -"directory. You can expand or collapse the search results to view the " -"matches in each file. Clicking on a match will automatically open the " -"file and highlight the line where the text was found." +msgid "To search for text in the Find pane, enter it in the field in the top left and press the search button. This will allow you to view and navigate through all the occurrences of your search text in your working directory. You can expand or collapse the search results to view the matches in each file. Clicking on a match will automatically open the file and highlight the line where the text was found." +msgstr "" + +#: ../../panes/findinfiles.rst:21 +msgid "Spyder Find pane showing search and going to a file" msgstr "" #: ../../panes/findinfiles.rst:24 -msgid "" -"If you want to change the scope of your search, select another directory," -" project or file in the :guilabel:`Search in` menu. The locations that " -"you select for your search will be stored in the list so you can access " -"them easily in the future. To erase all of these saved directories, " -"select the :guilabel:`Clear the list` option from the dropdown menu in " -"the :guilabel:`Search in` field." +msgid "If you want to change the scope of your search, select another directory, project or file in the :guilabel:`Search in` menu. The locations that you select for your search will be stored in the list so you can access them easily in the future. To erase all of these saved directories, select the :guilabel:`Clear the list` option from the dropdown menu in the :guilabel:`Search in` field." +msgstr "" + +#: ../../panes/findinfiles.rst:28 +msgid "Spyder Find pane showing choosing new directory and directory stored in the list" msgstr "" #: ../../panes/findinfiles.rst:35 @@ -876,35 +760,39 @@ msgid "Choosing search options" msgstr "" #: ../../panes/findinfiles.rst:37 -msgid "" -"You can select from a number of options to enable searches as broad or " -"refined as you need." +msgid "You can select from a number of options to enable searches as broad or refined as you need." msgstr "" #: ../../panes/findinfiles.rst:39 -msgid "" -"To enable case sensitivity, which only returns matches with identical " -"capitalization to your search text, toggle the :guilabel:`Aa` button on." +msgid "To enable case sensitivity, which only returns matches with identical capitalization to your search text, toggle the :guilabel:`Aa` button on." +msgstr "" + +#: ../../panes/findinfiles.rst:41 +msgid "Spyder Find pane showing search with case sensitive activated" msgstr "" #: ../../panes/findinfiles.rst:44 -msgid "" -"To parse your search string as a `regular expression`_, enable the " -":guilabel:`.*` button." +msgid "To parse your search string as a `regular expression`_, enable the :guilabel:`.*` button." +msgstr "" + +#: ../../panes/findinfiles.rst:48 +msgid "Spyder Find pane showing regular expression search" msgstr "" #: ../../panes/findinfiles.rst:51 -msgid "" -"To exclude certain filenames, extensions or directories from your search," -" click the :guilabel:`Plus` button to display the advanced options for " -"the pane, and then enter them in the :guilabel:`Exclude` text box." +msgid "To exclude certain filenames, extensions or directories from your search, click the :guilabel:`Plus` button to display the advanced options for the pane, and then enter them in the :guilabel:`Exclude` text box." +msgstr "" + +#: ../../panes/findinfiles.rst:53 +msgid "Spyder Find pane showing search excluding several file-types" msgstr "" #: ../../panes/findinfiles.rst:56 -msgid "" -"Finally, to change the number of matches displayed, select the " -":guilabel:`Set maximum number of results` option under the pane's Options" -" menu in the top right." +msgid "Finally, to change the number of matches displayed, select the :guilabel:`Set maximum number of results` option under the pane's Options menu in the top right." +msgstr "" + +#: ../../panes/findinfiles.rst:58 +msgid "Spyder Find pane showing window with maximum results dialog open" msgstr "" #: ../../panes/help.rst:3 @@ -912,17 +800,19 @@ msgid "Help" msgstr "" #: ../../panes/help.rst:5 -msgid "" -"You can use the **Help** pane to find, render and display rich " -"documentation for any object with a docstring, including modules, " -"classes, functions and methods. This allows you to access documentation " -"easily directly from Spyder, without having to interrupt your workflow." +msgid "You can use the **Help** pane to find, render and display rich documentation for any object with a docstring, including modules, classes, functions and methods. This allows you to access documentation easily directly from Spyder, without having to interrupt your workflow." +msgstr "" + +#: ../../panes/help.rst:8 +msgid "Spyder main window showing getting help for numpy arrays from editor" msgstr "" #: ../../panes/help.rst:11 -msgid "" -"You can also access Spyder's tutorial from here, which will guide you " -"through some basic steps for using its key features." +msgid "You can also access Spyder's tutorial from here, which will guide you through some basic steps for using its key features." +msgstr "" + +#: ../../panes/help.rst:13 +msgid "Spyder Help pane showing the link for the Spyder's tutorial" msgstr "" #: ../../panes/help.rst:21 @@ -930,29 +820,27 @@ msgid "Getting help" msgstr "" #: ../../panes/help.rst:23 -msgid "" -"Help can be retrieved both by static analysis of open files in the " -":doc:`editor`, or by dynamically inspecting an object in an " -":doc:`ipythonconsole`. You can trigger help manually by pressing the " -"configurable help shortcut (:kbd:`Ctrl-I` by default)." +msgid "Help can be retrieved both by static analysis of open files in the :doc:`editor`, or by dynamically inspecting an object in an :doc:`ipythonconsole`. You can trigger help manually by pressing the configurable help shortcut (:kbd:`Ctrl-I` by default)." +msgstr "" + +#: ../../panes/help.rst:26 +msgid "Spyder Editor and Help panes, with the latter displaying documentation for an object selected in the former." msgstr "" #: ../../panes/help.rst:29 -msgid "" -"You can also manually enter the object's name into the :guilabel:`Object`" -" textbox at the top of the pane, if :guilabel:`Console` is selected as " -"the :guilabel:`Source`." +msgid "You can also manually enter the object's name into the :guilabel:`Object` textbox at the top of the pane, if :guilabel:`Console` is selected as the :guilabel:`Source`." +msgstr "" + +#: ../../panes/help.rst:31 +msgid "Spyder Help pane, displaying documentation for an object whose name was written in the object text box" msgstr "" #: ../../panes/help.rst:34 -msgid "" -"Automatic help can be individually enabled for both the " -":guilabel:`Editor` and the :guilabel:`Console` under " -":menuselection:`Preferences --> Help --> Automatic Connections`, and " -"turned on and off dynamically via the lock icon in the top right corner " -"of the :guilabel:`Help` pane. If enabled, simply typing a left " -"parenthesis (``(``) after a function or method name will show its " -"associated help." +msgid "Automatic help can be individually enabled for both the :guilabel:`Editor` and the :guilabel:`Console` under :menuselection:`Preferences --> Help --> Automatic Connections`, and turned on and off dynamically via the lock icon in the top right corner of the :guilabel:`Help` pane. If enabled, simply typing a left parenthesis (``(``) after a function or method name will show its associated help." +msgstr "" + +#: ../../panes/help.rst:37 +msgid "Spyder console and help pane showing automatic help with parenthesis" msgstr "" #: ../../panes/help.rst:44 @@ -960,19 +848,15 @@ msgid "Understanding help modes" msgstr "" #: ../../panes/help.rst:46 -msgid "" -"You can use the options menu (:guilabel:`Hamburger` icon) in the top " -"right of the :guilabel:`Help` pane to toggle the help display mode." +msgid "You can use the options menu (:guilabel:`Hamburger` icon) in the top right of the :guilabel:`Help` pane to toggle the help display mode." msgstr "" #: ../../panes/help.rst:48 -msgid "" -":guilabel:`Rich Text` mode renders the object's docstrings with " -"``Sphinx``, :guilabel:`Plain Text` mode displays the docstring without " -"formatting while :guilabel:`Show Source` displays the docstring inline " -"with the code for the selected object, or any Python portion of it (if " -"the object is not pure Python). The latter can be useful when docstrings " -"are not available or insufficient to document the object." +msgid ":guilabel:`Rich Text` mode renders the object's docstrings with ``Sphinx``, :guilabel:`Plain Text` mode displays the docstring without formatting while :guilabel:`Show Source` displays the docstring inline with the code for the selected object, or any Python portion of it (if the object is not pure Python). The latter can be useful when docstrings are not available or insufficient to document the object." +msgstr "" + +#: ../../panes/help.rst:51 +msgid "Spyder help pane showing different modes" msgstr "" #: ../../panes/help.rst:59 @@ -980,10 +864,11 @@ msgid "Getting help by hovering" msgstr "" #: ../../panes/help.rst:61 -msgid "" -"You can also get summary help for objects by hovering over them in the " -":guilabel:`Editor`. Clicking the hover popup will open the full " -"documentation in the :guilabel:`Help` pane." +msgid "You can also get summary help for objects by hovering over them in the :guilabel:`Editor`. Clicking the hover popup will open the full documentation in the :guilabel:`Help` pane." +msgstr "" + +#: ../../panes/help.rst:64 +msgid "Editor pane showing help of an object from hover" msgstr "" #: ../../panes/help.rst:71 @@ -991,13 +876,7 @@ msgid "Control automatic import" msgstr "" #: ../../panes/help.rst:73 -msgid "" -"When you get help in the :guilabel:`IPython Console` for an object that " -"has not been previously imported, it is automatically loaded in Spyder's " -"own internal interpreter so that documentation can be shown when " -"available. This can be disabled in the :guilabel:`Help` pane's top-right " -"options menu so that only documentation from imported objects is " -"displayed." +msgid "When you get help in the :guilabel:`IPython Console` for an object that has not been previously imported, it is automatically loaded in Spyder's own internal interpreter so that documentation can be shown when available. This can be disabled in the :guilabel:`Help` pane's top-right options menu so that only documentation from imported objects is displayed." msgstr "" #: ../../panes/help.rst:84 @@ -1009,10 +888,11 @@ msgid "History" msgstr "" #: ../../panes/historylog.rst:5 -msgid "" -"With the **History** pane, you can view the recent code and commands " -"you've entered into any :doc:`ipythonconsole`, along with their " -"timestamp." +msgid "With the **History** pane, you can view the recent code and commands you've entered into any :doc:`ipythonconsole`, along with their timestamp." +msgstr "" + +#: ../../panes/historylog.rst:7 +msgid "Spyder History Log, displaying a list of previously executed commands" msgstr "" #: ../../panes/historylog.rst:14 @@ -1020,14 +900,7 @@ msgid "Using the History pane" msgstr "" #: ../../panes/historylog.rst:16 -msgid "" -"Navigating the :guilabel:`History` pane is very straightforward. Each " -"Spyder session is marked by a date and timestamp, making it easy to " -"remember when you executed a certain command. Statements can be selected " -"and copied from the context menu or with the normal system shortcuts. " -"Just like in the Editor, selecting a word or phrase displays all other " -"occurrences, and full syntax highlighting is also supported. The last " -"≈1000 lines entered are stored in the pane." +msgid "Navigating the :guilabel:`History` pane is very straightforward. Each Spyder session is marked by a date and timestamp, making it easy to remember when you executed a certain command. Statements can be selected and copied from the context menu or with the normal system shortcuts. Just like in the Editor, selecting a word or phrase displays all other occurrences, and full syntax highlighting is also supported. The last ≈1000 lines entered are stored in the pane." msgstr "" #: ../../panes/historylog.rst:26 @@ -1035,11 +908,11 @@ msgid "Options Menu" msgstr "" #: ../../panes/historylog.rst:28 -msgid "" -"The top-right options menu (:guilabel:`Hamburger` icon) allows you to " -"toggle wrapping of long lines (:guilabel:`Wrap lines`), and whether the " -"line number is displayed to the left of the text (:guilabel:`Show line " -"numbers`)." +msgid "The top-right options menu (:guilabel:`Hamburger` icon) allows you to toggle wrapping of long lines (:guilabel:`Wrap lines`), and whether the line number is displayed to the left of the text (:guilabel:`Show line numbers`)." +msgstr "" + +#: ../../panes/historylog.rst:30 +msgid "Spyder History Log, displaying wrapping lines and showing line number" msgstr "" #: ../../panes/historylog.rst:37 @@ -1047,24 +920,19 @@ msgid "Advanced usage" msgstr "" #: ../../panes/historylog.rst:39 -msgid "" -"The list of commands shown in the :guilabel:`History` pane are stored in " -":file:`history.py` in the :file:`.spyder-py3` directory in your user home" -" folder (by default, :file:`C:/Users/{username}` on Windows, " -":file:`/Users/{username}` for macOS, and typically " -":file:`/home/{username}` on GNU/Linux). You might need to show invisible " -"files in order to see it on a non-Windows operating system." +msgid "The list of commands shown in the :guilabel:`History` pane are stored in :file:`history.py` in the :file:`.spyder-py3` directory in your user home folder (by default, :file:`C:/Users/{username}` on Windows, :file:`/Users/{username}` for macOS, and typically :file:`/home/{username}` on GNU/Linux). You might need to show invisible files in order to see it on a non-Windows operating system." +msgstr "" + +#: ../../panes/historylog.rst:42 +msgid "Spyder History Log file" msgstr "" #: ../../panes/historylog.rst:45 -msgid "" -"While there is currently no built-in way to clear history from the Spyder" -" interface aside from resetting preferences, you can do so by closing " -"Spyder, deleting this file and restarting Spyder again." +msgid "While there is currently no built-in way to clear history from the Spyder interface aside from resetting preferences, you can do so by closing Spyder, deleting this file and restarting Spyder again." msgstr "" #: ../../panes/index.rst:3 -msgid "Panes in Depth" +msgid "Panes" msgstr "" #: ../../panes/ipythonconsole.rst:3 @@ -1072,28 +940,23 @@ msgid "IPython Console" msgstr "" #: ../../panes/ipythonconsole.rst:5 -msgid "" -"The **IPython Console** allows you to execute commands and interact with " -"data inside `IPython`_ interpreters." +msgid "The **IPython Console** allows you to execute commands and interact with data inside `IPython`_ interpreters." +msgstr "" + +#: ../../panes/ipythonconsole.rst:9 +msgid "Spyder IPython Console with code, inline plots, and the In prompt" msgstr "" #: ../../panes/ipythonconsole.rst:12 -msgid "" -"To launch a new IPython instance, go to :guilabel:`New console (default " -"settings)` under the :guilabel:`Consoles` menu, or use the keyboard " -"shortcut :kbd:`Ctrl-T` (:kbd:`Cmd-T` on macOS) when the console is " -"focused." +msgid "To launch a new IPython instance, go to :guilabel:`New console (default settings)` under the :guilabel:`Consoles` menu, or use the keyboard shortcut :kbd:`Ctrl-T` (:kbd:`Cmd-T` on macOS) when the console is focused." +msgstr "" + +#: ../../panes/ipythonconsole.rst:14 +msgid "Spyder showing opening a new Ipython Console" msgstr "" #: ../../panes/ipythonconsole.rst:17 -msgid "" -"From the same menu, you can stop currently executing code with " -":guilabel:`Interrupt kernel`, clear a console's namespace with " -":guilabel:`Remove all variables`, or relaunch a fresh one with " -":guilabel:`Restart kernel`. As each console is executed in a separate " -"process, this won't affect any others you've opened, and you will be able" -" to easily test your code in a clean environment without disrupting your " -"primary session." +msgid "From the same menu, you can stop currently executing code with :guilabel:`Interrupt kernel`, clear a console's namespace with :guilabel:`Remove all variables`, or relaunch a fresh one with :guilabel:`Restart kernel`. As each console is executed in a separate process, this won't affect any others you've opened, and you will be able to easily test your code in a clean environment without disrupting your primary session." msgstr "" #: ../../panes/ipythonconsole.rst:26 @@ -1101,9 +964,7 @@ msgid "Supported features" msgstr "" #: ../../panes/ipythonconsole.rst:28 -msgid "" -"Any :guilabel:`IPython Console`, whether :ref:`external` or started by Spyder, supports:" +msgid "Any :guilabel:`IPython Console`, whether :ref:`external` or started by Spyder, supports:" msgstr "" #: ../../panes/ipythonconsole.rst:30 @@ -1119,24 +980,19 @@ msgid "Full GUI integration with the enhanced Spyder :doc:`Debugger`. msgstr "" #: ../../panes/ipythonconsole.rst:33 -msgid "" -"The :doc:`variableexplorer`, with GUI-based editors for many built-in and" -" third-party Python objects." +msgid "The :doc:`variableexplorer`, with GUI-based editors for many built-in and third-party Python objects." msgstr "" #: ../../panes/ipythonconsole.rst:34 -msgid "" -"Display of Matplotlib graphics in Spyder's :doc:`plots` pane, if the " -":guilabel:`Inline` backend is selected under :menuselection:`Preferences " -"--> IPython console --> Graphics --> Graphics backend`, and inline in the" -" console if :guilabel:`Mute inline plotting` is unchecked under the " -":guilabel:`Plots` pane's options menu." +msgid "Display of Matplotlib graphics in Spyder's :doc:`plots` pane, if the :guilabel:`Inline` backend is selected under :menuselection:`Preferences --> IPython console --> Graphics --> Graphics backend`, and inline in the console if :guilabel:`Mute inline plotting` is unchecked under the :guilabel:`Plots` pane's options menu." +msgstr "" + +#: ../../panes/ipythonconsole.rst:36 +msgid "Spyder IPython Console, with a popup list of code completion guesses" msgstr "" #: ../../panes/ipythonconsole.rst:39 -msgid "" -"For information on the features, commands and capabilities built into " -"IPython itself, see the `IPython documentation`_." +msgid "For information on the features, commands and capabilities built into IPython itself, see the `IPython documentation`_." msgstr "" #: ../../panes/ipythonconsole.rst:47 @@ -1144,30 +1000,27 @@ msgid "Special consoles" msgstr "" #: ../../panes/ipythonconsole.rst:49 -msgid "" -"Spyder also supports several types of specialized consoles. A `Sympy " -"console`_ enables creating and displaying symbolic math expressions right" -" inside Spyder. A `Cython console`_ allows you to use the Cython language" -" to speed up your code and call C functions directly from Python. " -"Finally, a `Pylab console`_ loads common Numpy and Matplotlib functions " -"by default; while this is deprecated and strongly discouraged for new " -"code, it can still be used if necessary for legacy scripts that need it." +msgid "Spyder also supports several types of specialized consoles. A `Sympy console`_ enables creating and displaying symbolic math expressions right inside Spyder. A `Cython console`_ allows you to use the Cython language to speed up your code and call C functions directly from Python. Finally, a `Pylab console`_ loads common Numpy and Matplotlib functions by default; while this is deprecated and strongly discouraged for new code, it can still be used if necessary for legacy scripts that need it." +msgstr "" + +#: ../../panes/ipythonconsole.rst:58 +msgid "Spyder showing opening a new special Console" msgstr "" #: ../../panes/ipythonconsole.rst:67 -msgid "" -"The options menu allows you to inspect your current environment variables" -" (:guilabel:`Show environment variables`), and the contents of your " -"system's ``PATH`` (:guilabel:`Show sys.path contents`). In addition, you " -"can have each console display how long it has been running with " -":guilabel:`Show elapsed time`." +msgid "The options menu allows you to inspect your current environment variables (:guilabel:`Show environment variables`), and the contents of your system's ``PATH`` (:guilabel:`Show sys.path contents`). In addition, you can have each console display how long it has been running with :guilabel:`Show elapsed time`." +msgstr "" + +#: ../../panes/ipythonconsole.rst:70 +msgid "Spyder IPython Console with options menu" msgstr "" #: ../../panes/ipythonconsole.rst:73 -msgid "" -"You can also change the name of the current :guilabel:`IPython console` " -"tab with the :guilabel:`Rename tab` option, or by simply double-clicking " -"it." +msgid "You can also change the name of the current :guilabel:`IPython console` tab with the :guilabel:`Rename tab` option, or by simply double-clicking it." +msgstr "" + +#: ../../panes/ipythonconsole.rst:75 +msgid "Spyder IPython Console showing renaming console" msgstr "" #: ../../panes/ipythonconsole.rst:84 @@ -1175,13 +1028,11 @@ msgid "Using external kernels" msgstr "" #: ../../panes/ipythonconsole.rst:86 -msgid "" -"You can connect to external local and remote kernels (including those " -"managed by Jupyter Notebook or QtConsole) through the :guilabel:`Connect " -"to an existing kernel` dialog under the :guilabel:`Consoles` menu. For " -"this feature to work, a compatible version of the ``spyder-kernels`` " -"package :ref:`must be installed ` in the " -"environment or machine in which the external kernel is running." +msgid "You can connect to external local and remote kernels (including those managed by Jupyter Notebook or QtConsole) through the :guilabel:`Connect to an existing kernel` dialog under the :guilabel:`Consoles` menu. For this feature to work, a compatible version of the ``spyder-kernels`` package :ref:`must be installed ` in the environment or machine in which the external kernel is running." +msgstr "" + +#: ../../panes/ipythonconsole.rst:89 +msgid "Connect to external kernel dialog of the Spyder IPython console" msgstr "" #: ../../panes/ipythonconsole.rst:94 @@ -1189,37 +1040,38 @@ msgid "Connect to a local kernel" msgstr "" #: ../../panes/ipythonconsole.rst:96 -msgid "" -"To connect to a local kernel that is already running (e.g. one started by" -" Jupyter notebook)," +msgid "To connect to a local kernel that is already running (e.g. one started by Jupyter notebook)," msgstr "" #: ../../panes/ipythonconsole.rst:98 #, python-format -msgid "" -"Run ``%connect_info`` in the notebook or console you want to connect to, " -"and copy the name of its kernel connection file, shown after ``jupyter " -" --existing``." +msgid "Run ``%connect_info`` in the notebook or console you want to connect to, and copy the name of its kernel connection file, shown after ``jupyter --existing``." +msgstr "" + +#: ../../panes/ipythonconsole.rst:100 +msgid "Running connect_info in a Jupyter notebook" msgstr "" #: ../../panes/ipythonconsole.rst:103 -msgid "" -"In Spyder, click :guilabel:`Connect to an existing kernel` from the " -":guilabel:`Consoles` menu, and paste the name of the " -":guilabel:`Connection file` from the previous step." +msgid "In Spyder, click :guilabel:`Connect to an existing kernel` from the :guilabel:`Consoles` menu, and paste the name of the :guilabel:`Connection file` from the previous step." msgstr "" #: ../../panes/ipythonconsole.rst:105 -msgid "" -"As a convenience, kernel ID numbers (e.g. ``1234``) entered in the " -"connection file path field will be expanded to the full path of the file," -" i.e. :file:`{jupyter/runtime/dir/path}/kernal-{id}.json`." +msgid "As a convenience, kernel ID numbers (e.g. ``1234``) entered in the connection file path field will be expanded to the full path of the file, i.e. :file:`{jupyter/runtime/dir/path}/kernal-{id}.json`." +msgstr "" + +#: ../../panes/ipythonconsole.rst:107 +msgid "Copying the connection filename into Spyder's dialog" msgstr "" #: ../../panes/ipythonconsole.rst:110 msgid "Click :guilabel:`OK` to connect to the kernel." msgstr "" +#: ../../panes/ipythonconsole.rst:112 +msgid "Connecting to the kernel and running basic commands." +msgstr "" + #: ../../panes/ipythonconsole.rst:117 msgid "Connect to a remote kernel" msgstr "" @@ -1229,69 +1081,59 @@ msgid "To connect to a kernel on a remote machine," msgstr "" #: ../../panes/ipythonconsole.rst:121 -msgid "" -"Launch a Spyder kernel on the remote host if one is not already running, " -"with ``python -m spyder_kernels.console``." +msgid "Launch a Spyder kernel on the remote host if one is not already running, with ``python -m spyder_kernels.console``." +msgstr "" + +#: ../../panes/ipythonconsole.rst:123 +msgid "Staring a Spyder kernel on a remote machine" msgstr "" #: ../../panes/ipythonconsole.rst:126 -msgid "" -"Copy the kernel's connection file " -"(:file:`{jupyter/runtime/dir/path}/kernel-{pid}.json`) to the machine " -"you're running Spyder on." +msgid "Copy the kernel's connection file (:file:`{jupyter/runtime/dir/path}/kernel-{pid}.json`) to the machine you're running Spyder on." msgstr "" #: ../../panes/ipythonconsole.rst:128 -msgid "" -"You can get :file:`{jupyter/runtime/dir/path}` by executing ``jupyter " -"--runtime-dir`` in the same Python environment as the kernel. Usually, " -"the connection file you are looking for will be one of the newest in this" -" directory, corresponding to the time you started the external kernel." +msgid "You can get :file:`{jupyter/runtime/dir/path}` by executing ``jupyter --runtime-dir`` in the same Python environment as the kernel. Usually, the connection file you are looking for will be one of the newest in this directory, corresponding to the time you started the external kernel." +msgstr "" + +#: ../../panes/ipythonconsole.rst:131 +msgid "Using SCP to copy the connection file to the local machine" msgstr "" #: ../../panes/ipythonconsole.rst:134 -msgid "" -"Click :guilabel:`Connect to an existing kernel` from the " -":guilabel:`Consoles` menu, and browse for or enter the path to the " -"connection file from the previous step." +msgid "Click :guilabel:`Connect to an existing kernel` from the :guilabel:`Consoles` menu, and browse for or enter the path to the connection file from the previous step." msgstr "" #: ../../panes/ipythonconsole.rst:136 -msgid "" -"As a convenience, kernel ID numbers (e.g. ``1234``) entered in the " -"connection file path field will be expanded to " -":file:`{jupyter/runtime/dir/path}/kernal-{id}.json` on your local " -"machine, if you've copied the connection file there." +msgid "As a convenience, kernel ID numbers (e.g. ``1234``) entered in the connection file path field will be expanded to :file:`{jupyter/runtime/dir/path}/kernal-{id}.json` on your local machine, if you've copied the connection file there." +msgstr "" + +#: ../../panes/ipythonconsole.rst:138 +msgid "Opening the connect to kernel dialog and browsing for the path" msgstr "" #: ../../panes/ipythonconsole.rst:141 -msgid "" -"Check the :guilabel:`This is a remote kernel (via SSH)` box and enter the" -" :guilabel:`Hostname` or IP address, username and port to connect to on " -"the remote machine. Then, enter *either* :file:`{username}`'s password on" -" the remote machine, or browse to an SSH keyfile (typically in the " -":file:`.ssh` directory in your home folder on the local machine, often " -"called :file:`id_rsa` or similar) registered on it; only one is needed to" -" connect. If you check :guilabel:`Save connection settings`, these " -"details will be remembered and filled for you automatically next time you" -" open the dialog." +msgid "Check the :guilabel:`This is a remote kernel (via SSH)` box and enter the :guilabel:`Hostname` or IP address, username and port to connect to on the remote machine. Then, enter *either* :file:`{username}`'s password on the remote machine, or browse to an SSH keyfile (typically in the :file:`.ssh` directory in your home folder on the local machine, often called :file:`id_rsa` or similar) registered on it; only one is needed to connect. If you check :guilabel:`Save connection settings`, these details will be remembered and filled for you automatically next time you open the dialog." msgstr "" #: ../../panes/ipythonconsole.rst:145 -msgid "" -"Note that :guilabel:`Port` is the port number on your remote machine that" -" the SSH daemon (``sshd``) is listening on, typically 22 unless you or " -"your administrator has configured it otherwise." +msgid "Note that :guilabel:`Port` is the port number on your remote machine that the SSH daemon (``sshd``) is listening on, typically 22 unless you or your administrator has configured it otherwise." +msgstr "" + +#: ../../panes/ipythonconsole.rst:147 +msgid "Entering pre-filled SSH details into the connection dialog" msgstr "" #: ../../panes/ipythonconsole.rst:150 msgid "Click :guilabel:`OK` to connect to the remote kernel" msgstr "" +#: ../../panes/ipythonconsole.rst:152 +msgid "Connecting to the remote kernel and running basic commands" +msgstr "" + #: ../../panes/ipythonconsole.rst:155 -msgid "" -"For more technical details about connecting to remote kernels, see the " -"`Connecting to a remote kernel`_ page in the IPython Cookbook." +msgid "For more technical details about connecting to remote kernels, see the `Connecting to a remote kernel`_ page in the IPython Cookbook." msgstr "" #: ../../panes/ipythonconsole.rst:165 @@ -1299,26 +1141,23 @@ msgid "Reload changed modules" msgstr "" #: ../../panes/ipythonconsole.rst:167 -msgid "" -"When working in an interactive session, Python only loads a module from " -"its source file once, the first time it is imported." +msgid "When working in an interactive session, Python only loads a module from its source file once, the first time it is imported." msgstr "" #: ../../panes/ipythonconsole.rst:169 -msgid "" -"Spyder's :guilabel:`User Module Reloader` (UMR) automatically reloads " -"modules right in your existing IPython consoles whenever they are " -"modified and re-imported. With the UMR enabled, you can test changes to " -"your code without restarting the kernel." +msgid "Spyder's :guilabel:`User Module Reloader` (UMR) automatically reloads modules right in your existing IPython consoles whenever they are modified and re-imported. With the UMR enabled, you can test changes to your code without restarting the kernel." +msgstr "" + +#: ../../panes/ipythonconsole.rst:172 +msgid "Spyder showing reloading modules in console" msgstr "" #: ../../panes/ipythonconsole.rst:175 -msgid "" -"UMR is enabled by default, and it will provide you with a red ``Reloaded " -"modules:`` message in the console listing the files it has refreshed when" -" it is activated. If desired, you can turn it on or off, and prevent " -"specific modules from being reloaded, under :menuselection:`Preferences " -"--> Python interpreter --> User Module Reloader (UMR)`." +msgid "UMR is enabled by default, and it will provide you with a red ``Reloaded modules:`` message in the console listing the files it has refreshed when it is activated. If desired, you can turn it on or off, and prevent specific modules from being reloaded, under :menuselection:`Preferences --> Python interpreter --> User Module Reloader (UMR)`." +msgstr "" + +#: ../../panes/ipythonconsole.rst:178 +msgid "Spyder preferences showing option to use module reloader" msgstr "" #: ../../panes/ipythonconsole.rst:187 ../../panes/variableexplorer.rst:196 @@ -1338,10 +1177,11 @@ msgid "Online Help" msgstr "" #: ../../panes/onlinehelp.rst:5 -msgid "" -"The **Online Help** pane provides a built-in web browser to explore " -"dynamically generated Python documentation on installed modules—including" -" your own—rendered by a `pydoc`_ server running in the background." +msgid "The **Online Help** pane provides a built-in web browser to explore dynamically generated Python documentation on installed modules—including your own—rendered by a `pydoc`_ server running in the background." +msgstr "" + +#: ../../panes/onlinehelp.rst:9 +msgid "Spyder Online Help pane on the index page, a list of builtin modules" msgstr "" #: ../../panes/onlinehelp.rst:16 @@ -1349,42 +1189,51 @@ msgid "Using the Online Help" msgstr "" #: ../../panes/onlinehelp.rst:18 -msgid "" -"The Online Help's home shows an index where you can browse the " -"documentation of standard library modules, third party packages installed" -" in your Python environment, and your own local code. Click on the name " -"of any module to open its documentation." +msgid "The Online Help's home shows an index where you can browse the documentation of standard library modules, third party packages installed in your Python environment, and your own local code. Click on the name of any module to open its documentation." +msgstr "" + +#: ../../panes/onlinehelp.rst:21 +msgid "Spyder Online Help pane showing module browsing" msgstr "" #: ../../panes/onlinehelp.rst:24 -msgid "" -"Enter the name of the item you'd like help on in the :guilabel:`Package` " -"field to load its documentation directly." +msgid "Enter the name of the item you'd like help on in the :guilabel:`Package` field to load its documentation directly." +msgstr "" + +#: ../../panes/onlinehelp.rst:26 +msgid "Spyder Online Help pane showing module browsing by name" msgstr "" #: ../../panes/onlinehelp.rst:29 -msgid "" -"The module's file location is linked to the right of the doc's title, " -"which you can click to view its source code." +msgid "The module's file location is linked to the right of the doc's title, which you can click to view its source code." +msgstr "" + +#: ../../panes/onlinehelp.rst:31 +msgid "Spyder Online Help pane showing source code clicking module's path" msgstr "" #: ../../panes/onlinehelp.rst:34 -msgid "" -"Standard library modules also have a link to the corresponding `Python " -"docs`_, which can be viewed right inside of the pane." +msgid "Standard library modules also have a link to the corresponding `Python docs`_, which can be viewed right inside of the pane." +msgstr "" + +#: ../../panes/onlinehelp.rst:38 +msgid "Spyder Online Help pane showing python docs embedded in pane" msgstr "" #: ../../panes/onlinehelp.rst:41 -msgid "" -"If you're not sure of the name of the object you want help on, or are " -"looking for a specific keyword, use the :guilabel:`Search` field to get a" -" list of results." +msgid "If you're not sure of the name of the object you want help on, or are looking for a specific keyword, use the :guilabel:`Search` field to get a list of results." +msgstr "" + +#: ../../panes/onlinehelp.rst:43 +msgid "Spyder Online Help pane showing search of a keyword" msgstr "" #: ../../panes/onlinehelp.rst:46 -msgid "" -"Links above the search field provide an index of topics with general help" -" and a list of Python keywords linked to their corresponding docs." +msgid "Links above the search field provide an index of topics with general help and a list of Python keywords linked to their corresponding docs." +msgstr "" + +#: ../../panes/onlinehelp.rst:48 +msgid "Spyder Online Help pane on the topics page" msgstr "" #: ../../panes/onlinehelp.rst:55 @@ -1392,38 +1241,43 @@ msgid "Toolbar items" msgstr "" #: ../../panes/onlinehelp.rst:57 -msgid "" -"Just like in a web browser, the forward and back buttons move through the" -" pages you have visited, and the home button (house icon) returns you to " -"the module index." +msgid "Just like in a web browser, the forward and back buttons move through the pages you have visited, and the home button (house icon) returns you to the module index." +msgstr "" + +#: ../../panes/onlinehelp.rst:59 +msgid "Spyder Online Help pane showing navigation with arrows" msgstr "" #: ../../panes/onlinehelp.rst:62 -msgid "" -"Perform a realtime search within a page's content with the " -":guilabel:`Find` button (magnifying glass icon top left) or " -":kbd:`Ctrl-F`, navigate through matches with the Up and Down buttons, and" -" make matching case sensitive with the :guilabel:`Aa` button." +msgid "Perform a realtime search within a page's content with the :guilabel:`Find` button (magnifying glass icon top left) or :kbd:`Ctrl-F`, navigate through matches with the Up and Down buttons, and make matching case sensitive with the :guilabel:`Aa` button." +msgstr "" + +#: ../../panes/onlinehelp.rst:64 +msgid "Spyder Online Help pane showing finding a word on a module" msgstr "" #: ../../panes/onlinehelp.rst:67 -msgid "" -"You can view and re-run previous searches from the drop-down menu in the " -":guilabel:`Package` field." +msgid "You can view and re-run previous searches from the drop-down menu in the :guilabel:`Package` field." +msgstr "" + +#: ../../panes/onlinehelp.rst:69 +msgid "Spyder Online Help pane showing previous searches" msgstr "" #: ../../panes/onlinehelp.rst:72 -msgid "" -"You can also use the zoom in/out buttons (:guilabel:`-` and " -":guilabel:`+`, top right) to change the font size to suit your " -"preferences." +msgid "You can also use the zoom in/out buttons (:guilabel:`-` and :guilabel:`+`, top right) to change the font size to suit your preferences." +msgstr "" + +#: ../../panes/onlinehelp.rst:74 +msgid "Spyder Online Help pane showing changing the font" msgstr "" #: ../../panes/onlinehelp.rst:77 -msgid "" -"To cancel searching or page loading, click the stop button (red square), " -"and to reload the page (such as when you change your own package's " -"documentation), press the refresh button (circular arrow)." +msgid "To cancel searching or page loading, click the stop button (red square), and to reload the page (such as when you change your own package's documentation), press the refresh button (circular arrow)." +msgstr "" + +#: ../../panes/onlinehelp.rst:79 +msgid "Spyder Online Help pane showing refreshing pane when updating docs" msgstr "" #: ../../panes/outline.rst:3 @@ -1431,20 +1285,19 @@ msgid "Outline" msgstr "" #: ../../panes/outline.rst:5 -msgid "" -"The **Outline** pane allows you to view and navigate the functions, " -"classes, methods, cells and comments in open Python files. To show or " -"hide the Outline pane, use :menuselection:`View --> Panes --> Outline` or" -" :kbd:`Ctrl-Shift-O` / :kbd:`Cmd-Shift-O`. Click an entry in the outline " -"to jump to its source file location, and use the :guilabel:`Go to cursor " -"position` toolbar button to highlight the item corresponding to the " -"current :doc:`editor` position." +msgid "The **Outline** pane allows you to view and navigate the functions, classes, methods, cells and comments in open Python files. To show or hide the Outline pane, use :menuselection:`View --> Panes --> Outline` or :kbd:`Ctrl-Shift-O` / :kbd:`Cmd-Shift-O`. Click an entry in the outline to jump to its source file location, and use the :guilabel:`Go to cursor position` toolbar button to highlight the item corresponding to the current :doc:`editor` position." +msgstr "" + +#: ../../panes/outline.rst:9 +msgid "Outline pane" msgstr "" #: ../../panes/outline.rst:18 -msgid "" -"The options menu in the top-right of the pane allows customizing how the " -"outline is displayed." +msgid "The options menu in the top-right of the pane allows customizing how the outline is displayed." +msgstr "" + +#: ../../panes/outline.rst:20 +msgid "Outline options menu" msgstr "" #: ../../panes/outline.rst:23 @@ -1452,48 +1305,31 @@ msgid "These customization settings include:" msgstr "" #: ../../panes/outline.rst:25 -msgid "" -":guilabel:`Show absolute path`: Display the full path to each file " -"instead of just the name." +msgid ":guilabel:`Show absolute path`: Display the full path to each file instead of just the name." msgstr "" #: ../../panes/outline.rst:26 -msgid "" -":guilabel:`Show all files`: List every open file rather than just the " -"current one. This allows using the Outline as a file switcher." +msgid ":guilabel:`Show all files`: List every open file rather than just the current one. This allows using the Outline as a file switcher." msgstr "" #: ../../panes/outline.rst:28 -msgid "" -":guilabel:`Group code cells`: Group code cells in multiple nested levels " -"in the outline rather than showing all cells in one level. You can create" -" subsections by adding more ``%`` signs to the cell separator." +msgid ":guilabel:`Group code cells`: Group code cells in multiple nested levels in the outline rather than showing all cells in one level. You can create subsections by adding more ``%`` signs to the cell separator." msgstr "" #: ../../panes/outline.rst:30 -msgid "" -":guilabel:`Display variables and attributes`: Display top-level " -"variable/constant definitions and class attributes in the outline." +msgid ":guilabel:`Display variables and attributes`: Display top-level variable/constant definitions and class attributes in the outline." msgstr "" #: ../../panes/outline.rst:31 -msgid "" -":guilabel:`Follow cursor position`: Automatically highlight and expand " -"the entry corresponding to the current cursor position in the " -":doc:`editor`." +msgid ":guilabel:`Follow cursor position`: Automatically highlight and expand the entry corresponding to the current cursor position in the :doc:`editor`." msgstr "" #: ../../panes/outline.rst:32 -msgid "" -":guilabel:`Show special comments`: List special comments in the outline, " -"which start with ``# ----``." +msgid ":guilabel:`Show special comments`: List special comments in the outline, which start with ``# ----``." msgstr "" #: ../../panes/outline.rst:33 -msgid "" -":guilabel:`Sort files alphabetically`: Sort the file list in alphabetical" -" order. When disabled, all tabs will be sorted by the tab order of the " -"currently selected Editor panel." +msgid ":guilabel:`Sort files alphabetically`: Sort the file list in alphabetical order. When disabled, all tabs will be sorted by the tab order of the currently selected Editor panel." msgstr "" #: ../../panes/outline.rst:40 @@ -1529,26 +1365,23 @@ msgid "Plots" msgstr "" #: ../../panes/plots.rst:5 -msgid "" -"The **Plots** pane shows the static figures and images created during " -"your session. It will show you plots from the :doc:`ipythonconsole`, " -"produced by your code in the :doc:`editor` or generated by the " -":doc:`variableexplorer` allowing you to interact with them in several " -"ways." +msgid "The **Plots** pane shows the static figures and images created during your session. It will show you plots from the :doc:`ipythonconsole`, produced by your code in the :doc:`editor` or generated by the :doc:`variableexplorer` allowing you to interact with them in several ways." +msgstr "" + +#: ../../panes/plots.rst:8 +msgid "Spyder main window showing execution for the Plots pane" msgstr "" #: ../../panes/plots.rst:11 -msgid "" -"The figures shown in the Plots pane are those associated with the " -"currently active :guilabel:`Console` tab; if you switch consoles, the " -"list of plots displayed (or none at all, if a new console) will change " -"accordingly." +msgid "The figures shown in the Plots pane are those associated with the currently active :guilabel:`Console` tab; if you switch consoles, the list of plots displayed (or none at all, if a new console) will change accordingly." +msgstr "" + +#: ../../panes/plots.rst:13 +msgid "Spyder's plots pane and console showing switching consoles" msgstr "" #: ../../panes/plots.rst:22 -msgid "" -"The options menu in the top right of the :guilabel:`Plots` pane offers " -"several ways to customize how your plots are displayed." +msgid "The options menu in the top right of the :guilabel:`Plots` pane offers several ways to customize how your plots are displayed." msgstr "" #: ../../panes/plots.rst:26 @@ -1556,10 +1389,11 @@ msgid "Mute inline plotting" msgstr "" #: ../../panes/plots.rst:28 -msgid "" -"The :guilabel:`Mute inline plotting` option is enabled by default, " -"preventing your plots from appearing in the Console. If you deactivate " -"this option, figures will display in both the Plots pane and the Console." +msgid "The :guilabel:`Mute inline plotting` option is enabled by default, preventing your plots from appearing in the Console. If you deactivate this option, figures will display in both the Plots pane and the Console." +msgstr "" + +#: ../../panes/plots.rst:31 +msgid "Spyder's plots pane and console showing plots in the console" msgstr "" #: ../../panes/plots.rst:36 @@ -1567,10 +1401,11 @@ msgid "Show plot outline" msgstr "" #: ../../panes/plots.rst:38 -msgid "" -"The :guilabel:`Show plot outline` option, off by default, shows a thin " -"stroke surrounding the area of the figure area, which will also appear in" -" the exported images." +msgid "The :guilabel:`Show plot outline` option, off by default, shows a thin stroke surrounding the area of the figure area, which will also appear in the exported images." +msgstr "" + +#: ../../panes/plots.rst:40 +msgid "Spyder's plots pane showing a plot's outline" msgstr "" #: ../../panes/plots.rst:45 @@ -1578,11 +1413,11 @@ msgid "Fit plots to window" msgstr "" #: ../../panes/plots.rst:47 -msgid "" -"The :guilabel:`Fit plots to Window` option, also enabled by default, " -"sizes the figures to match the pane. Disabling it will display plots at " -"their native size, and allow you use the zoom buttons at the top of the " -"pane to scale them manually." +msgid "The :guilabel:`Fit plots to Window` option, also enabled by default, sizes the figures to match the pane. Disabling it will display plots at their native size, and allow you use the zoom buttons at the top of the pane to scale them manually." +msgstr "" + +#: ../../panes/plots.rst:50 +msgid "Spyder main window showing plots zoom" msgstr "" #: ../../panes/plots.rst:57 @@ -1590,32 +1425,35 @@ msgid "Toolbar options" msgstr "" #: ../../panes/plots.rst:59 -msgid "" -"The toolbar at the top of the Plots pane provides several useful features" -" that allow you to interact with your figures. For example, you can cycle" -" sequentially through the plot list with the forward and back arrows." +msgid "The toolbar at the top of the Plots pane provides several useful features that allow you to interact with your figures. For example, you can cycle sequentially through the plot list with the forward and back arrows." +msgstr "" + +#: ../../panes/plots.rst:62 +msgid "Spyder main window showing plot navigation using arrows." msgstr "" #: ../../panes/plots.rst:65 -msgid "" -"You can also save one or all the plots in the pane to file(s) by clicking" -" the respective \"save\"/\"save all\" icons in the toolbar. Plots are " -"rendered and saved as PNG by default, but SVG can be selected as an " -"option under :menuselection:`Preferences --> IPython console --> Graphics" -" --> Inline backend --> Format`." +msgid "You can also save one or all the plots in the pane to file(s) by clicking the respective \"save\"/\"save all\" icons in the toolbar. Plots are rendered and saved as PNG by default, but SVG can be selected as an option under :menuselection:`Preferences --> IPython console --> Graphics --> Inline backend --> Format`." +msgstr "" + +#: ../../panes/plots.rst:68 +msgid "Spyder plots pane showing saving a plot." msgstr "" #: ../../panes/plots.rst:71 -msgid "" -"Additionally, if you want to use a figure in another document, you can " -"click the \"copy to clipboard\" button and paste your plot wherever you " -"want, such as a word processor." +msgid "Additionally, if you want to use a figure in another document, you can click the \"copy to clipboard\" button and paste your plot wherever you want, such as a word processor." +msgstr "" + +#: ../../panes/plots.rst:73 +msgid "Spyder Plots pane showing pasting plot in LibreOffice." msgstr "" #: ../../panes/plots.rst:76 -msgid "" -"Finally, you can use the \"remove\" and \"remove all\" buttons in the " -"toolbar to clear plots from the list." +msgid "Finally, you can use the \"remove\" and \"remove all\" buttons in the toolbar to clear plots from the list." +msgstr "" + +#: ../../panes/plots.rst:78 +msgid "Spyder plots pane showing pasting plot in LibreOffice." msgstr "" #: ../../panes/profiler.rst:3 @@ -1623,13 +1461,12 @@ msgid "Profiler" msgstr "" #: ../../panes/profiler.rst:5 -msgid "" -"The **Profiler** pane recursively determines the run time and number of " -"calls for every function and method called in a file, breaking down each " -"procedure into its smallest individual units. This allows you to easily " -"identify the bottlenecks in your code, points you toward the exact " -"statements most critical for optimization, and measures the performance " -"delta after followup changes." +msgid "The **Profiler** pane recursively determines the run time and number of calls for every function and method called in a file, breaking down each procedure into its smallest individual units. This allows you to easily identify the bottlenecks in your code, points you toward the exact statements most critical for optimization, and measures the performance delta after followup changes." +msgstr "" + +#: ../../panes/profiler.rst:8 ../../panes/profiler.rst:84 +#: ../../panes/profiler.rst:92 +msgid "Spyder Profiler pane, displaying a list of functions and their execution time" msgstr "" #: ../../panes/profiler.rst:15 @@ -1637,60 +1474,55 @@ msgid "Running the Profiler" msgstr "" #: ../../panes/profiler.rst:17 -msgid "" -"You can browse for a file using the open button to the right of the " -"Profiler's path box (top left of the pane), which will run profiling over" -" this file automatically." +msgid "You can browse for a file using the open button to the right of the Profiler's path box (top left of the pane), which will run profiling over this file automatically." +msgstr "" + +#: ../../panes/profiler.rst:19 +msgid "Spyder Profiler pane, showing browsing a file and running profiler" msgstr "" #: ../../panes/profiler.rst:22 -msgid "" -"You can manually enter the path in the pane's path box and then run the " -"analysis on the file by pressing :guilabel:`Profile` in the Profiler " -"pane." +msgid "You can manually enter the path in the pane's path box and then run the analysis on the file by pressing :guilabel:`Profile` in the Profiler pane." msgstr "" #: ../../panes/profiler.rst:24 -msgid "" -"You can also run profiling for the file that is currently open in the " -":doc:`editor` by clicking :menuselection:`&Run --> Profile` in the menu " -"bar, or by using a configurable shortcut (:kbd:`F10` by default)." +msgid "You can also run profiling for the file that is currently open in the :doc:`editor` by clicking :menuselection:`&Run --> Profile` in the menu bar, or by using a configurable shortcut (:kbd:`F10` by default)." +msgstr "" + +#: ../../panes/profiler.rst:27 ../../panes/profiler.rst:51 +msgid "Spyder Profiler pane, showing running profiler from menu bar" msgstr "" #: ../../panes/profiler.rst:30 -msgid "" -"If you'd like to cancel an in-progress run, click the :guilabel:`Stop` " -"button in the top right, and if profiling fails for any reason, the " -":guilabel:`Output` dialog will be displayed, indicating the error that " -"occurred." +msgid "If you'd like to cancel an in-progress run, click the :guilabel:`Stop` button in the top right, and if profiling fails for any reason, the :guilabel:`Output` dialog will be displayed, indicating the error that occurred." msgstr "" #: ../../panes/profiler.rst:32 -msgid "" -"By double-clicking an item in the Profiler, you will be taken to the file" -" and line in the :doc:`editor` where it was called." +msgid "By double-clicking an item in the Profiler, you will be taken to the file and line in the :doc:`editor` where it was called." +msgstr "" + +#: ../../panes/profiler.rst:34 +msgid "Spyder Profiler pane, showing opening a file when clicking on its analysis" msgstr "" #: ../../panes/profiler.rst:37 -msgid "" -"You can increase the number of levels displayed for a particular object " -"by clicking the dropdown arrows to the left of the name, and " -"expand/collapse all the items with the buttons in the top left." +msgid "You can increase the number of levels displayed for a particular object by clicking the dropdown arrows to the left of the name, and expand/collapse all the items with the buttons in the top left." +msgstr "" + +#: ../../panes/profiler.rst:39 +msgid "Spyder Profiler pane, showing dropdown arrows and buttons for expanding and collapsing" msgstr "" #: ../../panes/profiler.rst:42 -msgid "" -"By clicking the dropdown or press the :kbd:`Down Arrow` key in the " -"filename field, you can recall paths of previous profiled files." +msgid "By clicking the dropdown or press the :kbd:`Down Arrow` key in the filename field, you can recall paths of previous profiled files." +msgstr "" + +#: ../../panes/profiler.rst:44 +msgid "Spyder Profiler pane, showing dropdown of previous profiled files" msgstr "" #: ../../panes/profiler.rst:47 -msgid "" -"Finally, you can save the data for a given run to disk as a file with the" -" ``.Result`` extension using the :guilabel:`Save data` button. This can " -"be loaded to compare with a previous run of the same file using the " -":guilabel:`Load data` button. To remove the loaded data, click the " -":guilabel:`Clear comparison` button." +msgid "Finally, you can save the data for a given run to disk as a file with the ``.Result`` extension using the :guilabel:`Save data` button. This can be loaded to compare with a previous run of the same file using the :guilabel:`Load data` button. To remove the loaded data, click the :guilabel:`Clear comparison` button." msgstr "" #: ../../panes/profiler.rst:58 @@ -1698,31 +1530,15 @@ msgid "Interpreting the results" msgstr "" #: ../../panes/profiler.rst:60 -msgid "" -"Results are broken down by function/method/statement, with each sub-" -"element listed hierarchically under the top-level item that called them. " -":guilabel:`Total Time` is that taken by the specified item and every " -"function \"underneath\" (*i.e.* called by) it, while :guilabel:`Local " -"Time` only counts the time spent in the particular callable object's own " -"scope. The :guilabel:`Calls` column displays the total number of times " -"the specified object was called at that level inside its parent calling " -"function (or within the ``__main__`` scope, if a top-level object). " -"Finally, the numbers in the :guilabel:`Diff` columns for each of the " -"three appear if a comparison is loaded, and indicate the deltas between " -"each measurement." +msgid "Results are broken down by function/method/statement, with each sub-element listed hierarchically under the top-level item that called them. :guilabel:`Total Time` is that taken by the specified item and every function \"underneath\" (*i.e.* called by) it, while :guilabel:`Local Time` only counts the time spent in the particular callable object's own scope. The :guilabel:`Calls` column displays the total number of times the specified object was called at that level inside its parent calling function (or within the ``__main__`` scope, if a top-level object). Finally, the numbers in the :guilabel:`Diff` columns for each of the three appear if a comparison is loaded, and indicate the deltas between each measurement." +msgstr "" + +#: ../../panes/profiler.rst:65 +msgid "Profiler with a comparison loaded, displaying the time deltas between two runs" msgstr "" #: ../../panes/profiler.rst:68 -msgid "" -"For example, suppose you ran the :guilabel:`Profiler` on a file calling a" -" function ``sleep_wrapper()`` that in turn called the ``sleep()`` " -"function, and the ``sleep_wrapper()`` function took a total of 3.87 ms to" -" run, with 3.86 ms of that spent executing the ``sleep()`` function " -"inside it. Therefore, if ``sleep()`` called nothing else itself, its " -":guilabel:`Total Time` and :guilabel:`Local Time` would both be " -"identical, at 3.87 ms. Meanwhile, :guilabel:`Total Time` for " -"``sleep_wrapper()`` would be 3.86 ms, but :guilabel:`Local Time` only " -"0.01 ms as the rest was spent inside the ``sleep()`` function it called." +msgid "For example, suppose you ran the :guilabel:`Profiler` on a file calling a function ``sleep_wrapper()`` that in turn called the ``sleep()`` function, and the ``sleep_wrapper()`` function took a total of 3.87 ms to run, with 3.86 ms of that spent executing the ``sleep()`` function inside it. Therefore, if ``sleep()`` called nothing else itself, its :guilabel:`Total Time` and :guilabel:`Local Time` would both be identical, at 3.87 ms. Meanwhile, :guilabel:`Total Time` for ``sleep_wrapper()`` would be 3.86 ms, but :guilabel:`Local Time` only 0.01 ms as the rest was spent inside the ``sleep()`` function it called." msgstr "" #: ../../panes/profiler.rst:76 @@ -1730,17 +1546,11 @@ msgid "Profiler plugins" msgstr "" #: ../../panes/profiler.rst:78 -msgid "" -"There are two additional plugins that you can install to enable other " -"types of profiling in Spyder. First, Spyder Line Profiler allows you to " -"benchmark each line of your code individually. To learn more, visit the " -"`spyder-line-profiler git repository`_." +msgid "There are two additional plugins that you can install to enable other types of profiling in Spyder. First, Spyder Line Profiler allows you to benchmark each line of your code individually. To learn more, visit the `spyder-line-profiler git repository`_." msgstr "" #: ../../panes/profiler.rst:87 -msgid "" -"Second, Spyder Memory Profiler measures the memory usage of your code. " -"For more information, go to the `spyder-memory-profiler git repository`_." +msgid "Second, Spyder Memory Profiler measures the memory usage of your code. For more information, go to the `spyder-memory-profiler git repository`_." msgstr "" #: ../../panes/projects.rst:3 @@ -1748,28 +1558,19 @@ msgid "Projects" msgstr "" #: ../../panes/projects.rst:5 -msgid "" -"Spyder allows you to associate a given directory with a **Project**, " -"which automatically saves and restores the files you have open in the " -":doc:`editor` from the last time you opened that project. With the " -":ref:`Project ` pane, you can browse all your project's" -" files, regardless of your current working directory or " -":doc:`fileexplorer` location." +msgid "Spyder allows you to associate a given directory with a **Project**, which automatically saves and restores the files you have open in the :doc:`editor` from the last time you opened that project. With the :ref:`Project ` pane, you can browse all your project's files, regardless of your current working directory or :doc:`fileexplorer` location." +msgstr "" + +#: ../../panes/projects.rst:8 +msgid "Spyder showing Project Explorer and projects menu" msgstr "" #: ../../panes/projects.rst:11 -msgid "" -"In addition, your project's root folder is used to set your working " -"directory, and automatically added to the ``PYTHONPATH``, so you can " -"easily ``import`` and work with any modules and packages you create " -"inside of it." +msgid "In addition, your project's root folder is used to set your working directory, and automatically added to the ``PYTHONPATH``, so you can easily ``import`` and work with any modules and packages you create inside of it." msgstr "" #: ../../panes/projects.rst:15 -msgid "" -"Projects are completely optional and not imposed on users. All of Spyder'" -" functionality (code completion, session saving, File Explorer, working " -"directory, etc) is available without creating a :guilabel:`Project`." +msgid "Projects are completely optional and not imposed on users. All of Spyder' functionality (code completion, session saving, File Explorer, working directory, etc) is available without creating a :guilabel:`Project`." msgstr "" #: ../../panes/projects.rst:22 @@ -1777,11 +1578,11 @@ msgid "Creating a Project" msgstr "" #: ../../panes/projects.rst:24 -msgid "" -"To create a :guilabel:`Project`, click the :guilabel:`New Project` entry " -"in the :guilabel:`Projects` menu, choose whether you'd like to associate " -"a :guilabel:`Project` with an existing directory or make a new one, and " -"enter the :guilabel:`Project`'s name and path." +msgid "To create a :guilabel:`Project`, click the :guilabel:`New Project` entry in the :guilabel:`Projects` menu, choose whether you'd like to associate a :guilabel:`Project` with an existing directory or make a new one, and enter the :guilabel:`Project`'s name and path." +msgstr "" + +#: ../../panes/projects.rst:26 +msgid "Spyder showing opening a new project" msgstr "" #: ../../panes/projects.rst:35 @@ -1789,11 +1590,11 @@ msgid "Using the Projects Pane" msgstr "" #: ../../panes/projects.rst:37 -msgid "" -"Once a :guilabel:`Project` is opened, the :guilabel:`Project` pane is " -"shown, presenting a tree view of the current :guilabel:`Project`'s files " -"and directories. It allows you to perform all the same :ref:`operations" -"` as Spyder's :doc:`fileexplorer` pane." +msgid "Once a :guilabel:`Project` is opened, the :guilabel:`Project` pane is shown, presenting a tree view of the current :guilabel:`Project`'s files and directories. It allows you to perform all the same :ref:`operations` as Spyder's :doc:`fileexplorer` pane." +msgstr "" + +#: ../../panes/projects.rst:40 +msgid "Spyder Project Explorer, displaying a directory tree of project files" msgstr "" #: ../../panes/projects.rst:49 @@ -1801,18 +1602,11 @@ msgid "Working with version control" msgstr "" #: ../../panes/projects.rst:51 -msgid "" -"The :guilabel:`Project` pane has basic integration with the `Git`_ " -"distributed version control system, just like :ref:`in the Files pane" -"`. You can commit or browse a file, directory or the " -"entire repository via the commands in the context menu." +msgid "The :guilabel:`Project` pane has basic integration with the `Git`_ distributed version control system, just like :ref:`in the Files pane`. You can commit or browse a file, directory or the entire repository via the commands in the context menu." msgstr "" #: ../../panes/projects.rst:56 -msgid "" -"To use this functionality, the :guilabel:`Project` must be located in a " -"``git`` repository and the ``git`` and ``gitk`` commands must be on the " -"system path." +msgid "To use this functionality, the :guilabel:`Project` must be located in a ``git`` repository and the ``git`` and ``gitk`` commands must be on the system path." msgstr "" #: ../../panes/pylint.rst:3 @@ -1820,14 +1614,11 @@ msgid "Code Analysis" msgstr "" #: ../../panes/pylint.rst:5 -msgid "" -"The **Code Analysis** pane detects style issues, bad practices, potential" -" bugs, and other quality problems in your code, all without having to " -"actually execute it. Based on these results, it also gives your code an " -"overall quality score. Spyder's code analyzer is powered by the best-in-" -"class `Pylint`_ back-end, which can intelligently detect an enormous and " -"customizable range of potential errors, bad practices, quality issues, " -"style violations, and more." +msgid "The **Code Analysis** pane detects style issues, bad practices, potential bugs, and other quality problems in your code, all without having to actually execute it. Based on these results, it also gives your code an overall quality score. Spyder's code analyzer is powered by the best-in-class `Pylint`_ back-end, which can intelligently detect an enormous and customizable range of potential errors, bad practices, quality issues, style violations, and more." +msgstr "" + +#: ../../panes/pylint.rst:11 +msgid "Spyder Pylint pane, showing numerous issues discovered in a file" msgstr "" #: ../../panes/pylint.rst:18 @@ -1835,52 +1626,51 @@ msgid "Using the code analyzer" msgstr "" #: ../../panes/pylint.rst:20 -msgid "" -"You can select the desired file to analyze directly in the :doc:`editor` " -"by clicking anywhere within it. To run the analysis, press the " -"configurable shortcut (:kbd:`F8` by default), select " -":menuselection:`Source --> Run code analysis` from the menu bar or click " -"the :guilabel:`Analyze` button in the Code Analysis pane. If the Code " -"Analysis pane is not visible, you can open it under :menuselection:`View " -"--> Panes --> Code Analysis`. All standard checks are run by default. To " -"go directly to a line in the :doc:`editor` highlighted by a failed check," -" just click its name." +msgid "You can select the desired file to analyze directly in the :doc:`editor` by clicking anywhere within it. To run the analysis, press the configurable shortcut (:kbd:`F8` by default), select :menuselection:`Source --> Run code analysis` from the menu bar or click the :guilabel:`Analyze` button in the Code Analysis pane. If the Code Analysis pane is not visible, you can open it under :menuselection:`View --> Panes --> Code Analysis`. All standard checks are run by default. To go directly to a line in the :doc:`editor` highlighted by a failed check, just click its name." +msgstr "" + +#: ../../panes/pylint.rst:26 +msgid "Spyder Pylint pane, showing running analysis and clicking failed check" msgstr "" #: ../../panes/pylint.rst:29 -msgid "" -"You can also manually enter the path of a file you'd like it to check in " -"the path entry box in the pane's toolbar. The analyzer works with both " -"individual scripts and whole Python packages (directories containing an " -":file:`__init__.py` file)." +msgid "You can also manually enter the path of a file you'd like it to check in the path entry box in the pane's toolbar. The analyzer works with both individual scripts and whole Python packages (directories containing an :file:`__init__.py` file)." +msgstr "" + +#: ../../panes/pylint.rst:32 +msgid "Spyder Pylint pane, showing running analysis browsing file" msgstr "" #: ../../panes/pylint.rst:35 -msgid "" -"Cancel analyzing a file with the :guilabel:`Stop` button, and if analysis" -" fails, click the :guilabel:`Output` button to find out why. If Pylint " -"does succeed, the :guilabel:`Output` will show the raw plain text " -"analysis results on the selected file, allowing you to easily browse and " -"copy/paste the full message names and descriptions." +msgid "Cancel analyzing a file with the :guilabel:`Stop` button, and if analysis fails, click the :guilabel:`Output` button to find out why. If Pylint does succeed, the :guilabel:`Output` will show the raw plain text analysis results on the selected file, allowing you to easily browse and copy/paste the full message names and descriptions." +msgstr "" + +#: ../../panes/pylint.rst:38 +msgid "Spyder Pylint pane, showing output" msgstr "" #: ../../panes/pylint.rst:41 -msgid "" -"Finally, you can click the dropdown or press the dropdown arrow in the " -"filename field to view results of previous analyses." +msgid "Finally, you can click the dropdown or press the dropdown arrow in the filename field to view results of previous analyses." +msgstr "" + +#: ../../panes/pylint.rst:43 +msgid "Spyder Pylint pane, showing history" msgstr "" #: ../../panes/pylint.rst:52 -msgid "" -"The number of recent runs Spyder should remember can be customized in the" -" :guilabel:`History` dialog, available from the Code Analysis options " -"menu." +msgid "The number of recent runs Spyder should remember can be customized in the :guilabel:`History` dialog, available from the Code Analysis options menu." +msgstr "" + +#: ../../panes/pylint.rst:54 +msgid "Spyder Pylint pane, customizing history dialog" msgstr "" #: ../../panes/pylint.rst:57 -msgid "" -"You can also expand or collapse one or all the sections in the pane by " -"using the corresponding options in the options menu." +msgid "You can also expand or collapse one or all the sections in the pane by using the corresponding options in the options menu." +msgstr "" + +#: ../../panes/pylint.rst:59 +msgid "Spyder Pylint pane, expanding and collapsing sections" msgstr "" #: ../../panes/pylint.rst:66 @@ -1888,23 +1678,19 @@ msgid "Advanced options" msgstr "" #: ../../panes/pylint.rst:68 -msgid "" -"You can turn certain messages off at the line, block or file/module level" -" by adding a ``# pylint: disable=MESSAGE-NAMES`` comment at the " -"respective `scope`_, where ``MESSAGE_NAMES`` should be replaced with a " -"comma-separated list (or single value) of `Pylint message names`_. For " -"example, a directive might look like ``# pylint: disable=invalid-name``, " -"or ``# pylint: disable=fixme, line-too-long``." +msgid "You can turn certain messages off at the line, block or file/module level by adding a ``# pylint: disable=MESSAGE-NAMES`` comment at the respective `scope`_, where ``MESSAGE_NAMES`` should be replaced with a comma-separated list (or single value) of `Pylint message names`_. For example, a directive might look like ``# pylint: disable=invalid-name``, or ``# pylint: disable=fixme, line-too-long``." +msgstr "" + +#: ../../panes/pylint.rst:75 +msgid "Spyder Pylint pane, showing disabling a message locally" msgstr "" #: ../../panes/pylint.rst:78 -msgid "" -"Or, you can globally suppress specific messages and adjust other Pylint " -"settings by editing the :file:`.pylintrc` configuration file in your user" -" folder. If it doesn't exist, you can generate it by running ``pylint " -"--generate-rcfile > .pylintrc`` in your user directory, from Anaconda " -"Prompt (on Windows) or your terminal (macOS/Linux). For more details on " -"configuring Pylint, see the `Pylint documentation`_." +msgid "Or, you can globally suppress specific messages and adjust other Pylint settings by editing the :file:`.pylintrc` configuration file in your user folder. If it doesn't exist, you can generate it by running ``pylint --generate-rcfile > .pylintrc`` in your user directory, from Anaconda Prompt (on Windows) or your terminal (macOS/Linux). For more details on configuring Pylint, see the `Pylint documentation`_." +msgstr "" + +#: ../../panes/pylint.rst:84 +msgid "Spyder Pylint pane, disabling a message globally in the .pylintrc" msgstr "" #: ../../panes/pylint.rst:94 @@ -1916,24 +1702,27 @@ msgid "Variable Explorer" msgstr "" #: ../../panes/variableexplorer.rst:5 -msgid "" -"The **Variable Explorer** allows you to interactively browse and manage " -"the objects generated running your code." +msgid "The **Variable Explorer** allows you to interactively browse and manage the objects generated running your code." +msgstr "" + +#: ../../panes/variableexplorer.rst:7 +msgid "Spyder Variable Explorer execution with a variable of type list" msgstr "" #: ../../panes/variableexplorer.rst:10 -msgid "" -"It shows the namespace contents (including all global objects, variables," -" class instances and more) of the currently selected " -":doc:`ipythonconsole` session, and allows you to add, remove, and edit " -"their values through a variety of GUI-based editors." +msgid "It shows the namespace contents (including all global objects, variables, class instances and more) of the currently selected :doc:`ipythonconsole` session, and allows you to add, remove, and edit their values through a variety of GUI-based editors." +msgstr "" + +#: ../../panes/variableexplorer.rst:12 +msgid "Spyder Variable Explorer, with a list of variables and their contents" msgstr "" #: ../../panes/variableexplorer.rst:15 -msgid "" -"The Variable Explorer gives you information on the name, size, type and " -"value of each object. To modify a scalar variable, like an number, string" -" or boolean, simply double click it in the pane and type its new value." +msgid "The Variable Explorer gives you information on the name, size, type and value of each object. To modify a scalar variable, like an number, string or boolean, simply double click it in the pane and type its new value." +msgstr "" + +#: ../../panes/variableexplorer.rst:18 +msgid "Spyder Variable Explorer modifying value of a variable" msgstr "" #: ../../panes/variableexplorer.rst:25 @@ -1941,11 +1730,7 @@ msgid "Object viewers" msgstr "" #: ../../panes/variableexplorer.rst:27 -msgid "" -"Spyder's :guilabel:`Variable Explorer` offers built in support for " -"editing lists, strings, dictionaries, NumPy arrays, Pandas DataFrames, " -"Series and more; as well as being able to plot and visualize them with " -"one click." +msgid "Spyder's :guilabel:`Variable Explorer` offers built in support for editing lists, strings, dictionaries, NumPy arrays, Pandas DataFrames, Series and more; as well as being able to plot and visualize them with one click." msgstr "" #: ../../panes/variableexplorer.rst:31 @@ -1953,9 +1738,11 @@ msgid "Strings" msgstr "" #: ../../panes/variableexplorer.rst:33 -msgid "" -"When a string variable is longer than forty characters, you can double " -"click it to see its value in a text editor to more easily modify it." +msgid "When a string variable is longer than forty characters, you can double click it to see its value in a text editor to more easily modify it." +msgstr "" + +#: ../../panes/variableexplorer.rst:35 +msgid "Variable Explorer text editor, displaying a long string in a window" msgstr "" #: ../../panes/variableexplorer.rst:41 @@ -1963,11 +1750,11 @@ msgid "Dictionaries" msgstr "" #: ../../panes/variableexplorer.rst:43 -msgid "" -"Double-clicking on dictionaries will show a viewer displaying each of its" -" keys with its associated value. You can double click any of the values " -"to modify them, which will open a new viewer if the value is itself an " -"object." +msgid "Double-clicking on dictionaries will show a viewer displaying each of its keys with its associated value. You can double click any of the values to modify them, which will open a new viewer if the value is itself an object." +msgstr "" + +#: ../../panes/variableexplorer.rst:46 +msgid "Dictionary editor displaying keys and their types, sizes, and values" msgstr "" #: ../../panes/variableexplorer.rst:52 @@ -1975,11 +1762,11 @@ msgid "Lists" msgstr "" #: ../../panes/variableexplorer.rst:54 -msgid "" -"For lists, the main Variable Explorer displays a preview of the first ten" -" values. To see them all, double click the list to open a viewer that " -"will display the index, type, size and value of each element of the list." -" Just like dictionaries, you can double-click values to edit them." +msgid "For lists, the main Variable Explorer displays a preview of the first ten values. To see them all, double click the list to open a viewer that will display the index, type, size and value of each element of the list. Just like dictionaries, you can double-click values to edit them." +msgstr "" + +#: ../../panes/variableexplorer.rst:58 +msgid "List editor displaying a list, showing one being edited" msgstr "" #: ../../panes/variableexplorer.rst:64 @@ -1987,29 +1774,23 @@ msgid "Numpy arrays" msgstr "" #: ../../panes/variableexplorer.rst:66 -msgid "" -"Like lists, for Numpy arrays the Variable Explorer shows a preview of " -"their values. Double-clicking them will open a viewer displaying the " -"array values in a \"heat map\", with each value in a grid cell colored " -"based on its numeric quantity. You can deactivate the background color by" -" unchecking the appropriate option in the viewer, which will happen " -"automatically if the array is too large to improve performance." +msgid "Like lists, for Numpy arrays the Variable Explorer shows a preview of their values. Double-clicking them will open a viewer displaying the array values in a \"heat map\", with each value in a grid cell colored based on its numeric quantity. You can deactivate the background color by unchecking the appropriate option in the viewer, which will happen automatically if the array is too large to improve performance." +msgstr "" + +#: ../../panes/variableexplorer.rst:70 +msgid "Array editor array, displaying a \"heatmap\" of its values" msgstr "" #: ../../panes/variableexplorer.rst:73 -msgid "" -"If supported by the datatype, you can also change the format of the " -"array's values, choosing the number of decimals that you want the array " -"to display. For this, click the :guilabel:`Format` button and and set the" -" desired formatting in the dialog that appears, using standard `Printf-" -"style syntax`_." +msgid "If supported by the datatype, you can also change the format of the array's values, choosing the number of decimals that you want the array to display. For this, click the :guilabel:`Format` button and and set the desired formatting in the dialog that appears, using standard `Printf-style syntax`_." msgstr "" #: ../../panes/variableexplorer.rst:78 -msgid "" -"Additionally, you can adjust the size of the rows and columns of the " -"array by expanding or contracting their headers. Clicking the " -":guilabel:`Resize` button will set it automatically." +msgid "Additionally, you can adjust the size of the rows and columns of the array by expanding or contracting their headers. Clicking the :guilabel:`Resize` button will set it automatically." +msgstr "" + +#: ../../panes/variableexplorer.rst:81 +msgid "Array editor with a 2D int array, showing resizing of columns" msgstr "" #: ../../panes/variableexplorer.rst:86 @@ -2017,29 +1798,35 @@ msgid "DataFrames" msgstr "" #: ../../panes/variableexplorer.rst:88 -msgid "" -"DataFrames, like Numpy arrays, display in a viewer where you can show or " -"hide \"heatmap\" colors, change the format and resize the rows and " -"columns either manually or automatically." +msgid "DataFrames, like Numpy arrays, display in a viewer where you can show or hide \"heatmap\" colors, change the format and resize the rows and columns either manually or automatically." +msgstr "" + +#: ../../panes/variableexplorer.rst:90 +msgid "Dataframe editor showing data frame \"heatmap\"" msgstr "" #: ../../panes/variableexplorer.rst:93 -msgid "" -"Additionally, starting in Spyder 4, the Variable Explorer has MultiIndex " -"support in its DataFrame inspector, including for multi-level and multi-" -"dimensional indices." +msgid "Additionally, starting in Spyder 4, the Variable Explorer has MultiIndex support in its DataFrame inspector, including for multi-level and multi-dimensional indices." +msgstr "" + +#: ../../panes/variableexplorer.rst:96 +msgid "Dataframe editor showing multi-index support" msgstr "" #: ../../panes/variableexplorer.rst:105 -msgid "" -"The options menu in the top right of the Variable Explorer pane allows " -"you filter the objects shown by a number of different criteria." +msgid "The options menu in the top right of the Variable Explorer pane allows you filter the objects shown by a number of different criteria." +msgstr "" + +#: ../../panes/variableexplorer.rst:107 +msgid "Spyder Variable Explorer, with options menu" msgstr "" #: ../../panes/variableexplorer.rst:110 -msgid "" -"It also allows you to display the min and max of Numpy arrays instead of " -"a preview of their values." +msgid "It also allows you to display the min and max of Numpy arrays instead of a preview of their values." +msgstr "" + +#: ../../panes/variableexplorer.rst:112 +msgid "Variable Explorer showing max and min values of numpy array" msgstr "" #: ../../panes/variableexplorer.rst:120 @@ -2047,35 +1834,27 @@ msgid "Toolbar buttons" msgstr "" #: ../../panes/variableexplorer.rst:122 -msgid "" -"The Variable Explorer's toolbar includes several useful features that " -"affect the entire namespace. For example, you can save the current " -"session's data as a ``.spydata`` file, which can be loaded later to " -"recover all the variables stored." +msgid "The Variable Explorer's toolbar includes several useful features that affect the entire namespace. For example, you can save the current session's data as a ``.spydata`` file, which can be loaded later to recover all the variables stored." +msgstr "" + +#: ../../panes/variableexplorer.rst:125 +msgid "Variable Explorer showing how to save and import data" msgstr "" #: ../../panes/variableexplorer.rst:130 -msgid "" -"You should **not** load any ``.spydata`` file from any source you don't " -"fully trust (ideally, only those files you've saved yourself). Like with " -"any `Python pickle`_, it is inherently not secure against malicious code," -" as it can load any Python object and can execute arbitrary code on your " -"machine. Additionally, it is not guaranteed to work reliably across all " -"Python environments other than the one it was created in, so it should be" -" only used as a local persistence format, not for interchange." +msgid "You should **not** load any ``.spydata`` file from any source you don't fully trust (ideally, only those files you've saved yourself). Like with any `Python pickle`_, it is inherently not secure against malicious code, as it can load any Python object and can execute arbitrary code on your machine. Additionally, it is not guaranteed to work reliably across all Python environments other than the one it was created in, so it should be only used as a local persistence format, not for interchange." msgstr "" #: ../../panes/variableexplorer.rst:136 -msgid "" -"There is also a button to remove all displayed variables, and a search " -"box to find objects by name or type." +msgid "There is also a button to remove all displayed variables, and a search box to find objects by name or type." +msgstr "" + +#: ../../panes/variableexplorer.rst:138 +msgid "Variable Explorer showing how to search variables" msgstr "" #: ../../panes/variableexplorer.rst:141 -msgid "" -"Finally, there is a button to refresh the Variable Explorer's contents, " -"which will update it to show the current state of the code running in the" -" IPython console." +msgid "Finally, there is a button to refresh the Variable Explorer's contents, which will update it to show the current state of the code running in the IPython console." msgstr "" #: ../../panes/variableexplorer.rst:147 @@ -2083,59 +1862,58 @@ msgid "Advanced functionality" msgstr "" #: ../../panes/variableexplorer.rst:149 -msgid "" -"The context menu, available by right-clicking any variable, provides " -"numerous additional options to interact with objects of various types. " -"These include renaming, removing or editing existing variables, as well " -"as the :guilabel:`duplicate` option to create a new copy of one of them " -"under a new name you enter in the resulting dialog box." +msgid "The context menu, available by right-clicking any variable, provides numerous additional options to interact with objects of various types. These include renaming, removing or editing existing variables, as well as the :guilabel:`duplicate` option to create a new copy of one of them under a new name you enter in the resulting dialog box." +msgstr "" + +#: ../../panes/variableexplorer.rst:152 +msgid "Variable Explorer showing duplicating a variable" msgstr "" #: ../../panes/variableexplorer.rst:155 -msgid "" -"Furthermore, you can copy and paste the value of a variable, saving it in" -" the Variable Explorer with any name that you choose. This allows you to " -"change the type of the variable that you are pasting which can be very " -"useful, allowing you to, for example, easily copy the elements of a list " -"into an array." +msgid "Furthermore, you can copy and paste the value of a variable, saving it in the Variable Explorer with any name that you choose. This allows you to change the type of the variable that you are pasting which can be very useful, allowing you to, for example, easily copy the elements of a list into an array." +msgstr "" + +#: ../../panes/variableexplorer.rst:158 +msgid "Variable Explorer showing copying list into array" msgstr "" #: ../../panes/variableexplorer.rst:161 -msgid "" -"Additionally, you can create an object from scratch directly in the " -"Variable Explorer with the :guilabel:`Insert` option, which allows you to" -" type the key (which should be in quotation marks) and the value for the " -"item that you want to insert. In addition to adding a new top-level " -"variable, this feature also allows you to create a new key in a " -"dictionary, a new element in a list, and much more." +msgid "Additionally, you can create an object from scratch directly in the Variable Explorer with the :guilabel:`Insert` option, which allows you to type the key (which should be in quotation marks) and the value for the item that you want to insert. In addition to adding a new top-level variable, this feature also allows you to create a new key in a dictionary, a new element in a list, and much more." +msgstr "" + +#: ../../panes/variableexplorer.rst:164 +msgid "Variable Explorer showing insertion of a new variable" msgstr "" #: ../../panes/variableexplorer.rst:167 -msgid "" -"For lists and Numpy arrays, more advanced options are available, " -"including generating plots and histograms of their values appropriate to " -"their type and dimensions." +msgid "For lists and Numpy arrays, more advanced options are available, including generating plots and histograms of their values appropriate to their type and dimensions." +msgstr "" + +#: ../../panes/variableexplorer.rst:169 +msgid "Plot window showing a plot, generated via the previous options" msgstr "" #: ../../panes/variableexplorer.rst:172 -msgid "" -"You can even save an array to a ``.npy`` file by simply clicking the " -"appropriate option, which can later be loaded by Spyder or in your code " -"via ``numpy.load()``." +msgid "You can even save an array to a ``.npy`` file by simply clicking the appropriate option, which can later be loaded by Spyder or in your code via ``numpy.load()``." +msgstr "" + +#: ../../panes/variableexplorer.rst:174 +msgid "Context menu for an int array, with the Show image option selected" msgstr "" #: ../../panes/variableexplorer.rst:178 -msgid "" -"For two-dimensional arrays, you can also display them as images, treating" -" their values as RGB colors. For this, Spyder uses Matplotlib's " -"colormaps, which can be `easily changed to match your preferences`_." +msgid "For two-dimensional arrays, you can also display them as images, treating their values as RGB colors. For this, Spyder uses Matplotlib's colormaps, which can be `easily changed to match your preferences`_." +msgstr "" + +#: ../../panes/variableexplorer.rst:182 +msgid "Interactive image based on the array's data" msgstr "" #: ../../panes/variableexplorer.rst:185 -msgid "" -"Finally, we added a context-menu action to open any object using the new " -"Object Explorer even if they already have a builtin viewer (DataFrames, " -"arrays, etc), allowing for deeper inspection of the inner workings of " -"these datatypes." +msgid "Finally, we added a context-menu action to open any object using the new Object Explorer even if they already have a builtin viewer (DataFrames, arrays, etc), allowing for deeper inspection of the inner workings of these datatypes." +msgstr "" + +#: ../../panes/variableexplorer.rst:187 +msgid "Object explorer showing dataframe" msgstr "" diff --git a/doc/locales/en/LC_MESSAGES/plugins.po b/doc/locales/en/LC_MESSAGES/plugins.po index 94bf8b81..665c242c 100644 --- a/doc/locales/en/LC_MESSAGES/plugins.po +++ b/doc/locales/en/LC_MESSAGES/plugins.po @@ -8,19 +8,19 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" #: ../../plugins/index.rst:3 -msgid "Spyder Plugins" +msgid "Plugins" msgstr "" #: ../../plugins/lineprofiler.rst:3 @@ -28,10 +28,11 @@ msgid "Spyder Line Profiler" msgstr "" #: ../../plugins/lineprofiler.rst:5 -msgid "" -"**Spyder-Line-Profiler** is a plugin to run the Python `line profiler`_. " -"This package profiles the time that individual lines of code take to " -"execute." +msgid "**Spyder-Line-Profiler** is a plugin to run the Python `line profiler`_. This package profiles the time that individual lines of code take to execute." +msgstr "" + +#: ../../plugins/lineprofiler.rst:10 +msgid "Spyder with the Line Profiler pane open" msgstr "" #: ../../plugins/lineprofiler.rst:17 @@ -39,17 +40,11 @@ msgid "Installing the Line Profiler" msgstr "" #: ../../plugins/lineprofiler.rst:19 -msgid "" -"If you installed Spyder using conda, the best way to obtain Spyder-Line-" -"Profiler is to run the following command in your terminal (or Anaconda " -"prompt on Windows):" +msgid "If you installed Spyder using conda, the best way to obtain Spyder-Line-Profiler is to run the following command in your terminal (or Anaconda prompt on Windows):" msgstr "" #: ../../plugins/lineprofiler.rst:27 -msgid "" -"At the moment it is not possible to use this plugin with the Spyder :ref" -":`install-standalone` for Windows and macOS. We're working to add support" -" for them in the future." +msgid "At the moment it is not possible to use this plugin with the Spyder :ref:`install-standalone` for Windows and macOS. We're working to add support for them in the future." msgstr "" #: ../../plugins/lineprofiler.rst:30 ../../plugins/notebook.rst:26 @@ -62,32 +57,35 @@ msgid "Using the Line Profiler" msgstr "" #: ../../plugins/lineprofiler.rst:38 -msgid "" -"When the Line Profiler is installed, it will be available under the menu " -"item :menuselection:`View --> Panes --> Line Profiler`." +msgid "When the Line Profiler is installed, it will be available under the menu item :menuselection:`View --> Panes --> Line Profiler`." +msgstr "" + +#: ../../plugins/lineprofiler.rst:40 +msgid "Spyder showing View Panes Line Profiler" msgstr "" #: ../../plugins/lineprofiler.rst:43 -msgid "" -"You will see it then as a tab next to the :guilabel:`Files` tab. For the " -"Line Profiler to work, you must place the ``@profile`` decorator on the " -"line above any functions that you wish to profile." +msgid "You will see it then as a tab next to the :guilabel:`Files` tab. For the Line Profiler to work, you must place the ``@profile`` decorator on the line above any functions that you wish to profile." +msgstr "" + +#: ../../plugins/lineprofiler.rst:46 +msgid "Adding 'profile' decorators to script to profile it line by line." msgstr "" #: ../../plugins/lineprofiler.rst:49 -msgid "" -"Now that the decorators have been added, you can then either select a " -"script with the button present in the pane or run the profiler from " -":menuselection:`Run --> Profile line by line`. Your file will then be " -"profiled line by line." +msgid "Now that the decorators have been added, you can then either select a script with the button present in the pane or run the profiler from :menuselection:`Run --> Profile line by line`. Your file will then be profiled line by line." +msgstr "" + +#: ../../plugins/lineprofiler.rst:52 +msgid "Spyder showing the line profiler button in the Run menu" msgstr "" #: ../../plugins/lineprofiler.rst:55 -msgid "" -"After running the profiler, either from the button in the pane or the " -":menuselection:`Run` menu, the results are shown in the :guilabel:`Line " -"Profiler` pane. The path displayed there is that of the file being " -"profiled." +msgid "After running the profiler, either from the button in the pane or the :menuselection:`Run` menu, the results are shown in the :guilabel:`Line Profiler` pane. The path displayed there is that of the file being profiled." +msgstr "" + +#: ../../plugins/lineprofiler.rst:58 +msgid "Running the line profiler and inspecting the results." msgstr "" #: ../../plugins/lineprofiler.rst:61 @@ -103,9 +101,7 @@ msgid "``Hits:`` how many times that line is hit in the scope." msgstr "" #: ../../plugins/lineprofiler.rst:65 -msgid "" -"``Time (ms):`` time spent running the line in total for all hits, in " -"milliseconds." +msgid "``Time (ms):`` time spent running the line in total for all hits, in milliseconds." msgstr "" #: ../../plugins/lineprofiler.rst:66 @@ -129,16 +125,15 @@ msgid "Spyder Notebook" msgstr "" #: ../../plugins/notebook.rst:5 -msgid "" -"**Spyder-notebook** is a plugin that allows you to open, edit and " -"interact with Jupyter Notebooks right inside Spyder." +msgid "**Spyder-notebook** is a plugin that allows you to open, edit and interact with Jupyter Notebooks right inside Spyder." +msgstr "" + +#: ../../plugins/notebook.rst:7 +msgid "Spyder Notebook in Spyder" msgstr "" #: ../../plugins/notebook.rst:10 -msgid "" -"Using notebooks inside Spyder allows you to take advantage of their web " -"interface alongside Spyder’s powerful features such as the Variable " -"explorer, console and debugger." +msgid "Using notebooks inside Spyder allows you to take advantage of their web interface alongside Spyder’s powerful features such as the Variable explorer, console and debugger." msgstr "" #: ../../plugins/notebook.rst:14 @@ -146,17 +141,11 @@ msgid "Installing the Notebook" msgstr "" #: ../../plugins/notebook.rst:16 -msgid "" -"If you installed Spyder using conda, the best way to install Spyder-" -"notebook is to run the following command in your terminal or Anaconda " -"prompt on Windows:" +msgid "If you installed Spyder using conda, the best way to install Spyder-notebook is to run the following command in your terminal or Anaconda prompt on Windows:" msgstr "" #: ../../plugins/notebook.rst:24 ../../plugins/terminal.rst:25 -msgid "" -"At the moment it is not possible to use this plugin with the Spyder :ref" -":`install-standalone` for Windows and macOS. We're working to make that " -"possible in the future." +msgid "At the moment it is not possible to use this plugin with the Spyder :ref:`install-standalone` for Windows and macOS. We're working to make that possible in the future." msgstr "" #: ../../plugins/notebook.rst:30 @@ -164,49 +153,47 @@ msgid "Using the Notebook" msgstr "" #: ../../plugins/notebook.rst:32 -msgid "" -"When the Notebook is installed, it will be available under the menu item " -":menuselection:`View --> Panes --> Notebook`." +msgid "When the Notebook is installed, it will be available under the menu item :menuselection:`View --> Panes --> Notebook`." +msgstr "" + +#: ../../plugins/notebook.rst:34 +msgid "Spyder showing view panes Notebook" msgstr "" #: ../../plugins/notebook.rst:37 -msgid "" -"You will see it then as a tab in the bottom of the editor area. When " -"switching to it, a welcome screen will be displayed, from where you can " -"create a new notebook by right-clicking it and selecting :guilabel:`New " -"notebook`." +msgid "You will see it then as a tab in the bottom of the editor area. When switching to it, a welcome screen will be displayed, from where you can create a new notebook by right-clicking it and selecting :guilabel:`New notebook`." +msgstr "" + +#: ../../plugins/notebook.rst:39 +msgid "Spyder with context menu showing new notebook option" msgstr "" #: ../../plugins/notebook.rst:42 -msgid "" -"You can also click the :guilabel:`Plus` button at the top right of the " -"pane. A new Jupyter Notebook will be opened as a tab, ready for user " -"input in a temporary file. This can serve as a scratch pad where you can " -"do quick calculations and plots." +msgid "You can also click the :guilabel:`Plus` button at the top right of the pane. A new Jupyter Notebook will be opened as a tab, ready for user input in a temporary file. This can serve as a scratch pad where you can do quick calculations and plots." +msgstr "" + +#: ../../plugins/notebook.rst:44 +msgid "Spyder showing a new notebook" msgstr "" #: ../../plugins/notebook.rst:47 -msgid "" -"To save this notebook go to the options menu at the top right of the pane" -" and click the :guilabel:`Save as...` option. This will store your " -"notebook locally with the ``ipynb`` extension, which will allow you to " -"open it then as a Jupyter Notebook outside of Spyder." +msgid "To save this notebook go to the options menu at the top right of the pane and click the :guilabel:`Save as...` option. This will store your notebook locally with the ``ipynb`` extension, which will allow you to open it then as a Jupyter Notebook outside of Spyder." +msgstr "" + +#: ../../plugins/notebook.rst:49 +msgid "Gif showing save as" msgstr "" #: ../../plugins/notebook.rst:52 -msgid "" -"You can also open any Jupyter Notebook inside Spyder. For this go to the " -"options menu at the top right of the pane and click :guilabel:`Open`, " -"which will allow you to look for ``ipynb`` files in your computer. Click " -"any notebook that you want to open inside Spyder and you will be able to " -"see it as a new tab in the Notebook pane." +msgid "You can also open any Jupyter Notebook inside Spyder. For this go to the options menu at the top right of the pane and click :guilabel:`Open`, which will allow you to look for ``ipynb`` files in your computer. Click any notebook that you want to open inside Spyder and you will be able to see it as a new tab in the Notebook pane." +msgstr "" + +#: ../../plugins/notebook.rst:54 +msgid "Gif showing opening a Jupyter notebook inside Spyder" msgstr "" #: ../../plugins/notebook.rst:57 -msgid "" -"The :guilabel:`Open recent` option displays a list of the recent " -"notebooks you opened in Spyder, from which you can select them and open " -"them again in Spyder." +msgid "The :guilabel:`Open recent` option displays a list of the recent notebooks you opened in Spyder, from which you can select them and open them again in Spyder." msgstr "" #: ../../plugins/notebook.rst:61 @@ -214,14 +201,11 @@ msgid "Connecting an IPython Console" msgstr "" #: ../../plugins/notebook.rst:63 -msgid "" -"You can connect an :doc:`/panes/ipythonconsole` to your notebook, which " -"will allow you to view your variables in the " -":doc:`/panes/variableexplorer`. To do so, go to the options menu and " -"click the :guilabel:`Open console` option. This will open a new console " -"with the same name of your notebook and display the variables of the " -"cells that you have executed previously in your Notebook. If you don't " -"see them, press :kbd:`Enter` in the console." +msgid "You can connect an :doc:`/panes/ipythonconsole` to your notebook, which will allow you to view your variables in the :doc:`/panes/variableexplorer`. To do so, go to the options menu and click the :guilabel:`Open console` option. This will open a new console with the same name of your notebook and display the variables of the cells that you have executed previously in your Notebook. If you don't see them, press :kbd:`Enter` in the console." +msgstr "" + +#: ../../plugins/notebook.rst:65 +msgid "Gif showing connecting console and displaying variables" msgstr "" #: ../../plugins/notebook.rst:68 @@ -229,10 +213,7 @@ msgid "You can view, modify and create new ones in the console too." msgstr "" #: ../../plugins/notebook.rst:70 -msgid "" -"Since the Variable Explorer is associated to each console, closing the " -"notebook's console will immediately hide the variables from the Variable " -"Explorer." +msgid "Since the Variable Explorer is associated to each console, closing the notebook's console will immediately hide the variables from the Variable Explorer." msgstr "" #: ../../plugins/notebook.rst:74 @@ -240,21 +221,27 @@ msgid "Additional Options" msgstr "" #: ../../plugins/notebook.rst:76 -msgid "" -"The context menu, available by right-clicking the pane area outside the " -"notebook, allows you to zoom your notebook in or out." +msgid "The context menu, available by right-clicking the pane area outside the notebook, allows you to zoom your notebook in or out." +msgstr "" + +#: ../../plugins/notebook.rst:78 +msgid "Gif zooming in and out the notebook." msgstr "" #: ../../plugins/notebook.rst:81 -msgid "" -"You can also select the code from your Notebook and copy it on your " -"clipboard to paste this code anywhere you want." +msgid "You can also select the code from your Notebook and copy it on your clipboard to paste this code anywhere you want." +msgstr "" + +#: ../../plugins/notebook.rst:83 +msgid "Gif copying and pasting" msgstr "" #: ../../plugins/notebook.rst:86 -msgid "" -"Finally, you can see all the server information of your notebook by " -"clicking the :guilabel:`Server info` option in the context menu." +msgid "Finally, you can see all the server information of your notebook by clicking the :guilabel:`Server info` option in the context menu." +msgstr "" + +#: ../../plugins/notebook.rst:88 +msgid "Server info for notebook in Spyder" msgstr "" #: ../../plugins/terminal.rst:3 @@ -262,17 +249,15 @@ msgid "Spyder Terminal" msgstr "" #: ../../plugins/terminal.rst:5 -msgid "" -"**Spyder-terminal** is a plugin that allows you to have integrated system" -" terminals inside Spyder." +msgid "**Spyder-terminal** is a plugin that allows you to have integrated system terminals inside Spyder." +msgstr "" + +#: ../../plugins/terminal.rst:7 +msgid "Spyder Terminal in Spyder" msgstr "" #: ../../plugins/terminal.rst:10 -msgid "" -"Spyder-terminal allows you to use any system shell installed in your " -"system (e.g. Bash, Zsh or Powershell) rather than just the IPython " -"console. You can use it to issue commands, interact with version control " -"or to run programs." +msgid "Spyder-terminal allows you to use any system shell installed in your system (e.g. Bash, Zsh or Powershell) rather than just the IPython console. You can use it to issue commands, interact with version control or to run programs." msgstr "" #: ../../plugins/terminal.rst:15 @@ -280,10 +265,7 @@ msgid "Installing the Terminal" msgstr "" #: ../../plugins/terminal.rst:17 -msgid "" -"If you installed Spyder using conda, the best way to install Spyder-" -"terminal is to run the following command in your Terminal or Anaconda " -"prompt on Windows:" +msgid "If you installed Spyder using conda, the best way to install Spyder-terminal is to run the following command in your Terminal or Anaconda prompt on Windows:" msgstr "" #: ../../plugins/terminal.rst:31 @@ -291,31 +273,35 @@ msgid "Using the Terminal" msgstr "" #: ../../plugins/terminal.rst:33 -msgid "" -"When the Terminal is installed, it will be available under the menu item " -":menuselection:`View --> Panes --> Terminal`." +msgid "When the Terminal is installed, it will be available under the menu item :menuselection:`View --> Panes --> Terminal`." +msgstr "" + +#: ../../plugins/terminal.rst:35 +msgid "Spyder showing view panes Terminal" msgstr "" #: ../../plugins/terminal.rst:38 -msgid "" -"You will see it then as a tab at the bottom of the console area. When " -"switching to it, a new terminal tab will be created. You can also create " -"more terminals by clicking in the :guilabel:`+` button at the upper right" -" corner of the terminal area." +msgid "You will see it then as a tab at the bottom of the console area. When switching to it, a new terminal tab will be created. You can also create more terminals by clicking in the :guilabel:`+` button at the upper right corner of the terminal area." +msgstr "" + +#: ../../plugins/terminal.rst:40 +msgid "Spyder showing the new terminal button" msgstr "" #: ../../plugins/terminal.rst:43 -msgid "" -"Clicking the :guilabel:`Options` button next to the :guilabel:`+` button " -"will allow you to rename terminals, undock the terminal, and open a " -"terminal in the directory of the current Editor file." +msgid "Clicking the :guilabel:`Options` button next to the :guilabel:`+` button will allow you to rename terminals, undock the terminal, and open a terminal in the directory of the current Editor file." +msgstr "" + +#: ../../plugins/terminal.rst:45 +msgid "Spyder showing the terminal Options menu" msgstr "" #: ../../plugins/terminal.rst:48 -msgid "" -"If you right click the terminal area, it's possible to issue commands " -"such as :guilabel:`Clear Terminal`, :guilabel:`Zoom In/Out` and " -":guilabel:`Copy/Paste Text`." +msgid "If you right click the terminal area, it's possible to issue commands such as :guilabel:`Clear Terminal`, :guilabel:`Zoom In/Out` and :guilabel:`Copy/Paste Text`." +msgstr "" + +#: ../../plugins/terminal.rst:50 +msgid "Spyder showing the terminal context menu" msgstr "" #: ../../plugins/terminal.rst:55 @@ -323,10 +309,10 @@ msgid "Terminal Preferences" msgstr "" #: ../../plugins/terminal.rst:57 -msgid "" -"It's also possible to customize the Terminal by going to " -":menuselection:`python --> Preferences...` and then clicking on the " -"Terminal tab on the menu to the left. You can select the shell " -"interpreter, set the buffer limit and the type of cursor." +msgid "It's also possible to customize the Terminal by going to :menuselection:`python --> Preferences...` and then clicking on the Terminal tab on the menu to the left. You can select the shell interpreter, set the buffer limit and the type of cursor." +msgstr "" + +#: ../../plugins/terminal.rst:60 +msgid "Preferences of the Terminal plugin" msgstr "" diff --git a/doc/locales/en/LC_MESSAGES/quickstart.po b/doc/locales/en/LC_MESSAGES/quickstart.po index 5bd942f2..cbc3979b 100644 --- a/doc/locales/en/LC_MESSAGES/quickstart.po +++ b/doc/locales/en/LC_MESSAGES/quickstart.po @@ -8,27 +8,22 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" #: ../../quickstart.rst:3 -msgid "Quickstart" +msgid "Tour" msgstr "" #: ../../quickstart.rst:5 -msgid "" -"Welcome to our Quickstart! Here you will find an interactive tour that " -"will guide you through Spyder's interface. You'll get familiar with the " -"most important parts of the IDE, especially those we'll be mentioning " -"throughout our docs. Finally, you'll get to walk through some of Spyder's" -" key panes and functionality." +msgid "Welcome to our Quickstart! Here you will find an interactive tour that will guide you through Spyder's interface. You'll get familiar with the most important parts of the IDE, especially those we'll be mentioning throughout our docs. Finally, you'll get to walk through some of Spyder's key panes and functionality." msgstr "" diff --git a/doc/locales/en/LC_MESSAGES/troubleshooting.po b/doc/locales/en/LC_MESSAGES/troubleshooting.po index 25b170e8..c8a07f0b 100644 --- a/doc/locales/en/LC_MESSAGES/troubleshooting.po +++ b/doc/locales/en/LC_MESSAGES/troubleshooting.po @@ -8,25 +8,23 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" #: ../../troubleshooting/basic-first-aid.rst:3 msgid "Basic First Aid" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:5 -msgid "" -"These suggestions, while more of a shotgun approach, tend to fix the " -"majority of reported issues just on their own." +msgid "These suggestions, while more of a shotgun approach, tend to fix the majority of reported issues just on their own." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:11 @@ -38,77 +36,48 @@ msgid "**Restart Spyder**, and try what you were doing before again." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:15 -msgid "" -"**Upgrade Spyder** to the latest release, and you might find your issue " -"is resolved (along with new features, enhancements, and other bug fixes)." -" Minor releases come out every couple months, so unless you've updated " -"recently, there is a good chance your version isn't the latest. You can " -"find out with the :guilabel:`Check for updates` command under the " -":guilabel:`Help` menu." +msgid "**Upgrade Spyder** to the latest release, and you might find your issue is resolved (along with new features, enhancements, and other bug fixes). Minor releases come out every couple months, so unless you've updated recently, there is a good chance your version isn't the latest. You can find out with the :guilabel:`Check for updates` command under the :guilabel:`Help` menu." +msgstr "" + +#: ../../troubleshooting/basic-first-aid.rst:19 +#: ../../troubleshooting/first-steps.rst:25 +msgid "Spyder showing view internal console option" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:22 -msgid "" -"To perform the update with Conda (strongly recommended), from your " -"terminal (or Anaconda Prompt on Windows) run:" +msgid "To perform the update with Conda (strongly recommended), from your terminal (or Anaconda Prompt on Windows) run:" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:29 -msgid "" -"**Update Spyder's dependencies and environment**, either by installing " -"the latest version of your distribution (e.g. the recommended Anaconda), " -"or with the relevant \"update all\" command in your terminal (or Anaconda" -" Prompt on Windows). To get the latest stable version of everything using" -" Conda, you can run:" +msgid "**Update Spyder's dependencies and environment**, either by installing the latest version of your distribution (e.g. the recommended Anaconda), or with the relevant \"update all\" command in your terminal (or Anaconda Prompt on Windows). To get the latest stable version of everything using Conda, you can run:" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:36 -msgid "" -"**Restart your machine**, in case the problem lies with a lingering " -"process or another such issue." +msgid "**Restart your machine**, in case the problem lies with a lingering process or another such issue." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:38 -msgid "" -"**Restore Spyder's config files** to their defaults, which solves a huge " -"variety of Spyder issues. From your terminal (or Anaconda Prompt on " -"Windows), run:" +msgid "**Restore Spyder's config files** to their defaults, which solves a huge variety of Spyder issues. From your terminal (or Anaconda Prompt on Windows), run:" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:47 -msgid "" -"This will reset your preferences, as well as any custom keyboard " -"shortcuts or syntax highlighting schemes. If you particularly care about " -"any of those, you should make a copy of the :file:`.spyder-py3` folder in" -" your user home directory (:file:`C:/Users/YOUR_USERNAME` on Windows, " -":file:`/Users/YOUR_USERNAME` on macOS, or :file:`/home/YOUR_USERNAME` on " -"Linux), and restore it afterwards if this doesn't solve the problem." +msgid "This will reset your preferences, as well as any custom keyboard shortcuts or syntax highlighting schemes. If you particularly care about any of those, you should make a copy of the :file:`.spyder-py3` folder in your user home directory (:file:`C:/Users/YOUR_USERNAME` on Windows, :file:`/Users/YOUR_USERNAME` on macOS, or :file:`/home/YOUR_USERNAME` on Linux), and restore it afterwards if this doesn't solve the problem." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:50 -msgid "" -"**Try installing Spyder into a new Conda environment** (recommended) or " -"``virtualenv``/``venv``, and see if the issue reoccurs." +msgid "**Try installing Spyder into a new Conda environment** (recommended) or ``virtualenv``/``venv``, and see if the issue reoccurs." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:52 -msgid "" -"In your system terminal (or Anaconda Prompt on Windows), run the " -"following commands to create an a fresh, clean environment and start " -"Spyder in it:" +msgid "In your system terminal (or Anaconda Prompt on Windows), run the following commands to create an a fresh, clean environment and start Spyder in it:" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:60 -msgid "" -"If this fixes the issue, the problem was likely due to another package " -"installed on your system, particularly if done with pip, which can cause " -"many problems and should be avoided if at all possible." +msgid "If this fixes the issue, the problem was likely due to another package installed on your system, particularly if done with pip, which can cause many problems and should be avoided if at all possible." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:62 -msgid "" -"**Watch our video** on solving and avoiding problems with pip, Conda and " -"Conda-Forge, and follow its instructions." +msgid "**Watch our video** on solving and avoiding problems with pip, Conda and Conda-Forge, and follow its instructions." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:75 @@ -116,35 +85,23 @@ msgid "Reinstalling Spyder" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:77 -msgid "" -"If none of the previous steps solve your issue, you should do a full " -"uninstall of Spyder by whatever means you originally installed it." +msgid "If none of the previous steps solve your issue, you should do a full uninstall of Spyder by whatever means you originally installed it." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:79 -msgid "" -"For Anaconda, follow all the steps under Option B in the `Anaconda " -"uninstall guide`_, delete the Anaconda directory wherever it was " -"originally installed, and (on Windows) remove the " -":file:`%appdata%/python` directory if it exists." +msgid "For Anaconda, follow all the steps under Option B in the `Anaconda uninstall guide`_, delete the Anaconda directory wherever it was originally installed, and (on Windows) remove the :file:`%appdata%/python` directory if it exists." +msgstr "" + +#: ../../troubleshooting/basic-first-aid.rst:81 +msgid "Deleting appdata/python directory" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:84 -msgid "" -"Then, do a clean install of the latest version of the `Anaconda " -"distribution`_ which is how we recommend you install Spyder and keep it " -"up to date." +msgid "Then, do a clean install of the latest version of the `Anaconda distribution`_ which is how we recommend you install Spyder and keep it up to date." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:88 -msgid "" -"While you are welcome to get Spyder working on your own by one of the " -"many other means we offer, we are only able to provide individual support" -" for install-related issues for users of the Anaconda distribution. In " -"particular, pip installation, while doable, is only really for experts, " -"as there are many pitfalls involved and different issues specific to your" -" setup, which is why we recommend using Conda whenever possible. For " -"further information, please visit our :doc:`/installation`." +msgid "While you are welcome to get Spyder working on your own by one of the many other means we offer, we are only able to provide individual support for install-related issues for users of the Anaconda distribution. In particular, pip installation, while doable, is only really for experts, as there are many pitfalls involved and different issues specific to your setup, which is why we recommend using Conda whenever possible. For further information, please visit our :doc:`/installation`." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:99 @@ -152,68 +109,39 @@ msgid "Isolating problems" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:101 -msgid "" -"If you get an error while running a specific line, block, or " -"script/program, it may not be an issue with Spyder, but rather something " -"lower down in the packages it depends on. Try running it in the following" -" in order if and until it starts working as you expect. If you manage to " -"isolate the bug, report it to the last one it *doesn't* work in." +msgid "If you get an error while running a specific line, block, or script/program, it may not be an issue with Spyder, but rather something lower down in the packages it depends on. Try running it in the following in order if and until it starts working as you expect. If you manage to isolate the bug, report it to the last one it *doesn't* work in." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:105 -msgid "" -"**Spyder** itself, of course! Make sure you can reproduce the error after" -" closing and reopening it, if possible." +msgid "**Spyder** itself, of course! Make sure you can reproduce the error after closing and reopening it, if possible." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:108 -msgid "" -"**A bare QtConsole instance**, e.g. launched from Anaconda navigator or " -"from the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux) with " -"``jupyter qtconsole``." +msgid "**A bare QtConsole instance**, e.g. launched from Anaconda navigator or from the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux) with ``jupyter qtconsole``." +msgstr "" + +#: ../../troubleshooting/basic-first-aid.rst:110 +msgid "Anaconda navigator showing qtconsole" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:113 -msgid "" -"QtConsole is the GUI console backend Spyder depends on to run its code, " -"so most issues involving Spyder's :doc:`/panes/ipythonconsole` are " -"actually something with QtConsole instead, and can be reported to their " -"`issue tracker`_." +msgid "QtConsole is the GUI console backend Spyder depends on to run its code, so most issues involving Spyder's :doc:`/panes/ipythonconsole` are actually something with QtConsole instead, and can be reported to their `issue tracker`_." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:115 -msgid "" -"**An IPython command line shell**, launched with e.g. ``ipython`` from " -"the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). " -"Reproducible bugs can be reported to their `Github page`_, though make " -"sure to read their guidelines and docs first." +msgid "**An IPython command line shell**, launched with e.g. ``ipython`` from the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). Reproducible bugs can be reported to their `Github page`_, though make sure to read their guidelines and docs first." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:118 -msgid "" -"**A standard Python interpreter**, either run as a script file with " -"``python path/to/your/file.py`` or launched interactively with ``python``" -" from your Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). " -"While it is not impossible that you've found Python bug, it is much more " -"likely to be an issue with the code itself or a package you are using, so" -" your best sources are the `Python docs`_ and the other resources listed " -"above." +msgid "**A standard Python interpreter**, either run as a script file with ``python path/to/your/file.py`` or launched interactively with ``python`` from your Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). While it is not impossible that you've found Python bug, it is much more likely to be an issue with the code itself or a package you are using, so your best sources are the `Python docs`_ and the other resources listed above." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:127 -msgid "" -"If the problem reoccurs in a similar or identical way with any of these " -"methods (other than only Spyder itself), then it is almost certainly not " -"an issue with Spyder, and would be best handled elsewhere. As we usually " -"aren't able to do much about issues not related to Spyder, a forum like " -"`Stack Overflow`_ or the relevant package's docs is a much better place " -"to get help or report the issue." +msgid "If the problem reoccurs in a similar or identical way with any of these methods (other than only Spyder itself), then it is almost certainly not an issue with Spyder, and would be best handled elsewhere. As we usually aren't able to do much about issues not related to Spyder, a forum like `Stack Overflow`_ or the relevant package's docs is a much better place to get help or report the issue." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:132 -msgid "" -"See the :doc:`call-for-help` section for other places to look for " -"information and assistance." +msgid "See the :doc:`call-for-help` section for other places to look for information and assistance." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:138 @@ -221,25 +149,19 @@ msgid "Debugging and patching" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:140 -msgid "" -"If you know your way around Python, you can often diagnose and even fix " -"Spyder issues yourself, since the IDE is written in the same language you" -" use in it. You can explore the error messages you're receiving and " -"Spyder's inner workings with the :guilabel:`Internal Console`, available " -"under the menu item :menuselection:`View --> Panes --> Internal Console`." +msgid "If you know your way around Python, you can often diagnose and even fix Spyder issues yourself, since the IDE is written in the same language you use in it. You can explore the error messages you're receiving and Spyder's inner workings with the :guilabel:`Internal Console`, available under the menu item :menuselection:`View --> Panes --> Internal Console`." +msgstr "" + +#: ../../troubleshooting/basic-first-aid.rst:143 +msgid "Spyder showing Internal console" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:146 -msgid "" -"For more detailed debug output, start Spyder from the command line " -"(Anaconda Prompt on Windows) with ``spyder --debug-info verbose``." +msgid "For more detailed debug output, start Spyder from the command line (Anaconda Prompt on Windows) with ``spyder --debug-info verbose``." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:148 -msgid "" -"Even if you don't manage to fix the problem yourself, this output can be " -"very helpful in aiding us to quickly narrow down and solve your issue for" -" you." +msgid "Even if you don't manage to fix the problem yourself, this output can be very helpful in aiding us to quickly narrow down and solve your issue for you." msgstr "" #: ../../troubleshooting/call-for-help.rst:3 @@ -247,12 +169,7 @@ msgid "Calling for Help" msgstr "" #: ../../troubleshooting/call-for-help.rst:5 -msgid "" -"Aside from this troubleshooting guide, there are a number of other " -"sources of documentation and troubleshooting information you can check " -"before submitting an issue, as they might already offer an answer, or at " -"least help you better understand the problem. Even if we aren't able to " -"help you, these places might." +msgid "Aside from this troubleshooting guide, there are a number of other sources of documentation and troubleshooting information you can check before submitting an issue, as they might already offer an answer, or at least help you better understand the problem. Even if we aren't able to help you, these places might." msgstr "" #: ../../troubleshooting/call-for-help.rst:14 @@ -264,9 +181,7 @@ msgid "Spyder's FAQ section" msgstr "" #: ../../troubleshooting/call-for-help.rst:21 -msgid "" -"Spyder's documentation has a FAQ section, where you might find the " -"answers that you are looking for." +msgid "Spyder's documentation has a FAQ section, where you might find the answers that you are looking for." msgstr "" #: ../../troubleshooting/call-for-help.rst:27 @@ -274,10 +189,7 @@ msgid "Spyder's YouTube channel" msgstr "" #: ../../troubleshooting/call-for-help.rst:29 -msgid "" -"Our `YouTube channel`_ contains helpful videos that will guide you " -"through many of Spyder's features, and provide a starting point for newer" -" users." +msgid "Our `YouTube channel`_ contains helpful videos that will guide you through many of Spyder's features, and provide a starting point for newer users." msgstr "" #: ../../troubleshooting/call-for-help.rst:37 @@ -285,10 +197,7 @@ msgid "Spyder Gitter" msgstr "" #: ../../troubleshooting/call-for-help.rst:39 -msgid "" -"We have a public `Gitter room`_ where you can chat directly with the " -"Spyder developers. If you've got a quick question to ask the team and are" -" looking for a quick answer, this is a great place to go." +msgid "We have a public `Gitter room`_ where you can chat directly with the Spyder developers. If you've got a quick question to ask the team and are looking for a quick answer, this is a great place to go." msgstr "" #: ../../troubleshooting/call-for-help.rst:48 @@ -296,9 +205,7 @@ msgid "Spyder Google Group" msgstr "" #: ../../troubleshooting/call-for-help.rst:50 -msgid "" -"Our `Google Group`_ is great for help-related questions, particularly " -"those you aren't sure are a full-on Spyder issue." +msgid "Our `Google Group`_ is great for help-related questions, particularly those you aren't sure are a full-on Spyder issue." msgstr "" #: ../../troubleshooting/call-for-help.rst:58 @@ -306,9 +213,7 @@ msgid "Spyder website" msgstr "" #: ../../troubleshooting/call-for-help.rst:60 -msgid "" -"The `Spyder site`_ contains basic information about the IDE and links to " -"many other helpful resources." +msgid "The `Spyder site`_ contains basic information about the IDE and links to many other helpful resources." msgstr "" #: ../../troubleshooting/call-for-help.rst:68 @@ -316,13 +221,7 @@ msgid "Stack Overflow tag" msgstr "" #: ../../troubleshooting/call-for-help.rst:70 -msgid "" -"`Stack Overflow`_ is a great place to start searching and posting, " -"particularly if your question is more programming-related, or has to do " -"with something specific to your own code. It has an vibrant Spyder " -"community as well, with new questions posted every day, and the " -"developers (especially Carlos Cordoba, the lead maintainer) are active in" -" answering them." +msgid "`Stack Overflow`_ is a great place to start searching and posting, particularly if your question is more programming-related, or has to do with something specific to your own code. It has an vibrant Spyder community as well, with new questions posted every day, and the developers (especially Carlos Cordoba, the lead maintainer) are active in answering them." msgstr "" #: ../../troubleshooting/call-for-help.rst:79 @@ -330,11 +229,7 @@ msgid "OpenTeams support" msgstr "" #: ../../troubleshooting/call-for-help.rst:81 -msgid "" -"On `OpenTeams`_, you can get help from expert Spyder consultants. " -"OpenTeams offers services from Spyder experts ranging from a brief " -"consultation to an experienced team to help you with a large scale " -"implementation project." +msgid "On `OpenTeams`_, you can get help from expert Spyder consultants. OpenTeams offers services from Spyder experts ranging from a brief consultation to an experienced team to help you with a large scale implementation project." msgstr "" #: ../../troubleshooting/call-for-help.rst:91 @@ -346,10 +241,7 @@ msgid "Official Python help page" msgstr "" #: ../../troubleshooting/call-for-help.rst:98 -msgid "" -"The `Python help page`_ is a great resource that lists a number of places" -" you can get assistance, support and learning resources for the language " -"and its packages." +msgid "The `Python help page`_ is a great resource that lists a number of places you can get assistance, support and learning resources for the language and its packages." msgstr "" #: ../../troubleshooting/call-for-help.rst:106 @@ -357,10 +249,7 @@ msgid "Python documentation" msgstr "" #: ../../troubleshooting/call-for-help.rst:108 -msgid "" -"The `Python docs`_ can help you understand a number of issues that can be" -" caused by quirks in the language itself, or misunderstandings as to how " -"it behaves." +msgid "The `Python docs`_ can help you understand a number of issues that can be caused by quirks in the language itself, or misunderstandings as to how it behaves." msgstr "" #: ../../troubleshooting/call-for-help.rst:116 @@ -368,10 +257,7 @@ msgid "Python subreddits" msgstr "" #: ../../troubleshooting/call-for-help.rst:118 -msgid "" -"`r/python`_ and `r/learnpython`_ are resources you can use to ask about " -"and discuss issues with Python and its packages. The former is aimed more" -" at general Python usage, and the latter more specifically at beginners." +msgid "`r/python`_ and `r/learnpython`_ are resources you can use to ask about and discuss issues with Python and its packages. The former is aimed more at general Python usage, and the latter more specifically at beginners." msgstr "" #: ../../troubleshooting/call-for-help.rst:130 @@ -383,11 +269,7 @@ msgid "Anaconda help" msgstr "" #: ../../troubleshooting/call-for-help.rst:138 -msgid "" -"The `Anaconda docs`_ site offers free community help and documentation " -"for the Anaconda applications, installing the Anaconda distribution, and " -"using the Conda package and environment manager; along with paid support " -"options." +msgid "The `Anaconda docs`_ site offers free community help and documentation for the Anaconda applications, installing the Anaconda distribution, and using the Conda package and environment manager; along with paid support options." msgstr "" #: ../../troubleshooting/call-for-help.rst:145 @@ -395,11 +277,7 @@ msgid "SciPy.org website" msgstr "" #: ../../troubleshooting/call-for-help.rst:147 -msgid "" -"The `Scipy website`_ is the the central home of the SciPy stack, with " -"information, documentation, help, and bug tracking for many of the core " -"packages used with Spyder, including NumPy, SciPy, Matplotlib, Pandas, " -"Sympy and IPython." +msgid "The `Scipy website`_ is the the central home of the SciPy stack, with information, documentation, help, and bug tracking for many of the core packages used with Spyder, including NumPy, SciPy, Matplotlib, Pandas, Sympy and IPython." msgstr "" #: ../../troubleshooting/call-for-help.rst:155 @@ -407,9 +285,7 @@ msgid "Project Jupyter" msgstr "" #: ../../troubleshooting/call-for-help.rst:157 -msgid "" -"`Jupyter`_ is the development hub for IPython, Spyder's QtConsole, " -"Jupyter notebooks used with the `Spyder-Notebook`_ plugin, and more." +msgid "`Jupyter`_ is the development hub for IPython, Spyder's QtConsole, Jupyter notebooks used with the `Spyder-Notebook`_ plugin, and more." msgstr "" #: ../../troubleshooting/call-for-help.rst:166 @@ -417,9 +293,7 @@ msgid "Data Science Stack Exchange" msgstr "" #: ../../troubleshooting/call-for-help.rst:168 -msgid "" -"The `Data Science`_ site in Stack Exchange can be very useful for " -"questions that relate more to data science than programming specifically." +msgid "The `Data Science`_ site in Stack Exchange can be very useful for questions that relate more to data science than programming specifically." msgstr "" #: ../../troubleshooting/common-illnesses.rst:3 @@ -427,9 +301,7 @@ msgid "Common Illnesses" msgstr "" #: ../../troubleshooting/common-illnesses.rst:5 -msgid "" -"Beyond the general troubleshooting steps, some frequently-reported " -"problems require more specialized solutions." +msgid "Beyond the general troubleshooting steps, some frequently-reported problems require more specialized solutions." msgstr "" #: ../../troubleshooting/common-illnesses.rst:13 @@ -437,12 +309,7 @@ msgid "Errors starting the kernel" msgstr "" #: ../../troubleshooting/common-illnesses.rst:15 -msgid "" -"If you receive the message ``An error occurred while starting the " -"kernel`` in the :doc:`/panes/ipythonconsole`, Spyder was unable to launch" -" a new Python interpreter in the current working environment to run your " -"code. There are a number of problems that can cause this, but most can be" -" fixed fairly quickly with a few easy steps." +msgid "If you receive the message ``An error occurred while starting the kernel`` in the :doc:`/panes/ipythonconsole`, Spyder was unable to launch a new Python interpreter in the current working environment to run your code. There are a number of problems that can cause this, but most can be fixed fairly quickly with a few easy steps." msgstr "" #: ../../troubleshooting/common-illnesses.rst:22 @@ -450,22 +317,19 @@ msgid "Spyder-Kernels not installed/incompatible" msgstr "" #: ../../troubleshooting/common-illnesses.rst:24 -msgid "" -"Spyder requires a supported version of the ``spyder-kernels`` package to " -"be present in the working environment you want to run your console in." +msgid "Spyder requires a supported version of the ``spyder-kernels`` package to be present in the working environment you want to run your console in." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:26 +msgid "Kernel version error dialog" msgstr "" #: ../../troubleshooting/common-illnesses.rst:29 -msgid "" -"It is included by default with Anaconda, but if you want to run your code" -" in another Python environment or installation, you'll need to make sure " -"it's installed and updated to the latest version." +msgid "It is included by default with Anaconda, but if you want to run your code in another Python environment or installation, you'll need to make sure it's installed and updated to the latest version." msgstr "" #: ../../troubleshooting/common-illnesses.rst:31 -msgid "" -"Check the required version of spyder-kernels for your version of Spyder " -"in the following table:" +msgid "Check the required version of spyder-kernels for your version of Spyder in the following table:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:33 @@ -577,21 +441,15 @@ msgid "2.4.3" msgstr "" #: ../../troubleshooting/common-illnesses.rst:52 -msgid "" -"To do so, activate the environment, then install ``spyder-kernels``. If " -"using Anaconda, open a terminal (Anaconda Prompt on Windows) and run:" +msgid "To do so, activate the environment, then install ``spyder-kernels``. If using Anaconda, open a terminal (Anaconda Prompt on Windows) and run:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:60 -msgid "" -"Otherwise, activate your environment by whatever means you created it, " -"and execute:" +msgid "Otherwise, activate your environment by whatever means you created it, and execute:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:66 -msgid "" -"For both of the previous commands, replace ```` with the " -"corresponding version in the table." +msgid "For both of the previous commands, replace ```` with the corresponding version in the table." msgstr "" #: ../../troubleshooting/common-illnesses.rst:70 @@ -599,12 +457,7 @@ msgid "Issue with another dependency" msgstr "" #: ../../troubleshooting/common-illnesses.rst:72 -msgid "" -"If the kernel displays a long error traceback that mentions other " -"packages like ``ipython``, ``ipykernel``, ``jupyter_client``, " -"``traitlets`` or ``pyzmq``, the problem may be an out of date or " -"incompatible version of a dependency package. To fix this, activate the " -"environment and update the key dependencies." +msgid "If the kernel displays a long error traceback that mentions other packages like ``ipython``, ``ipykernel``, ``jupyter_client``, ``traitlets`` or ``pyzmq``, the problem may be an out of date or incompatible version of a dependency package. To fix this, activate the environment and update the key dependencies." msgstr "" #: ../../troubleshooting/common-illnesses.rst:75 @@ -612,9 +465,7 @@ msgid "In an Anaconda environment:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:82 -msgid "" -"Otherwise, activate your environment by whatever means you created it, " -"and run:" +msgid "Otherwise, activate your environment by whatever means you created it, and run:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:90 @@ -622,22 +473,15 @@ msgid "AttributeError/ImportError" msgstr "" #: ../../troubleshooting/common-illnesses.rst:92 -msgid "" -"Check the last few lines of the error message, and see if its an " -"``AttributeError`` or ``ImportError``, or refers to a file you created in" -" your current working directory or your home folder " -"(:file:`C:/Users/YOUR_USERNAME` on Windows, :file:`/Users/YOUR_USERNAME` " -"on macOS, or :file:`/home/YOUR_USERNAME` on Linux)." +msgid "Check the last few lines of the error message, and see if its an ``AttributeError`` or ``ImportError``, or refers to a file you created in your current working directory or your home folder (:file:`C:/Users/YOUR_USERNAME` on Windows, :file:`/Users/YOUR_USERNAME` on macOS, or :file:`/home/YOUR_USERNAME` on Linux)." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:94 +msgid "Spyder's AtributeError dialog" msgstr "" #: ../../troubleshooting/common-illnesses.rst:97 -msgid "" -"If so, the the error is likely due to your file being named the same as a" -" Python standard library module, such as ``string.py`` or ``time.py``, " -"which overrides the built-in module that Spyder-Kernels is trying to " -"load. To fix this, simply rename your file to something other than one of" -" these names, and try restarting the kernel. To check the names of these " -"modules, see the list in the `Python standard library documentation`_." +msgid "If so, the the error is likely due to your file being named the same as a Python standard library module, such as ``string.py`` or ``time.py``, which overrides the built-in module that Spyder-Kernels is trying to load. To fix this, simply rename your file to something other than one of these names, and try restarting the kernel. To check the names of these modules, see the list in the `Python standard library documentation`_." msgstr "" #: ../../troubleshooting/common-illnesses.rst:109 @@ -645,13 +489,7 @@ msgid "Completion/help not working" msgstr "" #: ../../troubleshooting/common-illnesses.rst:111 -msgid "" -"To provide code completions, help and real-time analysis in the Editor, " -"Spyder uses the Python Language Server (PyLS), an implementation of the " -"Language Server Protocol specification used by VSCode, Atom and other " -"popular editors/IDEs. Most help and completion issues lie outside of " -"Spyder's control, and are either limitations with PyLS or the code that " -"is being introspected, but some can be worked around." +msgid "To provide code completions, help and real-time analysis in the Editor, Spyder uses the Python Language Server (PyLS), an implementation of the Language Server Protocol specification used by VSCode, Atom and other popular editors/IDEs. Most help and completion issues lie outside of Spyder's control, and are either limitations with PyLS or the code that is being introspected, but some can be worked around." msgstr "" #: ../../troubleshooting/common-illnesses.rst:116 @@ -659,15 +497,15 @@ msgid "Object missing docstring" msgstr "" #: ../../troubleshooting/common-illnesses.rst:118 -msgid "" -"If nothing is displayed in the calltip, hover hint or help pane, the " -"object you're trying to introspect may not have a docstring." +msgid "If nothing is displayed in the calltip, hover hint or help pane, the object you're trying to introspect may not have a docstring." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:120 +msgid "Docstring not found in help pane" msgstr "" #: ../../troubleshooting/common-illnesses.rst:124 -msgid "" -"In this case, the only solution is to add one in the source code of the " -"original function, method or class." +msgid "In this case, the only solution is to add one in the source code of the original function, method or class." msgstr "" #: ../../troubleshooting/common-illnesses.rst:128 @@ -675,16 +513,15 @@ msgid "Object cannot be found" msgstr "" #: ../../troubleshooting/common-illnesses.rst:130 -msgid "" -"Some objects, whether due to being written in C, Cython or another " -"language; generated dynamically at runtime; or being a method of an " -"object you create, cannot be easily found without executing the code." +msgid "Some objects, whether due to being written in C, Cython or another language; generated dynamically at runtime; or being a method of an object you create, cannot be easily found without executing the code." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:132 +msgid "Object not found in help pane" msgstr "" #: ../../troubleshooting/common-illnesses.rst:136 -msgid "" -"However, once you run your code in the :doc:`/panes/ipythonconsole`, you " -"might be able to get help and completions on the object there." +msgid "However, once you run your code in the :doc:`/panes/ipythonconsole`, you might be able to get help and completions on the object there." msgstr "" #: ../../troubleshooting/common-illnesses.rst:140 @@ -692,12 +529,11 @@ msgid "LSP has stopped working" msgstr "" #: ../../troubleshooting/common-illnesses.rst:142 -msgid "" -"Occasionally, especially after using Spyder for a while, code completion," -" help and analysis may stop working. If this is the case, you can check " -"LSP status with the :guilabel:`LSP Python` item in Spyder's status bar at" -" the bottom of the screen, and restart it by right-clicking it and " -"selecting the :guilabel:`Restart Python Language Server` item." +msgid "Occasionally, especially after using Spyder for a while, code completion, help and analysis may stop working. If this is the case, you can check LSP status with the :guilabel:`LSP Python` item in Spyder's status bar at the bottom of the screen, and restart it by right-clicking it and selecting the :guilabel:`Restart Python Language Server` item." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:145 +msgid "Spyder with LSP restart dialog" msgstr "" #: ../../troubleshooting/common-illnesses.rst:150 @@ -705,17 +541,11 @@ msgid "Spyder bug/dependency issue" msgstr "" #: ../../troubleshooting/common-illnesses.rst:152 -msgid "" -"Given the variety of dependencies involved in making LSP work, an " -"incompatible or out of date version in your environment can result in " -"error messages, incomplete results, or help/analysis not working at all." +msgid "Given the variety of dependencies involved in making LSP work, an incompatible or out of date version in your environment can result in error messages, incomplete results, or help/analysis not working at all." msgstr "" #: ../../troubleshooting/common-illnesses.rst:154 -msgid "" -"To address this, first try updating Anaconda and Spyder as described in " -":doc:`basic-first-aid`. If the issue still isn't resolved, update the " -"various relevant dependencies with:" +msgid "To address this, first try updating Anaconda and Spyder as described in :doc:`basic-first-aid`. If the issue still isn't resolved, update the various relevant dependencies with:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:165 @@ -727,29 +557,19 @@ msgid "Plugin does not work at all" msgstr "" #: ../../troubleshooting/common-illnesses.rst:170 -msgid "" -"If you have installed a Spyder plugin, but you can't see it, go to the " -":guilabel:`Panes` submenu of the :guilabel:`View` menu and select the " -"plugin's name, which should make its pane visible. If you don't see the " -"plugin there, select the :guilabel:`Dependencies` item under the " -":guilabel:`Help` menu and see if the plugin appears at the bottom." +msgid "If you have installed a Spyder plugin, but you can't see it, go to the :guilabel:`Panes` submenu of the :guilabel:`View` menu and select the plugin's name, which should make its pane visible. If you don't see the plugin there, select the :guilabel:`Dependencies` item under the :guilabel:`Help` menu and see if the plugin appears at the bottom." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:173 +msgid "Dependencies dialog showing Unittest plugin" msgstr "" #: ../../troubleshooting/common-illnesses.rst:176 -msgid "" -"If the plugin with the problem is not listed in the dependencies dialog, " -"check that you installed it in the same environment as Spyder. If you " -"have, then the problem may well be caused by a dependency issue. Test " -"whether you can import the plug-in manually by opening a Python console " -"in the same environment as Spyder and typing, for instance, ``import " -"spyder_unittest`` to test the Spyder-Unittest` plug-in; this command " -"should run without errors." +msgid "If the plugin with the problem is not listed in the dependencies dialog, check that you installed it in the same environment as Spyder. If you have, then the problem may well be caused by a dependency issue. Test whether you can import the plug-in manually by opening a Python console in the same environment as Spyder and typing, for instance, ``import spyder_unittest`` to test the Spyder-Unittest` plug-in; this command should run without errors." msgstr "" #: ../../troubleshooting/common-illnesses.rst:180 -msgid "" -"If none of this helps you to resolve the problem, then continue to the " -"next section." +msgid "If none of this helps you to resolve the problem, then continue to the next section." msgstr "" #: ../../troubleshooting/common-illnesses.rst:184 @@ -757,25 +577,15 @@ msgid "Other issues" msgstr "" #: ../../troubleshooting/common-illnesses.rst:186 -msgid "" -"If you get an error which mentions or involves a Spyder plugin, such as " -"``spyder-unittest``, ``spyder-terminal`` or ``spyder-notebook``, or if " -"you encounter any other problem with a Spyder plugin, then the first " -"approach should be to update Spyder and the plugin to their latest " -"versions." +msgid "If you get an error which mentions or involves a Spyder plugin, such as ``spyder-unittest``, ``spyder-terminal`` or ``spyder-notebook``, or if you encounter any other problem with a Spyder plugin, then the first approach should be to update Spyder and the plugin to their latest versions." msgstr "" #: ../../troubleshooting/common-illnesses.rst:188 -msgid "" -"If this doesn't fix the problem, you should check the plugin's website or" -" repository to see if it is compatible with your version of Spyder." +msgid "If this doesn't fix the problem, you should check the plugin's website or repository to see if it is compatible with your version of Spyder." msgstr "" #: ../../troubleshooting/common-illnesses.rst:190 -msgid "" -"Finally, if compatibility doesn't seem to be the problem, please check " -"those repositories to see if an issue was already opened, and report it " -"there if not." +msgid "Finally, if compatibility doesn't seem to be the problem, please check those repositories to see if an issue was already opened, and report it there if not." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:3 @@ -783,9 +593,7 @@ msgid "Emergency CPR" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:5 -msgid "" -"Is Spyder not launching at all? The steps on this section should " -"hopefully get it back up and running in no time." +msgid "Is Spyder not launching at all? The steps on this section should hopefully get it back up and running in no time." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:12 @@ -793,48 +601,31 @@ msgid "Common solutions" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:14 -msgid "" -"Try :doc:`basic-first-aid` first, which usually resolves most Spyder " -"install-related issues." +msgid "Try :doc:`basic-first-aid` first, which usually resolves most Spyder install-related issues." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:16 -msgid "" -"**Make sure Spyder isn't already running** and no Spyder related windows " -"(*e.g.* :doc:`/panes/variableexplorer` dialogs) are left open, and check " -"that the preference setting :menuselection:`Application --> Advanced " -"Settings --> Use a single instance` isn't checked." +msgid "**Make sure Spyder isn't already running** and no Spyder related windows (*e.g.* :doc:`/panes/variableexplorer` dialogs) are left open, and check that the preference setting :menuselection:`Application --> Advanced Settings --> Use a single instance` isn't checked." +msgstr "" + +#: ../../troubleshooting/emergency-cpr.rst:18 +msgid "Spyder showing Use a single instance setting" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:21 -msgid "" -"Try **starting Spyder via a different means**, such as from a shortcut, " -"Anaconda navigator, or your command line (or Anaconda Prompt on Windows) " -"by simply typing ``spyder`` then :kbd:`Enter`/:kbd:`Return`, and see if " -"any of those work. If so, then something's wrong with your install, not " -"Spyder itself, and so we recommend following :ref:`troubleshooting-" -"reinstalling-spyder-ref` to uninstall and reinstall Anaconda." +msgid "Try **starting Spyder via a different means**, such as from a shortcut, Anaconda navigator, or your command line (or Anaconda Prompt on Windows) by simply typing ``spyder`` then :kbd:`Enter`/:kbd:`Return`, and see if any of those work. If so, then something's wrong with your install, not Spyder itself, and so we recommend following :ref:`troubleshooting-reinstalling-spyder-ref` to uninstall and reinstall Anaconda." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:24 -msgid "" -"**Disable any security software** you may be using, such as a firewall or" -" antivirus, as these products can occasionally interfere with Spyder or " -"its related packages. Make sure to re-enable it if it doesn't fix the " -"problem, and if it does, add a rule or exception for Spyder or Python." +msgid "**Disable any security software** you may be using, such as a firewall or antivirus, as these products can occasionally interfere with Spyder or its related packages. Make sure to re-enable it if it doesn't fix the problem, and if it does, add a rule or exception for Spyder or Python." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:27 -msgid "" -"If it is currently installed \"for just you\", **try uninstalling and " -"reinstalling Anaconda \"for all users\" instead**, and vice versa, as " -"some systems can have issues with one or the other installation method." +msgid "If it is currently installed \"for just you\", **try uninstalling and reinstalling Anaconda \"for all users\" instead**, and vice versa, as some systems can have issues with one or the other installation method." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:29 -msgid "" -"**Check and repair/reset permissions**, your disk, and OS if all else " -"fails." +msgid "**Check and repair/reset permissions**, your disk, and OS if all else fails." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:35 @@ -842,18 +633,11 @@ msgid "Advanced tricks" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:37 -msgid "" -"If none of the above solves the problem, you can try starting Spyder " -"directly from its Python source files which may either get it running, or" -" at least provide useful information to help debug the issue further." +msgid "If none of the above solves the problem, you can try starting Spyder directly from its Python source files which may either get it running, or at least provide useful information to help debug the issue further." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:39 -msgid "" -"This technique consists of starting Spyder from your terminal (or " -"Anaconda Prompt on Windows) by manually running the Spyder startup " -"routine ( :guilabel:`start.py` ) with a known good Python interpreter, " -"and observing the results." +msgid "This technique consists of starting Spyder from your terminal (or Anaconda Prompt on Windows) by manually running the Spyder startup routine ( :guilabel:`start.py` ) with a known good Python interpreter, and observing the results." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:41 @@ -861,9 +645,7 @@ msgid "To do so, you'll need to:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:43 -msgid "" -"Find the path to the Spyder :file:`app` directory from the command line. " -"For this, run:" +msgid "Find the path to the Spyder :file:`app` directory from the command line. For this, run:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:50 @@ -871,23 +653,19 @@ msgid "Go to the output path of the above command on your command line:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:56 -msgid "" -"Once inside the :file:`app` directory, run ``python start.py`` to launch " -"Spyder." +msgid "Once inside the :file:`app` directory, run ``python start.py`` to launch Spyder." +msgstr "" + +#: ../../troubleshooting/emergency-cpr.rst:58 +msgid "Command line showing python start to launch Spyder" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:62 -msgid "" -"#. If it doesn't start successfully, then you should see an error " -"traceback printed; carefully copy that for future reference. Also run " -"``python mainwindow.py``, and record your results as well." +msgid "#. If it doesn't start successfully, then you should see an error traceback printed; carefully copy that for future reference. Also run ``python mainwindow.py``, and record your results as well." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:65 -msgid "" -"(*Windows only*) In case the command window disappears immediately after " -"the error, create a ``.bat`` file in the :file:`app` directory with the " -"following content:" +msgid "(*Windows only*) In case the command window disappears immediately after the error, create a ``.bat`` file in the :file:`app` directory with the following content:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:73 @@ -895,115 +673,71 @@ msgid "Replace ```` with the output of:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:79 -msgid "" -"Then, double click the batch file to run it, and you should see the error" -" information you need." +msgid "Then, double click the batch file to run it, and you should see the error information you need." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:81 -msgid "" -"If reading the output (particularly the last line) doesn't help you solve" -" the problem, then record all of it carefully, and post it as part of " -"your bug report as described under the :doc:`submit-a-report` section." +msgid "If reading the output (particularly the last line) doesn't help you solve the problem, then record all of it carefully, and post it as part of your bug report as described under the :doc:`submit-a-report` section." msgstr "" -#: ../../troubleshooting/first-steps.rst:3 +#: ../../troubleshooting/first-steps.rst:6 msgid "First Steps" msgstr "" -#: ../../troubleshooting/first-steps.rst:5 -msgid "" -"If Spyder crashes or you receive an error message, please read the " -"following troubleshooting steps before opening a new issue. There's a " -"good chance that someone else has already experienced the same problem, " -"so checking for an existing solution will likely get Spyder working again" -" for you as quickly as possible." +#: ../../troubleshooting/first-steps.rst:8 +msgid "If Spyder crashes or you receive an error message, please read the following troubleshooting steps before opening a new issue. There's a good chance that someone else has already experienced the same problem, so checking for an existing solution will likely get Spyder working again for you as quickly as possible." msgstr "" -#: ../../troubleshooting/first-steps.rst:9 -msgid "" -"To make sure you're getting the most relevant help for your problem, " -"please make sure the issue is actually related to Spyder:" +#: ../../troubleshooting/first-steps.rst:12 +msgid "To make sure you're getting the most relevant help for your problem, please make sure the issue is actually related to Spyder:" msgstr "" -#: ../../troubleshooting/first-steps.rst:11 -msgid "" -"If the problem appears to be a result of *your own code*, `Stack " -"Overflow`_ is a better place to start." +#: ../../troubleshooting/first-steps.rst:14 +msgid "If the problem appears to be a result of *your own code*, `Stack Overflow`_ is a better place to start." msgstr "" -#: ../../troubleshooting/first-steps.rst:12 -msgid "" -"If the bug also occurs in the *standard Python, IPython, or QtConsole* " -"environments, or only with *a specific package*, it is unlikely to be " -"something in Spyder, and you should report it to those sources instead." +#: ../../troubleshooting/first-steps.rst:15 +msgid "If the bug also occurs in the *standard Python, IPython, or QtConsole* environments, or only with *a specific package*, it is unlikely to be something in Spyder, and you should report it to those sources instead." msgstr "" -#: ../../troubleshooting/first-steps.rst:13 -msgid "" -"If the problem lies with *your specific install*, uninstalling and clean-" -"reinstalling the `Anaconda`_ distribution is strongly recommended. As the" -" other methods of installing Spyder can result in tricky user-specific " -"problems, we generally aren't able to give individual support for install" -" issues." +#: ../../troubleshooting/first-steps.rst:16 +msgid "If the problem lies with *your specific install*, uninstalling and clean-reinstalling the `Anaconda`_ distribution is strongly recommended. As the other methods of installing Spyder can result in tricky user-specific problems, we generally aren't able to give individual support for install issues." msgstr "" -#: ../../troubleshooting/first-steps.rst:19 -msgid "" -"Just like the programs you code in it, Spyder is written in Python, so " -"you can often figure out many problems just by reading the last line of " -"the traceback or error message. To view it, simply click :guilabel:`Show " -"details` in the Spyder error dialog." +#: ../../troubleshooting/first-steps.rst:22 +msgid "Just like the programs you code in it, Spyder is written in Python, so you can often figure out many problems just by reading the last line of the traceback or error message. To view it, simply click :guilabel:`Show details` in the Spyder error dialog." msgstr "" -#: ../../troubleshooting/first-steps.rst:25 -msgid "" -"Often, that alone will tell you how to fix the problem on your own, but " -"if not, we're here to help." +#: ../../troubleshooting/first-steps.rst:28 +msgid "Often, that alone will tell you how to fix the problem on your own, but if not, we're here to help." msgstr "" -#: ../../troubleshooting/first-steps.rst:31 +#: ../../troubleshooting/first-steps.rst:34 msgid "Where to go from here" msgstr "" -#: ../../troubleshooting/first-steps.rst:33 -msgid "" -"If you check out our list of issue categories and problem descriptions " -"and see a question, error message or traceback that looks familiar, the " -"relevant sub-section will likely be of the most specific help solving " -"your issue as quickly as possible." +#: ../../troubleshooting/first-steps.rst:36 +msgid "If you check out our list of issue categories and problem descriptions and see a question, error message or traceback that looks familiar, the relevant sub-section will likely be of the most specific help solving your issue as quickly as possible." msgstr "" -#: ../../troubleshooting/first-steps.rst:37 -msgid "" -"As a first step to solving your issue, you can try some :doc:`basic-" -"first-aid`." +#: ../../troubleshooting/first-steps.rst:40 +msgid "As a first step to solving your issue, you can try some :doc:`basic-first-aid`." msgstr "" -#: ../../troubleshooting/first-steps.rst:41 -msgid "" -"If Spyder won't launch, check the :doc:`emergency-cpr` section and see if" -" that clears it up." +#: ../../troubleshooting/first-steps.rst:44 +msgid "If Spyder won't launch, check the :doc:`emergency-cpr` section and see if that clears it up." msgstr "" -#: ../../troubleshooting/first-steps.rst:45 -msgid "" -"If your problem is related to the kernel not starting, autocompletion or " -"a plugin go to :doc:`common-illnesses` section." +#: ../../troubleshooting/first-steps.rst:48 +msgid "If your problem is related to the kernel not starting, autocompletion or a plugin go to :doc:`common-illnesses` section." msgstr "" -#: ../../troubleshooting/first-steps.rst:49 -msgid "" -"If you still can't get it to work, and the problem is indeed Spyder-" -"related, you should consult the the :doc:`call-for-help` section for " -"other resources to explore." +#: ../../troubleshooting/first-steps.rst:52 +msgid "If you still can't get it to work, and the problem is indeed Spyder-related, you should consult the the :doc:`call-for-help` section for other resources to explore." msgstr "" -#: ../../troubleshooting/first-steps.rst:53 -msgid "" -"Finally, if you couldn't solve your problem and want to submit an issue " -"to our Github issue tracker, so the bug can hopefully be fixed for " -"everyone, :doc:`submit-a-report`." +#: ../../troubleshooting/first-steps.rst:56 +msgid "Finally, if you couldn't solve your problem and want to submit an issue to our Github issue tracker, so the bug can hopefully be fixed for everyone, :doc:`submit-a-report`." msgstr "" #: ../../troubleshooting/index.rst:3 @@ -1015,19 +749,17 @@ msgid "Submit a Report" msgstr "" #: ../../troubleshooting/submit-a-report.rst:5 -msgid "" -"If you can't fix your issue with any of the troubleshooting steps, then " -"you'll want to submit it to our issue tracker so our team can take a look" -" at it for you. You'll need a `Github account`_ to do this, so make sure " -"you have one before you begin (a good idea anyway)." +msgid "If you can't fix your issue with any of the troubleshooting steps, then you'll want to submit it to our issue tracker so our team can take a look at it for you. You'll need a `Github account`_ to do this, so make sure you have one before you begin (a good idea anyway)." +msgstr "" + +#: ../../troubleshooting/submit-a-report.rst:8 +#: ../../troubleshooting/submit-a-report.rst:32 +#: ../../troubleshooting/submit-a-report.rst:39 +msgid "Github page on Spyder's issue tracker" msgstr "" #: ../../troubleshooting/submit-a-report.rst:13 -msgid "" -"Before you submit an issue, make sure you've searched a description of " -"the problem and a relevant portion of the error traceback, on both Google" -" and Spyder's `issue tracker`_ to make sure it hasn't been submitted " -"before. If that's the case, your issue will be closed as a duplicate." +msgid "Before you submit an issue, make sure you've searched a description of the problem and a relevant portion of the error traceback, on both Google and Spyder's `issue tracker`_ to make sure it hasn't been submitted before. If that's the case, your issue will be closed as a duplicate." msgstr "" #: ../../troubleshooting/submit-a-report.rst:23 @@ -1035,44 +767,27 @@ msgid "Ways to submit an issue" msgstr "" #: ../../troubleshooting/submit-a-report.rst:25 -msgid "" -"There are several ways to submit an issue, either from Spyder or GitHub " -"directly. In order of preference and difficulty:" +msgid "There are several ways to submit an issue, either from Spyder or GitHub directly. In order of preference and difficulty:" msgstr "" #: ../../troubleshooting/submit-a-report.rst:28 -msgid "" -"**If Spyder presents an error dialog** you can submit an issue directly " -"from it. You will have to fill out a title for your issue, specify the " -"steps that lead to this problem and click :guilabel:`submit to Github`. " -"This will prefill an error report with your environment details, key " -"versions and dependencies and automatically insert the error/traceback " -"for you." +msgid "**If Spyder presents an error dialog** you can submit an issue directly from it. You will have to fill out a title for your issue, specify the steps that lead to this problem and click :guilabel:`submit to Github`. This will prefill an error report with your environment details, key versions and dependencies and automatically insert the error/traceback for you." msgstr "" #: ../../troubleshooting/submit-a-report.rst:36 -msgid "" -"**If Spyder opens and your issue does not involve an error dialog**, the " -"best way to do so is to simply select :guilabel:`Report issue` from the " -":guilabel:`Help` menu, which manually brings up the issue report form and" -" fills in the key information about your Spyder installation. Describe " -"the issue you're experiencing (including any error/traceback information)" -" along with a descriptive title, and click :guilabel:`Submit to Github`." +msgid "**If Spyder opens and your issue does not involve an error dialog**, the best way to do so is to simply select :guilabel:`Report issue` from the :guilabel:`Help` menu, which manually brings up the issue report form and fills in the key information about your Spyder installation. Describe the issue you're experiencing (including any error/traceback information) along with a descriptive title, and click :guilabel:`Submit to Github`." msgstr "" #: ../../troubleshooting/submit-a-report.rst:42 -msgid "" -"**If Spyder won't launch**, you can submit a report manually at our " -"issues page on `Github`_. Unlike the above, you'll need to manually " -"provide the versions of everything (Spyder, Python, OS, Qt/PyQt, " -"Anaconda, and Spyder's dependencies) as listed in the error report " -"template; see below for more on that." +msgid "**If Spyder won't launch**, you can submit a report manually at our issues page on `Github`_. Unlike the above, you'll need to manually provide the versions of everything (Spyder, Python, OS, Qt/PyQt, Anaconda, and Spyder's dependencies) as listed in the error report template; see below for more on that." +msgstr "" + +#: ../../troubleshooting/submit-a-report.rst:45 +msgid "Github page on Spyder's issue template" msgstr "" #: ../../troubleshooting/submit-a-report.rst:50 -msgid "" -"Once you submit your report, our team will try to get back to you as soon" -" as possible, often within 24 hours or less, to try to help you fix it." +msgid "Once you submit your report, our team will try to get back to you as soon as possible, often within 24 hours or less, to try to help you fix it." msgstr "" #: ../../troubleshooting/submit-a-report.rst:55 @@ -1080,10 +795,7 @@ msgid "What to include in your report" msgstr "" #: ../../troubleshooting/submit-a-report.rst:57 -msgid "" -"**Please include as much as possible of the following in your report** to" -" maximize your chances of getting relevant help and our ability to " -"diagnose, reproduce and solve your issue." +msgid "**Please include as much as possible of the following in your report** to maximize your chances of getting relevant help and our ability to diagnose, reproduce and solve your issue." msgstr "" #: ../../troubleshooting/submit-a-report.rst:59 @@ -1091,105 +803,70 @@ msgid "The key items, in order of priority:" msgstr "" #: ../../troubleshooting/submit-a-report.rst:61 -msgid "" -"The full, **complete error message or traceback** copy/pasted or " -"automatically entered exactly as displayed by Spyder:" +msgid "The full, **complete error message or traceback** copy/pasted or automatically entered exactly as displayed by Spyder:" msgstr "" #: ../../troubleshooting/submit-a-report.rst:63 -msgid "" -"Auto-generated reports directly from the error dialog should include this" -" automatically, but double check to make sure." +msgid "Auto-generated reports directly from the error dialog should include this automatically, but double check to make sure." msgstr "" #: ../../troubleshooting/submit-a-report.rst:64 -msgid "" -"You can copy and paste this from the the :guilabel:`Show Details` section" -" of the error dialog." +msgid "You can copy and paste this from the the :guilabel:`Show Details` section of the error dialog." msgstr "" #: ../../troubleshooting/submit-a-report.rst:65 -msgid "" -"If not present, or a dialog is not displayed, you can also find it " -"printed to Spyder's :guilabel:`Internal Console`, located under the " -":guilabel:`View` menu at :menuselection:`Panes --> Internal Console`." +msgid "If not present, or a dialog is not displayed, you can also find it printed to Spyder's :guilabel:`Internal Console`, located under the :guilabel:`View` menu at :menuselection:`Panes --> Internal Console`." msgstr "" #: ../../troubleshooting/submit-a-report.rst:66 -msgid "" -"If you prefer, or if Spyder won't start, you can start Spyder from your " -"command line (or Anaconda prompt on windows) with ``spyder`` and copy the" -" output printed there." +msgid "If you prefer, or if Spyder won't start, you can start Spyder from your command line (or Anaconda prompt on windows) with ``spyder`` and copy the output printed there." msgstr "" #: ../../troubleshooting/submit-a-report.rst:70 -msgid "" -"If you are reporting a specific behavior rather than an error, or the " -"message does not fully explain what occurs, please describe in detail " -"what actually happened, and what you expected Spyder to do." +msgid "If you are reporting a specific behavior rather than an error, or the message does not fully explain what occurs, please describe in detail what actually happened, and what you expected Spyder to do." msgstr "" #: ../../troubleshooting/submit-a-report.rst:72 -msgid "" -"A **detailed, step by step description of exactly what you did** leading " -"up to the error occurring, complete with sample code that triggers it, if" -" applicable." +msgid "A **detailed, step by step description of exactly what you did** leading up to the error occurring, complete with sample code that triggers it, if applicable." msgstr "" #: ../../troubleshooting/submit-a-report.rst:74 -msgid "" -"**Information about Spyder and its environment** as listed in the error " -"report template, which you can find under :guilabel:`About Spyder` in the" -" :guilabel:`Help` menu; along with its key dependencies, shown in the " -"dialog under :menuselection:`Help --> Dependencies` (there's a button to " -"copy-paste them)." +msgid "**Information about Spyder and its environment** as listed in the error report template, which you can find under :guilabel:`About Spyder` in the :guilabel:`Help` menu; along with its key dependencies, shown in the dialog under :menuselection:`Help --> Dependencies` (there's a button to copy-paste them)." +msgstr "" + +#: ../../troubleshooting/submit-a-report.rst:76 +msgid "Spyder showing Spyder's info and dependencies" msgstr "" #: ../../troubleshooting/submit-a-report.rst:79 -msgid "" -"If Spyder won't launch, paste the output of ``conda list`` from your " -"command line (or Anaconda prompt on Windows) in the " -":guilabel:`Dependencies` section of the issue template." +msgid "If Spyder won't launch, paste the output of ``conda list`` from your command line (or Anaconda prompt on Windows) in the :guilabel:`Dependencies` section of the issue template." +msgstr "" + +#: ../../troubleshooting/submit-a-report.rst:81 +msgid "Command line showing output of conda list" msgstr "" #: ../../troubleshooting/submit-a-report.rst:85 -msgid "" -"**How you installed Spyder** and any other relevant packages, *e.g.* " -"Anaconda, MacPorts or pip and **whether Spyder has worked before** since " -"you installed it." +msgid "**How you installed Spyder** and any other relevant packages, *e.g.* Anaconda, MacPorts or pip and **whether Spyder has worked before** since you installed it." msgstr "" #: ../../troubleshooting/submit-a-report.rst:87 -msgid "" -"**What else you've tried to fix it**, *e.g.* from this guide or elsewhere" -" on the web, and if you've **tried to reproduce it in standalone " -"QtConsole, IPython, and/or the plain Python** interpreter." +msgid "**What else you've tried to fix it**, *e.g.* from this guide or elsewhere on the web, and if you've **tried to reproduce it in standalone QtConsole, IPython, and/or the plain Python** interpreter." msgstr "" #: ../../troubleshooting/submit-a-report.rst:89 -msgid "" -"**Whether the problem occurred consistently before** in similar " -"situations or if this is the first time you've observed it." +msgid "**Whether the problem occurred consistently before** in similar situations or if this is the first time you've observed it." msgstr "" #: ../../troubleshooting/submit-a-report.rst:91 -msgid "" -"**Anything else special or unusual** about your system, environment, " -"packages, or specific usage that might have anything to do with the " -"problem" +msgid "**Anything else special or unusual** about your system, environment, packages, or specific usage that might have anything to do with the problem" msgstr "" #: ../../troubleshooting/submit-a-report.rst:95 -msgid "" -"If including block(s) of code in your report, be sure to precede and " -"follow it with a line of three backticks \\`\\`\\` to get a code block " -"like this:" +msgid "If including block(s) of code in your report, be sure to precede and follow it with a line of three backticks \\`\\`\\` to get a code block like this:" msgstr "" #: ../../troubleshooting/submit-a-report.rst:101 -msgid "" -"Otherwise, your code will likely contain random formatting or missing " -"indentation, making it difficult to examine and run it to reproduce and " -"fix your issue." +msgid "Otherwise, your code will likely contain random formatting or missing indentation, making it difficult to examine and run it to reproduce and fix your issue." msgstr "" diff --git a/doc/locales/en/LC_MESSAGES/videos.po b/doc/locales/en/LC_MESSAGES/videos.po index dd96de33..d1e881bf 100644 --- a/doc/locales/en/LC_MESSAGES/videos.po +++ b/doc/locales/en/LC_MESSAGES/videos.po @@ -8,27 +8,23 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" #: ../../videos/first-steps-with-spyder.rst:3 msgid "First Steps with Spyder" msgstr "" #: ../../videos/first-steps-with-spyder.rst:5 -msgid "" -"The videos in this section provide a starting point for new users who " -"have never opened Spyder before. You'll get familiar with opening Spyder " -"in different ways, working with the four main panes and customizing the " -"Spyder to your heart's content." +msgid "The videos in this section provide a starting point for new users who have never opened Spyder before. You'll get familiar with opening Spyder in different ways, working with the four main panes and customizing the Spyder to your heart's content." msgstr "" #: ../../videos/first-steps-with-spyder.rst:12 @@ -36,9 +32,7 @@ msgid "Getting started" msgstr "" #: ../../videos/first-steps-with-spyder.rst:14 -msgid "" -"Discover the basics of using the Spyder interface and get an introduction" -" to its four main panes, along with a quick look at the others." +msgid "Discover the basics of using the Spyder interface and get an introduction to its four main panes, along with a quick look at the others." msgstr "" #: ../../videos/first-steps-with-spyder.rst:16 @@ -57,76 +51,41 @@ msgstr "" msgid "Explore the other default panes" msgstr "" +#: ../../videos/first-steps-with-spyder.rst +#: ../../videos/working-with-spyder.rst +msgid "Transcript" +msgstr "" + #: ../../videos/first-steps-with-spyder.rst:33 -msgid "" -"Hello everyone! I'm Juanita, and in this video I'm going to show you how " -"to open Spyder and go over the basics of Spyder's interface. We will " -"learn about Spyder's four panes that you'll likely be using most often, " -"as well as briefly explore the others that are open by default. If you " -"don't have Spyder installed and would like to follow along, you can " -"`download it here`_." +msgid "Hello everyone! I'm Juanita, and in this video I'm going to show you how to open Spyder and go over the basics of Spyder's interface. We will learn about Spyder's four panes that you'll likely be using most often, as well as briefly explore the others that are open by default. If you don't have Spyder installed and would like to follow along, you can `download it here`_." msgstr "" #: ../../videos/first-steps-with-spyder.rst:37 -msgid "" -"The easiest way to open Spyder is by opening Anaconda Navigator and " -"clicking on the Spyder application. In case you have an older version of " -"Spyder in Anaconda, open the command line (or the Anaconda Prompt in the " -"case of Windows) and type the commands:" +msgid "The easiest way to open Spyder is by opening Anaconda Navigator and clicking on the Spyder application. In case you have an older version of Spyder in Anaconda, open the command line (or the Anaconda Prompt in the case of Windows) and type the commands:" msgstr "" #: ../../videos/first-steps-with-spyder.rst:44 -msgid "" -"To launch Spyder without opening Navigator, open your command line and " -"type ``spyder``. If you followed the :doc:`/installation`, you should " -"have everything necessary to open Spyder 4." +msgid "To launch Spyder without opening Navigator, open your command line and type ``spyder``. If you followed the :doc:`/installation`, you should have everything necessary to open Spyder 4." msgstr "" #: ../../videos/first-steps-with-spyder.rst:46 -msgid "" -"This is what Spyder 4 looks like in its default configuration, though you" -" can thoroughly customize it, which we'll get to in a later tutorial. You" -" can see that it is divided into three sections showing three different " -"panes: the Editor, the IPython Console and the Help viewer. These three, " -"along with the Variable Explorer, are the four core panes you'll work " -"with the most in Spyder." +msgid "This is what Spyder 4 looks like in its default configuration, though you can thoroughly customize it, which we'll get to in a later tutorial. You can see that it is divided into three sections showing three different panes: the Editor, the IPython Console and the Help viewer. These three, along with the Variable Explorer, are the four core panes you'll work with the most in Spyder." msgstr "" #: ../../videos/first-steps-with-spyder.rst:48 -msgid "" -"On the left we have the Editor, where you can open, edit and run files. " -"Bottom right is the IPython Console, which you can use both interactively" -" and to run your code in the Editor. It shows you which version of Python" -" you are using. Above it, you'll find the Help pane, where you can get " -"more information and documentation for any object in the Editor or " -"Console by pressing :kbd:`Ctrl-I` (or :kbd:`Cmd-I` on macOS). We'll see " -"how to do this in our next video." +msgid "On the left we have the Editor, where you can open, edit and run files. Bottom right is the IPython Console, which you can use both interactively and to run your code in the Editor. It shows you which version of Python you are using. Above it, you'll find the Help pane, where you can get more information and documentation for any object in the Editor or Console by pressing :kbd:`Ctrl-I` (or :kbd:`Cmd-I` on macOS). We'll see how to do this in our next video." msgstr "" #: ../../videos/first-steps-with-spyder.rst:50 -msgid "" -"For the two sections on the right, you can switch tabs to see the other " -"panes that are open by default when launching Spyder. In the top section," -" you can switch to the Variable Explorer, which shows you the name, type," -" size and value of the variables that you have previously defined in the " -"Editor or the Console. You can also modify the value of these variables " -"directly from this pane by double clicking them under the Value column. " -"The Plots pane will show you the figures you generate with Matplotlib and" -" other libraries, and the Files pane allows you to browse the files on " -"your computer and open them in the Editor with just a click." +msgid "For the two sections on the right, you can switch tabs to see the other panes that are open by default when launching Spyder. In the top section, you can switch to the Variable Explorer, which shows you the name, type, size and value of the variables that you have previously defined in the Editor or the Console. You can also modify the value of these variables directly from this pane by double clicking them under the Value column. The Plots pane will show you the figures you generate with Matplotlib and other libraries, and the Files pane allows you to browse the files on your computer and open them in the Editor with just a click." msgstr "" #: ../../videos/first-steps-with-spyder.rst:52 -msgid "" -"Finally, in the bottom section you can also access the History pane, " -"which shows you the commands you have entered in the Console, including " -"those from previous sessions." +msgid "Finally, in the bottom section you can also access the History pane, which shows you the commands you have entered in the Console, including those from previous sessions." msgstr "" #: ../../videos/first-steps-with-spyder.rst:54 -msgid "" -"I hope you're now familiar with the basics of using the Spyder interface." -" In the next video, we will start working with Spyder's core panes." +msgid "I hope you're now familiar with the basics of using the Spyder interface. In the next video, we will start working with Spyder's core panes." msgstr "" #: ../../videos/first-steps-with-spyder.rst:56 @@ -154,9 +113,7 @@ msgid "Execute basic Python commands in the IPython Console" msgstr "" #: ../../videos/first-steps-with-spyder.rst:69 -msgid "" -"Define variables in the Editor and modify their values in the IPython " -"Console" +msgid "Define variables in the Editor and modify their values in the IPython Console" msgstr "" #: ../../videos/first-steps-with-spyder.rst:70 @@ -168,68 +125,27 @@ msgid "Get documentation in the Help pane in two different ways" msgstr "" #: ../../videos/first-steps-with-spyder.rst:84 -msgid "" -"Hello everyone! I'm Juanita, and in this video I will show you how to " -"start working with Spyder's four main panes. First, let's take a look at " -"the Editor, which you can use to open, edit and run files from your " -"computer. I will open a short \"Hello World\" program for this demo, " -"which you can `download here`_. Once you have it open in your Editor, you" -" can execute it by pressing the green run button. We can see the output " -"in the Python Console [Show IPython console] as well as the path of the " -"file that we are running and the working directory where this code was " -"run." +msgid "Hello everyone! I'm Juanita, and in this video I will show you how to start working with Spyder's four main panes. First, let's take a look at the Editor, which you can use to open, edit and run files from your computer. I will open a short \"Hello World\" program for this demo, which you can `download here`_. Once you have it open in your Editor, you can execute it by pressing the green run button. We can see the output in the Python Console [Show IPython console] as well as the path of the file that we are running and the working directory where this code was run." msgstr "" #: ../../videos/first-steps-with-spyder.rst:88 -msgid "" -"We can also run any Python code that is entered directly in the IPython " -"Console. For example, we can type ``print(\"Hello\")`` and see the " -"output. Or, we can try some math operations and see the results here too." -" Note that for implicitly printed output, there is a red indication that " -"differs from the output of the ``print()`` function." +msgid "We can also run any Python code that is entered directly in the IPython Console. For example, we can type ``print(\"Hello\")`` and see the output. Or, we can try some math operations and see the results here too. Note that for implicitly printed output, there is a red indication that differs from the output of the ``print()`` function." msgstr "" #: ../../videos/first-steps-with-spyder.rst:90 -msgid "" -"Now, let's start defining some variables. We can do this both from the " -"editor or from the Console. If I define a variable ``a = 10`` and then " -"run this code, I can see its value in the console just by typing its name" -" ``a``. However, you can also assign any variable in the IPython console " -"(``b = 20``) and its value will be stored too. In both cases, they can " -"also be seen in the Variable Explorer pane, which shows the name, type, " -"size and value of each of the objects previously defined. In this case, " -"we see variables ``a`` and ``b``, both of type int and with size 1. We " -"can also define a list ``l`` with ``l = [1, 2, 3]`` and see that the type" -" of the variable is list and the size is 3." +msgid "Now, let's start defining some variables. We can do this both from the editor or from the Console. If I define a variable ``a = 10`` and then run this code, I can see its value in the console just by typing its name ``a``. However, you can also assign any variable in the IPython console (``b = 20``) and its value will be stored too. In both cases, they can also be seen in the Variable Explorer pane, which shows the name, type, size and value of each of the objects previously defined. In this case, we see variables ``a`` and ``b``, both of type int and with size 1. We can also define a list ``l`` with ``l = [1, 2, 3]`` and see that the type of the variable is list and the size is 3." msgstr "" #: ../../videos/first-steps-with-spyder.rst:92 -msgid "" -"We can change the values of the variables in the Variable Explorer too by" -" double-clicking them and typing their new value. Now, we can check their" -" new value in the console. In the case of a more complex type like a " -"list, double-clicking it will open a viewer in which you can modify each " -"of its values separately, along with other more complex operations which " -"we'll demonstrate in a future video. We can remove a variable by right-" -"clicking it and selecting the option Remove. After doing this, we can " -"check in the IPython Console that the variable was actually deleted." +msgid "We can change the values of the variables in the Variable Explorer too by double-clicking them and typing their new value. Now, we can check their new value in the console. In the case of a more complex type like a list, double-clicking it will open a viewer in which you can modify each of its values separately, along with other more complex operations which we'll demonstrate in a future video. We can remove a variable by right-clicking it and selecting the option Remove. After doing this, we can check in the IPython Console that the variable was actually deleted." msgstr "" #: ../../videos/first-steps-with-spyder.rst:94 -msgid "" -"Finally, we are going to learn how to get help for objects in two " -"different ways. First, we can press :kbd:`Ctrl-I` (or :kbd:`Cmd-I` on " -"macOS) right after the name of an object written in the Editor or the " -"Console, for example ``numpy.array``. You can see that we obtain its " -"documentation in the Help pane if it is available. Second, if we change " -"the Source dropdown option to Console, we can type its name in the object" -" box in the Help pane. Now we can get help for Numpy arrays." +msgid "Finally, we are going to learn how to get help for objects in two different ways. First, we can press :kbd:`Ctrl-I` (or :kbd:`Cmd-I` on macOS) right after the name of an object written in the Editor or the Console, for example ``numpy.array``. You can see that we obtain its documentation in the Help pane if it is available. Second, if we change the Source dropdown option to Console, we can type its name in the object box in the Help pane. Now we can get help for Numpy arrays." msgstr "" #: ../../videos/first-steps-with-spyder.rst:96 -msgid "" -"You should now be ready to start using Spyder's four main panes. Check " -"out our next video to continue learning and as always, Happy Spydering!" +msgid "You should now be ready to start using Spyder's four main panes. Check out our next video to continue learning and as always, Happy Spydering!" msgstr "" #: ../../videos/first-steps-with-spyder.rst:102 @@ -237,9 +153,7 @@ msgid "Customization" msgstr "" #: ../../videos/first-steps-with-spyder.rst:104 -msgid "" -"Learn how to customize Spyder’s interface to match your workflow and " -"development style." +msgid "Learn how to customize Spyder’s interface to match your workflow and development style." msgstr "" #: ../../videos/first-steps-with-spyder.rst:106 @@ -259,73 +173,35 @@ msgid "Split, close and pop out Editor panels" msgstr "" #: ../../videos/first-steps-with-spyder.rst:123 -msgid "" -"Hello everyone, I'm Juanita! In this video, I will show you how to " -"customize Spyder to match your workflow and development style." +msgid "Hello everyone, I'm Juanita! In this video, I will show you how to customize Spyder to match your workflow and development style." msgstr "" #: ../../videos/first-steps-with-spyder.rst:125 -msgid "" -"First, we are going to learn how to change the font in the Editor, " -"IPython Console and Help panes. To do this, go to Preferences, select the" -" Appearance entry and scroll down to Fonts. You can change both the style" -" and the size of the font for both plain and rich text. You can see how " -"this affects the font in the Editor, Console and Help panes." +msgid "First, we are going to learn how to change the font in the Editor, IPython Console and Help panes. To do this, go to Preferences, select the Appearance entry and scroll down to Fonts. You can change both the style and the size of the font for both plain and rich text. You can see how this affects the font in the Editor, Console and Help panes." msgstr "" #: ../../videos/first-steps-with-spyder.rst:127 -msgid "" -"In this same dialog, you can easily change the syntax highlighting theme," -" for which you can see the preview at the right of the window. Note that " -"Spyder's interface theme changes to match the highlighting theme because " -"the Interface theme option is set to Automatic by default. However, you " -"can change the theme for the entire Spyder interface, choosing between " -"Light and Dark. After selecting this change, click Apply to restart " -"Spyder to apply the new theme." +msgid "In this same dialog, you can easily change the syntax highlighting theme, for which you can see the preview at the right of the window. Note that Spyder's interface theme changes to match the highlighting theme because the Interface theme option is set to Automatic by default. However, you can change the theme for the entire Spyder interface, choosing between Light and Dark. After selecting this change, click Apply to restart Spyder to apply the new theme." msgstr "" #: ../../videos/first-steps-with-spyder.rst:129 -msgid "" -"Beyond just Spyder's preferences, you can freely rearrange the panes in " -"Spyder's main window. To show or hide panes, go to Panes under the View " -"menu, and select which ones you want to see. For example, let's hide the " -"Files pane and show the Profiler pane. You can also close a pane from its" -" options menu, which will hide it from the main window." +msgid "Beyond just Spyder's preferences, you can freely rearrange the panes in Spyder's main window. To show or hide panes, go to Panes under the View menu, and select which ones you want to see. For example, let's hide the Files pane and show the Profiler pane. You can also close a pane from its options menu, which will hide it from the main window." msgstr "" #: ../../videos/first-steps-with-spyder.rst:131 -msgid "" -"By default, the panes and toolbars are locked so they can't be moved " -"accidentally. However, unchecking the option Lock panes and toolbars in " -"the View menu will allow you to move them freely anywhere on the window, " -"by dragging them from the top and dropping them at any position you like." -" You can also undock a pane, which will open a new window with it. You " -"can have as many separate windows as you have panes, if you choose. This " -"feature is very useful if you work with several monitors because you can " -"undock the Editor and move it to a different monitor, while working with " -"the rest of the panes in your main monitor." +msgid "By default, the panes and toolbars are locked so they can't be moved accidentally. However, unchecking the option Lock panes and toolbars in the View menu will allow you to move them freely anywhere on the window, by dragging them from the top and dropping them at any position you like. You can also undock a pane, which will open a new window with it. You can have as many separate windows as you have panes, if you choose. This feature is very useful if you work with several monitors because you can undock the Editor and move it to a different monitor, while working with the rest of the panes in your main monitor." msgstr "" #: ../../videos/first-steps-with-spyder.rst:133 -msgid "" -"Additionally, you can split the Editor pane vertically or horizontally in" -" as many copies as you want, and open one or more panels in separate " -"Spyder windows, complete with their own toolbar, outline and status bar." +msgid "Additionally, you can split the Editor pane vertically or horizontally in as many copies as you want, and open one or more panels in separate Spyder windows, complete with their own toolbar, outline and status bar." msgstr "" #: ../../videos/first-steps-with-spyder.rst:135 -msgid "" -"Finally, each pane can be customized further under its respective options" -" menu and Preferences panel." +msgid "Finally, each pane can be customized further under its respective options menu and Preferences panel." msgstr "" #: ../../videos/first-steps-with-spyder.rst:137 -msgid "" -"With all these options, you can customize Spyder to your heart's content." -" However, if you ever want to return to its default configuration, you " -"can always reset the window layout under Window Layouts in the View menu," -" or your entire Spyder configuration with the Reset to Default button in " -"the Preferences." +msgid "With all these options, you can customize Spyder to your heart's content. However, if you ever want to return to its default configuration, you can always reset the window layout under Window Layouts in the View menu, or your entire Spyder configuration with the Reset to Default button in the Preferences." msgstr "" #: ../../videos/first-steps-with-spyder.rst:139 @@ -333,7 +209,7 @@ msgid "Enjoy your customized version of Spyder, and Happy Spydering!" msgstr "" #: ../../videos/index.rst:3 -msgid "Intro Videos" +msgid "Tutorials" msgstr "" #: ../../videos/working-with-spyder.rst:3 @@ -341,9 +217,7 @@ msgid "Working with Spyder" msgstr "" #: ../../videos/working-with-spyder.rst:5 -msgid "" -"In this section, you will learn about Spyder's more advanced " -"functionality, and explore most of the panes." +msgid "In this section, you will learn about Spyder's more advanced functionality, and explore most of the panes." msgstr "" #: ../../videos/working-with-spyder.rst:11 @@ -351,9 +225,7 @@ msgid "Beyond the main panes" msgstr "" #: ../../videos/working-with-spyder.rst:13 -msgid "" -"Explore how to take advantage of Spyder’s functionality beyond just the " -"four core panes." +msgid "Explore how to take advantage of Spyder’s functionality beyond just the four core panes." msgstr "" #: ../../videos/working-with-spyder.rst:15 @@ -369,9 +241,7 @@ msgid "Quickly navigate within and between files with the Outline pane" msgstr "" #: ../../videos/working-with-spyder.rst:18 -msgid "" -"Search for text or regular expressions across your entire project with " -"the Find pane" +msgid "Search for text or regular expressions across your entire project with the Find pane" msgstr "" #: ../../videos/working-with-spyder.rst:19 @@ -379,121 +249,43 @@ msgid "Discover and explore structured documentation in the Online Help pane" msgstr "" #: ../../videos/working-with-spyder.rst:33 -msgid "" -"Hello everyone! I'm Juanita, and I am going to show you how to use some " -"of the remaining panes available in Spyder beyond just the four primary " -"ones." +msgid "Hello everyone! I'm Juanita, and I am going to show you how to use some of the remaining panes available in Spyder beyond just the four primary ones." msgstr "" #: ../../videos/working-with-spyder.rst:35 -msgid "" -"Let's start with the Plots pane, which is open by default when launching " -"Spyder. To see how it works, let's open a file that will generate a " -"couple plots from Matplotlib's documentation. You can view the generated " -"plots in the Plots pane and browse between them using the arrows, or " -"simply clicking them in the sidebar." +msgid "Let's start with the Plots pane, which is open by default when launching Spyder. To see how it works, let's open a file that will generate a couple plots from Matplotlib's documentation. You can view the generated plots in the Plots pane and browse between them using the arrows, or simply clicking them in the sidebar." msgstr "" #: ../../videos/working-with-spyder.rst:37 -msgid "" -"If you open the pane's options menu, you will see that Fit Plots to " -"Window is enabled by default. Disabling it will allow you to zoom the " -"plots in or out. You can also see that Mute inline plotting is enabled, " -"which prevents the same figures from also appearing in the IPython " -"Console. Note that every time that the code is run, new copies of the " -"plots are generated in the pane, but you can remove any you don't want to" -" keep around with the X button in the pane toolbar. Additionally, the " -"pane automatically updates to show the plots generated by each console as" -" you switch between them." +msgid "If you open the pane's options menu, you will see that Fit Plots to Window is enabled by default. Disabling it will allow you to zoom the plots in or out. You can also see that Mute inline plotting is enabled, which prevents the same figures from also appearing in the IPython Console. Note that every time that the code is run, new copies of the plots are generated in the pane, but you can remove any you don't want to keep around with the X button in the pane toolbar. Additionally, the pane automatically updates to show the plots generated by each console as you switch between them." msgstr "" #: ../../videos/working-with-spyder.rst:39 -msgid "" -"To use a plot in another document, click the Copy to Clipboard button and" -" paste it wherever you want, such as a word processor. Additionally, you " -"can save a plot as a PNG by clicking the save icon." +msgid "To use a plot in another document, click the Copy to Clipboard button and paste it wherever you want, such as a word processor. Additionally, you can save a plot as a PNG by clicking the save icon." msgstr "" #: ../../videos/working-with-spyder.rst:41 -msgid "" -"The Files pane, also open by default, lets you browse the contents of the" -" directories on your computer, open them in the Editor, and perform a " -"variety of other file operations. You can show or hide the size, kind and" -" date of the files in the pane's options menu. As you change the top-" -"level folder you're viewing in the pane, Spyder's working directory shown" -" in the top right of the main toolbar will update, which will also be " -"synchronized with the currently active console. Double-clicking a text " -"file will open it in the Editor, and copying one or more files will allow" -" you to paste them as automatically-formatted absolute or relative paths." -" Right-clicking any item will offer an array of additional options for " -"interacting with it." +msgid "The Files pane, also open by default, lets you browse the contents of the directories on your computer, open them in the Editor, and perform a variety of other file operations. You can show or hide the size, kind and date of the files in the pane's options menu. As you change the top-level folder you're viewing in the pane, Spyder's working directory shown in the top right of the main toolbar will update, which will also be synchronized with the currently active console. Double-clicking a text file will open it in the Editor, and copying one or more files will allow you to paste them as automatically-formatted absolute or relative paths. Right-clicking any item will offer an array of additional options for interacting with it." msgstr "" #: ../../videos/working-with-spyder.rst:43 -msgid "" -"You can also open a file in the system default external application, or " -"set up a custom file association in the File Associations tab of the " -"Files preferences pane. For example, we can add the ``.csv`` extension " -"and associate it with LibreOffice Calc under associated applications. Now" -" every time you click a file with this extension, it opens externally " -"with this program." +msgid "You can also open a file in the system default external application, or set up a custom file association in the File Associations tab of the Files preferences pane. For example, we can add the ``.csv`` extension and associate it with LibreOffice Calc under associated applications. Now every time you click a file with this extension, it opens externally with this program." msgstr "" #: ../../videos/working-with-spyder.rst:45 -msgid "" -"Now, let's see how to use the Outline pane to navigate within a file. " -"First, we have to open the pane under Panes in the View menu, since it " -"isn't visible by default. As you can see, it shows you all the classes, " -"methods and functions that are currently defined, and allows you to move " -"between them with just a click. For a very large file like this one, it " -"is very useful to switch between classes easily instead of scrolling " -"through the four-thousand-plus lines of code. You can also browse the " -"methods of a class by expanding it using the arrows, or the buttons in " -"the Outline pane's toolbar. The Outline continuously updates to highlight" -" the function, method or class corresponding to the cursor position in " -"your code, so you can easily keep track of what object you are working " -"on. Finally, by going to the pane options menu and activating Show all " -"files, you can easily switch between the scripts and modules you have " -"open, which is particularly important for navigating larger projects." +msgid "Now, let's see how to use the Outline pane to navigate within a file. First, we have to open the pane under Panes in the View menu, since it isn't visible by default. As you can see, it shows you all the classes, methods and functions that are currently defined, and allows you to move between them with just a click. For a very large file like this one, it is very useful to switch between classes easily instead of scrolling through the four-thousand-plus lines of code. You can also browse the methods of a class by expanding it using the arrows, or the buttons in the Outline pane's toolbar. The Outline continuously updates to highlight the function, method or class corresponding to the cursor position in your code, so you can easily keep track of what object you are working on. Finally, by going to the pane options menu and activating Show all files, you can easily switch between the scripts and modules you have open, which is particularly important for navigating larger projects." msgstr "" #: ../../videos/working-with-spyder.rst:47 -msgid "" -"The Files pane is another useful tool for particularly larger projects. " -"Like the Outline pane, it can be opened under Panes in the View menu. " -"This allows you to view and navigate through all occurrences of text or " -"regular expressions in any file in the working directory, project or " -"another custom directory. We see, for example, in the ``mainwindow.py`` " -"file we import the ``is_dark_font_color`` function. If we want to quickly" -" find the file where it was defined, we can write this string in the " -"search bar. With this search, we get 7 matches from 3 different files. " -"When we click on any of these matches, the file is opened automatically " -"in the Editor, right where this string appears." +msgid "The Files pane is another useful tool for particularly larger projects. Like the Outline pane, it can be opened under Panes in the View menu. This allows you to view and navigate through all occurrences of text or regular expressions in any file in the working directory, project or another custom directory. We see, for example, in the ``mainwindow.py`` file we import the ``is_dark_font_color`` function. If we want to quickly find the file where it was defined, we can write this string in the search bar. With this search, we get 7 matches from 3 different files. When we click on any of these matches, the file is opened automatically in the Editor, right where this string appears." msgstr "" #: ../../videos/working-with-spyder.rst:49 -msgid "" -"Finally, we'll learn how to browse documentation using the Online Help " -"pane. Once you open it, again under Panes in the View menu, you will see " -"an index of modules from which documentation is available, including both" -" those in the Python standard library and any third-party packages that " -"may be installed in Spyder's environment. For example, we can find help " -"for Numpy, Pandas and Matplotlib, which are all installed if you've " -"downloaded Spyder with Anaconda. You can browse the contents in the " -"built-in web browser provided by the pane, and click the hyperlinks " -"within to navigate to different pages. You can also enter the name of the" -" item you'd like documentation on in the Get field or in the space over " -"the pane's toolbar, to load its information directly. If you're not sure " -"of the object's name, use the Search field to view a list of results " -"applicable to any keyword." +msgid "Finally, we'll learn how to browse documentation using the Online Help pane. Once you open it, again under Panes in the View menu, you will see an index of modules from which documentation is available, including both those in the Python standard library and any third-party packages that may be installed in Spyder's environment. For example, we can find help for Numpy, Pandas and Matplotlib, which are all installed if you've downloaded Spyder with Anaconda. You can browse the contents in the built-in web browser provided by the pane, and click the hyperlinks within to navigate to different pages. You can also enter the name of the item you'd like documentation on in the Get field or in the space over the pane's toolbar, to load its information directly. If you're not sure of the object's name, use the Search field to view a list of results applicable to any keyword." msgstr "" #: ../../videos/working-with-spyder.rst:51 -msgid "" -"Now that you're familiar with a wider array of Spyder's panes and " -"features, you can accomplish a variety of common programming tasks with " -"ease. Stay tuned for our our next videos to further add to your " -"scientific toolbox, and as always, Happy Spydering!" +msgid "Now that you're familiar with a wider array of Spyder's panes and features, you can accomplish a variety of common programming tasks with ease. Stay tuned for our our next videos to further add to your scientific toolbox, and as always, Happy Spydering!" msgstr "" #: ../../videos/working-with-spyder.rst:57 @@ -505,9 +297,7 @@ msgid "Learn how to improve the quality of your programs using code analysis." msgstr "" #: ../../videos/working-with-spyder.rst:61 -msgid "" -"Open and use Code Analysis to evaluate the quality and style of Python " -"files" +msgid "Open and use Code Analysis to evaluate the quality and style of Python files" msgstr "" #: ../../videos/working-with-spyder.rst:62 @@ -523,127 +313,71 @@ msgid "Turn off messages on a line, in a file or globally" msgstr "" #: ../../videos/working-with-spyder.rst:78 -msgid "" -"Hello everyone! I'm Juanita, and in this video we will learn how to " -"improve your code quality using the Code Analysis pane. To display it, we" -" can click its name under Panes in the View menu." +msgid "Hello everyone! I'm Juanita, and in this video we will learn how to improve your code quality using the Code Analysis pane. To display it, we can click its name under Panes in the View menu." msgstr "" #: ../../videos/working-with-spyder.rst:80 -msgid "" -"This pane detects style issues, bad practices, potential bugs and other " -"quality problems in your code, without having to execute it. There are " -"three ways of running code analysis:" +msgid "This pane detects style issues, bad practices, potential bugs and other quality problems in your code, without having to execute it. There are three ways of running code analysis:" msgstr "" #: ../../videos/working-with-spyder.rst:82 -msgid "" -"To analyze a file that is open in the Editor, we can press the " -"configurable shortcut, :kbd:`F8` by default, or select Source --> Run " -"code analysis from the menu bar." +msgid "To analyze a file that is open in the Editor, we can press the configurable shortcut, :kbd:`F8` by default, or select Source --> Run code analysis from the menu bar." msgstr "" #: ../../videos/working-with-spyder.rst:84 -msgid "" -"We can also select a file to analyze by browsing for it using the file " -"button next to the path box. This will start the analysis automatically." +msgid "We can also select a file to analyze by browsing for it using the file button next to the path box. This will start the analysis automatically." msgstr "" #: ../../videos/working-with-spyder.rst:86 -msgid "" -"The third way is to manually enter the path of a file we'd like to check " -"in the path entry box in the pane's toolbar, and click the Analyze button" -" in the pane." +msgid "The third way is to manually enter the path of a file we'd like to check in the path entry box in the pane's toolbar, and click the Analyze button in the pane." msgstr "" #: ../../videos/working-with-spyder.rst:88 -msgid "" -"Based on these results, the code analysis shows an overall score of " -"4.34/10, which allows us to track improvements in our code quality. We " -"can also expand or collapse one or all the sections in the pane to be " -"able to see the Pylint errors, warnings and messages identifying the " -"issues with our code." +msgid "Based on these results, the code analysis shows an overall score of 4.34/10, which allows us to track improvements in our code quality. We can also expand or collapse one or all the sections in the pane to be able to see the Pylint errors, warnings and messages identifying the issues with our code." msgstr "" #: ../../videos/working-with-spyder.rst:90 -msgid "" -"For example, the results tell us that there is a warning on line 20. To " -"go directly to this line in the Editor, just click the message. Here, the" -" code analysis says there is a ``bad-whitespace`` issue. To understand " -"what this means, open the Pylint documentation. On the `Pylint docs " -"page`_ , click on Pylint features and search for the code of the message." +msgid "For example, the results tell us that there is a warning on line 20. To go directly to this line in the Editor, just click the message. Here, the code analysis says there is a ``bad-whitespace`` issue. To understand what this means, open the Pylint documentation. On the `Pylint docs page`_ , click on Pylint features and search for the code of the message." msgstr "" #: ../../videos/working-with-spyder.rst:94 -msgid "" -"We can see that the docs say that we used the wrong number of spaces " -"around an operator." +msgid "We can see that the docs say that we used the wrong number of spaces around an operator." msgstr "" #: ../../videos/working-with-spyder.rst:102 -msgid "" -"We can fix the error by adding one space before and after the operator in" -" this variable assignment. If we run the analysis again, we can see the " -"error isn't shown any more on this line." +msgid "We can fix the error by adding one space before and after the operator in this variable assignment. If we run the analysis again, we can see the error isn't shown any more on this line." msgstr "" #: ../../videos/working-with-spyder.rst:104 -msgid "" -"We can click the dropdown arrow in the filename field to view the list of" -" previous analyses. Clicking one of them will show us the results." +msgid "We can click the dropdown arrow in the filename field to view the list of previous analyses. Clicking one of them will show us the results." msgstr "" #: ../../videos/working-with-spyder.rst:106 -msgid "" -"Sometimes, it is useful to turn certain messages off. We can do that in " -"three different ways." +msgid "Sometimes, it is useful to turn certain messages off. We can do that in three different ways." msgstr "" #: ../../videos/working-with-spyder.rst:108 -msgid "" -"We might want to silence warnings on only one line; for example, this " -"\"unused\" import that is still necessary for the code execution. For " -"this, type ``# pylint: disable=unused-import`` as a comment at the end of" -" the line. Running the analysis again will show us that the error is no " -"longer visible." +msgid "We might want to silence warnings on only one line; for example, this \"unused\" import that is still necessary for the code execution. For this, type ``# pylint: disable=unused-import`` as a comment at the end of the line. Running the analysis again will show us that the error is no longer visible." msgstr "" #: ../../videos/working-with-spyder.rst:110 -msgid "" -"If we want to silence a message in the whole file, we can do it by " -"writing the disable command at the beginning of the file. For example, we" -" can disable the ``invalid-name`` warning that appears several times in " -"this file. If we run the analysis again, all of these warnings are gone." +msgid "If we want to silence a message in the whole file, we can do it by writing the disable command at the beginning of the file. For example, we can disable the ``invalid-name`` warning that appears several times in this file. If we run the analysis again, all of these warnings are gone." msgstr "" #: ../../videos/working-with-spyder.rst:112 -msgid "" -"Finally, we can suppress specific messages for all files by editing the " -"``.pylintrc`` configuration file in your user folder. If it doesn't " -"exist, we can generate it by opening our terminal, or the Anaconda Prompt" -" if you're using Windows, and running ``pylint --generate-rc > " -".pylintrc`` in our user directory." +msgid "Finally, we can suppress specific messages for all files by editing the ``.pylintrc`` configuration file in your user folder. If it doesn't exist, we can generate it by opening our terminal, or the Anaconda Prompt if you're using Windows, and running ``pylint --generate-rc > .pylintrc`` in our user directory." msgstr "" #: ../../videos/working-with-spyder.rst:114 -msgid "" -"Now, we can go to the ``MESSAGE CONTROL`` section in this file and add " -"the corresponding Pylint message name, for example ``no-name-in-module``." -" If we run the analysis one more time, we see that the ``no-name-in-" -"module`` warnings don't appear anymore." +msgid "Now, we can go to the ``MESSAGE CONTROL`` section in this file and add the corresponding Pylint message name, for example ``no-name-in-module``. If we run the analysis one more time, we see that the ``no-name-in-module`` warnings don't appear anymore." msgstr "" #: ../../videos/working-with-spyder.rst:116 -msgid "" -"We can see that the score of our file increased to 7.63/10, a big " -"improvement over the previous 4.34." +msgid "We can see that the score of our file increased to 7.63/10, a big improvement over the previous 4.34." msgstr "" #: ../../videos/working-with-spyder.rst:118 -msgid "" -"Now that we've learned how to improve the quality of our code, you are " -"ready to write cleaner and more correct programs using Spyder. Stay tuned" -" for our next videos and as always, Happy Spydering!" +msgid "Now that we've learned how to improve the quality of our code, you are ready to write cleaner and more correct programs using Spyder. Stay tuned for our next videos and as always, Happy Spydering!" msgstr "" #: ../../videos/working-with-spyder.rst:124 @@ -671,108 +405,55 @@ msgid "Use the information to speed up the run time of your code" msgstr "" #: ../../videos/working-with-spyder.rst:145 -msgid "" -"Hello everyone! I'm Juanita, and in this video we will learn how to " -"optimize your code using the profiler. To display it, click its name " -"under Panes in the View menu." +msgid "Hello everyone! I'm Juanita, and in this video we will learn how to optimize your code using the profiler. To display it, click its name under Panes in the View menu." msgstr "" #: ../../videos/working-with-spyder.rst:147 -msgid "" -"The Profiler will determine the run time and number of calls for every " -"function and method used in a file. There are three ways of profiling a " -"file:" +msgid "The Profiler will determine the run time and number of calls for every function and method used in a file. There are three ways of profiling a file:" msgstr "" #: ../../videos/working-with-spyder.rst:149 -msgid "" -"We can browse for a file using the open button to the right of the " -"Profiler's path box, which will run profiling over it automatically." +msgid "We can browse for a file using the open button to the right of the Profiler's path box, which will run profiling over it automatically." msgstr "" #: ../../videos/working-with-spyder.rst:151 -msgid "" -"We can also manually enter the path in the pane's path box, and then run " -"the analysis on the file by pressing the Profile button." +msgid "We can also manually enter the path in the pane's path box, and then run the analysis on the file by pressing the Profile button." msgstr "" #: ../../videos/working-with-spyder.rst:153 -msgid "" -"If we want to run the profiler for the file that is currently open in the" -" Editor, we can click Run --> Profile... in the menu bar, or use the " -"configurable shortcut :kbd:`F10`." +msgid "If we want to run the profiler for the file that is currently open in the Editor, we can click Run --> Profile... in the menu bar, or use the configurable shortcut :kbd:`F10`." msgstr "" #: ../../videos/working-with-spyder.rst:155 -msgid "" -"We see that the results in the pane show us the different functions and " -"methods in our file, with each sub-function listed hierarchically under " -"the item that called them. The columns show the total time taken by each " -"function and everything it called, while the local time includes only the" -" time spent in that particular function." +msgid "We see that the results in the pane show us the different functions and methods in our file, with each sub-function listed hierarchically under the item that called them. The columns show the total time taken by each function and everything it called, while the local time includes only the time spent in that particular function." msgstr "" #: ../../videos/working-with-spyder.rst:157 -msgid "" -"For example, the function ``values`` in this file calls a function " -"``internal_values`` values took a total of 482 us to run, with 338 us of " -"that spent executing internal_values inside of it. Therefore, the total " -"time for values is 482 us, but its local time is only 144 us as the rest " -"was spent inside ``internal_values``." +msgid "For example, the function ``values`` in this file calls a function ``internal_values`` values took a total of 482 us to run, with 338 us of that spent executing internal_values inside of it. Therefore, the total time for values is 482 us, but its local time is only 144 us as the rest was spent inside ``internal_values``." msgstr "" #: ../../videos/working-with-spyder.rst:159 -msgid "" -"The Calls column displays the total number of times that function was " -"called at that level. Finally, the numbers in the Diff columns for each " -"of the three appear if a comparison is loaded, and indicate the change in" -" runtime between the two measurements." +msgid "The Calls column displays the total number of times that function was called at that level. Finally, the numbers in the Diff columns for each of the three appear if a comparison is loaded, and indicate the change in runtime between the two measurements." msgstr "" #: ../../videos/working-with-spyder.rst:161 -msgid "" -"By double-clicking an item in the Profiler, we will be taken to the file " -"and line in the Editor where it was called. If this function was not " -"called in one of your open scripts, clicking it will open the file that " -"contains it. We can click the down arrow button in the filename field to " -"recall paths of previously profiled files." +msgid "By double-clicking an item in the Profiler, we will be taken to the file and line in the Editor where it was called. If this function was not called in one of your open scripts, clicking it will open the file that contains it. We can click the down arrow button in the filename field to recall paths of previously profiled files." msgstr "" #: ../../videos/working-with-spyder.rst:163 -msgid "" -"Now that we know how to interpret the results of our profiling, let's " -"optimize our code by finding the functions that take the longest time and" -" making them faster. In this case, ``to_datetime`` takes 39 seconds to " -"run. The reason for this is Pandas has to parse the non-standard " -"timestamp format and is not told to try to use a faster parser than the " -"default." +msgid "Now that we know how to interpret the results of our profiling, let's optimize our code by finding the functions that take the longest time and making them faster. In this case, ``to_datetime`` takes 39 seconds to run. The reason for this is Pandas has to parse the non-standard timestamp format and is not told to try to use a faster parser than the default." msgstr "" #: ../../videos/working-with-spyder.rst:165 #, python-format -msgid "" -"We can reduce the time this function takes and compare it with the one " -"before. For this, first we have to save the data as a ``.Result`` file " -"with the save button in the pane. Now we have to figure out how to " -"optimize the function, so let's search for it. We see that we can speed " -"up this function by `manually specifying a datetime format`_. So, we add " -"the appropriate argument, ``format=\"%Y-%m-%d %H:%M:%S.%f %z\"``, to our " -"function call." +msgid "We can reduce the time this function takes and compare it with the one before. For this, first we have to save the data as a ``.Result`` file with the save button in the pane. Now we have to figure out how to optimize the function, so let's search for it. We see that we can speed up this function by `manually specifying a datetime format`_. So, we add the appropriate argument, ``format=\"%Y-%m-%d %H:%M:%S.%f %z\"``, to our function call." msgstr "" #: ../../videos/working-with-spyder.rst:169 -msgid "" -"Now, we run the profiling again to see how our script's performance has " -"improved. If we want to see how much we lowered the time, we can load our" -" previous result and take a look at the diff columns. Notice the " -"difference is green because the time was reduced by three times, taking " -"only 13 seconds instead of 39. Our code is now 26 seconds faster!" +msgid "Now, we run the profiling again to see how our script's performance has improved. If we want to see how much we lowered the time, we can load our previous result and take a look at the diff columns. Notice the difference is green because the time was reduced by three times, taking only 13 seconds instead of 39. Our code is now 26 seconds faster!" msgstr "" #: ../../videos/working-with-spyder.rst:171 -msgid "" -"Now that you've learned how to analyze the execution time of your code, " -"you are ready to write more efficient programs with Spyder's help. Stay " -"tuned for our next videos and as always, Happy Spydering!" +msgid "Now that you've learned how to analyze the execution time of your code, you are ready to write more efficient programs with Spyder's help. Stay tuned for our next videos and as always, Happy Spydering!" msgstr "" diff --git a/doc/locales/en/LC_MESSAGES/workshops.po b/doc/locales/en/LC_MESSAGES/workshops.po index ade8a7b3..53e581ba 100644 --- a/doc/locales/en/LC_MESSAGES/workshops.po +++ b/doc/locales/en/LC_MESSAGES/workshops.po @@ -8,28 +8,23 @@ msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: en\n" "Language-Team: en \n" -"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.9.1\n" +"Generated-By: Babel 2.16.0\n" #: ../../workshops/financial.rst:3 msgid "Financial Data Analysis with Spyder" msgstr "" #: ../../workshops/financial.rst:5 -msgid "" -"By the end of this workshop participants will be able to use Spyder " -"effectively for applying some normative financial theories and models to" -" assemble a portfolio of assets in a way that maximizes the expected " -"return for a given level of risk. In this way, statistically-based tools " -"are used to construct investment portfolios." +msgid "By the end of this workshop participants will be able to use Spyder effectively for applying some normative financial theories and models to assemble a portfolio of assets in a way that maximizes the expected return for a given level of risk. In this way, statistically-based tools are used to construct investment portfolios." msgstr "" #: ../../workshops/financial.rst:11 ../../workshops/plugin-development.rst:15 @@ -38,30 +33,15 @@ msgid "Prerequisites" msgstr "" #: ../../workshops/financial.rst:13 -msgid "" -"To follow this workshop we recommend that you have a intermediate " -"knowledge of Python. You can visit `The Python Tutorial`_ to learn the " -"basics of this programming language or to refresh your knowledge of " -"Python." +msgid "To follow this workshop we recommend that you have a intermediate knowledge of Python. You can visit `The Python Tutorial`_ to learn the basics of this programming language or to refresh your knowledge of Python." msgstr "" #: ../../workshops/financial.rst:17 -msgid "" -"You will also need to have `Anaconda " -"`_ (or `Miniconda " -"`_) and Spyder installed." -" More information about Spyder installation in :doc:`installation " -"guide<../installation>`." +msgid "You will also need to have `Anaconda `_ (or `Miniconda `_) and Spyder installed. More information about Spyder installation in :doc:`installation guide<../installation>`." msgstr "" #: ../../workshops/financial.rst:21 ../../workshops/scientific-computing.rst:17 -msgid "" -"Spyder now offers :ref:`install-standalone` for Windows and macOS, making" -" it easier to get up and running with the application without having to " -"download Anaconda or manually install it in your existing environment. " -"While we still support Anaconda, we recommend this install method on " -"those platforms to avoid most problems with package conflicts and other " -"issues." +msgid "Spyder now offers :ref:`install-standalone` for Windows and macOS, making it easier to get up and running with the application without having to download Anaconda or manually install it in your existing environment. While we still support Anaconda, we recommend this install method on those platforms to avoid most problems with package conflicts and other issues." msgstr "" #: ../../workshops/financial.rst:25 ../../workshops/plugin-development.rst:24 @@ -90,16 +70,11 @@ msgid "After completing this workshop, you should be able to:" msgstr "" #: ../../workshops/financial.rst:38 -msgid "" -"Apply elementary statistical analysis to stock and cryptocurrency " -"portfolios to measure their performance" +msgid "Apply elementary statistical analysis to stock and cryptocurrency portfolios to measure their performance" msgstr "" #: ../../workshops/financial.rst:39 -msgid "" -"Understand the advantages of programming with an IDE, such as inspecting " -"variables using the Variable Explorer and interacting with plots " -"leveraging the Plots Pane." +msgid "Understand the advantages of programming with an IDE, such as inspecting variables using the Variable Explorer and interacting with plots leveraging the Plots Pane." msgstr "" #: ../../workshops/financial.rst:44 ../../workshops/scientific-computing.rst:45 @@ -107,9 +82,7 @@ msgid "Learner profile" msgstr "" #: ../../workshops/financial.rst:46 -msgid "" -"This workshop is intended for people interested in finance who want to " -"take their first steps in Financial Analysis using Python and Spyder." +msgid "This workshop is intended for people interested in finance who want to take their first steps in Financial Analysis using Python and Spyder." msgstr "" #: ../../workshops/financial.rst:52 ../../workshops/scientific-computing.rst:53 @@ -117,10 +90,7 @@ msgid "Intro" msgstr "" #: ../../workshops/financial.rst:54 -msgid "" -"In this workshop we will obtain financial data in real-time from `Yahoo! " -"Finance`_ API and explore financial portfolios using Econometrics and " -"computational tools." +msgid "In this workshop we will obtain financial data in real-time from `Yahoo! Finance`_ API and explore financial portfolios using Econometrics and computational tools." msgstr "" #: ../../workshops/financial.rst:58 @@ -128,24 +98,15 @@ msgid "Why use Python for financial analysis?" msgstr "" #: ../../workshops/financial.rst:60 -msgid "" -"Real-time analysis of historical and current financial data is essential " -"for those investing in financial instruments. Python has a number of " -"features that make it ideal for financial tasks:" +msgid "Real-time analysis of historical and current financial data is essential for those investing in financial instruments. Python has a number of features that make it ideal for financial tasks:" msgstr "" #: ../../workshops/financial.rst:62 -msgid "" -"It is easy to learn for anyone, whether they have previous programming " -"experience or not" +msgid "It is easy to learn for anyone, whether they have previous programming experience or not" msgstr "" #: ../../workshops/financial.rst:63 -msgid "" -"It has a variety of specialized mathematical and statistical libraries " -"(`SciPy `_, `NumPy `_, `Pandas " -"`_) that are commonly used for financial " -"analysis" +msgid "It has a variety of specialized mathematical and statistical libraries (`SciPy `_, `NumPy `_, `Pandas `_) that are commonly used for financial analysis" msgstr "" #: ../../workshops/financial.rst:64 @@ -153,11 +114,7 @@ msgid "It can be connected to APIs for loading financial data in real time" msgstr "" #: ../../workshops/financial.rst:65 -msgid "" -"It is the programming language with the most resources for machine " -"learning (supervised learning, unsupervised learning, reinforcement " -"learning), which is one of the most useful tools for Econometrics " -"nowadays" +msgid "It is the programming language with the most resources for machine learning (supervised learning, unsupervised learning, reinforcement learning), which is one of the most useful tools for Econometrics nowadays" msgstr "" #: ../../workshops/financial.rst:66 ../../workshops/scientific-computing.rst:68 @@ -165,10 +122,7 @@ msgid "It has excellent libraries for plotting" msgstr "" #: ../../workshops/financial.rst:67 -msgid "" -"You can use resources such as `Google Colab " -"`_ or `Binder `_" -" to do your analysis in the cloud." +msgid "You can use resources such as `Google Colab `_ or `Binder `_ to do your analysis in the cloud." msgstr "" #: ../../workshops/financial.rst:71 @@ -176,12 +130,7 @@ msgid "Why should I use an IDE?" msgstr "" #: ../../workshops/financial.rst:73 -msgid "" -"Although you can use Python without an IDE (Integrated Development " -"Environment), you will work much better with one. Spyder is a Scientific " -"Integrated Development Environment written in Python, and designed by and" -" for scientists, engineers, and data analysts. Spyder's capabilities and " -"its integration with Python make it perfect for financial analysis." +msgid "Although you can use Python without an IDE (Integrated Development Environment), you will work much better with one. Spyder is a Scientific Integrated Development Environment written in Python, and designed by and for scientists, engineers, and data analysts. Spyder's capabilities and its integration with Python make it perfect for financial analysis." msgstr "" #: ../../workshops/financial.rst:77 @@ -189,10 +138,7 @@ msgid "Introduction to financial analysis with Spyder" msgstr "" #: ../../workshops/financial.rst:79 ../../workshops/scientific-computing.rst:96 -msgid "" -"If you're not familiar with Spyder, we recommend you start with our " -":doc:`Quickstart<../quickstart>`. But if you want a summary, here's a " -"quick overview." +msgid "If you're not familiar with Spyder, we recommend you start with our :doc:`Quickstart<../quickstart>`. But if you want a summary, here's a quick overview." msgstr "" #: ../../workshops/financial.rst:83 @@ -206,12 +152,7 @@ msgstr "" #: ../../workshops/financial.rst:89 #: ../../workshops/scientific-computing.rst:106 -msgid "" -"The :doc:`Editor<../panes/editor>` is the place where you write your code" -" and save it as a file (script). It allows you to easily persist your " -"work. This is where you write the code you want to keep from the data " -"analysis you do in IPython Console. **Here you will also be able to read," -" edit and run the code from this workshop**." +msgid "The :doc:`Editor<../panes/editor>` is the place where you write your code and save it as a file (script). It allows you to easily persist your work. This is where you write the code you want to keep from the data analysis you do in IPython Console. **Here you will also be able to read, edit and run the code from this workshop**." msgstr "" #: ../../workshops/financial.rst:93 @@ -221,18 +162,12 @@ msgstr "" #: ../../workshops/financial.rst:95 #: ../../workshops/scientific-computing.rst:112 -msgid "" -"The :doc:`IPython Console<../panes/ipythonconsole>` is the Spyder's " -"component where you write chunks of code that you want to experiment " -"with. **In this workshop, we are going to give you pieces of code that " -"you can copy and run in this console**." +msgid "The :doc:`IPython Console<../panes/ipythonconsole>` is the Spyder's component where you write chunks of code that you want to experiment with. **In this workshop, we are going to give you pieces of code that you can copy and run in this console**." msgstr "" #: ../../workshops/financial.rst:97 #: ../../workshops/scientific-computing.rst:114 -msgid "" -"In essence, the IPython Console allows you to execute commands and " -"interact with data using Python." +msgid "In essence, the IPython Console allows you to execute commands and interact with data using Python." msgstr "" #: ../../workshops/financial.rst:101 @@ -242,18 +177,11 @@ msgstr "" #: ../../workshops/financial.rst:103 #: ../../workshops/scientific-computing.rst:120 -msgid "" -"The :doc:`Variable Explorer<../panes/variableexplorer>` is one of " -"Spyder's best features. It allows you to interactively browse and manage " -"the objects generated in the code of the currently selected " -":doc:`../panes/ipythonconsole` session." +msgid "The :doc:`Variable Explorer<../panes/variableexplorer>` is one of Spyder's best features. It allows you to interactively browse and manage the objects generated in the code of the currently selected :doc:`../panes/ipythonconsole` session." msgstr "" #: ../../workshops/financial.rst:105 -msgid "" -"The Variable Explorer is one of the most frequently used components in " -"this workshop. **This is the pane where we will observe the data and most" -" of the results of the analysis, except for the plots**." +msgid "The Variable Explorer is one of the most frequently used components in this workshop. **This is the pane where we will observe the data and most of the results of the analysis, except for the plots**." msgstr "" #: ../../workshops/financial.rst:109 @@ -262,12 +190,7 @@ msgid "Plots pane" msgstr "" #: ../../workshops/financial.rst:111 -msgid "" -"The :doc:`Plots pane <../panes/plots>` shows all the static graphs and " -"images created in your IPython Console session. **All plots generated by " -"the code will appear in this component**. This pane also allows you to " -"save each graphic in a local file or copy it to the clipboard to share it" -" with other people." +msgid "The :doc:`Plots pane <../panes/plots>` shows all the static graphs and images created in your IPython Console session. **All plots generated by the code will appear in this component**. This pane also allows you to save each graphic in a local file or copy it to the clipboard to share it with other people." msgstr "" #: ../../workshops/financial.rst:117 @@ -277,10 +200,7 @@ msgstr "" #: ../../workshops/financial.rst:119 #: ../../workshops/scientific-computing.rst:142 -msgid "" -"Before starting, you must have installed some packages and libraries " -"needed to run the code. We recommend you to install these requirements in" -" a virtual environment. Here we explain step by step how to do it." +msgid "Before starting, you must have installed some packages and libraries needed to run the code. We recommend you to install these requirements in a virtual environment. Here we explain step by step how to do it." msgstr "" #: ../../workshops/financial.rst:123 @@ -289,9 +209,7 @@ msgstr "" #: ../../workshops/financial.rst:125 #: ../../workshops/scientific-computing.rst:148 -msgid "" -"If you would like to have Spyder in a dedicated environment to update it " -"separately from your other packages and avoid any conflicts, you can." +msgid "If you would like to have Spyder in a dedicated environment to update it separately from your other packages and avoid any conflicts, you can." msgstr "" #: ../../workshops/financial.rst:127 @@ -300,10 +218,7 @@ msgid "You can set up your environment in two different ways." msgstr "" #: ../../workshops/financial.rst:131 -msgid "" -"We recommend creating the virtual environment with Anaconda (or " -"Miniconda) as it integrates seamlessly with Spyder. You can find " -"installation instructions in `Anaconda documentation`_." +msgid "We recommend creating the virtual environment with Anaconda (or Miniconda) as it integrates seamlessly with Spyder. You can find installation instructions in `Anaconda documentation`_." msgstr "" #: ../../workshops/financial.rst:137 @@ -311,23 +226,15 @@ msgid "With commands" msgstr "" #: ../../workshops/financial.rst:139 -msgid "" -"Just run the following command in your Anaconda Prompt (Windows) or " -"terminal (other platforms), to create a new environment called " -"``financial-analysis``:" +msgid "Just run the following command in your Anaconda Prompt (Windows) or terminal (other platforms), to create a new environment called ``financial-analysis``:" msgstr "" #: ../../workshops/financial.rst:145 -msgid "" -"To install Spyder's optional dependencies as well for full functionality," -" use the following command:" +msgid "To install Spyder's optional dependencies as well for full functionality, use the following command:" msgstr "" #: ../../workshops/financial.rst:156 -msgid "" -"Spyder now offers :ref:`install-standalone` for Windows and macOS, making" -" it easier to get up and running with the application without having to " -"download Anaconda or manually install it in your existing environment." +msgid "Spyder now offers :ref:`install-standalone` for Windows and macOS, making it easier to get up and running with the application without having to download Anaconda or manually install it in your existing environment." msgstr "" #: ../../workshops/financial.rst:160 @@ -335,21 +242,15 @@ msgid "Download the datasets" msgstr "" #: ../../workshops/financial.rst:162 -msgid "" -"Although during the workshop we will explain how to use some APIs to " -"download up-to-date data, you can also download the datasets in csv " -"format from `this link " -"`_." +msgid "Although during the workshop we will explain how to use some APIs to download up-to-date data, you can also download the datasets in csv format from `this link `_." msgstr "" #: ../../workshops/financial.rst:164 -msgid "" -"To follow this workshop you do not need to create a new directory. " -"However, if you have downloaded the data and want to use it instead of " -"the APIs, you must set the directory that has the downloaded data as the " -"working directory. In order to do this, check that the working directory " -"is correct. You should see in the upper right corner the path to the " -"directory where you have the downloaded data. Something like this:" +msgid "To follow this workshop you do not need to create a new directory. However, if you have downloaded the data and want to use it instead of the APIs, you must set the directory that has the downloaded data as the working directory. In order to do this, check that the working directory is correct. You should see in the upper right corner the path to the directory where you have the downloaded data. Something like this:" +msgstr "" + +#: ../../workshops/financial.rst:166 +msgid "Spyder's Working Directory plugin showing the working directory downloaded-data-dir" msgstr "" #: ../../workshops/financial.rst:171 @@ -357,11 +258,11 @@ msgid "Setting up the virtual environment in Spyder" msgstr "" #: ../../workshops/financial.rst:173 -msgid "" -"Let's check that the virtual environment we created is enabled in Spyder." -" Go to :guilabel:`Preferences > Python interpreter`, and use the dropdown" -" below :guilabel:`Use the following Python interpreter` to choose your " -"virtual environment. You should see something like this:" +msgid "Let's check that the virtual environment we created is enabled in Spyder. Go to :guilabel:`Preferences > Python interpreter`, and use the dropdown below :guilabel:`Use the following Python interpreter` to choose your virtual environment. You should see something like this:" +msgstr "" + +#: ../../workshops/financial.rst:175 +msgid "Screenshot on how to set up environment in Spyder's Preferences" msgstr "" #: ../../workshops/financial.rst:178 @@ -375,12 +276,7 @@ msgid "Download the code" msgstr "" #: ../../workshops/financial.rst:184 -msgid "" -"Although the workshop is designed for you to write the code in the " -"IPython Console, we have created a file that you can download " -":download:`here `. This script provides all the " -"code you will write in this workshop, and you can use it as a guide if " -"you get lost." +msgid "Although the workshop is designed for you to write the code in the IPython Console, we have created a file that you can download :download:`here `. This script provides all the code you will write in this workshop, and you can use it as a guide if you get lost." msgstr "" #: ../../workshops/financial.rst:190 @@ -388,28 +284,25 @@ msgid "Obtain financial data" msgstr "" #: ../../workshops/financial.rst:192 -msgid "" -"When it comes to finance, being up to date is very important. So we are " -"going to use a Python library that allows us to get updated historical " -"Stock Market records from `Yahoo! Finance`_ API. In this way, we will be " -"able to download data in the period of time we are interested in " -"analyzing." +msgid "When it comes to finance, being up to date is very important. So we are going to use a Python library that allows us to get updated historical Stock Market records from `Yahoo! Finance`_ API. In this way, we will be able to download data in the period of time we are interested in analyzing." msgstr "" #: ../../workshops/financial.rst:197 #: ../../workshops/scientific-computing.rst:261 -msgid "" -"Remember to type and run all code for this workshop in the \"IPython " -"Console\" at the bottom right of Spyder." +msgid "Remember to type and run all code for this workshop in the \"IPython Console\" at the bottom right of Spyder." +msgstr "" + +#: ../../workshops/financial.rst:199 +msgid "Screenshot IPython Console location in Spyder IDE" msgstr "" #: ../../workshops/financial.rst:202 -msgid "" -"You can also write your code in the Editor (the pane that occupies the " -"entire left side of Spyder). If you use the Editor, you can run the code " -"by selecting it and pressing the :guilabel:`Run selection or current " -"line` button in the :guilabel:`Run toolbar` or by pressing the :kbd:`F9` " -"key." +msgid "You can also write your code in the Editor (the pane that occupies the entire left side of Spyder). If you use the Editor, you can run the code by selecting it and pressing the :guilabel:`Run selection or current line` button in the :guilabel:`Run toolbar` or by pressing the :kbd:`F9` key." +msgstr "" + +#: ../../workshops/financial.rst:204 +#: ../../workshops/scientific-computing.rst:268 +msgid "Editor location in Spyder IDE" msgstr "" #: ../../workshops/financial.rst:207 @@ -418,23 +311,15 @@ msgid "To get started, import the libraries." msgstr "" #: ../../workshops/financial.rst:222 -msgid "" -"The first group of imports is for basic operations. The second " -"(``Historic_Crypto`` and ``yfinance``) imports the libraries that we will" -" use to download financial data." +msgid "The first group of imports is for basic operations. The second (``Historic_Crypto`` and ``yfinance``) imports the libraries that we will use to download financial data." msgstr "" #: ../../workshops/financial.rst:224 -msgid "" -"Let's start exploring libraries with an example. We are going to get " -"financial information about Netflix with one line of code:" +msgid "Let's start exploring libraries with an example. We are going to get financial information about Netflix with one line of code:" msgstr "" #: ../../workshops/financial.rst:230 -msgid "" -"We have used the ``Ticker`` class of the ``yfinance`` library to create a" -" ``netflix`` object. This object contains attributes and methods that we " -"can query to obtain various types of information." +msgid "We have used the ``Ticker`` class of the ``yfinance`` library to create a ``netflix`` object. This object contains attributes and methods that we can query to obtain various types of information." msgstr "" #: ../../workshops/financial.rst:234 @@ -442,51 +327,47 @@ msgid "General stock information" msgstr "" #: ../../workshops/financial.rst:236 -msgid "" -"If you want to know which methods and attributes you can query, you can " -"do so with the built-in ``help()`` function." +msgid "If you want to know which methods and attributes you can query, you can do so with the built-in ``help()`` function." msgstr "" #: ../../workshops/financial.rst:238 -msgid "" -"You can also type the name of the object (``netflix``) in the console, " -"then type a period and hit the Tab key once. IPython suggestions will " -"then appear to help you navigate the object:" +msgid "You can also type the name of the object (``netflix``) in the console, then type a period and hit the Tab key once. IPython suggestions will then appear to help you navigate the object:" +msgstr "" + +#: ../../workshops/financial.rst:240 +msgid "IPython Console auto-suggestions" msgstr "" #: ../../workshops/financial.rst:243 -msgid "" -"For example, we can obtain general information with the ``info`` property" -" of the object." +msgid "For example, we can obtain general information with the ``info`` property of the object." msgstr "" #: ../../workshops/financial.rst:249 -msgid "" -"We can observe the result in the Variable Explorer, in the " -"``netflix_info`` variable." +msgid "We can observe the result in the Variable Explorer, in the ``netflix_info`` variable." +msgstr "" + +#: ../../workshops/financial.rst:251 +msgid "First variable in Variable Explorer" msgstr "" #: ../../workshops/financial.rst:254 -msgid "" -"If we double-click on it, a new window with detailed information will be " -"displayed." +msgid "If we double-click on it, a new window with detailed information will be displayed." +msgstr "" + +#: ../../workshops/financial.rst:256 +msgid "Python dict example in Variable Explorer" msgstr "" #: ../../workshops/financial.rst:259 -msgid "" -"In that window we can see a Python dictionary in which each key has a " -"value assigned to it. Each type of value is represented by a distinctive " -"color. For example, we see that Netflix is an Entertainment industry, the" -" summary of the business type, among other indicators. The Variable " -"Explorer is a very convenient way to view these types of results. We can " -"compare it to viewing them in the IPython Console with the ``pprint`` " -"function:" +msgid "In that window we can see a Python dictionary in which each key has a value assigned to it. Each type of value is represented by a distinctive color. For example, we see that Netflix is an Entertainment industry, the summary of the business type, among other indicators. The Variable Explorer is a very convenient way to view these types of results. We can compare it to viewing them in the IPython Console with the ``pprint`` function:" +msgstr "" + +#: ../../workshops/financial.rst:265 +msgid "netflix_info output in IPython Console" msgstr "" #: ../../workshops/financial.rst:268 -msgid "" -"Although ``pprint`` displays all the information, it is easier to view it" -" in the Variable Explorer." +msgid "Although ``pprint`` displays all the information, it is easier to view it in the Variable Explorer." msgstr "" #: ../../workshops/financial.rst:272 @@ -494,24 +375,19 @@ msgid "Historical stock data" msgstr "" #: ../../workshops/financial.rst:274 -msgid "" -"We can download in a dataset the history of a stock with the following " -"line of code:" +msgid "We can download in a dataset the history of a stock with the following line of code:" msgstr "" #: ../../workshops/financial.rst:280 -msgid "" -"We can see a summary and more details of this dataset in the Variable " -"Explorer. It appears as a DataFrame object, with 7 columns and thousands " -"of rows. If we double-click on it we will see the historical records of " -"Netflix stock organized by ascending dates." +msgid "We can see a summary and more details of this dataset in the Variable Explorer. It appears as a DataFrame object, with 7 columns and thousands of rows. If we double-click on it we will see the historical records of Netflix stock organized by ascending dates." +msgstr "" + +#: ../../workshops/financial.rst:282 +msgid "Netflix historical operations" msgstr "" #: ../../workshops/financial.rst:285 -msgid "" -"Throughout this workshop we will use this historical information to " -"compare, with various normative financial theories, different types of " -"financial portfolios." +msgid "Throughout this workshop we will use this historical information to compare, with various normative financial theories, different types of financial portfolios." msgstr "" #: ../../workshops/financial.rst:291 @@ -519,22 +395,11 @@ msgid "First portfolio" msgstr "" #: ../../workshops/financial.rst:293 -msgid "" -"Let's build our first stock investment portfolio! Say we are interested " -"in investing in technology, and we want to know what performance can be " -"obtained by putting money into some of the \"heavyweights\" in this " -"industry." +msgid "Let's build our first stock investment portfolio! Say we are interested in investing in technology, and we want to know what performance can be obtained by putting money into some of the \"heavyweights\" in this industry." msgstr "" #: ../../workshops/financial.rst:295 -msgid "" -"To measure the performance of our first portfolio we are going to use a " -"classic theory in the world of finance: `mean-variance portfolio (MVP) " -"theory`_. This model assumes that investors only care about expected " -"returns and the variance of such returns. The analysis is based entirely " -"on statistical measures based on a time series of share prices, such as " -"periodic mean returns and the variances of those returns with the same " -"periodicity." +msgid "To measure the performance of our first portfolio we are going to use a classic theory in the world of finance: `mean-variance portfolio (MVP) theory`_. This model assumes that investors only care about expected returns and the variance of such returns. The analysis is based entirely on statistical measures based on a time series of share prices, such as periodic mean returns and the variances of those returns with the same periodicity." msgstr "" #: ../../workshops/financial.rst:301 @@ -542,72 +407,51 @@ msgid "Prepare portfolio data" msgstr "" #: ../../workshops/financial.rst:303 -msgid "" -"Before we start, let's run some lines of code to style the plots. These " -"lines are optional, but we recommend that you run them so that the " -"graphics look like the screenshots we present in this workshop." +msgid "Before we start, let's run some lines of code to style the plots. These lines are optional, but we recommend that you run them so that the graphics look like the screenshots we present in this workshop." msgstr "" #: ../../workshops/financial.rst:312 -msgid "" -"Suppose we want to measure the performance of a portfolio consisting of " -"Google, Apple, Microsoft, Netflix and Amazon stocks. Let's call this set " -"``SYMBOLS_1``." +msgid "Suppose we want to measure the performance of a portfolio consisting of Google, Apple, Microsoft, Netflix and Amazon stocks. Let's call this set ``SYMBOLS_1``." msgstr "" #: ../../workshops/financial.rst:320 -msgid "" -"If you search for ``SYMBOLS_1`` in Variable Explorer you will not find " -"it: Python interprets this element not as a variable, but as a " -"**constant**. This is because the name is written with uppercase letters " -"(no letter is lowercase). By default, the Variable Explorer doesn't show " -"this, but actually you can change the settings in the " -":guilabel:`Preferences` to be able to see these constants." +msgid "If you search for ``SYMBOLS_1`` in Variable Explorer you will not find it: Python interprets this element not as a variable, but as a **constant**. This is because the name is written with uppercase letters (no letter is lowercase). By default, the Variable Explorer doesn't show this, but actually you can change the settings in the :guilabel:`Preferences` to be able to see these constants." msgstr "" #: ../../workshops/financial.rst:322 -msgid "" -"We are going to download the historical data for this portfolio. To do " -"this, we are going to use the ``yfinance`` ``download()`` function, which" -" takes as its first argument a string with the symbols (``SYMBOLS_1``) " -"defined above. The rest of the arguments are the start date " -"(``start=\"2012-01-01\"``), the end date (``end=\"2021-01-01\"``) and how" -" the data will be grouped (``group_by=\"Ticker\"``)." +msgid "We are going to download the historical data for this portfolio. To do this, we are going to use the ``yfinance`` ``download()`` function, which takes as its first argument a string with the symbols (``SYMBOLS_1``) defined above. The rest of the arguments are the start date (``start=\"2012-01-01\"``), the end date (``end=\"2021-01-01\"``) and how the data will be grouped (``group_by=\"Ticker\"``)." msgstr "" #: ../../workshops/financial.rst:328 -msgid "" -"The last argument (``group_by=\"Ticker\"``) groups the information mainly" -" by stock. Otherwise, the primary grouping is done by the type of " -"information (e.g., opening price, closing price, volume traded) of the " -"transactions. In the following image you can see the differences (above " -"is the default organization and below is the grouping by \"Ticker\")." +msgid "The last argument (``group_by=\"Ticker\"``) groups the information mainly by stock. Otherwise, the primary grouping is done by the type of information (e.g., opening price, closing price, volume traded) of the transactions. In the following image you can see the differences (above is the default organization and below is the grouping by \"Ticker\")." +msgstr "" + +#: ../../workshops/financial.rst:330 +msgid "Data grouped by Ticker" msgstr "" #: ../../workshops/financial.rst:334 -msgid "" -"The historical data has been downloaded as a Pandas DataFrame. We can " -"explore this data in the variable ``data_1`` in the Variable Explorer." +msgid "The historical data has been downloaded as a Pandas DataFrame. We can explore this data in the variable ``data_1`` in the Variable Explorer." +msgstr "" + +#: ../../workshops/financial.rst:336 +msgid "Portfolio 1 historical data" msgstr "" #: ../../workshops/financial.rst:339 -msgid "" -"Let's change the formatting of the data a bit so that the symbols appear " -"as the column names, and the Ticker moves from columns to rows. We will " -"do this with the ``stack()`` operation of the DataFrame." +msgid "Let's change the formatting of the data a bit so that the symbols appear as the column names, and the Ticker moves from columns to rows. We will do this with the ``stack()`` operation of the DataFrame." +msgstr "" + +#: ../../workshops/financial.rst:345 +msgid "Portfolio 1 historical data stacked by Ticker" msgstr "" #: ../../workshops/financial.rst:348 -msgid "" -"From the Ticker we are only interested in the daily closing price. So we " -"will leave only the values for ``\"Close\"`` and eliminate the Ticker " -"column afterwards." +msgid "From the Ticker we are only interested in the daily closing price. So we will leave only the values for ``\"Close\"`` and eliminate the Ticker column afterwards." msgstr "" #: ../../workshops/financial.rst:354 -msgid "" -"You will notice that there is a new DataFrame in the Variable Explorer " -"called ``close_data_1`` with 2,265 rows and 5 columns." +msgid "You will notice that there is a new DataFrame in the Variable Explorer called ``close_data_1`` with 2,265 rows and 5 columns." msgstr "" #: ../../workshops/financial.rst:358 @@ -615,92 +459,55 @@ msgid "A first glance at the portfolio" msgstr "" #: ../../workshops/financial.rst:360 -msgid "" -"We want to see how our portfolio would have performed if we had invested " -"in it from 2012 to early 2021. How could we obtain this measurement? " -"Let's look at the monthly closing prices of each stock. To do this we " -"will do an automatic resample of the data. And then we will calculate the" -" change in relative frequencies (percentages)." +msgid "We want to see how our portfolio would have performed if we had invested in it from 2012 to early 2021. How could we obtain this measurement? Let's look at the monthly closing prices of each stock. To do this we will do an automatic resample of the data. And then we will calculate the change in relative frequencies (percentages)." msgstr "" #: ../../workshops/financial.rst:362 -msgid "" -"The resampling will be performed with the ``resample(\"M\")`` method and " -"the calculation of percentages with the ``pct_change()`` method. The " -"result will be stored in the ``monthly_data_1`` variable." +msgid "The resampling will be performed with the ``resample(\"M\")`` method and the calculation of percentages with the ``pct_change()`` method. The result will be stored in the ``monthly_data_1`` variable." msgstr "" #: ../../workshops/financial.rst:368 -msgid "" -"Since each stock is a column, we can use the ``mean()`` method on the " -"DataFrame to see the results." +msgid "Since each stock is a column, we can use the ``mean()`` method on the DataFrame to see the results." msgstr "" #: ../../workshops/financial.rst:383 -msgid "" -"Remember that this closing information represents the relative growth of " -"each stock, not its closing price in any currency." +msgid "Remember that this closing information represents the relative growth of each stock, not its closing price in any currency." msgstr "" #: ../../workshops/financial.rst:385 -msgid "" -"As we can see, all the results are positive, so this portfolio has been " -"profitable over the years. In relative terms, the biggest gains would " -"come from Netflix (0.4 percent). These percentages show an average of the" -" monthly variation of the stock price. But how stable have that prices " -"been? To find this out, we can calculate the standard deviation of stock " -"price growth:" +msgid "As we can see, all the results are positive, so this portfolio has been profitable over the years. In relative terms, the biggest gains would come from Netflix (0.4 percent). These percentages show an average of the monthly variation of the stock price. But how stable have that prices been? To find this out, we can calculate the standard deviation of stock price growth:" msgstr "" #: ../../workshops/financial.rst:398 -msgid "" -"The highest volatility is found in Netflix (0.1454), which indicates that" -" its price, despite being the fastest growing, has also had a lot of " -"variation during these years. The most stable price, on the other hand, " -"has been Microsoft's (0.0583)." +msgid "The highest volatility is found in Netflix (0.1454), which indicates that its price, despite being the fastest growing, has also had a lot of variation during these years. The most stable price, on the other hand, has been Microsoft's (0.0583)." msgstr "" #: ../../workshops/financial.rst:400 -msgid "" -"A good way to observe both growth and variability is to draw a time-" -"series plot. To scale the values, we are going to divide the relative " -"frequency of the closing price of the actions by the initial value it has" -" in the dataframe ``close_data_1`` (these initial values can be found " -"with ``close_data_1.iloc[0])``). The plot is drawn with the ``plot()`` " -"method of the Pandas DataFrame (to which we pass as arguments the size of" -" the plot and the plot title)." +msgid "A good way to observe both growth and variability is to draw a time-series plot. To scale the values, we are going to divide the relative frequency of the closing price of the actions by the initial value it has in the dataframe ``close_data_1`` (these initial values can be found with ``close_data_1.iloc[0])``). The plot is drawn with the ``plot()`` method of the Pandas DataFrame (to which we pass as arguments the size of the plot and the plot title)." +msgstr "" + +#: ../../workshops/financial.rst:406 +msgid "Portfolio 1 daily stock price" msgstr "" #: ../../workshops/financial.rst:411 -msgid "" -"You will be able to see the graph in the Plots pane. On the left, you " -"will see the plot in detail. On the right, a stack will be created with " -"all the plots that are generated both in the Console and by running the " -"code directly in the Editor. You can copy, delete or save the plot to " -"disk by clicking on it with the right mouse button or trackpad." +msgid "You will be able to see the graph in the Plots pane. On the left, you will see the plot in detail. On the right, a stack will be created with all the plots that are generated both in the Console and by running the code directly in the Editor. You can copy, delete or save the plot to disk by clicking on it with the right mouse button or trackpad." msgstr "" #: ../../workshops/financial.rst:413 -msgid "" -"The above time-series plot clearly shows the growth of all stocks, " -"particularly Netflix. The high volatility discussed above can also be " -"seen. For example, it can be seen from the plots that, due to high " -"volatility, investing in Netflix in the years 2014 and 2019 left " -"virtually no profit (if shares were bought at the beginning of the year " -"and sold right at the end)." +msgid "The above time-series plot clearly shows the growth of all stocks, particularly Netflix. The high volatility discussed above can also be seen. For example, it can be seen from the plots that, due to high volatility, investing in Netflix in the years 2014 and 2019 left virtually no profit (if shares were bought at the beginning of the year and sold right at the end)." msgstr "" #: ../../workshops/financial.rst:415 -msgid "" -"We can also plot with the ``plot()`` method the DataFrame we already have" -" with the monthly data. To do this, we will add 1 to all the values and " -"calculate the accumulated product with the ``cumprod()`` method:" +msgid "We can also plot with the ``plot()`` method the DataFrame we already have with the monthly data. To do this, we will add 1 to all the values and calculate the accumulated product with the ``cumprod()`` method:" +msgstr "" + +#: ../../workshops/financial.rst:421 +msgid "Portfolio 1 monthly stock price" msgstr "" #: ../../workshops/financial.rst:424 -msgid "" -"This plot of the monthly data is \"smoother\" than the plot of the daily " -"data." +msgid "This plot of the monthly data is \"smoother\" than the plot of the daily data." msgstr "" #: ../../workshops/financial.rst:428 @@ -708,67 +515,35 @@ msgid "Returns and volatility" msgstr "" #: ../../workshops/financial.rst:430 -msgid "" -"Remember that in the *mean-variance portfolio theory* what matters are " -"the expected returns and variances. To calculate these returns, we will " -"divide the price of the stock on one day by the price of the same stock " -"on the previous day. We will do this by dividing the ``close_data_1`` " -"DataFrame by a version of itself in which we shift each record one date " -"backwards (``shift(1)``). For example, if on the date 2012-01-03 a stock " -"was valued at 1, and on the next day (2012-01-02), it was valued at 2, " -"then in our shifted dataset, on the day 2012-01-03 the stock would be " -"worth 1. In this way, we would divide 1 by 2. And so on with all the " -"values of all the shares. We will also normalize the results by passing " -"them to a logarithmic scale with ``np.log()``." +msgid "Remember that in the *mean-variance portfolio theory* what matters are the expected returns and variances. To calculate these returns, we will divide the price of the stock on one day by the price of the same stock on the previous day. We will do this by dividing the ``close_data_1`` DataFrame by a version of itself in which we shift each record one date backwards (``shift(1)``). For example, if on the date 2012-01-03 a stock was valued at 1, and on the next day (2012-01-02), it was valued at 2, then in our shifted dataset, on the day 2012-01-03 the stock would be worth 1. In this way, we would divide 1 by 2. And so on with all the values of all the shares. We will also normalize the results by passing them to a logarithmic scale with ``np.log()``." msgstr "" #: ../../workshops/financial.rst:434 -msgid "" -"Trend lines are more easily drawn in logarithmic scale because they tend " -"to fit better to the minimums. In addition, the logarithmic scale gives a" -" more realistic view of price movements." +msgid "Trend lines are more easily drawn in logarithmic scale because they tend to fit better to the minimums. In addition, the logarithmic scale gives a more realistic view of price movements." msgstr "" #: ../../workshops/financial.rst:440 -msgid "" -"In the variable ``rets_1`` you can see the resulting DataFrame. If you " -"double-click on the variable name in the Variable Explorer, you will see " -"that there are positive values (the share price increased) and negative " -"values (the price decreased at the time of closing)." +msgid "In the variable ``rets_1`` you can see the resulting DataFrame. If you double-click on the variable name in the Variable Explorer, you will see that there are positive values (the share price increased) and negative values (the price decreased at the time of closing)." +msgstr "" + +#: ../../workshops/financial.rst:442 +msgid "Portfolio 1 daily returns" msgstr "" #: ../../workshops/financial.rst:445 -msgid "" -"In addition to the returns of each stock, we will need the specific " -"weight of each stock in the portfolio, i.e., how many shares of each " -"company are in the portfolio. In this workshop we will assume that there " -"is one share of each company and, therefore, the weights will be " -"distributed equally." +msgid "In addition to the returns of each stock, we will need the specific weight of each stock in the portfolio, i.e., how many shares of each company are in the portfolio. In this workshop we will assume that there is one share of each company and, therefore, the weights will be distributed equally." msgstr "" #: ../../workshops/financial.rst:449 -msgid "" -"A stock is a financial security that represents that you own a part of a " -"company (whatever the size of this part). A share, on the other hand, is " -"the smallest unit of denomination of a stock. A stock is composed of one " -"or several shares." +msgid "A stock is a financial security that represents that you own a part of a company (whatever the size of this part). A share, on the other hand, is the smallest unit of denomination of a stock. A stock is composed of one or several shares." msgstr "" #: ../../workshops/financial.rst:451 -msgid "" -"This weight will be a vector (Python list) composed of the relative " -"weight (between 0 and 1) of each stock in the portfolio. The sum of these" -" weights has to be 1. Since we will assume that each stock is a single " -"share, the distribution will be equal: ``[0.2, 0.2, 0.2, 0.2, 0.2]``." +msgid "This weight will be a vector (Python list) composed of the relative weight (between 0 and 1) of each stock in the portfolio. The sum of these weights has to be 1. Since we will assume that each stock is a single share, the distribution will be equal: ``[0.2, 0.2, 0.2, 0.2, 0.2]``." msgstr "" #: ../../workshops/financial.rst:457 -msgid "" -"With this information we can calculate the expected return of this " -"portfolio. The math is simple: this is given by the dot product of the " -"portfolio weights vector and the vector of expected returns. This result " -"must be multiplied by the number of days for which the return is to be " -"calculated (a year has approximately 252 stock price closings)." +msgid "With this information we can calculate the expected return of this portfolio. The math is simple: this is given by the dot product of the portfolio weights vector and the vector of expected returns. This result must be multiplied by the number of days for which the return is to be calculated (a year has approximately 252 stock price closings)." msgstr "" #: ../../workshops/financial.rst:459 @@ -776,21 +551,12 @@ msgid "Let's put all this into a function:" msgstr "" #: ../../workshops/financial.rst:466 -msgid "" -"Let's look at the expected return of this portfolio if we hold it for one" -" year:" +msgid "Let's look at the expected return of this portfolio if we hold it for one year:" msgstr "" #: ../../workshops/financial.rst:474 #, python-format -msgid "" -"An expected gain of almost 30% in one year. Not bad, right? But don't " -"forget the other side of this coin: volatility. This calculation is a bit" -" more complex. First, the dot product of the annualized covariance of the" -" returns (this is multiplied by the number of trading days in a year) and" -" the weights is calculated. Then the dot product of the weights and the " -"previous result is obtained. Finally, the square root of this result is " -"extracted. Let's implement this into a function as well." +msgid "An expected gain of almost 30% in one year. Not bad, right? But don't forget the other side of this coin: volatility. This calculation is a bit more complex. First, the dot product of the annualized covariance of the returns (this is multiplied by the number of trading days in a year) and the weights is calculated. Then the dot product of the weights and the previous result is obtained. Finally, the square root of this result is extracted. Let's implement this into a function as well." msgstr "" #: ../../workshops/financial.rst:481 @@ -798,9 +564,7 @@ msgid "Let's see how our portfolio performs with respect to its volatility:" msgstr "" #: ../../workshops/financial.rst:489 -msgid "" -"If high return is desirable, high volatility is undesirable. The risk of " -"this portfolio is relatively large." +msgid "If high return is desirable, high volatility is undesirable. The risk of this portfolio is relatively large." msgstr "" #: ../../workshops/financial.rst:493 @@ -808,14 +572,7 @@ msgid "Sharpe ratio" msgstr "" #: ../../workshops/financial.rst:495 -msgid "" -"The `Sharpe`_ ratio or index is a measure of portfolio performance. It " -"relates the portfolio's return to its volatility, comparing the " -"expected/realized return with the expected/realized risk. It is " -"calculated as the difference between the actual investment returns and " -"the expected return in a zero-risk situation, divided by the volatility " -"of the investment. **It provides a model of the additional amount of " -"returns received for each additional unit of risk**." +msgid "The `Sharpe`_ ratio or index is a measure of portfolio performance. It relates the portfolio's return to its volatility, comparing the expected/realized return with the expected/realized risk. It is calculated as the difference between the actual investment returns and the expected return in a zero-risk situation, divided by the volatility of the investment. **It provides a model of the additional amount of returns received for each additional unit of risk**." msgstr "" #: ../../workshops/financial.rst:499 @@ -827,33 +584,19 @@ msgid "And let's apply this to our portfolio." msgstr "" #: ../../workshops/financial.rst:516 -msgid "" -"The Sharpe ratio measure is best understood in context: when comparing " -"two or more portfolios, the one with the higher Sharpe ratio provides " -"more profit for the same amount of risk." +msgid "The Sharpe ratio measure is best understood in context: when comparing two or more portfolios, the one with the higher Sharpe ratio provides more profit for the same amount of risk." msgstr "" #: ../../workshops/financial.rst:518 -msgid "" -"We can also use a `Monte Carlo " -"`_ simulation to " -"randomize the weights of each stock in the portfolio so that we can see " -"the range over which the Sharpe ratio can vary. In this way we can plot " -"some scenarios that together will give us a good insight of the " -"relationship between expected returns and expected volatility." +msgid "We can also use a `Monte Carlo `_ simulation to randomize the weights of each stock in the portfolio so that we can see the range over which the Sharpe ratio can vary. In this way we can plot some scenarios that together will give us a good insight of the relationship between expected returns and expected volatility." msgstr "" #: ../../workshops/financial.rst:520 -msgid "" -"We are going to do this with a function that we will explain step by step" -" in the `monte_carlo_sharpe function explained`_ section." +msgid "We are going to do this with a function that we will explain step by step in the `monte_carlo_sharpe function explained`_ section." msgstr "" #: ../../workshops/financial.rst:538 -msgid "" -"You do not need to type the following code in the IPython Console. If you" -" write the function above it will be enough. It is just a code " -"presentation to explain what is inside the function." +msgid "You do not need to type the following code in the IPython Console. If you write the function above it will be enough. It is just a code presentation to explain what is inside the function." msgstr "" #: ../../workshops/financial.rst:542 @@ -861,24 +604,15 @@ msgid "``monte_carlo_sharpe`` function explained" msgstr "" #: ../../workshops/financial.rst:544 -msgid "" -"Let's now break the function down to understand what is happening. First," -" we create a numpy array of length 1,000 and width of the number of " -"shares in the portfolio. Each row of the array has random weights that " -"always add up to 1:" +msgid "Let's now break the function down to understand what is happening. First, we create a numpy array of length 1,000 and width of the number of shares in the portfolio. Each row of the array has random weights that always add up to 1:" msgstr "" #: ../../workshops/financial.rst:552 -msgid "" -"The next section calculates the volatility and returns for the new random" -" weights using a list comprehension. The resulting list is transformed " -"back into a numpy array:" +msgid "The next section calculates the volatility and returns for the new random weights using a list comprehension. The resulting list is transformed back into a numpy array:" msgstr "" #: ../../workshops/financial.rst:559 -msgid "" -"Finally, we obtain the Sharpe ratio by dividing the index 1 " -"(volatilities) by the index 0 (returns) of the numpy array:" +msgid "Finally, we obtain the Sharpe ratio by dividing the index 1 (volatilities) by the index 0 (returns) of the numpy array:" msgstr "" #: ../../workshops/financial.rst:567 @@ -886,10 +620,7 @@ msgid "Using the ``monte_carlo_sharpe`` function" msgstr "" #: ../../workshops/financial.rst:569 -msgid "" -"We use the function to get the simulated returns and volatility of " -"portfolio 1 (``port_1_vr``) and the related Sharpe ratios " -"(``port_1_sr``)." +msgid "We use the function to get the simulated returns and volatility of portfolio 1 (``port_1_vr``) and the related Sharpe ratios (``port_1_sr``)." msgstr "" #: ../../workshops/financial.rst:571 @@ -897,33 +628,27 @@ msgid "Enter the following code in the console." msgstr "" #: ../../workshops/financial.rst:579 -msgid "" -"Remember that the weights are initialized randomly, so each time you run " -"this code you will get different results." +msgid "Remember that the weights are initialized randomly, so each time you run this code you will get different results." msgstr "" #: ../../workshops/financial.rst:581 -msgid "" -"With this we obtain two arrays with 1,000 simulated cases for our " -"portfolio. But the best way to explore this is with a plot." +msgid "With this we obtain two arrays with 1,000 simulated cases for our portfolio. But the best way to explore this is with a plot." msgstr "" #: ../../workshops/financial.rst:593 msgid "You should see in the Plots pane something like this:" msgstr "" +#: ../../workshops/financial.rst:595 +msgid "Portfolio 1 Monte Carlo Sharpe simulation scatter plot" +msgstr "" + #: ../../workshops/financial.rst:598 -msgid "" -"A roughly linear relationship can be observed between returns and " -"volatility: the higher the volatility, the higher the gains. And the " -"Sharpe ratio shows an important amount of variability (it is noticeable " -"in the \"width\" of the line drawn)." +msgid "A roughly linear relationship can be observed between returns and volatility: the higher the volatility, the higher the gains. And the Sharpe ratio shows an important amount of variability (it is noticeable in the \"width\" of the line drawn)." msgstr "" #: ../../workshops/financial.rst:600 -msgid "" -"This seems to be a good portfolio because it has a good performance with " -"a not very large variance." +msgid "This seems to be a good portfolio because it has a good performance with a not very large variance." msgstr "" #: ../../workshops/financial.rst:604 @@ -931,10 +656,7 @@ msgid "Optimal portfolio weights" msgstr "" #: ../../workshops/financial.rst:606 -msgid "" -"Can we use the data obtained to calculate the optimal weights for the " -"portfolio by year? Of course we can. Let's start by delimiting the " -"previous years as variables." +msgid "Can we use the data obtained to calculate the optimal weights for the portfolio by year? Of course we can. Let's start by delimiting the previous years as variables." msgstr "" #: ../../workshops/financial.rst:612 @@ -942,55 +664,27 @@ msgid "We will now write a function to calculate these optimal weights." msgstr "" #: ../../workshops/financial.rst:629 -msgid "" -"Let's describe this function in broad strokes. ``bounds`` indicates the " -"maximum and minimum weights for each stock in the portfolio. The lowest " -"weight will be 0 and the highest weight will be 1 for each stock in the " -"portfolio. ``constraints`` is a function that ensures that the sum of the" -" weights of all actions always adds up to 1. Then a loop is initialized " -"that will segment the data for each year. In the variable ``_rets`` the " -"returns for the specified year are obtained. In ``_opt_w`` the " -"``portfolio_shape()`` function is used to calculate the weights that " -"maximize the Sharpe ratio. This is done with the ``minimize()`` function " -"of SciPy (which takes as arguments the ``portfolio_shape`` function, the " -"actual weights of our stocks in the portfolio, and the ``bounds`` and the" -" ``constraints`` variables). Notice the ``-`` sign before " -"``portfolio_sharpe``? It's because ``minimize()`` aims to find the " -"minimum value of a function relative to a parameter, but we are " -"interested in the maximum, so we make the result of ``portfolio_sharpe`` " -"a negative one." +msgid "Let's describe this function in broad strokes. ``bounds`` indicates the maximum and minimum weights for each stock in the portfolio. The lowest weight will be 0 and the highest weight will be 1 for each stock in the portfolio. ``constraints`` is a function that ensures that the sum of the weights of all actions always adds up to 1. Then a loop is initialized that will segment the data for each year. In the variable ``_rets`` the returns for the specified year are obtained. In ``_opt_w`` the ``portfolio_shape()`` function is used to calculate the weights that maximize the Sharpe ratio. This is done with the ``minimize()`` function of SciPy (which takes as arguments the ``portfolio_shape`` function, the actual weights of our stocks in the portfolio, and the ``bounds`` and the ``constraints`` variables). Notice the ``-`` sign before ``portfolio_sharpe``? It's because ``minimize()`` aims to find the minimum value of a function relative to a parameter, but we are interested in the maximum, so we make the result of ``portfolio_sharpe`` a negative one." msgstr "" #: ../../workshops/financial.rst:631 -msgid "" -"We will use the function we just defined to calculate the optimal weights" -" for each year, and we are going to save the result in a Pandas DataFrame" -" to take advantage of the Variable Explorer display options." +msgid "We will use the function we just defined to calculate the optimal weights for each year, and we are going to save the result in a Pandas DataFrame to take advantage of the Variable Explorer display options." msgstr "" #: ../../workshops/financial.rst:639 -msgid "" -"Double click on the ``port_1_ow`` variable in the Variable Explorer. In " -"the table, you can specify the number of decimal places to display, by " -"clicking the format button at the bottom left of the pane, as you can see" -" in the following image:" +msgid "Double click on the ``port_1_ow`` variable in the Variable Explorer. In the table, you can specify the number of decimal places to display, by clicking the format button at the bottom left of the pane, as you can see in the following image:" +msgstr "" + +#: ../../workshops/financial.rst:641 +msgid "Portfolio 1 optimal weights by year" msgstr "" #: ../../workshops/financial.rst:644 -msgid "" -"We set the number of decimal places to 4 and uncheck the **Column " -"min/max** checkbox to better appreciate the contrasts in the row values " -"(years)." +msgid "We set the number of decimal places to 4 and uncheck the **Column min/max** checkbox to better appreciate the contrasts in the row values (years)." msgstr "" #: ../../workshops/financial.rst:646 -msgid "" -"You can see, for example, how 2015 was a particularly good year for " -"investing in Amazon and Netflix, while 2014 was the year of Apple. " -"Despite Netflix's rapid growth over the years, its high volatility means " -"that its Sharpe Ratio is not very remarkable in any year, especially (as " -"we said above) in 2014 and 2019. In the same respect, Apple and Microsoft" -" seem to be safer bets in the return/volatility ratio." +msgid "You can see, for example, how 2015 was a particularly good year for investing in Amazon and Netflix, while 2014 was the year of Apple. Despite Netflix's rapid growth over the years, its high volatility means that its Sharpe Ratio is not very remarkable in any year, especially (as we said above) in 2014 and 2019. In the same respect, Apple and Microsoft seem to be safer bets in the return/volatility ratio." msgstr "" #: ../../workshops/financial.rst:650 @@ -998,54 +692,35 @@ msgid "Comparison of expected and realized returns" msgstr "" #: ../../workshops/financial.rst:652 -msgid "" -"Finally, we will use the optimal weights to calculate the expected " -"returns and compare them with the actual returns." +msgid "Finally, we will use the optimal weights to calculate the expected returns and compare them with the actual returns." msgstr "" #: ../../workshops/financial.rst:668 -msgid "" -"In this function we compare year to year realized returns with " -"theoretically expected returns. This is done by estimating:" +msgid "In this function we compare year to year realized returns with theoretically expected returns. This is done by estimating:" msgstr "" #: ../../workshops/financial.rst:670 -msgid "" -"The returns from applying the optimal weights of the previous year's " -"stocks to the data for that same year (``expected_pr``)." +msgid "The returns from applying the optimal weights of the previous year's stocks to the data for that same year (``expected_pr``)." msgstr "" #: ../../workshops/financial.rst:671 -msgid "" -"The returns from applying the optimal weights of the previous year's " -"stocks to the following year's data (``realized_pr``)." +msgid "The returns from applying the optimal weights of the previous year's stocks to the following year's data (``realized_pr``)." msgstr "" #: ../../workshops/financial.rst:673 -msgid "" -"We are going to apply this function to the data in portfolio 1 and store " -"the results in a DataFrame that we can review in the Variable Explorer." +msgid "We are going to apply this function to the data in portfolio 1 and store the results in a DataFrame that we can review in the Variable Explorer." msgstr "" #: ../../workshops/financial.rst:680 -msgid "" -"The expected column shows the predicted values if the optimal portfolio " -"composition had been used. The realized column, on the other hand, shows " -"the actual profits that would have been obtained with those weights. It " -"can be seen that there are notable differences in some years. Let's look " -"at this in a plot." +msgid "The expected column shows the predicted values if the optimal portfolio composition had been used. The realized column, on the other hand, shows the actual profits that would have been obtained with those weights. It can be seen that there are notable differences in some years. Let's look at this in a plot." +msgstr "" + +#: ../../workshops/financial.rst:686 +msgid "Portfolio 1 expected and realized returns comparison" msgstr "" #: ../../workshops/financial.rst:689 -msgid "" -"The most notable differences are seen in 2014 and 2016. In those years, " -"the previous year's optimal portfolio weights (in blue in the above plot)" -" are a lousy indicator of the following year's stock performance (in " -"red). In 2013, our model estimated that Google and Netflix were excellent" -" investments. But by 2014 their share price did not grow if we compare " -"the price at the beginning and at the end of that year. And something " -"similar happened in 2016, in which Amazon's growing trend of the previous" -" year diminished, and the value of Microsoft and Apple shares grew." +msgid "The most notable differences are seen in 2014 and 2016. In those years, the previous year's optimal portfolio weights (in blue in the above plot) are a lousy indicator of the following year's stock performance (in red). In 2013, our model estimated that Google and Netflix were excellent investments. But by 2014 their share price did not grow if we compare the price at the beginning and at the end of that year. And something similar happened in 2016, in which Amazon's growing trend of the previous year diminished, and the value of Microsoft and Apple shares grew." msgstr "" #: ../../workshops/financial.rst:691 @@ -1053,23 +728,15 @@ msgid "Let's summarize these numbers." msgstr "" #: ../../workshops/financial.rst:701 -msgid "" -"Our optimal weight model offered us a profit of around 40%, but the " -"profit we would have obtained, due to real market fluctuations, would " -"have been almost 20%. Not bad, but the mean-variance portfolio model we " -"have applied for annual calculations is not very accurate, is it?" +msgid "Our optimal weight model offered us a profit of around 40%, but the profit we would have obtained, due to real market fluctuations, would have been almost 20%. Not bad, but the mean-variance portfolio model we have applied for annual calculations is not very accurate, is it?" msgstr "" #: ../../workshops/financial.rst:703 -msgid "" -"And this result is less encouraging if we calculate the correlations " -"between expected and realized profits." +msgid "And this result is less encouraging if we calculate the correlations between expected and realized profits." msgstr "" #: ../../workshops/financial.rst:713 -msgid "" -"As we can see, the correlations are negative, which warns us that we " -"should be cautious when using this type of modeling." +msgid "As we can see, the correlations are negative, which warns us that we should be cautious when using this type of modeling." msgstr "" #: ../../workshops/financial.rst:719 @@ -1077,11 +744,7 @@ msgid "Second portfolio" msgstr "" #: ../../workshops/financial.rst:721 -msgid "" -"We are now going to apply all the previous code with a portfolio of a " -"different nature. Let's assume that instead of technology companies, we " -"are now interested in pharmaceuticals. We will build a portfolio with " -"stocks of Pfizer, Astra Zeneca, Johnson & Johnson." +msgid "We are now going to apply all the previous code with a portfolio of a different nature. Let's assume that instead of technology companies, we are now interested in pharmaceuticals. We will build a portfolio with stocks of Pfizer, Astra Zeneca, Johnson & Johnson." msgstr "" #: ../../workshops/financial.rst:725 @@ -1093,12 +756,7 @@ msgid "Let's download the data and format it." msgstr "" #: ../../workshops/financial.rst:740 -msgid "" -"If you do not want to use the yfinance API, you can download the " -"``close_data_2.csv`` file containing the closing information for this " -"portfolio. Copy this file to your working directory. Load the data with " -"the following instruction: ``>>> close_data_2 = " -"pd.read_csv(\"close_data_2.csv\")``." +msgid "If you do not want to use the yfinance API, you can download the ``close_data_2.csv`` file containing the closing information for this portfolio. Copy this file to your working directory. Load the data with the following instruction: ``>>> close_data_2 = pd.read_csv(\"close_data_2.csv\")``." msgstr "" #: ../../workshops/financial.rst:744 @@ -1106,18 +764,11 @@ msgid "Mean and standard deviation" msgstr "" #: ../../workshops/financial.rst:746 -msgid "" -"We are going to put the data in a monthly format and observe the mean and" -" standard deviation." +msgid "We are going to put the data in a monthly format and observe the mean and standard deviation." msgstr "" #: ../../workshops/financial.rst:768 -msgid "" -"As in portfolio 1, all means are positive. But its largest value (that of" -" JNJ) barely reaches 1% per month, which is slower growth than that of " -"portfolio 1. The variation is also smaller compared to that of the " -"previous portfolio (here the largest deviation is 0.06) which makes it a " -"lower risk investment." +msgid "As in portfolio 1, all means are positive. But its largest value (that of JNJ) barely reaches 1% per month, which is slower growth than that of portfolio 1. The variation is also smaller compared to that of the previous portfolio (here the largest deviation is 0.06) which makes it a lower risk investment." msgstr "" #: ../../workshops/financial.rst:772 @@ -1128,11 +779,16 @@ msgstr "" msgid "Let's better visualize the above with a couple of charts." msgstr "" +#: ../../workshops/financial.rst:785 +msgid "Portfolio 2 daily stock price" +msgstr "" + +#: ../../workshops/financial.rst:788 +msgid "Portfolio 2 monthly stock price" +msgstr "" + #: ../../workshops/financial.rst:791 -msgid "" -"These two plots show a steady growth over the years, but also a high " -"variability in each year. This seems to be a good portfolio only if taken" -" as a long-term investment." +msgid "These two plots show a steady growth over the years, but also a high variability in each year. This seems to be a good portfolio only if taken as a long-term investment." msgstr "" #: ../../workshops/financial.rst:795 @@ -1140,32 +796,23 @@ msgid "Returns, volatility and Sharpe ratio" msgstr "" #: ../../workshops/financial.rst:797 -msgid "" -"To confirm what was said in the previous section, let's calculate " -"returns, volatility and Sharpe ratio." +msgid "To confirm what was said in the previous section, let's calculate returns, volatility and Sharpe ratio." msgstr "" #: ../../workshops/financial.rst:811 -msgid "" -"The return of this portfolio is significantly lower than that of the " -"previous portfolio (0.0809 < 0.2859). Its volatility (0.1637 < 0.2370) is" -" also lower, but to a lesser extent. This is reflected in a lower Sharpe " -"ratio as well (0.4940 < 1.2062). This means, within the mean-variance " -"theory approach, that the first portfolio is a better investment than the" -" second one." +msgid "The return of this portfolio is significantly lower than that of the previous portfolio (0.0809 < 0.2859). Its volatility (0.1637 < 0.2370) is also lower, but to a lesser extent. This is reflected in a lower Sharpe ratio as well (0.4940 < 1.2062). This means, within the mean-variance theory approach, that the first portfolio is a better investment than the second one." msgstr "" #: ../../workshops/financial.rst:813 -msgid "" -"The different behavior is clearly observed if we apply a Monte Carlo " -"simulation and visualize it with a graph:" +msgid "The different behavior is clearly observed if we apply a Monte Carlo simulation and visualize it with a graph:" +msgstr "" + +#: ../../workshops/financial.rst:827 +msgid "Portfolio 2 Monte Carlo Sharpe simulation scatter plot" msgstr "" #: ../../workshops/financial.rst:830 -msgid "" -"High volatility does not correspond in most cases with high returns. In " -"fact, there are scenarios in the simulation in which higher expected " -"returns are related to lower expected volatility." +msgid "High volatility does not correspond in most cases with high returns. In fact, there are scenarios in the simulation in which higher expected returns are related to lower expected volatility." msgstr "" #: ../../workshops/financial.rst:834 @@ -1173,44 +820,35 @@ msgid "Optimal pharmaceutical stock weights" msgstr "" #: ../../workshops/financial.rst:836 -msgid "" -"Let us now see what are the optimal weights for each stock using the " -"``optimal_weights`` function." +msgid "Let us now see what are the optimal weights for each stock using the ``optimal_weights`` function." +msgstr "" + +#: ../../workshops/financial.rst:846 +msgid "Portfolio 2 optimal weights by year" msgstr "" #: ../../workshops/financial.rst:849 -msgid "" -"In addition, we can use these optimal weights to plot the expected and " -"realized returns of this portfolio for each year." +msgid "In addition, we can use these optimal weights to plot the expected and realized returns of this portfolio for each year." +msgstr "" + +#: ../../workshops/financial.rst:858 +msgid "Portfolio 2 expected and realized returns comparison" msgstr "" #: ../../workshops/financial.rst:861 -msgid "" -"Due to the high volatility of this portfolio, our model has not been able" -" to adequately forecast expected returns in several of the years. Higher " -"than expected returns would have been realized in 2013 and 2017, but in " -"2015 and 2018 using the model would have generated losses." +msgid "Due to the high volatility of this portfolio, our model has not been able to adequately forecast expected returns in several of the years. Higher than expected returns would have been realized in 2013 and 2017, but in 2015 and 2018 using the model would have generated losses." msgstr "" #: ../../workshops/financial.rst:863 -msgid "" -"Finally, let us look at the differences between the expected and realized" -" means, and the linear correlation between the data." +msgid "Finally, let us look at the differences between the expected and realized means, and the linear correlation between the data." msgstr "" #: ../../workshops/financial.rst:881 -msgid "" -"As we can see, the model with optimal weights predicted a return close to" -" 15% per year, but the realized return would have barely reached 6%. And " -"the negative correlations show, as with portfolio 1, that there does not " -"seem to be any correspondence between these values." +msgid "As we can see, the model with optimal weights predicted a return close to 15% per year, but the realized return would have barely reached 6%. And the negative correlations show, as with portfolio 1, that there does not seem to be any correspondence between these values." msgstr "" #: ../../workshops/financial.rst:883 -msgid "" -"The comparison is then favorable for portfolio 1. But what if we compare " -"portfolio 1 with a \"higher risk\" investment such as cryptocurrencies? " -"Let's discuss it below." +msgid "The comparison is then favorable for portfolio 1. But what if we compare portfolio 1 with a \"higher risk\" investment such as cryptocurrencies? Let's discuss it below." msgstr "" #: ../../workshops/financial.rst:889 @@ -1222,20 +860,11 @@ msgid "Download cryptocurrencies data" msgstr "" #: ../../workshops/financial.rst:894 -msgid "" -"Our third portfolio will consist of three cryptocurrencies: bitcoin " -"(BTC), ethereum (ETH) and litecoin (LTC). To access historical data, we " -"are going to use a library called **Historic-Crypto**." +msgid "Our third portfolio will consist of three cryptocurrencies: bitcoin (BTC), ethereum (ETH) and litecoin (LTC). To access historical data, we are going to use a library called **Historic-Crypto**." msgstr "" #: ../../workshops/financial.rst:898 -msgid "" -"If you want to make use of the data without the Historic-Crypto library, " -"you can `download the dataset " -"`_" -" \"crypto_hist.csv\" in your working directory, and load it in memory " -"with the instruction ``crypto_hist = pd.read_csv(\"crypto_hist.csv\")``, " -"and skip to section `Monthly data`_." +msgid "If you want to make use of the data without the Historic-Crypto library, you can `download the dataset `_ \"crypto_hist.csv\" in your working directory, and load it in memory with the instruction ``crypto_hist = pd.read_csv(\"crypto_hist.csv\")``, and skip to section `Monthly data`_." msgstr "" #: ../../workshops/financial.rst:900 @@ -1243,26 +872,15 @@ msgid "Import the libraries:" msgstr "" #: ../../workshops/financial.rst:907 -msgid "" -"We are going to use the ``Cryptocurrencies`` class to obtain a list of " -"available cryptocurrencies." +msgid "We are going to use the ``Cryptocurrencies`` class to obtain a list of available cryptocurrencies." msgstr "" #: ../../workshops/financial.rst:915 -msgid "" -"If you want more information about the use of this library you can make a" -" quick query using the Spyder Help panel (type in the console " -"``Cryptocurrencies`` and use :kbd:`Ctrl-I` or :kbd:`Cmd-I` to display " -"it). Or you can read the documentation in their `official repository " -"`_" +msgid "If you want more information about the use of this library you can make a quick query using the Spyder Help panel (type in the console ``Cryptocurrencies`` and use :kbd:`Ctrl-I` or :kbd:`Cmd-I` to display it). Or you can read the documentation in their `official repository `_" msgstr "" #: ../../workshops/financial.rst:917 -msgid "" -"A new variable has appeared in the Variable Explorer: ``crypto_list``. It" -" is a Pandas DataFrame that has a basic description of the types of " -"cryptocurrency transactions. For example, we can look up which token is " -"the token for ethereum transactions in US dollars." +msgid "A new variable has appeared in the Variable Explorer: ``crypto_list``. It is a Pandas DataFrame that has a basic description of the types of cryptocurrency transactions. For example, we can look up which token is the token for ethereum transactions in US dollars." msgstr "" #: ../../workshops/financial.rst:923 @@ -1270,32 +888,19 @@ msgid "In this case, we are interested in the symbol with ID 171: ETH-USD." msgstr "" #: ../../workshops/financial.rst:925 -msgid "" -"We can use the HistoricalData class of Historic-Crypto to download the " -"history of transactions done in the cryptocurrencies of our portfolio, in" -" US dollars." +msgid "We can use the HistoricalData class of Historic-Crypto to download the history of transactions done in the cryptocurrencies of our portfolio, in US dollars." msgstr "" #: ../../workshops/financial.rst:946 -msgid "" -"Let's merge the resulting dataframes to have all the data in a single " -"table." +msgid "Let's merge the resulting dataframes to have all the data in a single table." msgstr "" #: ../../workshops/financial.rst:953 -msgid "" -"We will not present the procedures and code in this section, but only the" -" results of the analysis. You can follow the steps in the previous " -"sections to recreate these results." +msgid "We will not present the procedures and code in this section, but only the results of the analysis. You can follow the steps in the previous sections to recreate these results." msgstr "" #: ../../workshops/financial.rst:957 -msgid "" -"Use all this section on portfolio 3 to check your understanding of the " -"concepts and code we have presented until now. If you have any questions," -" you can consult the :download:`code ` code that " -"accompanies this workshop. But we encourage you to try as much as " -"possible to solve the code on your own." +msgid "Use all this section on portfolio 3 to check your understanding of the concepts and code we have presented until now. If you have any questions, you can consult the :download:`code ` code that accompanies this workshop. But we encourage you to try as much as possible to solve the code on your own." msgstr "" #: ../../workshops/financial.rst:961 @@ -1306,10 +911,12 @@ msgstr "" msgid "Let's take a look at the monthly history of cryptocurrency price growth." msgstr "" +#: ../../workshops/financial.rst:965 +msgid "Portfolio 3 daily stock price" +msgstr "" + #: ../../workshops/financial.rst:968 -msgid "" -"We can note that the scale here is much larger. And the proportion of ETH" -" growth over the other two coins is quite remarkable." +msgid "We can note that the scale here is much larger. And the proportion of ETH growth over the other two coins is quite remarkable." msgstr "" #: ../../workshops/financial.rst:972 @@ -1333,12 +940,7 @@ msgid "Sharpe: 0.8176" msgstr "" #: ../../workshops/financial.rst:980 -msgid "" -"These numbers are higher than those obtained for portfolios 1 and 2, " -"except for the Sharpe ratio. This is a very volatile portfolio (in fact " -"three times more volatile than that of the technology companies), and " -"that makes it ultimately not as profitable as portfolio 1. The returns " -"are higher (almost double) but the risk may not compensate for it." +msgid "These numbers are higher than those obtained for portfolios 1 and 2, except for the Sharpe ratio. This is a very volatile portfolio (in fact three times more volatile than that of the technology companies), and that makes it ultimately not as profitable as portfolio 1. The returns are higher (almost double) but the risk may not compensate for it." msgstr "" #: ../../workshops/financial.rst:984 @@ -1346,57 +948,43 @@ msgid "Monte carlo simulation" msgstr "" #: ../../workshops/financial.rst:986 -msgid "" -"The Monte Carlo simulation also shows the non-linear correlation between " -"risk and returns (as you can see, sometimes high risk involves only " -"modest profits):" +msgid "The Monte Carlo simulation also shows the non-linear correlation between risk and returns (as you can see, sometimes high risk involves only modest profits):" +msgstr "" + +#: ../../workshops/financial.rst:988 +msgid "Portfolio 3 Monte Carlo Sharpe simulation scatter plot" msgstr "" #: ../../workshops/financial.rst:991 -msgid "" -"As can be seen, there are points (bottom right) that show a very high " -"volatility and yet have a very low expected return. In this sense, " -"portfolio 1 represents a safer investment because the higher risk is " -"consistently offset by higher returns." +msgid "As can be seen, there are points (bottom right) that show a very high volatility and yet have a very low expected return. In this sense, portfolio 1 represents a safer investment because the higher risk is consistently offset by higher returns." msgstr "" #: ../../workshops/financial.rst:995 msgid "Optimal cryptocurrency weights" msgstr "" +#: ../../workshops/financial.rst:997 +msgid "Portfolio 3 optimal weights by year" +msgstr "" + #: ../../workshops/financial.rst:1000 -msgid "" -"The optimal portfolio weights, if calculated annually, suggest that our " -"portfolio should have been quite polarized in some years: the " -"recommendation is to have bought only bitcoins before the start of 2016 " -"and 2019, and only ethereum in 2018. Starting 2017 and 2020, on the other" -" hand, our weights recommended a more balanced investment between bitcoin" -" and ethereum. Litecoin is not recommended by our model." +msgid "The optimal portfolio weights, if calculated annually, suggest that our portfolio should have been quite polarized in some years: the recommendation is to have bought only bitcoins before the start of 2016 and 2019, and only ethereum in 2018. Starting 2017 and 2020, on the other hand, our weights recommended a more balanced investment between bitcoin and ethereum. Litecoin is not recommended by our model." msgstr "" #: ../../workshops/financial.rst:1004 msgid "Expected and realized returns" msgstr "" +#: ../../workshops/financial.rst:1006 +msgid "Portfolio 3 expected and realized returns comparison" +msgstr "" + #: ../../workshops/financial.rst:1009 -msgid "" -"In this graph we can see that in 2017 and 2020 the earnings obtained " -"would have exceeded the expected earnings (with our calculated weights). " -"In 2019 our model predicted a sharp drop in the portfolio, but in reality" -" the portfolio did not make either annualized gains or losses that year. " -"In contrast, in 2018, our model would have brought us heavy losses, as " -"the value of cryptocurrencies declined sharply that year." +msgid "In this graph we can see that in 2017 and 2020 the earnings obtained would have exceeded the expected earnings (with our calculated weights). In 2019 our model predicted a sharp drop in the portfolio, but in reality the portfolio did not make either annualized gains or losses that year. In contrast, in 2018, our model would have brought us heavy losses, as the value of cryptocurrencies declined sharply that year." msgstr "" #: ../../workshops/financial.rst:1011 -msgid "" -"The mean expected return for our portfolio is 0.6972, which is higher " -"than the realized return of 0.4181 that we would have obtained. Having " -"invested in this portfolio over the long term (from 2016 to the present) " -"would have been a very good deal. Due to the high variability, investing " -"in the short term would have been very risky. In terms of gross profits, " -"the realized returns of this portfolio were more than double those of " -"portfolio 1 (0.4181 > 0.1997)." +msgid "The mean expected return for our portfolio is 0.6972, which is higher than the realized return of 0.4181 that we would have obtained. Having invested in this portfolio over the long term (from 2016 to the present) would have been a very good deal. Due to the high variability, investing in the short term would have been very risky. In terms of gross profits, the realized returns of this portfolio were more than double those of portfolio 1 (0.4181 > 0.1997)." msgstr "" #: ../../workshops/financial.rst:1017 @@ -1406,18 +994,11 @@ msgid "Final words" msgstr "" #: ../../workshops/financial.rst:1019 -msgid "" -"The mean-variance portfolio (MVP) theory is one of the many tools " -"available to financial analysis. In recent years, machine learning " -"algorithms have even been used to predict the behavior of stock prices " -"more accurately than can be achieved with any standard financial theory." +msgid "The mean-variance portfolio (MVP) theory is one of the many tools available to financial analysis. In recent years, machine learning algorithms have even been used to predict the behavior of stock prices more accurately than can be achieved with any standard financial theory." msgstr "" #: ../../workshops/financial.rst:1021 -msgid "" -"The examples given during this workshop are not intended to serve as " -"guidelines for you to invest your money. It is only a first step towards " -"learning financial analysis using Python and a scientific IDE." +msgid "The examples given during this workshop are not intended to serve as guidelines for you to invest your money. It is only a first step towards learning financial analysis using Python and a scientific IDE." msgstr "" #: ../../workshops/financial.rst:1023 @@ -1475,25 +1056,17 @@ msgid "Obtain the optimal weights of the stocks in a portfolio." msgstr "" #: ../../workshops/financial.rst:1037 -msgid "" -"With the skills learned here, you will be able to approach more complex " -"topics of financial analysis such as those you will find in the " -"references in the next section." +msgid "With the skills learned here, you will be able to approach more complex topics of financial analysis such as those you will find in the references in the next section." msgstr "" #: ../../workshops/financial.rst:1039 #: ../../workshops/scientific-computing.rst:774 -msgid "" -"Thank you for reaching the end of this workshop! We hope you found it " -"helpful and informative." +msgid "Thank you for reaching the end of this workshop! We hope you found it helpful and informative." msgstr "" #: ../../workshops/financial.rst:1041 #: ../../workshops/plugin-development.rst:1422 -msgid "" -"If you are interested in an introduction to scientific computing with " -"Spyder, you can visit the workshop :doc:`Scientific Computing and " -"Visualization with Spyder <../workshops/scientific-computing>`." +msgid "If you are interested in an introduction to scientific computing with Spyder, you can visit the workshop :doc:`Scientific Computing and Visualization with Spyder <../workshops/scientific-computing>`." msgstr "" #: ../../workshops/financial.rst:1045 @@ -1503,11 +1076,7 @@ msgid "Homework" msgstr "" #: ../../workshops/financial.rst:1047 -msgid "" -"If you want to check what you have learned, we suggest you try to obtain " -"the results presented for the third portfolio. If you have any questions," -" you can consult the code that accompanies this workshop in our " -"repository." +msgid "If you want to check what you have learned, we suggest you try to obtain the results presented for the third portfolio. If you have any questions, you can consult the code that accompanies this workshop in our repository." msgstr "" #: ../../workshops/financial.rst:1053 @@ -1517,9 +1086,7 @@ msgid "Further reading" msgstr "" #: ../../workshops/financial.rst:1055 -msgid "" -"Much of the math used to apply MVP was the mathematics outlined in Yves " -"Hilpisch's excellent book, which we recommend to you:" +msgid "Much of the math used to apply MVP was the mathematics outlined in Yves Hilpisch's excellent book, which we recommend to you:" msgstr "" #: ../../workshops/financial.rst:1057 @@ -1527,9 +1094,7 @@ msgid "Yves Hilpisch, Y. (2020). *Artificial Intelligence in Finance*. O'Reilly. msgstr "" #: ../../workshops/financial.rst:1059 -msgid "" -"A classic that has been with us for decades and is one of Warren " -"Buffett's favorites:" +msgid "A classic that has been with us for decades and is one of Warren Buffett's favorites:" msgstr "" #: ../../workshops/financial.rst:1061 @@ -1537,9 +1102,7 @@ msgid "Graham, B. (1949). *The Intelligent Investor*. HarperCollins." msgstr "" #: ../../workshops/financial.rst:1063 -msgid "" -"Another good resource for financial analysis with Python is the following" -" book by James Ma Weiming:" +msgid "Another good resource for financial analysis with Python is the following book by James Ma Weiming:" msgstr "" #: ../../workshops/financial.rst:1065 @@ -1555,53 +1118,33 @@ msgid "Plugin Development with Spyder" msgstr "" #: ../../workshops/plugin-development.rst:5 -msgid "" -"This workshop reviews the features and possibilities of the API offered " -"by `Spyder`_ 5—the recently released version of our favorite IDE for " -"scientific Python—for plugin development and to extend its functionality." +msgid "This workshop reviews the features and possibilities of the API offered by `Spyder`_ 5—the recently released version of our favorite IDE for scientific Python—for plugin development and to extend its functionality." msgstr "" #: ../../workshops/plugin-development.rst:7 -msgid "" -"As a practical exercise, we will develop a simple plugin that " -"incorporates a configurable pomodoro timer in the status bar and some " -"toolbar buttons to interact with it." +msgid "As a practical exercise, we will develop a simple plugin that incorporates a configurable pomodoro timer in the status bar and some toolbar buttons to interact with it." msgstr "" #: ../../workshops/plugin-development.rst:17 #: ../../workshops/scientific-computing.rst:13 -msgid "" -"You will need to have Spyder installed. Visit our :doc:`installation " -"guide<../installation>` for more information." +msgid "You will need to have Spyder installed. Visit our :doc:`installation guide<../installation>` for more information." msgstr "" #: ../../workshops/plugin-development.rst:21 -msgid "" -"Spyder now offers :ref:`install-standalone` for Windows and macOS, making" -" it easier to get up and running with the application without having to " -"download Anaconda or manually install it in your existing environment. " -"However, readers of this workshop should install Spyder using Anaconda or" -" Miniconda, as standalone installers currently do not allow to add extra " -"packages like the plugin we are going to develop in this workshop." +msgid "Spyder now offers :ref:`install-standalone` for Windows and macOS, making it easier to get up and running with the application without having to download Anaconda or manually install it in your existing environment. However, readers of this workshop should install Spyder using Anaconda or Miniconda, as standalone installers currently do not allow to add extra packages like the plugin we are going to develop in this workshop." msgstr "" #: ../../workshops/plugin-development.rst:26 #: ../../workshops/scientific-computing.rst:22 -msgid "" -"Basic level of Python. You can visit `The Python Tutorial`_ to learn the " -"basics of this programming language." +msgid "Basic level of Python. You can visit `The Python Tutorial`_ to learn the basics of this programming language." msgstr "" #: ../../workshops/plugin-development.rst:27 -msgid "" -"Know the basics of Qt application development using Python, either with " -"`PyQT`_ or `PySide`_." +msgid "Know the basics of Qt application development using Python, either with `PyQT`_ or `PySide`_." msgstr "" #: ../../workshops/plugin-development.rst:29 -msgid "" -"To quickly get started in desktop application development with Qt and " -"Python here is a set of open access resources:" +msgid "To quickly get started in desktop application development with Qt and Python here is a set of open access resources:" msgstr "" #: ../../workshops/plugin-development.rst:31 @@ -1629,9 +1172,7 @@ msgid "By the end of this workshop participants will know:" msgstr "" #: ../../workshops/plugin-development.rst:50 -msgid "" -"The basics to develop plugins for Spyder, and get a general idea of its " -"inner workings." +msgid "The basics to develop plugins for Spyder, and get a general idea of its inner workings." msgstr "" #: ../../workshops/plugin-development.rst:51 @@ -1639,15 +1180,11 @@ msgid "What types of plugins can be developed with Spyder." msgstr "" #: ../../workshops/plugin-development.rst:52 -msgid "" -"The structure of a plugin and the functionality of each component and how" -" it connects to Spyder to extend its features." +msgid "The structure of a plugin and the functionality of each component and how it connects to Spyder to extend its features." msgstr "" #: ../../workshops/plugin-development.rst:53 -msgid "" -"How to package and publish our plugin so that it can be easily installed " -"and used by others." +msgid "How to package and publish our plugin so that it can be easily installed and used by others." msgstr "" #: ../../workshops/plugin-development.rst:59 @@ -1655,64 +1192,47 @@ msgid "Spyder for developers" msgstr "" #: ../../workshops/plugin-development.rst:61 -msgid "" -"The best place to find information about contributing to Spyder or " -"developing for Spyder is its Github repository, in particular the " -"`contribution guide`_." +msgid "The best place to find information about contributing to Spyder or developing for Spyder is its Github repository, in particular the `contribution guide`_." +msgstr "" + +#: ../../workshops/plugin-development.rst:63 +msgid "Spyder IDE components." msgstr "" #: ../../workshops/plugin-development.rst:66 -msgid "" -"The core of **Spyder** is `Spyder-IDE`_ , a desktop application developed" -" in *Qt*, which requires for its operation two packages with it is " -"closely related (and without which it cannot work): *spyder-kernels* and " -"*python-lsp-server*." +msgid "The core of **Spyder** is `Spyder-IDE`_ , a desktop application developed in *Qt*, which requires for its operation two packages with it is closely related (and without which it cannot work): *spyder-kernels* and *python-lsp-server*." msgstr "" #: ../../workshops/plugin-development.rst:68 -msgid "" -"`Qt`_ is an open source multiplatform widget toolkit for creating native " -"graphical user interfaces. Qt is a very complete development framework " -"that offers utilities for building applications, and has extensions for " -"Networking, Bluetooth, Charts, 3D rendering, Navigation (as GPS), among " -"others." +msgid "`Qt`_ is an open source multiplatform widget toolkit for creating native graphical user interfaces. Qt is a very complete development framework that offers utilities for building applications, and has extensions for Networking, Bluetooth, Charts, 3D rendering, Navigation (as GPS), among others." msgstr "" #: ../../workshops/plugin-development.rst:70 -msgid "" -"Spyder uses `qtpy`_ which is an abstraction layer that allows you to work" -" with Qt from Python regardless of whether you use either of the two " -"reference libraries: PyQt or PySide." +msgid "Spyder uses `qtpy`_ which is an abstraction layer that allows you to work with Qt from Python regardless of whether you use either of the two reference libraries: PyQt or PySide." msgstr "" #: ../../workshops/plugin-development.rst:72 -msgid "" -"`spyder-kernels`_ provide Jupyter kernels to Spyder, for use within its " -"consoles." +msgid "`spyder-kernels`_ provide Jupyter kernels to Spyder, for use within its consoles." msgstr "" #: ../../workshops/plugin-development.rst:76 -msgid "" -"Spyder is currently developed in such a way that most of its features are" -" implemented as plugins." +msgid "Spyder is currently developed in such a way that most of its features are implemented as plugins." msgstr "" #: ../../workshops/plugin-development.rst:89 msgid "Types of plugins we can develop in Spyder" msgstr "" +#: ../../workshops/plugin-development.rst:92 +msgid "Types of Spyder plugins." +msgstr "" + #: ../../workshops/plugin-development.rst:97 -msgid "" -"A plugin is a component that adds functionality to an application, it can" -" be a graphical component, for example, to display maps, or a non-" -"graphical one that adds additional syntax coloring schemes." +msgid "A plugin is a component that adds functionality to an application, it can be a graphical component, for example, to display maps, or a non-graphical one that adds additional syntax coloring schemes." msgstr "" #: ../../workshops/plugin-development.rst:99 -msgid "" -"Formally, plugins are instances of Qt classes that modify the behavior of" -" Spyder. Aside from a few fundamental components, most of Spyder's " -"functionality arises from the interaction of plugins of two types:" +msgid "Formally, plugins are instances of Qt classes that modify the behavior of Spyder. Aside from a few fundamental components, most of Spyder's functionality arises from the interaction of plugins of two types:" msgstr "" #: ../../workshops/plugin-development.rst:104 @@ -1720,10 +1240,7 @@ msgid "SpyderDockablePlugin" msgstr "" #: ../../workshops/plugin-development.rst:106 -msgid "" -"It is a plugin that works as a `QDockWidget`_, this is a Qt class that " -"provides a graphical control that can be docked inside a `QMainWindow`_ " -"or floated as a top-level window on the desktop." +msgid "It is a plugin that works as a `QDockWidget`_, this is a Qt class that provides a graphical control that can be docked inside a `QMainWindow`_ or floated as a top-level window on the desktop." msgstr "" #: ../../workshops/plugin-development.rst:113 @@ -1731,54 +1248,43 @@ msgid "SpyderPluginV2" msgstr "" #: ../../workshops/plugin-development.rst:115 -msgid "" -"``SpyderPluginV2`` is a plugin that does not create a new dock widget on " -"Spyder's main window. In fact, ``SpyderPluginV2`` is the parent class of " -"``SpyderDockablePlugin``." +msgid "``SpyderPluginV2`` is a plugin that does not create a new dock widget on Spyder's main window. In fact, ``SpyderPluginV2`` is the parent class of ``SpyderDockablePlugin``." msgstr "" #: ../../workshops/plugin-development.rst:120 msgid "Discovering Spyder plugins" msgstr "" +#: ../../workshops/plugin-development.rst:120 +msgid "``SpyderDockablePlugin``" +msgstr "" + #: ../../workshops/plugin-development.rst:124 -msgid "" -"If we look at the Spyder interface, we can find a number of different " -"panes on the right side (with the default layout), such as *Help*, " -"*Variable Explorer*, *Plots*, *Files* and *History*." +msgid "If we look at the Spyder interface, we can find a number of different panes on the right side (with the default layout), such as *Help*, *Variable Explorer*, *Plots*, *Files* and *History*." msgstr "" #: ../../workshops/plugin-development.rst:126 -msgid "" -"Each of these panes is a ``SpyderDockablePlugin`` that offers an *Undock*" -" option by clicking the hamburger menu button in the upper right corner." +msgid "Each of these panes is a ``SpyderDockablePlugin`` that offers an *Undock* option by clicking the hamburger menu button in the upper right corner." msgstr "" #: ../../workshops/plugin-development.rst:128 -msgid "" -"These plugins can also be hidden or shown via their entry in the *View > " -"Panes* menu, or using its corresponding keyboard shortcut displayed " -"there." +msgid "These plugins can also be hidden or shown via their entry in the *View > Panes* menu, or using its corresponding keyboard shortcut displayed there." +msgstr "" + +#: ../../workshops/plugin-development.rst:120 +msgid "``SpyderPluginV2``" msgstr "" #: ../../workshops/plugin-development.rst:132 -msgid "" -"High-level interface elements that do not offer an undocking option are " -"basically instances of ``SpyderPluginV2``. These are typically used to " -"handle more abstract functionality." +msgid "High-level interface elements that do not offer an undocking option are basically instances of ``SpyderPluginV2``. These are typically used to handle more abstract functionality." msgstr "" #: ../../workshops/plugin-development.rst:134 -msgid "" -"Examples of this are the *appearance* and *layout* plugins that manage " -"Spyder's code color schemes and window layouts respectively." +msgid "Examples of this are the *appearance* and *layout* plugins that manage Spyder's code color schemes and window layouts respectively." msgstr "" #: ../../workshops/plugin-development.rst:136 -msgid "" -"Other examples of this type of plugins are the *main menu* and keyboard " -"*shortcuts*. Some graphical elements, such as the main toolbar and the " -"status bar are also instances of the ``SpyderPluginV2`` class." +msgid "Other examples of this type of plugins are the *main menu* and keyboard *shortcuts*. Some graphical elements, such as the main toolbar and the status bar are also instances of the ``SpyderPluginV2`` class." msgstr "" #: ../../workshops/plugin-development.rst:142 @@ -1786,23 +1292,19 @@ msgid "What will we do?" msgstr "" #: ../../workshops/plugin-development.rst:144 -msgid "" -"Our practical work will consist in the implementation of the Pomodoro " -"technique for time management in the Spyder interface." +msgid "Our practical work will consist in the implementation of the Pomodoro technique for time management in the Spyder interface." +msgstr "" + +#: ../../workshops/plugin-development.rst:146 +msgid "Description of the pomodoro technique." msgstr "" #: ../../workshops/plugin-development.rst:151 -msgid "" -"The `Pomodoro Technique`_, designed by Francesco Cirillo, is a time " -"management practice used to increase your focus and productivity when " -"trying to complete assignments or meet deadlines. Choosing to use a " -"Pomodoro Timer can help to give a task your full, undivided attention." +msgid "The `Pomodoro Technique`_, designed by Francesco Cirillo, is a time management practice used to increase your focus and productivity when trying to complete assignments or meet deadlines. Choosing to use a Pomodoro Timer can help to give a task your full, undivided attention." msgstr "" #: ../../workshops/plugin-development.rst:154 -msgid "" -"The typical process of the Pomodoro Technique consists of the following " -"six steps:" +msgid "The typical process of the Pomodoro Technique consists of the following six steps:" msgstr "" #: ../../workshops/plugin-development.rst:157 @@ -1818,22 +1320,15 @@ msgid "Work only on that task until the timer ends." msgstr "" #: ../../workshops/plugin-development.rst:160 -msgid "" -"When the timer rings, put a checkmark on a piece of paper, this is called" -" \"a pomodoro\"." +msgid "When the timer rings, put a checkmark on a piece of paper, this is called \"a pomodoro\"." msgstr "" #: ../../workshops/plugin-development.rst:161 -msgid "" -"If you have less than 3 checkmarks take a short break (by default, 5 " -"minutes), and return to step 2." +msgid "If you have less than 3 checkmarks take a short break (by default, 5 minutes), and return to step 2." msgstr "" #: ../../workshops/plugin-development.rst:162 -msgid "" -"When you have completed four Pomodoro cycles, you deserve a longer break " -"(our default is 15 minutes). Checkmarks are reset to zero, go back to " -"step 1." +msgid "When you have completed four Pomodoro cycles, you deserve a longer break (our default is 15 minutes). Checkmarks are reset to zero, go back to step 1." msgstr "" #: ../../workshops/plugin-development.rst:168 @@ -1841,39 +1336,31 @@ msgid "Steps" msgstr "" #: ../../workshops/plugin-development.rst:170 -msgid "" -"These are the general steps that we will be following throughout this " -"workshop:" +msgid "These are the general steps that we will be following throughout this workshop:" msgstr "" #: ../../workshops/plugin-development.rst:172 -msgid "" -"Select the most suitable plugin type and create its initial structure " -"using `cookiecutter`_." +msgid "Select the most suitable plugin type and create its initial structure using `cookiecutter`_." msgstr "" #: ../../workshops/plugin-development.rst:173 -msgid "" -"Install the plugin in development mode in the virtual environment from " -"which we run Spyder." +msgid "Install the plugin in development mode in the virtual environment from which we run Spyder." msgstr "" #: ../../workshops/plugin-development.rst:174 -msgid "" -"Implement the functionality of our plugin using the Spyder classes and " -"following the guidelines indicated in the plugin structure." +msgid "Implement the functionality of our plugin using the Spyder classes and following the guidelines indicated in the plugin structure." msgstr "" #: ../../workshops/plugin-development.rst:175 -msgid "" -"Build a configuration page for our plugin, which would appear in Tools > " -"Preferences." +msgid "Build a configuration page for our plugin, which would appear in Tools > Preferences." msgstr "" +#: ../../workshops/plugin-development.rst:177 #: ../../workshops/plugin-development.rst:180 msgid "Location of Spyder Pomodoro Timer widgets in Spyder." msgstr "" +#: ../../workshops/plugin-development.rst:182 #: ../../workshops/plugin-development.rst:185 msgid "Spyder Pomodoro Timer in the preferences window." msgstr "" @@ -1895,23 +1382,15 @@ msgid "Status bar widget: to display the time for the current pomodoro interval. msgstr "" #: ../../workshops/plugin-development.rst:196 -msgid "" -"State: we have three activity states: *pomodoro*, *short-break* and " -"*long-break*. We can show a message (with `QMessageBox`_) to tell users " -"that the time to take a break has arrived." +msgid "State: we have three activity states: *pomodoro*, *short-break* and *long-break*. We can show a message (with `QMessageBox`_) to tell users that the time to take a break has arrived." msgstr "" #: ../../workshops/plugin-development.rst:197 -msgid "" -"Interactions: the user could use Start, Stop and Reset buttons to handle " -"the Pomodoro Timer. This can be implemented adding `QAction`_ instances " -"in a menu on the toolbar." +msgid "Interactions: the user could use Start, Stop and Reset buttons to handle the Pomodoro Timer. This can be implemented adding `QAction`_ instances in a menu on the toolbar." msgstr "" #: ../../workshops/plugin-development.rst:199 -msgid "" -"Tasks Logger - Counter: We need a variable to count the number of " -"pomodoros completed." +msgid "Tasks Logger - Counter: We need a variable to count the number of pomodoros completed." msgstr "" #: ../../workshops/plugin-development.rst:202 @@ -1919,18 +1398,11 @@ msgid "Notifications" msgstr "" #: ../../workshops/plugin-development.rst:204 -msgid "" -"Dialog: Each time a pomodoro or break interval is completed, a message " -"should appear to prompt the user to start working on a task or take a " -"break." +msgid "Dialog: Each time a pomodoro or break interval is completed, a message should appear to prompt the user to start working on a task or take a break." msgstr "" #: ../../workshops/plugin-development.rst:206 -msgid "" -"When working on a plugin for any system, we must check the data " -"structures and functions available in that system that can facilitate our" -" development. This involves spending considerable time understanding its " -"inner workings." +msgid "When working on a plugin for any system, we must check the data structures and functions available in that system that can facilitate our development. This involves spending considerable time understanding its inner workings." msgstr "" #: ../../workshops/plugin-development.rst:219 @@ -1938,18 +1410,15 @@ msgid "Set up a development environment" msgstr "" #: ../../workshops/plugin-development.rst:221 -msgid "" -"In principle, we could use any Spyder installed within a `conda " -"environment`_ according to the instructions given in the `installation " -"guide`_." +msgid "In principle, we could use any Spyder installed within a `conda environment`_ according to the instructions given in the `installation guide`_." msgstr "" #: ../../workshops/plugin-development.rst:223 -msgid "" -"However, if you use a working environment that has other dependencies and" -" you want to keep your plugin development independent of them, it is " -"recommended to create a new environment which only has Spyder with the " -"minimum dependencies needed for your plugin." +msgid "However, if you use a working environment that has other dependencies and you want to keep your plugin development independent of them, it is recommended to create a new environment which only has Spyder with the minimum dependencies needed for your plugin." +msgstr "" + +#: ../../workshops/plugin-development.rst:225 +msgid "Spyder development environment." msgstr "" #: ../../workshops/plugin-development.rst:228 @@ -1957,30 +1426,19 @@ msgid "We can install it in the following way:" msgstr "" #: ../../workshops/plugin-development.rst:240 -msgid "" -"`Anaconda Individual Edition`_ is a Python distribution for data science " -"and machine learning to be used in a single machine." +msgid "`Anaconda Individual Edition`_ is a Python distribution for data science and machine learning to be used in a single machine." msgstr "" #: ../../workshops/plugin-development.rst:241 -msgid "" -"`Conda`_ is an Anaconda tool that manages virtual environments and their " -"packages." +msgid "`Conda`_ is an Anaconda tool that manages virtual environments and their packages." msgstr "" #: ../../workshops/plugin-development.rst:242 -msgid "" -"Conda can work with *channels* that allow the use of packages that are " -"not part of the official distribution. The most important channel is " -"`conda-forge`_, where a more extensive and updated list of packages than " -"those offered by Anaconda Individual Edition are maintained." +msgid "Conda can work with *channels* that allow the use of packages that are not part of the official distribution. The most important channel is `conda-forge`_, where a more extensive and updated list of packages than those offered by Anaconda Individual Edition are maintained." msgstr "" #: ../../workshops/plugin-development.rst:243 -msgid "" -"Finally, `mamba`_, is an optimized implementation of conda's package " -"management features, that resolves dependencies and installs packages " -"much faster than conda." +msgid "Finally, `mamba`_, is an optimized implementation of conda's package management features, that resolves dependencies and installs packages much faster than conda." msgstr "" #: ../../workshops/plugin-development.rst:256 @@ -1988,11 +1446,11 @@ msgid "Create a repository" msgstr "" #: ../../workshops/plugin-development.rst:258 -msgid "" -"Now that we have our local virtual environment, it is good practice to " -"manage our source code with a version control system, and the most widely" -" used web service for this purpose is currently Github. Here you can " -"find, for example, the Spyder and Python repositories." +msgid "Now that we have our local virtual environment, it is good practice to manage our source code with a version control system, and the most widely used web service for this purpose is currently Github. Here you can find, for example, the Spyder and Python repositories." +msgstr "" + +#: ../../workshops/plugin-development.rst:260 +msgid "Git and Github repository concepts." msgstr "" #: ../../workshops/plugin-development.rst:263 @@ -2004,16 +1462,11 @@ msgid "Log in to your Github account." msgstr "" #: ../../workshops/plugin-development.rst:266 -msgid "" -"Click on the \"New repository\" option in the \"+\" menu at the top right" -" next to your profile picture." +msgid "Click on the \"New repository\" option in the \"+\" menu at the top right next to your profile picture." msgstr "" #: ../../workshops/plugin-development.rst:267 -msgid "" -"A dialog will appear where you can insert the repository name and some " -"basic options, e.g. to initialize the repository with a README or license" -" files." +msgid "A dialog will appear where you can insert the repository name and some basic options, e.g. to initialize the repository with a README or license files." msgstr "" #: ../../workshops/plugin-development.rst:268 @@ -2021,24 +1474,15 @@ msgid "Click the “Create repository” button." msgstr "" #: ../../workshops/plugin-development.rst:269 -msgid "" -"In the main window of the recently created repository, click on the green" -" \"Code\" button an copy the clone link." +msgid "In the main window of the recently created repository, click on the green \"Code\" button an copy the clone link." msgstr "" #: ../../workshops/plugin-development.rst:270 -msgid "" -"In your local command line run ``$ git clone [repo-link]``. You must have" -" git installed and configured on your computer. If you don't have " -"experience using git we recommend The Carpentries workshop `Version " -"control with git`_." +msgid "In your local command line run ``$ git clone [repo-link]``. You must have git installed and configured on your computer. If you don't have experience using git we recommend The Carpentries workshop `Version control with git`_." msgstr "" #: ../../workshops/plugin-development.rst:272 -msgid "" -"A detailed description of `repository creation`_ could be found in the " -"official Github documentation, and a `hello world`_ tutorial with basic " -"git operations from the Github interface." +msgid "A detailed description of `repository creation`_ could be found in the official Github documentation, and a `hello world`_ tutorial with basic git operations from the Github interface." msgstr "" #: ../../workshops/plugin-development.rst:282 @@ -2046,24 +1490,19 @@ msgid "Let's get started" msgstr "" #: ../../workshops/plugin-development.rst:284 -msgid "" -"We already have a git repository and a virtual environment where Spyder 5" -" is installed." +msgid "We already have a git repository and a virtual environment where Spyder 5 is installed." msgstr "" #: ../../workshops/plugin-development.rst:286 -msgid "" -"Let's activate our environment and go into the local folder of our " -"repository." +msgid "Let's activate our environment and go into the local folder of our repository." msgstr "" #: ../../workshops/plugin-development.rst:293 -msgid "" -"Then we need to use ``cookiecutter`` to create the initial structure of " -"our plugin. `cookiecutter`_ is a tool made in Python specifically " -"designed to create project templates. We have developed one of these " -"templates to generate the basic structure of a plugin, it can be found " -"at: https://github.com/spyder-ide/spyder5-plugin-cookiecutter" +msgid "Then we need to use ``cookiecutter`` to create the initial structure of our plugin. `cookiecutter`_ is a tool made in Python specifically designed to create project templates. We have developed one of these templates to generate the basic structure of a plugin, it can be found at: https://github.com/spyder-ide/spyder5-plugin-cookiecutter" +msgstr "" + +#: ../../workshops/plugin-development.rst:298 +msgid "Folder structure of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:301 @@ -2075,9 +1514,7 @@ msgid "The plugin structure" msgstr "" #: ../../workshops/plugin-development.rst:334 -msgid "" -"After ``cookicutter`` finishes its job, you'll get the following tree " -"structure in your repository" +msgid "After ``cookicutter`` finishes its job, you'll get the following tree structure in your repository" msgstr "" #: ../../workshops/plugin-development.rst:356 @@ -2089,19 +1526,11 @@ msgid "The Makefile, which has several useful commands:" msgstr "" #: ../../workshops/plugin-development.rst:375 -msgid "" -"``setup.py``, which helps you to install, package and distribute your " -"plugin with ``setuptools``, the standard for distributing Python Modules." -" On this file the ``entry_points`` parameter of ``setup`` is quite " -"important, as it is the one that allows Spyder to identify this package " -"as a plugin, and to know how to access its functionalities." +msgid "``setup.py``, which helps you to install, package and distribute your plugin with ``setuptools``, the standard for distributing Python Modules. On this file the ``entry_points`` parameter of ``setup`` is quite important, as it is the one that allows Spyder to identify this package as a plugin, and to know how to access its functionalities." msgstr "" #: ../../workshops/plugin-development.rst:380 -msgid "" -"The ``spyder-pomodoro-timer`` folder has the name you introduced when " -"running ``cookiecutter``. Inside this you'll see a folder called " -"``spyder``, where we will place the code of our plugin." +msgid "The ``spyder-pomodoro-timer`` folder has the name you introduced when running ``cookiecutter``. Inside this you'll see a folder called ``spyder``, where we will place the code of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:382 @@ -2109,56 +1538,31 @@ msgid "In the ``spyder`` directory you'll find the following files:" msgstr "" #: ../../workshops/plugin-development.rst:384 -msgid "" -"``api.py``: where the functionality of the plugin is exposed to the rest " -"of Spyder. That would allow additional functionality to be added from " -"other plugins." +msgid "``api.py``: where the functionality of the plugin is exposed to the rest of Spyder. That would allow additional functionality to be added from other plugins." msgstr "" #: ../../workshops/plugin-development.rst:386 -msgid "" -"``plugin.py``: is the core of the plugin. Depending on the type of plugin" -" we created, here you'll see an instance of ``SpyderDockablePlugin`` or " -"``SpyderPluginV2``." +msgid "``plugin.py``: is the core of the plugin. Depending on the type of plugin we created, here you'll see an instance of ``SpyderDockablePlugin`` or ``SpyderPluginV2``." msgstr "" #: ../../workshops/plugin-development.rst:388 -msgid "" -"If it is a ``SpyderPluginV2`` you should set a constant class named " -"``CONTAINER_CLASS`` with an instance of ``PluginMainContainer``." +msgid "If it is a ``SpyderPluginV2`` you should set a constant class named ``CONTAINER_CLASS`` with an instance of ``PluginMainContainer``." msgstr "" #: ../../workshops/plugin-development.rst:389 -msgid "" -"If it is a ``SpyderDockablePlugin`` you should set a constant class named" -" ``WIDGET_CLASS`` with an instance of ``PluginMainWidget``." +msgid "If it is a ``SpyderDockablePlugin`` you should set a constant class named ``WIDGET_CLASS`` with an instance of ``PluginMainWidget``." msgstr "" #: ../../workshops/plugin-development.rst:391 -msgid "" -"``container.py``: only used for ``SpyderPluginV2`` plugins. This file " -"contains an instance of ``PluginMainContainer`` that holds a reference to" -" all graphical elements (or widgets) that the plugin is going to add to " -"the interface. This is necessary because Qt requires widgets to be " -"children of other widgets before using them (otherwise they appear as " -"floating windows). Since ``SpyderPluginV2`` is not a widget, we need a " -"data structure (i.e. the container) that is a widget for that." +msgid "``container.py``: only used for ``SpyderPluginV2`` plugins. This file contains an instance of ``PluginMainContainer`` that holds a reference to all graphical elements (or widgets) that the plugin is going to add to the interface. This is necessary because Qt requires widgets to be children of other widgets before using them (otherwise they appear as floating windows). Since ``SpyderPluginV2`` is not a widget, we need a data structure (i.e. the container) that is a widget for that." msgstr "" #: ../../workshops/plugin-development.rst:393 -msgid "" -"``widgets.py``: in this file we will add the graphical components of our " -"plugin. If it is of type ``SpyderPluginV2`` and it does not have widgets," -" then it is not necessary. We can also place here the instance of " -"``PluginMainWidget`` necessary for ``SpyderDockablePlugin``, if we are " -"developing that kind of plugin." +msgid "``widgets.py``: in this file we will add the graphical components of our plugin. If it is of type ``SpyderPluginV2`` and it does not have widgets, then it is not necessary. We can also place here the instance of ``PluginMainWidget`` necessary for ``SpyderDockablePlugin``, if we are developing that kind of plugin." msgstr "" #: ../../workshops/plugin-development.rst:396 -msgid "" -"``confpage.py``: this is where you specify the configuration page that " -"will be displayed in ``Preferences``, so that the user can adjust the " -"options of our plugin." +msgid "``confpage.py``: this is where you specify the configuration page that will be displayed in ``Preferences``, so that the user can adjust the options of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:402 @@ -2166,10 +1570,7 @@ msgid "Building our first plugin" msgstr "" #: ../../workshops/plugin-development.rst:404 -msgid "" -"From now on we will be building the plugin step by step. In the `spyder " -"pomodoro timer repository`_ you will find the final version of the code " -"for you to take a look at it, in case we are missing any detail." +msgid "From now on we will be building the plugin step by step. In the `spyder pomodoro timer repository`_ you will find the final version of the code for you to take a look at it, in case we are missing any detail." msgstr "" #: ../../workshops/plugin-development.rst:409 @@ -2178,57 +1579,35 @@ msgid "Widgets" msgstr "" #: ../../workshops/plugin-development.rst:411 -msgid "" -"The best way to start building our plugin is by implementing its " -"graphical components first in ``widgets.py``" +msgid "The best way to start building our plugin is by implementing its graphical components first in ``widgets.py``" msgstr "" #: ../../workshops/plugin-development.rst:413 -msgid "" -"Let's call the initial version, without any editing ``INITIAL``. In " -"`INITIAL`_, widgets.py is as follows:" +msgid "Let's call the initial version, without any editing ``INITIAL``. In `INITIAL`_, widgets.py is as follows:" msgstr "" #: ../../workshops/plugin-development.rst:431 -msgid "" -"The preset imports are a guide to what we will need in our plugin. The " -"``on_conf_change`` decorator will allow us to propagate the changes in " -"configuration. ``get_translation`` helps us to generate translation " -"strings for the plugin and ``SpyderWidgetMixin`` adds to any widget the " -"attributes and methods needed to integrate it with Spyder (icon, style, " -"translation, actions and extra options)." +msgid "The preset imports are a guide to what we will need in our plugin. The ``on_conf_change`` decorator will allow us to propagate the changes in configuration. ``get_translation`` helps us to generate translation strings for the plugin and ``SpyderWidgetMixin`` adds to any widget the attributes and methods needed to integrate it with Spyder (icon, style, translation, actions and extra options)." msgstr "" #: ../../workshops/plugin-development.rst:433 -msgid "" -"When taking a look at the Spyder ``api`` module, we can find that in " -"Spyder there are two types of predefined components for the status bar:" +msgid "When taking a look at the Spyder ``api`` module, we can find that in Spyder there are two types of predefined components for the status bar:" msgstr "" #: ../../workshops/plugin-development.rst:435 -msgid "" -"``StatusBarWidget``, a class derived from ``QWidget`` and " -"``SpyderWidgetMixin``, which contains an icon, a label and a spinner (to " -"show the plugin loading)." +msgid "``StatusBarWidget``, a class derived from ``QWidget`` and ``SpyderWidgetMixin``, which contains an icon, a label and a spinner (to show the plugin loading)." msgstr "" #: ../../workshops/plugin-development.rst:436 -msgid "" -"``BaseTimerStatus``, a class derived from ``StatusBarWidget`` with an " -"internal ``QTimer`` to periodically update its content." +msgid "``BaseTimerStatus``, a class derived from ``StatusBarWidget`` with an internal ``QTimer`` to periodically update its content." msgstr "" #: ../../workshops/plugin-development.rst:440 -msgid "" -"Below, we will be indicating links in github with the diffs between the " -"tags, this as an aid to check the progressive changes that will be made " -"in the code." +msgid "Below, we will be indicating links in github with the diffs between the tags, this as an aid to check the progressive changes that will be made in the code." msgstr "" #: ../../workshops/plugin-development.rst:442 -msgid "" -"The first version that we are going to reach after the first editions " -"will be called ``HELLO WORLD``." +msgid "The first version that we are going to reach after the first editions will be called ``HELLO WORLD``." msgstr "" #: ../../workshops/plugin-development.rst:444 @@ -2236,9 +1615,7 @@ msgid "`INITIAL -> HELLO WORLD widgets.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:448 -msgid "" -"Since we want a widget that shows the pomodoro countdown and is " -"periodically updated, we will use a ``BaseTimerStatus`` instance." +msgid "Since we want a widget that shows the pomodoro countdown and is periodically updated, we will use a ``BaseTimerStatus`` instance." msgstr "" #: ../../workshops/plugin-development.rst:450 @@ -2258,34 +1635,27 @@ msgid "With that, we can write our first widget like this" msgstr "" #: ../../workshops/plugin-development.rst:493 -msgid "" -"Spyder needs ``ID`` to be defined for ``BaseTimerStatus``. Its " -"constructor calls the parent class constructor and initializes the label " -"with ``value``." +msgid "Spyder needs ``ID`` to be defined for ``BaseTimerStatus``. Its constructor calls the parent class constructor and initializes the label with ``value``." msgstr "" #: ../../workshops/plugin-development.rst:495 -msgid "" -"We add a tooltip to verify the presence of our widget. Since Spyder uses " -"``qtawesome`` (another of our projects that eases the incorporation of " -"iconic fonts into PyQt applications), we can select an appropriate icon " -"by running the ``qta-browser`` command on a terminal." +msgid "We add a tooltip to verify the presence of our widget. Since Spyder uses ``qtawesome`` (another of our projects that eases the incorporation of iconic fonts into PyQt applications), we can select an appropriate icon by running the ``qta-browser`` command on a terminal." msgstr "" #: ../../workshops/plugin-development.rst:501 msgid "From here we can select and copy the name of the icon of our preference." msgstr "" +#: ../../workshops/plugin-development.rst:503 +msgid "qta browser dialog" +msgstr "" + #: ../../workshops/plugin-development.rst:506 -msgid "" -"To finish the implementation of our widget, we need to add the following " -"method:" +msgid "To finish the implementation of our widget, we need to add the following method:" msgstr "" #: ../../workshops/plugin-development.rst:516 -msgid "" -"``BaseTimerStatus`` requires this method to be implemented to update its " -"content every time it is requested by the internal timer." +msgid "``BaseTimerStatus`` requires this method to be implemented to update its content every time it is requested by the internal timer." msgstr "" #: ../../workshops/plugin-development.rst:520 @@ -2293,12 +1663,7 @@ msgid "The container" msgstr "" #: ../../workshops/plugin-development.rst:522 -msgid "" -"The next step in the development of our plugin is to create an instance " -"of the widget we wrote above, so we can add it to Spyder's status bar. " -"For that, we need to use a container. Due to Qt specifics, we need an " -"instance of ``QWidget`` (the container) to be the parent of all other " -"widgets part of our plugin (as mentioned above)." +msgid "The next step in the development of our plugin is to create an instance of the widget we wrote above, so we can add it to Spyder's status bar. For that, we need to use a container. Due to Qt specifics, we need an instance of ``QWidget`` (the container) to be the parent of all other widgets part of our plugin (as mentioned above)." msgstr "" #: ../../workshops/plugin-development.rst:524 @@ -2310,15 +1675,11 @@ msgid "`INITIAL -> HELLO WORLD container.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:551 -msgid "" -"In this case ``SpyderPomodoroTimerContainer`` is already defined, and we " -"must implement the ``setup`` and ``update_actions`` methods." +msgid "In this case ``SpyderPomodoroTimerContainer`` is already defined, and we must implement the ``setup`` and ``update_actions`` methods." msgstr "" #: ../../workshops/plugin-development.rst:553 -msgid "" -"Now we are going to add the widget created earlier to the container. To " -"do so, first we need to import the widget." +msgid "Now we are going to add the widget created earlier to the container. To do so, first we need to import the widget." msgstr "" #: ../../workshops/plugin-development.rst:560 @@ -2330,10 +1691,7 @@ msgid "Plugin" msgstr "" #: ../../workshops/plugin-development.rst:572 -msgid "" -"Finally, we define our plugin so that it is registered within Spyder. The" -" `INITIAL`_ version (i.e. the one created by cookiecutter) for " -"``plugin.py`` is:" +msgid "Finally, we define our plugin so that it is registered within Spyder. The `INITIAL`_ version (i.e. the one created by cookiecutter) for ``plugin.py`` is:" msgstr "" #: ../../workshops/plugin-development.rst:575 @@ -2349,10 +1707,7 @@ msgid "`INITIAL -> HELLO WORLD plugin.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:637 -msgid "" -"First, we need to declare the dependencies of our plugin, by defining the" -" ``REQUIRES`` class constant. Since we're going to add a status bar " -"widget, we require the ``StatusBar`` plugin, as shown below." +msgid "First, we need to declare the dependencies of our plugin, by defining the ``REQUIRES`` class constant. Since we're going to add a status bar widget, we require the ``StatusBar`` plugin, as shown below." msgstr "" #: ../../workshops/plugin-development.rst:643 @@ -2370,9 +1725,7 @@ msgid "by" msgstr "" #: ../../workshops/plugin-development.rst:676 -msgid "" -"Due to recent changes to the Spyder API, we need to add to the spyder " -"imports" +msgid "Due to recent changes to the Spyder API, we need to add to the spyder imports" msgstr "" #: ../../workshops/plugin-development.rst:683 @@ -2380,9 +1733,7 @@ msgid "And add the following after the ``on_initialize`` method:" msgstr "" #: ../../workshops/plugin-development.rst:693 -msgid "" -"With these changes, Spyder will be aware of the presence of our plugin, " -"and that this plugin adds a new widget to the status bar." +msgid "With these changes, Spyder will be aware of the presence of our plugin, and that this plugin adds a new widget to the status bar." msgstr "" #: ../../workshops/plugin-development.rst:695 @@ -2390,21 +1741,19 @@ msgid "Finally, we add the following method to our plugin:" msgstr "" #: ../../workshops/plugin-development.rst:704 -msgid "" -"In this way, ``SpyderPomodoroTimer`` can access ``pomodoro_timer_status``" -" of ``SpyderPomodoroTimerContainer`` as if it were its own property." +msgid "In this way, ``SpyderPomodoroTimer`` can access ``pomodoro_timer_status`` of ``SpyderPomodoroTimerContainer`` as if it were its own property." msgstr "" #: ../../workshops/plugin-development.rst:706 msgid "In summary, we did the following:" msgstr "" +#: ../../workshops/plugin-development.rst:708 +msgid "Basic structure of Pomodoro Timer Spyder plugin." +msgstr "" + #: ../../workshops/plugin-development.rst:711 -msgid "" -"We created a widget, then we added it to the container, which is " -"registered in the plugin through the ``CONTAINER_CLASS`` constant. In the" -" plugin, we accessed the instance of that widget and added it to the " -"status bar." +msgid "We created a widget, then we added it to the container, which is registered in the plugin through the ``CONTAINER_CLASS`` constant. In the plugin, we accessed the instance of that widget and added it to the status bar." msgstr "" #: ../../workshops/plugin-development.rst:717 @@ -2416,9 +1765,7 @@ msgid "Now it is time to see how our plugin looks in the Spyder interface." msgstr "" #: ../../workshops/plugin-development.rst:721 -msgid "" -"**From the root folder of our plugin**, we activate the environment where" -" Spyder is installed, and run:" +msgid "**From the root folder of our plugin**, we activate the environment where Spyder is installed, and run:" msgstr "" #: ../../workshops/plugin-development.rst:729 @@ -2426,16 +1773,15 @@ msgid "Now we can see two outputs. The first one is shown in the command line:" msgstr "" #: ../../workshops/plugin-development.rst:736 -msgid "" -"And in Spyder you'll see our plugin in the status bar with the tooltip " -"\"I am the Pomodoro tooltip\"." +msgid "And in Spyder you'll see our plugin in the status bar with the tooltip \"I am the Pomodoro tooltip\"." +msgstr "" + +#: ../../workshops/plugin-development.rst:738 +msgid "First version of our plugin" msgstr "" #: ../../workshops/plugin-development.rst:741 -msgid "" -"Keep in mind that every time we make a change to our code, it is " -"necessary to restart Spyder so that the plugin is reloaded and we can " -"check the changes." +msgid "Keep in mind that every time we make a change to our code, it is necessary to restart Spyder so that the plugin is reloaded and we can check the changes." msgstr "" #: ../../workshops/plugin-development.rst:747 @@ -2443,12 +1789,7 @@ msgid "Enhancing our plugin" msgstr "" #: ../../workshops/plugin-development.rst:749 -msgid "" -"From now on we are going to go into details of how things are implemented" -" in Qt. So in case you have any doubts, the Qt documentation will be your" -" best guide. We created an annex to this workshop that quickly explains " -"way the fundamental concepts of Qt for those in a hurry: :ref:`qt-" -"fundamentals`" +msgid "From now on we are going to go into details of how things are implemented in Qt. So in case you have any doubts, the Qt documentation will be your best guide. We created an annex to this workshop that quickly explains way the fundamental concepts of Qt for those in a hurry: :ref:`qt-fundamentals`" msgstr "" #: ../../workshops/plugin-development.rst:754 @@ -2456,23 +1797,15 @@ msgid "Timer updates" msgstr "" #: ../../workshops/plugin-development.rst:756 -msgid "" -"The first problem with our plugin is that its pomodoro timer is not being" -" updated. To activate it we can use the ``QTimer`` in " -"``PomodoroTimerStatus``, which is present because it's an instance of " -"``BaseTimerStatus``." +msgid "The first problem with our plugin is that its pomodoro timer is not being updated. To activate it we can use the ``QTimer`` in ``PomodoroTimerStatus``, which is present because it's an instance of ``BaseTimerStatus``." msgstr "" #: ../../workshops/plugin-development.rst:758 -msgid "" -"The second version where the value in the status bar is updated is called" -" ``TIMER``." +msgid "The second version where the value in the status bar is updated is called ``TIMER``." msgstr "" #: ../../workshops/plugin-development.rst:760 -msgid "" -"Let's go back to ``widgets.py`` and add this constant below the import " -"lines (line 22)." +msgid "Let's go back to ``widgets.py`` and add this constant below the import lines (line 22)." msgstr "" #: ../../workshops/plugin-development.rst:762 @@ -2480,9 +1813,7 @@ msgid "`HELLO WORLD -> TIMER widgets.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:774 -msgid "" -"``POMODORO_DEFAULT`` is to set the pomodoro time limit in milliseconds, " -"and ``INTERVAL`` to the timer update rate." +msgid "``POMODORO_DEFAULT`` is to set the pomodoro time limit in milliseconds, and ``INTERVAL`` to the timer update rate." msgstr "" #: ../../workshops/plugin-development.rst:776 @@ -2490,22 +1821,11 @@ msgid "Now, in the ``__init__`` method of ``PomodoroTimerStatus`` we need to add msgstr "" #: ../../workshops/plugin-development.rst:788 -msgid "" -"Up to this point, we created a default value (``POMODORO_DEFAULT``) for " -"the timer duration during pomodoros; we added it to the " -"``pomodoro_limit`` attribute to be able to configure it; and with that " -"value we initialized the ``countdown`` attribute that will be modified " -"over time. As for the update interval of the timer, we set it to to the " -"value of ``INTERVAL``, which corresponds to 1 second (one thousand " -"milliseconds)." +msgid "Up to this point, we created a default value (``POMODORO_DEFAULT``) for the timer duration during pomodoros; we added it to the ``pomodoro_limit`` attribute to be able to configure it; and with that value we initialized the ``countdown`` attribute that will be modified over time. As for the update interval of the timer, we set it to to the value of ``INTERVAL``, which corresponds to 1 second (one thousand milliseconds)." msgstr "" #: ../../workshops/plugin-development.rst:791 -msgid "" -"The function of ``self.timer`` is to update our timer periodically. This " -"is done through the method ``timeout.connect()``, to which we pass as " -"parameter the reference to the ``update_timer`` function that will " -"perform the required adjustments." +msgid "The function of ``self.timer`` is to update our timer periodically. This is done through the method ``timeout.connect()``, to which we pass as parameter the reference to the ``update_timer`` function that will perform the required adjustments." msgstr "" #: ../../workshops/plugin-development.rst:793 @@ -2513,26 +1833,23 @@ msgid "Now let's implement ``update_timer`` at the end of the file:" msgstr "" #: ../../workshops/plugin-development.rst:813 -msgid "" -"Here we rely on the ``display_time`` method that converts the current " -"``countdown`` value, which is measured in milliseconds, into a human-" -"readable format. And ``update_timer`` simply keeps updating the countdown" -" until it reaches zero." +msgid "Here we rely on the ``display_time`` method that converts the current ``countdown`` value, which is measured in milliseconds, into a human-readable format. And ``update_timer`` simply keeps updating the countdown until it reaches zero." msgstr "" #: ../../workshops/plugin-development.rst:815 msgid "If we run Spyder again we will find that our timer has come to life." msgstr "" +#: ../../workshops/plugin-development.rst:817 +msgid "Timer countdown working." +msgstr "" + #: ../../workshops/plugin-development.rst:824 msgid "Timer controls" msgstr "" #: ../../workshops/plugin-development.rst:826 -msgid "" -"Now we need a way to control our timer. We can achieve this by adding " -"some buttons to Spyder's toolbar, which will be useful to learn how to " -"work with toolbars, menus and actions in Spyder." +msgid "Now we need a way to control our timer. We can achieve this by adding some buttons to Spyder's toolbar, which will be useful to learn how to work with toolbars, menus and actions in Spyder." msgstr "" #: ../../workshops/plugin-development.rst:830 @@ -2540,9 +1857,7 @@ msgid "PomodoroTimerToolbar" msgstr "" #: ../../workshops/plugin-development.rst:832 -msgid "" -"The next version where actions are added to the toolbar is called " -"``ACTIONS``." +msgid "The next version where actions are added to the toolbar is called ``ACTIONS``." msgstr "" #: ../../workshops/plugin-development.rst:834 @@ -2550,37 +1865,23 @@ msgid "`TIMER -> ACTIONS widgets.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:838 -msgid "" -"Let's go back to ``widgets.py`` and import the Spyder application toolbar" -" class:" +msgid "Let's go back to ``widgets.py`` and import the Spyder application toolbar class:" msgstr "" #: ../../workshops/plugin-development.rst:844 -msgid "" -"And create an instance of it by adding the following code before the " -"definition of ``PomodoroTimerStatus``:" +msgid "And create an instance of it by adding the following code before the definition of ``PomodoroTimerStatus``:" msgstr "" #: ../../workshops/plugin-development.rst:853 -msgid "" -"As you can see, this statement is very simple. It only needs to declare " -"an ``ID``, that serves to identify our toolabr among the rest." +msgid "As you can see, this statement is very simple. It only needs to declare an ``ID``, that serves to identify our toolabr among the rest." msgstr "" #: ../../workshops/plugin-development.rst:855 -msgid "" -"It is possible to include other Qt widgets in our toolbar, but in this " -"case it's better to use the appropriate Spyder methods for that in order " -"to maintain their relationship with the rest of the application. In other" -" words, as long as the widget you need exists in ``spyder.api.widgets``, " -"use it!" +msgid "It is possible to include other Qt widgets in our toolbar, but in this case it's better to use the appropriate Spyder methods for that in order to maintain their relationship with the rest of the application. In other words, as long as the widget you need exists in ``spyder.api.widgets``, use it!" msgstr "" #: ../../workshops/plugin-development.rst:858 -msgid "" -"Next, we need to declare a boolean variable in our status widget to " -"indicate if the countdown is paused or not. For that, let's add the " -"following inside the ``__init__`` method of ``PomodoroTimerStatus``:" +msgid "Next, we need to declare a boolean variable in our status widget to indicate if the countdown is paused or not. For that, let's add the following inside the ``__init__`` method of ``PomodoroTimerStatus``:" msgstr "" #: ../../workshops/plugin-development.rst:864 @@ -2592,12 +1893,7 @@ msgid "Create the Pomodoro Toolbar" msgstr "" #: ../../workshops/plugin-development.rst:882 -msgid "" -"Now we are going to create a new section in our toolbar and associate " -"some functionality to it by means of actions. This particular information" -" is recommended to be included in the ``api.py`` file because this way we" -" can offer endpoints to the rest of Spyder and new plugins for tweaking " -"the behavior of our plugin." +msgid "Now we are going to create a new section in our toolbar and associate some functionality to it by means of actions. This particular information is recommended to be included in the ``api.py`` file because this way we can offer endpoints to the rest of Spyder and new plugins for tweaking the behavior of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:884 @@ -2609,19 +1905,11 @@ msgid "Let's add the following to the end of ``api.py``:" msgstr "" #: ../../workshops/plugin-development.rst:904 -msgid "" -"With these we are telling the rest of Spyder, and our own plugin, that we" -" are going to have a new toolbar section called \"pomodoro_timer\". This " -"section will consist of a button containing a menu (with a single section" -" \"main_section\") and actions identified as \"start_timer\", " -"\"pause_timer\" and \"stop_timer\", to start, pause and stop (resetting) " -"our timer, respectively." +msgid "With these we are telling the rest of Spyder, and our own plugin, that we are going to have a new toolbar section called \"pomodoro_timer\". This section will consist of a button containing a menu (with a single section \"main_section\") and actions identified as \"start_timer\", \"pause_timer\" and \"stop_timer\", to start, pause and stop (resetting) our timer, respectively." msgstr "" #: ../../workshops/plugin-development.rst:906 -msgid "" -"Note that these are simple class definitions with class constants, to " -"ease the encapsulation and exchange of this information in a simple way." +msgid "Note that these are simple class definitions with class constants, to ease the encapsulation and exchange of this information in a simple way." msgstr "" #: ../../workshops/plugin-development.rst:909 @@ -2633,25 +1921,15 @@ msgid "`TIMER -> ACTIONS container.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:915 -msgid "" -"Now let's go to ``container.py``, where we are going to implement the " -"behavior of our new toolbar and its actions. In this case, we are not " -"going to specify the internal behavior of our plugin, but the " -"relationship between its widgets and other areas of Spyder, so it is more" -" convenient to do it in the container." +msgid "Now let's go to ``container.py``, where we are going to implement the behavior of our new toolbar and its actions. In this case, we are not going to specify the internal behavior of our plugin, but the relationship between its widgets and other areas of Spyder, so it is more convenient to do it in the container." msgstr "" #: ../../workshops/plugin-development.rst:918 -msgid "" -"As we did with ``PomodoroTimerStatus``, we are going to use ``qtawesome``" -" icons for our actions. For this purpose, let's add at the beginning of " -"our imports:" +msgid "As we did with ``PomodoroTimerStatus``, we are going to use ``qtawesome`` icons for our actions. For this purpose, let's add at the beginning of our imports:" msgstr "" #: ../../workshops/plugin-development.rst:926 -msgid "" -"We also imported ``QToolButton`` because it will be used to set the " -"button that we will add in our toolbar." +msgid "We also imported ``QToolButton`` because it will be used to set the button that we will add in our toolbar." msgstr "" #: ../../workshops/plugin-development.rst:928 @@ -2659,39 +1937,27 @@ msgid "At the end of the Spyder imports we also need:" msgstr "" #: ../../workshops/plugin-development.rst:934 -msgid "" -"Now, let's include ``PomodoroTimerToolbar`` and the actions and sections " -"we just declared in ``api.py`` in our local imports:" +msgid "Now, let's include ``PomodoroTimerToolbar`` and the actions and sections we just declared in ``api.py`` in our local imports:" msgstr "" #: ../../workshops/plugin-development.rst:948 -msgid "" -"Next, we need to do following things in the ``setup`` method of " -"``SpyderPomodoroTimerContainer``." +msgid "Next, we need to do following things in the ``setup`` method of ``SpyderPomodoroTimerContainer``." msgstr "" #: ../../workshops/plugin-development.rst:950 -msgid "" -"The first one is to create an instance of the toolbar class we declared " -"earlier:" +msgid "The first one is to create an instance of the toolbar class we declared earlier:" msgstr "" #: ../../workshops/plugin-development.rst:957 -msgid "" -"The second one is to create the actions corresponding to Start, Pause and" -" Stop our pomodoro timer:" +msgid "The second one is to create the actions corresponding to Start, Pause and Stop our pomodoro timer:" msgstr "" #: ../../workshops/plugin-development.rst:986 -msgid "" -"The third one is to create the menu that will contain our actions and add" -" them to it." +msgid "The third one is to create the menu that will contain our actions and add them to it." msgstr "" #: ../../workshops/plugin-development.rst:1004 -msgid "" -"The fourth one is to create a button that will contain the menu and " -"configure it as ``PopupMode``, so that it is displayed when clicked." +msgid "The fourth one is to create a button that will contain the menu and configure it as ``PopupMode``, so that it is displayed when clicked." msgstr "" #: ../../workshops/plugin-development.rst:1017 @@ -2699,24 +1965,15 @@ msgid "And finally, the fifth one is to add the button to our toolbar:" msgstr "" #: ../../workshops/plugin-development.rst:1028 -msgid "" -"When creating the actions, we indicate by means of the ``triggered`` " -"parameter the methods to be executed when they are activated, i.e. when " -"the corresponding buttons on the toolbar are clicked." +msgid "When creating the actions, we indicate by means of the ``triggered`` parameter the methods to be executed when they are activated, i.e. when the corresponding buttons on the toolbar are clicked." msgstr "" #: ../../workshops/plugin-development.rst:1030 -msgid "" -"We can insert these methods at the end of the " -"``SpyderPomodoroTimerContainer`` declaration, in the section that our " -"cookiecutter template indicates as ``# --- Public API``." +msgid "We can insert these methods at the end of the ``SpyderPomodoroTimerContainer`` declaration, in the section that our cookiecutter template indicates as ``# --- Public API``." msgstr "" #: ../../workshops/plugin-development.rst:1050 -msgid "" -"These methods simply manipulate the ``pause`` field of " -"``pomodoro_timer_status``, and in the case of ``stop_pomodoro_timer`` the" -" countdown is restarted." +msgid "These methods simply manipulate the ``pause`` field of ``pomodoro_timer_status``, and in the case of ``stop_pomodoro_timer`` the countdown is restarted." msgstr "" #: ../../workshops/plugin-development.rst:1053 @@ -2728,9 +1985,7 @@ msgid "`TIMER -> ACTIONS plugin.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1059 -msgid "" -"A final mandatory step is to go to ``plugin.py`` and register this new " -"toolbar component." +msgid "A final mandatory step is to go to ``plugin.py`` and register this new toolbar component." msgstr "" #: ../../workshops/plugin-development.rst:1061 @@ -2738,9 +1993,7 @@ msgid "To do this, add ``Plugins.Toolbar`` to the plugin requirements:" msgstr "" #: ../../workshops/plugin-development.rst:1067 -msgid "" -"And use this plugin's API to add the toolbar we have created in the " -"container to Spyder's toolbar." +msgid "And use this plugin's API to add the toolbar we have created in the container to Spyder's toolbar." msgstr "" #: ../../workshops/plugin-development.rst:1078 @@ -2748,27 +2001,31 @@ msgid "Review the changes" msgstr "" #: ../../workshops/plugin-development.rst:1080 -msgid "" -"The first thing we can notice is that we already have the corresponding " -"buttons in the toolbar." +msgid "The first thing we can notice is that we already have the corresponding buttons in the toolbar." +msgstr "" + +#: ../../workshops/plugin-development.rst:1082 +msgid "Pomodoro timer toolbar buttons" msgstr "" #: ../../workshops/plugin-development.rst:1085 -msgid "" -"The strings that were entered as the ``tip`` parameter in the creation of" -" the actions are shown here as the buttons' tooltips." +msgid "The strings that were entered as the ``tip`` parameter in the creation of the actions are shown here as the buttons' tooltips." msgstr "" #: ../../workshops/plugin-development.rst:1087 -msgid "" -"Also, if we check the menu \"View > Toolbars\", we find that there is a " -"new entry there corresponding to our toolbar." +msgid "Also, if we check the menu \"View > Toolbars\", we find that there is a new entry there corresponding to our toolbar." +msgstr "" + +#: ../../workshops/plugin-development.rst:1089 +msgid "View > Toolbars menu with \"Pomodoro Timer Toolbar\" option." msgstr "" #: ../../workshops/plugin-development.rst:1093 -msgid "" -"Finally, let's check how the new Pomodoro Timer control buttons in the " -"toolbar interact with the component in the status bar." +msgid "Finally, let's check how the new Pomodoro Timer control buttons in the toolbar interact with the component in the status bar." +msgstr "" + +#: ../../workshops/plugin-development.rst:1095 +msgid "Interaction between the Pomodoro Timer toolbar and its status bar." msgstr "" #: ../../workshops/plugin-development.rst:1102 @@ -2776,9 +2033,7 @@ msgid "Add a Configuration Page" msgstr "" #: ../../workshops/plugin-development.rst:1104 -msgid "" -"Another feature of Spyder plugins is that they can have configurable " -"options that appear in Spyder's Preferences window." +msgid "Another feature of Spyder plugins is that they can have configurable options that appear in Spyder's Preferences window." msgstr "" #: ../../workshops/plugin-development.rst:1107 @@ -2786,16 +2041,11 @@ msgid "Configuration defaults" msgstr "" #: ../../workshops/plugin-development.rst:1109 -msgid "" -"The final version in which we add a configurable parameter will be called" -" ``CONFPAGE``." +msgid "The final version in which we add a configurable parameter will be called ``CONFPAGE``." msgstr "" #: ../../workshops/plugin-development.rst:1111 -msgid "" -"The first step is to define what options we want to offer to our users. " -"For this we must create a new file, which we can call ``conf.py``. In " -"this file we will write the following:" +msgid "The first step is to define what options we want to offer to our users. For this we must create a new file, which we can call ``conf.py``. In this file we will write the following:" msgstr "" #: ../../workshops/plugin-development.rst:1113 @@ -2803,26 +2053,15 @@ msgid "`ACTIONS -> CONFPAGE config.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1138 -msgid "" -"We must highlight the declaration of ``CONF_SECTION``, which is the " -"internal name of the section in Preferences corresponding to our plugin; " -"and the dictionary keys associated with ``CONF_DEFAULTS``. In this case, " -"we are indicating that ``pomodoro_limit`` is a configurable parameter " -"within the ``spyder_pomodoro_timer`` section." +msgid "We must highlight the declaration of ``CONF_SECTION``, which is the internal name of the section in Preferences corresponding to our plugin; and the dictionary keys associated with ``CONF_DEFAULTS``. In this case, we are indicating that ``pomodoro_limit`` is a configurable parameter within the ``spyder_pomodoro_timer`` section." msgstr "" #: ../../workshops/plugin-development.rst:1140 -msgid "" -"At the end of this file it is necessary to set another important " -"constant, ``CONF_VERSION``, which must be updated when adding, removing " -"or renaming configurable parameters in successive versions of the plugin." +msgid "At the end of this file it is necessary to set another important constant, ``CONF_VERSION``, which must be updated when adding, removing or renaming configurable parameters in successive versions of the plugin." msgstr "" #: ../../workshops/plugin-development.rst:1153 -msgid "" -"Note that we are moving the definition of ``POMODORO_DEFAULT`` from " -"``widgets.py`` to ``conf.py``, since we now have a dedicated place for " -"default configuration values." +msgid "Note that we are moving the definition of ``POMODORO_DEFAULT`` from ``widgets.py`` to ``conf.py``, since we now have a dedicated place for default configuration values." msgstr "" #: ../../workshops/plugin-development.rst:1156 @@ -2830,10 +2069,7 @@ msgid "Configuration page" msgstr "" #: ../../workshops/plugin-development.rst:1158 -msgid "" -"Now, we need to build the page that will appear in the Preferences " -"window. For this, we edit the ``confpage.py`` file generated by " -"cokkiecutter as follows:" +msgid "Now, we need to build the page that will appear in the Preferences window. For this, we edit the ``confpage.py`` file generated by cokkiecutter as follows:" msgstr "" #: ../../workshops/plugin-development.rst:1160 @@ -2841,20 +2077,11 @@ msgid "`ACTIONS -> CONFPAGE confpage.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1206 -msgid "" -"This mostly corresponds to the regular code for user interfaces based on " -"Qt widgets. In this case, our options section corresponds to a " -"``QGroupBox``, where the parameters are organized vertically using a " -"``QVBoxLayout``, and each parameter corresponds to a ``QGridLayout`` " -"where labels and inputs are distributed (in this case a ``QSpinBox``)." +msgid "This mostly corresponds to the regular code for user interfaces based on Qt widgets. In this case, our options section corresponds to a ``QGroupBox``, where the parameters are organized vertically using a ``QVBoxLayout``, and each parameter corresponds to a ``QGridLayout`` where labels and inputs are distributed (in this case a ``QSpinBox``)." msgstr "" #: ../../workshops/plugin-development.rst:1208 -msgid "" -"Configuration pages in Spyder provide some helper methods to facilitate " -"this work. For instance, ``create_spinbox`` allows to instantiate and " -"initialize in a single step the widgets corresponding prefix an suffix " -"labels together with the spinbox." +msgid "Configuration pages in Spyder provide some helper methods to facilitate this work. For instance, ``create_spinbox`` allows to instantiate and initialize in a single step the widgets corresponding prefix an suffix labels together with the spinbox." msgstr "" #: ../../workshops/plugin-development.rst:1211 @@ -2862,9 +2089,7 @@ msgid "Propagate configuration changes" msgstr "" #: ../../workshops/plugin-development.rst:1213 -msgid "" -"Since we moved all the configuration information to ``conf.py``, now we " -"have to import it from there into ``widgets.py``." +msgid "Since we moved all the configuration information to ``conf.py``, now we have to import it from there into ``widgets.py``." msgstr "" #: ../../workshops/plugin-development.rst:1215 @@ -2872,19 +2097,11 @@ msgid "`ACTIONS -> CONFPAGE widgets.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1228 -msgid "" -"Now we can access the configuration options from anywhere in our plugin " -"using the ``get_conf`` method. In this case we use it to access the value" -" of ``pomodoro_limit`` from the configuration instead of the constant " -"``POMODORO_DEFAULT``." +msgid "Now we can access the configuration options from anywhere in our plugin using the ``get_conf`` method. In this case we use it to access the value of ``pomodoro_limit`` from the configuration instead of the constant ``POMODORO_DEFAULT``." msgstr "" #: ../../workshops/plugin-development.rst:1236 -msgid "" -"Now we can add a method that updates our configurable parameter " -"``pomodoro_limit``. The ``@on_conf_change`` decorator is the one in " -"charge of capturing the signal that is generated when applying the change" -" of a specific option." +msgid "Now we can add a method that updates our configurable parameter ``pomodoro_limit``. The ``@on_conf_change`` decorator is the one in charge of capturing the signal that is generated when applying the change of a specific option." msgstr "" #: ../../workshops/plugin-development.rst:1247 @@ -2892,9 +2109,7 @@ msgid "Registering preferences" msgstr "" #: ../../workshops/plugin-development.rst:1249 -msgid "" -"Finally, it is necessary to activate the use of preferences in " -"``plugin.py``, by requiring the Preferences plugin" +msgid "Finally, it is necessary to activate the use of preferences in ``plugin.py``, by requiring the Preferences plugin" msgstr "" #: ../../workshops/plugin-development.rst:1251 @@ -2902,18 +2117,15 @@ msgid "`ACTIONS -> CONFPAGE plugin.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1262 -msgid "" -"and registering our plugin in a method with the decorator " -"``@on_plugin_available``." +msgid "and registering our plugin in a method with the decorator ``@on_plugin_available``." msgstr "" #: ../../workshops/plugin-development.rst:1271 -msgid "" -"Now we can access the Preferences window either from the toolbar or from " -"the \"Tools > Preferences\" menu. There we will find a section called " -"*Spyder Pomodoro Timer* and inside it is the *Pomodoro timer limit* " -"parameter. If we change that value, we will see how the corresponding " -"label in the status bar changes." +msgid "Now we can access the Preferences window either from the toolbar or from the \"Tools > Preferences\" menu. There we will find a section called *Spyder Pomodoro Timer* and inside it is the *Pomodoro timer limit* parameter. If we change that value, we will see how the corresponding label in the status bar changes." +msgstr "" + +#: ../../workshops/plugin-development.rst:1273 +msgid "Pomodoro Timer toolbar configuration page." msgstr "" #: ../../workshops/plugin-development.rst:1276 @@ -2925,18 +2137,15 @@ msgid "Publishing your plugin" msgstr "" #: ../../workshops/plugin-development.rst:1284 -msgid "" -"Since the recommended way to install Spyder is through conda, the obvious" -" choice would be to publish our plugin through a channel like conda-" -"forge, but this is a task that is beyond the scope of this workshop due " -"to its complexity." +msgid "Since the recommended way to install Spyder is through conda, the obvious choice would be to publish our plugin through a channel like conda-forge, but this is a task that is beyond the scope of this workshop due to its complexity." msgstr "" #: ../../workshops/plugin-development.rst:1286 -msgid "" -"However, the tools used to publish packages in conda are usually based on" -" the packages published in PyPI. So let's see how to publish our plugin " -"there." +msgid "However, the tools used to publish packages in conda are usually based on the packages published in PyPI. So let's see how to publish our plugin there." +msgstr "" + +#: ../../workshops/plugin-development.rst:1288 +msgid "Publish your plugin in PyPI." msgstr "" #: ../../workshops/plugin-development.rst:1293 @@ -2944,25 +2153,15 @@ msgid "PyPI and TestPyPI" msgstr "" #: ../../workshops/plugin-development.rst:1295 -msgid "" -"The first thing we have to do is to create an account on the `PyPI`_ and " -"`TestPyPI`_ websites. Although our package will be finally published in " -"PyPI, it is advisable to use TestPyPI to test that our package can be " -"published properly without generating additional load to the PyPI servers" -" or affecting their logs." +msgid "The first thing we have to do is to create an account on the `PyPI`_ and `TestPyPI`_ websites. Although our package will be finally published in PyPI, it is advisable to use TestPyPI to test that our package can be published properly without generating additional load to the PyPI servers or affecting their logs." msgstr "" #: ../../workshops/plugin-development.rst:1297 -msgid "" -"Next, we need edit the ``setup.py`` file at the root of our project with " -"our own data. Fortunately, cookiecutter created one for us." +msgid "Next, we need edit the ``setup.py`` file at the root of our project with our own data. Fortunately, cookiecutter created one for us." msgstr "" #: ../../workshops/plugin-development.rst:1299 -msgid "" -"To upload our package to PyPI we have to use a tool called `Twine`_ that " -"makes this task much easier. And we can install it in our conda " -"environment using:" +msgid "To upload our package to PyPI we have to use a tool called `Twine`_ that makes this task much easier. And we can install it in our conda environment using:" msgstr "" #: ../../workshops/plugin-development.rst:1306 @@ -2970,29 +2169,19 @@ msgid "Build and check the package" msgstr "" #: ../../workshops/plugin-development.rst:1308 -msgid "" -"Before publishing our plugin we must package it. To do it we must write " -"the following from the root folder of our project (where ``setup.py`` is " -"placed):" +msgid "Before publishing our plugin we must package it. To do it we must write the following from the root folder of our project (where ``setup.py`` is placed):" msgstr "" #: ../../workshops/plugin-development.rst:1314 -msgid "" -"After that we will see that the following files are generated in the " -"``dist`` folder:" +msgid "After that we will see that the following files are generated in the ``dist`` folder:" msgstr "" #: ../../workshops/plugin-development.rst:1323 -msgid "" -"On Linux and macOS we can check that the newly built distribution " -"packages contain the expected files by inspecting the contents of the " -"``tar`` file:" +msgid "On Linux and macOS we can check that the newly built distribution packages contain the expected files by inspecting the contents of the ``tar`` file:" msgstr "" #: ../../workshops/plugin-development.rst:1329 -msgid "" -"You can also use ``twine`` to run a check on the created files in " -"``dist``:" +msgid "You can also use ``twine`` to run a check on the created files in ``dist``:" msgstr "" #: ../../workshops/plugin-development.rst:1338 @@ -3000,52 +2189,31 @@ msgid "Upload to PyPI" msgstr "" #: ../../workshops/plugin-development.rst:1340 -msgid "" -"Now we can use twine to upload the distribution packages we have built. " -"First, we will upload them to TestPyPI to make sure everything works:" +msgid "Now we can use twine to upload the distribution packages we have built. First, we will upload them to TestPyPI to make sure everything works:" msgstr "" #: ../../workshops/plugin-development.rst:1346 -msgid "" -"This command will prompt you for the username and password with which you" -" registered in TestPyPI." +msgid "This command will prompt you for the username and password with which you registered in TestPyPI." msgstr "" #: ../../workshops/plugin-development.rst:1348 -msgid "" -"If we open https://test.pypi.org/project/spyder-pomodoro-timer/ in the " -"browser we will be able to see the package we have just published." +msgid "If we open https://test.pypi.org/project/spyder-pomodoro-timer/ in the browser we will be able to see the package we have just published." msgstr "" #: ../../workshops/plugin-development.rst:1350 -msgid "" -"There we'll see that some details are missing, like the package " -"description, and that our package is marked as ``Development Status " -"5-Stable``." +msgid "There we'll see that some details are missing, like the package description, and that our package is marked as ``Development Status 5-Stable``." msgstr "" #: ../../workshops/plugin-development.rst:1352 -msgid "" -"To fix the first one, we can follow the instructions in `Making a PyPI-" -"friendly README`_. Since we already have a README file, we simply add the" -" following lines to the beginning of our ``setup.py`` file:" +msgid "To fix the first one, we can follow the instructions in `Making a PyPI-friendly README`_. Since we already have a README file, we simply add the following lines to the beginning of our ``setup.py`` file:" msgstr "" #: ../../workshops/plugin-development.rst:1368 -msgid "" -"We can also change the classifiers of our package using the following " -"site as a guide: https://pypi.org/classifiers. Here we can simply copy " -"the classifiers we consider appropriate and then paste them into our " -"code. Specifically in ``setup.py``, within the list that enters as the " -"``classifier`` argument in the call to function ``setup``." +msgid "We can also change the classifiers of our package using the following site as a guide: https://pypi.org/classifiers. Here we can simply copy the classifiers we consider appropriate and then paste them into our code. Specifically in ``setup.py``, within the list that enters as the ``classifier`` argument in the call to function ``setup``." msgstr "" #: ../../workshops/plugin-development.rst:1371 -msgid "" -"With these changes, and by bumping our plugin's version in the " -"``__init__.py`` file inside the ``spyder_pomodoro_timer`` folder, we can " -"repeat the cycle of building a new version of our package, loading it " -"into TestPyPI for checking, and finally loading it into PyPI by using:" +msgid "With these changes, and by bumping our plugin's version in the ``__init__.py`` file inside the ``spyder_pomodoro_timer`` folder, we can repeat the cycle of building a new version of our package, loading it into TestPyPI for checking, and finally loading it into PyPI by using:" msgstr "" #: ../../workshops/plugin-development.rst:1377 @@ -3053,36 +2221,19 @@ msgid "And check the result in https://pypi.org/project/spyder-pomodoro-timer/" msgstr "" #: ../../workshops/plugin-development.rst:1379 -msgid "" -"Once this is done, anyone can install our plugin in their environments " -"simply by running:" +msgid "Once this is done, anyone can install our plugin in their environments simply by running:" msgstr "" #: ../../workshops/plugin-development.rst:1396 -msgid "" -"The possibility of making a tool extensible through plugins, extensions " -"or addons, as they are usually called, is a fundamental feature that " -"allows taking advantage of the talent of third-party developers to " -"respond to needs and enhancements that are beyond the scope of the " -"application's core development team." +msgid "The possibility of making a tool extensible through plugins, extensions or addons, as they are usually called, is a fundamental feature that allows taking advantage of the talent of third-party developers to respond to needs and enhancements that are beyond the scope of the application's core development team." msgstr "" #: ../../workshops/plugin-development.rst:1398 -msgid "" -"Similarly, a plugin-based system makes the application much easier to " -"maintain. Eventually, the ability to enable and disable plugins makes it " -"more adaptable to different use cases. For instance, at present it would " -"be inconceivable to think of a web browser that does not have extensions " -"to block advertising or organize links, even if those features don't come" -" by default on them." +msgid "Similarly, a plugin-based system makes the application much easier to maintain. Eventually, the ability to enable and disable plugins makes it more adaptable to different use cases. For instance, at present it would be inconceivable to think of a web browser that does not have extensions to block advertising or organize links, even if those features don't come by default on them." msgstr "" #: ../../workshops/plugin-development.rst:1400 -msgid "" -"In Spyder we have put special interest in consolidating an API that " -"allows the development of plugins in a consistent way. The main focus of " -"the development effort between versions 4 and 5 was in this direction and" -" we are at a key moment where we expect to capitalize on all this work." +msgid "In Spyder we have put special interest in consolidating an API that allows the development of plugins in a consistent way. The main focus of the development effort between versions 4 and 5 was in this direction and we are at a key moment where we expect to capitalize on all this work." msgstr "" #: ../../workshops/plugin-development.rst:1404 @@ -3126,15 +2277,11 @@ msgid "Add a menu with actions in the toolbar." msgstr "" #: ../../workshops/plugin-development.rst:1414 -msgid "" -"Add configuration options to our plugin and display them appear in the " -"Preferences window." +msgid "Add configuration options to our plugin and display them appear in the Preferences window." msgstr "" #: ../../workshops/plugin-development.rst:1415 -msgid "" -"Edit the description and classifiers of the installable package of our " -"plugin." +msgid "Edit the description and classifiers of the installable package of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:1416 @@ -3142,45 +2289,28 @@ msgid "Publish our plugin to TestPyPI and PyPI." msgstr "" #: ../../workshops/plugin-development.rst:1418 -msgid "" -"With these skills we hope to ease the way for you to develop your own " -"Spyder plugins." +msgid "With these skills we hope to ease the way for you to develop your own Spyder plugins." msgstr "" #: ../../workshops/plugin-development.rst:1420 -msgid "" -"If you have ideas for plugin development feel free to contact us through " -"the `Spyder-IDE`_ Github organization space." +msgid "If you have ideas for plugin development feel free to contact us through the `Spyder-IDE`_ Github organization space." msgstr "" #: ../../workshops/plugin-development.rst:1424 #: ../../workshops/scientific-computing.rst:776 -msgid "" -"If you are interested in an introduction to financial analysis with " -"Spyder, you can visit the workshop :doc:`Financial Data Analysis with " -"Spyder<../workshops/financial>`." +msgid "If you are interested in an introduction to financial analysis with Spyder, you can visit the workshop :doc:`Financial Data Analysis with Spyder<../workshops/financial>`." msgstr "" #: ../../workshops/plugin-development.rst:1431 -msgid "" -"As you may have noticed, there were some features left to implement such " -"as notifications when pomodoros are completed. Try to implement them and " -"do not hesitate to contact us if you have any doubts." +msgid "As you may have noticed, there were some features left to implement such as notifications when pomodoros are completed. Try to implement them and do not hesitate to contact us if you have any doubts." msgstr "" #: ../../workshops/plugin-development.rst:1438 -msgid "" -"In the `plugin-examples`_ repository you can find additional examples " -"that will surely be useful for you to further understand Spyder plugin " -"development." +msgid "In the `plugin-examples`_ repository you can find additional examples that will surely be useful for you to further understand Spyder plugin development." msgstr "" #: ../../workshops/plugin-development.rst:1440 -msgid "" -"A more in-depth review of the Spyder repository itself, especially its " -"simpler plugins, such as History, Plots or Working directory, may help " -"you understand it better. As well as a review of the various helper " -"functions, widgets and mixins present in ``spyder.api``." +msgid "A more in-depth review of the Spyder repository itself, especially its simpler plugins, such as History, Plots or Working directory, may help you understand it better. As well as a review of the various helper functions, widgets and mixins present in ``spyder.api``." msgstr "" #: ../../workshops/qt_fundamentals.rst:5 @@ -3188,12 +2318,7 @@ msgid "Qt Fundamentals" msgstr "" #: ../../workshops/qt_fundamentals.rst:9 -msgid "" -"**Qt** is a multiplatform widget toolkit for creating native graphical " -"user interfaces. Qt is also a very complete development framework that " -"offers utilities for building applications, and libraries of extensions " -"for Networking, Bluetooth, Charts, 3D rendering, Navigation (as GPS), " -"among others." +msgid "**Qt** is a multiplatform widget toolkit for creating native graphical user interfaces. Qt is also a very complete development framework that offers utilities for building applications, and libraries of extensions for Networking, Bluetooth, Charts, 3D rendering, Navigation (as GPS), among others." msgstr "" #: ../../workshops/qt_fundamentals.rst:14 @@ -3201,40 +2326,23 @@ msgid "Basic Qt Components" msgstr "" #: ../../workshops/qt_fundamentals.rst:16 -msgid "" -"As mentioned before, Spyder's plugin development consists of extending " -"the functionality of its Qt-based graphical interface." +msgid "As mentioned before, Spyder's plugin development consists of extending the functionality of its Qt-based graphical interface." msgstr "" #: ../../workshops/qt_fundamentals.rst:18 -msgid "" -"To develop a GUI we will add graphical elements of interaction known as " -"widgets, arrange them using layouts. Then, we interconnect those widgets " -"using customized procedures implemented as functions or methods, allowing" -" to trigger behavior from user interaction. In the following, we will " -"develop these ideas in more detail." +msgid "To develop a GUI we will add graphical elements of interaction known as widgets, arrange them using layouts. Then, we interconnect those widgets using customized procedures implemented as functions or methods, allowing to trigger behavior from user interaction. In the following, we will develop these ideas in more detail." msgstr "" #: ../../workshops/qt_fundamentals.rst:20 -msgid "" -"Each type of Qt component is a class starting with the letter ``Q`` " -"followed by a name related to its functionality." +msgid "Each type of Qt component is a class starting with the letter ``Q`` followed by a name related to its functionality." msgstr "" #: ../../workshops/qt_fundamentals.rst:22 -msgid "" -"The core component of Qt is the ``QApplication`` class. Every Qt " -"application needs a single instance of this class as the base, from where" -" the Qt *event loop* is controlled. Spyder itself is an instance of " -"``QApplication``, its starting point is in the following two lines of " -"code (spyder/spyder/app/mainwindow.py):" +msgid "The core component of Qt is the ``QApplication`` class. Every Qt application needs a single instance of this class as the base, from where the Qt *event loop* is controlled. Spyder itself is an instance of ``QApplication``, its starting point is in the following two lines of code (spyder/spyder/app/mainwindow.py):" msgstr "" #: ../../workshops/qt_fundamentals.rst:30 -msgid "" -"``QMainWindow`` is a pre-built widget that provides many standard window " -"features as toolbars, menus, a status bar, dockable widgets and more, " -"which serves as the basis for the application." +msgid "``QMainWindow`` is a pre-built widget that provides many standard window features as toolbars, menus, a status bar, dockable widgets and more, which serves as the basis for the application." msgstr "" #: ../../workshops/qt_fundamentals.rst:34 @@ -3242,31 +2350,15 @@ msgid "Signals & Slots" msgstr "" #: ../../workshops/qt_fundamentals.rst:36 -msgid "" -"**Signals** are notifications emitted by widgets when something happens. " -"That something could be different things, from pressing a button, to " -"changing text in an input box, to changing text in the window. Many " -"signals are initiated by user action, but this is not a rule." +msgid "**Signals** are notifications emitted by widgets when something happens. That something could be different things, from pressing a button, to changing text in an input box, to changing text in the window. Many signals are initiated by user action, but this is not a rule." msgstr "" #: ../../workshops/qt_fundamentals.rst:39 -msgid "" -"**Slots** are signal receivers. Functions or methods could be used as " -"slots, by connecting a signal to them. If a signal sends data, the " -"receiver callable will also receive it. Many Qt widgets also have their " -"own built-in slots, so the corresponding widgets are notified " -"automatically." +msgid "**Slots** are signal receivers. Functions or methods could be used as slots, by connecting a signal to them. If a signal sends data, the receiver callable will also receive it. Many Qt widgets also have their own built-in slots, so the corresponding widgets are notified automatically." msgstr "" #: ../../workshops/qt_fundamentals.rst:47 -msgid "" -"In computer science a *Widget* is a shortened form of “window gadget”. A " -"widget is an element of interaction, such as a button, or a container for" -" other widgets, as panels or tabs. The ``QWidget`` class is the " -"fundamental class for creating interfaces in Qt, it receives events from " -"the window system, and renders its representation on the screen. A widget" -" can provide a container for grouping other widgets, and if it is not " -"embedded in a parent widget, it becomes a window." +msgid "In computer science a *Widget* is a shortened form of “window gadget”. A widget is an element of interaction, such as a button, or a container for other widgets, as panels or tabs. The ``QWidget`` class is the fundamental class for creating interfaces in Qt, it receives events from the window system, and renders its representation on the screen. A widget can provide a container for grouping other widgets, and if it is not embedded in a parent widget, it becomes a window." msgstr "" #: ../../workshops/qt_fundamentals.rst:52 @@ -3274,14 +2366,7 @@ msgid "Layouts" msgstr "" #: ../../workshops/qt_fundamentals.rst:54 -msgid "" -"Interfaces are built by embedding widgets inside widgets, and since they " -"are visual components they are visually organized by means of *layouts*. " -"A layout indicates how the widgets fill their container, either as " -"columns, rows, cells in a matrix or stacked so that only one is visible " -"at a time. Those are the 4 basic layouts available in Qt: " -"``QHBoxLayout``, ``QVBoxLayout``, ``QGridLayout``, and " -"``QStackedLayout``." +msgid "Interfaces are built by embedding widgets inside widgets, and since they are visual components they are visually organized by means of *layouts*. A layout indicates how the widgets fill their container, either as columns, rows, cells in a matrix or stacked so that only one is visible at a time. Those are the 4 basic layouts available in Qt: ``QHBoxLayout``, ``QVBoxLayout``, ``QGridLayout``, and ``QStackedLayout``." msgstr "" #: ../../workshops/qt_fundamentals.rst:61 @@ -3289,12 +2374,7 @@ msgid "Actions, Toolbars & Menus" msgstr "" #: ../../workshops/qt_fundamentals.rst:63 -msgid "" -"User interfaces of desktop applications usually use ``QToolbar`` and " -"``QMenu``. Since these are alternative ways to access the same " -"functionality, Qt provides ``QAction`` as a way to avoid duplication of " -"functions. Thus, each time a menu option or a toolbar button gives access" -" to the same function, they point to the same action." +msgid "User interfaces of desktop applications usually use ``QToolbar`` and ``QMenu``. Since these are alternative ways to access the same functionality, Qt provides ``QAction`` as a way to avoid duplication of functions. Thus, each time a menu option or a toolbar button gives access to the same function, they point to the same action." msgstr "" #: ../../workshops/qt_fundamentals.rst:67 @@ -3302,18 +2382,11 @@ msgid "Dialogs" msgstr "" #: ../../workshops/qt_fundamentals.rst:69 -msgid "" -"A *Dialog* is a GUI component that communicates with the user. Dialogs " -"are commonly used for functions that do not fit into the main interface. " -"In Qt, by design ``QDialog`` is a modal (or blocking) window that show in" -" front of the main Window until it is dismissed." +msgid "A *Dialog* is a GUI component that communicates with the user. Dialogs are commonly used for functions that do not fit into the main interface. In Qt, by design ``QDialog`` is a modal (or blocking) window that show in front of the main Window until it is dismissed." msgstr "" #: ../../workshops/qt_fundamentals.rst:72 -msgid "" -"Qt provides some *special dialogs* for the most common use-cases as *file" -" Open/Save*, *font selection*, *error messages*, *color choosing*, " -"*printing*, among others." +msgid "Qt provides some *special dialogs* for the most common use-cases as *file Open/Save*, *font selection*, *error messages*, *color choosing*, *printing*, among others." msgstr "" #: ../../workshops/qt_fundamentals.rst:76 @@ -3321,11 +2394,7 @@ msgid "Windows" msgstr "" #: ../../workshops/qt_fundamentals.rst:78 -msgid "" -"If an application requires additional windows that do not block the main " -"window, these are generated as non-parent ``QWidget`` instances. These " -"are used for tasks that happen in parallel over long-running processes " -"such as displaying graphs or document editing." +msgid "If an application requires additional windows that do not block the main window, these are generated as non-parent ``QWidget`` instances. These are used for tasks that happen in parallel over long-running processes such as displaying graphs or document editing." msgstr "" #: ../../workshops/qt_fundamentals.rst:83 @@ -3333,12 +2402,7 @@ msgid "Events" msgstr "" #: ../../workshops/qt_fundamentals.rst:85 -msgid "" -"An *Event* denote every interaction the user has with a Qt application. " -"There are several types of events designed to address different types of " -"interactions. In Qt they are represented by ``QEvent`` instances that " -"contain information about what prompted them, and are passed to specific " -"handlers that are responsible for triggering further actions." +msgid "An *Event* denote every interaction the user has with a Qt application. There are several types of events designed to address different types of interactions. In Qt they are represented by ``QEvent`` instances that contain information about what prompted them, and are passed to specific handlers that are responsible for triggering further actions." msgstr "" #: ../../workshops/scientific-computing.rst:3 @@ -3346,26 +2410,15 @@ msgid "Scientific Computing and Visualization with Spyder" msgstr "" #: ../../workshops/scientific-computing.rst:5 -msgid "" -"This workshop allows you to explore some of Spyder's features that make " -"Spyder an ideal IDE for using the scientific tools offered by Python. " -"Throughout the workshop, we will apply the scientific method to answer " -"some questions related to our preferences and cognitive abilities. By the" -" end of this workshop participants will be able to use Spyder to explore " -"data, analyze it with some statistical tools and plot the relationship " -"between variables." +msgid "This workshop allows you to explore some of Spyder's features that make Spyder an ideal IDE for using the scientific tools offered by Python. Throughout the workshop, we will apply the scientific method to answer some questions related to our preferences and cognitive abilities. By the end of this workshop participants will be able to use Spyder to explore data, analyze it with some statistical tools and plot the relationship between variables." msgstr "" #: ../../workshops/scientific-computing.rst:23 -msgid "" -"Some knowledge of Statistics (`hypothesis testing`_ , `ANOVA`_, " -"`p-value`_)" +msgid "Some knowledge of Statistics (`hypothesis testing`_ , `ANOVA`_, `p-value`_)" msgstr "" #: ../../workshops/scientific-computing.rst:38 -msgid "" -"Apply the scientific method to answer questions related to psychometric " -"variables" +msgid "Apply the scientific method to answer questions related to psychometric variables" msgstr "" #: ../../workshops/scientific-computing.rst:39 @@ -3373,16 +2426,11 @@ msgid "Understand how to use Spyder's built-in scientific computing tools" msgstr "" #: ../../workshops/scientific-computing.rst:47 -msgid "" -"This workshop is intended for people who want to learn how to answer " -"questions scientifically from a dataset. We have also designed it to " -"serve as a tutorial for learning how to use Spyder as a research tool." +msgid "This workshop is intended for people who want to learn how to answer questions scientifically from a dataset. We have also designed it to serve as a tutorial for learning how to use Spyder as a research tool." msgstr "" #: ../../workshops/scientific-computing.rst:55 -msgid "" -"In this workshop we will explore a data set and use it to answer some " -"questions using the scientific method." +msgid "In this workshop we will explore a data set and use it to answer some questions using the scientific method." msgstr "" #: ../../workshops/scientific-computing.rst:59 @@ -3390,10 +2438,7 @@ msgid "Why do scientific research with Python?" msgstr "" #: ../../workshops/scientific-computing.rst:61 -msgid "" -"Python is a mature programming language that has been chosen by much of " -"the scientific community to support the research process. There are a few" -" reasons for this:" +msgid "Python is a mature programming language that has been chosen by much of the scientific community to support the research process. There are a few reasons for this:" msgstr "" #: ../../workshops/scientific-computing.rst:63 @@ -3401,39 +2446,23 @@ msgid "It is versatile and easy to learn and use" msgstr "" #: ../../workshops/scientific-computing.rst:64 -msgid "" -"It allows for multiple ways to handle inputs and outputs. No matter what " -"format your data is in, in Python there is always a way to import it (and" -" export it in the format of your choice)" +msgid "It allows for multiple ways to handle inputs and outputs. No matter what format your data is in, in Python there is always a way to import it (and export it in the format of your choice)" msgstr "" #: ../../workshops/scientific-computing.rst:65 -msgid "" -"It is interpreted. You don't have to write code from start to finish to " -"see partial results. This makes it especially easy and fast to explore " -"data" +msgid "It is interpreted. You don't have to write code from start to finish to see partial results. This makes it especially easy and fast to explore data" msgstr "" #: ../../workshops/scientific-computing.rst:66 -msgid "" -"It has built-in support for scientific computing tasks: `SciPy " -"`_, `NumPy `_, `Pandas " -"`_, and a vast number of other libraries " -"created by and for scientists" +msgid "It has built-in support for scientific computing tasks: `SciPy `_, `NumPy `_, `Pandas `_, and a vast number of other libraries created by and for scientists" msgstr "" #: ../../workshops/scientific-computing.rst:67 -msgid "" -"It is the most widely used programming language for Machine Learning " -"(including Keras and TensorFlow)" +msgid "It is the most widely used programming language for Machine Learning (including Keras and TensorFlow)" msgstr "" #: ../../workshops/scientific-computing.rst:69 -msgid "" -"It can be integrated with `Jupyter Notebooks `_ and " -"implementations of these in the cloud (`Google Colab " -"`_ or `Binder " -"`_)" +msgid "It can be integrated with `Jupyter Notebooks `_ and implementations of these in the cloud (`Google Colab `_ or `Binder `_)" msgstr "" #: ../../workshops/scientific-computing.rst:73 @@ -3441,15 +2470,7 @@ msgid "How can Spyder help me in my scientific research?" msgstr "" #: ../../workshops/scientific-computing.rst:75 -msgid "" -"Spyder is a Scientific Integrated Development Environment written in " -"Python, and designed by and for scientists, engineers, and data analysts." -" It features a unique combination of the advanced editing, analysis, " -"debugging, and profiling functionality of a comprehensive development " -"tool with the data exploration, interactive execution, deep inspection, " -"and beautiful visualization capabilities of a scientific package. " -"Together with Python, it provides a very complete set of tools for " -"scientific computing." +msgid "Spyder is a Scientific Integrated Development Environment written in Python, and designed by and for scientists, engineers, and data analysts. It features a unique combination of the advanced editing, analysis, debugging, and profiling functionality of a comprehensive development tool with the data exploration, interactive execution, deep inspection, and beautiful visualization capabilities of a scientific package. Together with Python, it provides a very complete set of tools for scientific computing." msgstr "" #: ../../workshops/scientific-computing.rst:79 @@ -3457,11 +2478,7 @@ msgid "The basic steps of the scientific method" msgstr "" #: ../../workshops/scientific-computing.rst:81 -msgid "" -"The `scientific method " -"`_ is a set of good " -"practices used to achieve new knowledge in a valid way. Broadly speaking," -" the stages of the scientific method are as follows:" +msgid "The `scientific method `_ is a set of good practices used to achieve new knowledge in a valid way. Broadly speaking, the stages of the scientific method are as follows:" msgstr "" #: ../../workshops/scientific-computing.rst:83 @@ -3469,9 +2486,7 @@ msgid "Observation: first find something that needs an explanation" msgstr "" #: ../../workshops/scientific-computing.rst:84 -msgid "" -"Search/generate theory: say a thing or two about the state of the world " -"or how it works (an abstract thought about a phenomenon)" +msgid "Search/generate theory: say a thing or two about the state of the world or how it works (an abstract thought about a phenomenon)" msgstr "" #: ../../workshops/scientific-computing.rst:85 @@ -3479,9 +2494,7 @@ msgid "Hypothesis: identify variables and make predictions" msgstr "" #: ../../workshops/scientific-computing.rst:86 -msgid "" -"Testing/Experiment/More observation: measure relationship between " -"variables" +msgid "Testing/Experiment/More observation: measure relationship between variables" msgstr "" #: ../../workshops/scientific-computing.rst:87 @@ -3493,10 +2506,7 @@ msgid "Reporting: share new findings" msgstr "" #: ../../workshops/scientific-computing.rst:90 -msgid "" -"Throughout this workshop, we will be developing each of these steps in a " -"practical way. We will use Spyder as a research tool and psychometric " -"data from an online dating site to make it easy and fun." +msgid "Throughout this workshop, we will be developing each of these steps in a practical way. We will use Spyder as a research tool and psychometric data from an online dating site to make it easy and fun." msgstr "" #: ../../workshops/scientific-computing.rst:94 @@ -3504,25 +2514,15 @@ msgid "Introduction to scientific research with Spyder" msgstr "" #: ../../workshops/scientific-computing.rst:100 -msgid "" -"If you already have experience with Spyder, you can skip to `Preparation " -"work`_ section." +msgid "If you already have experience with Spyder, you can skip to `Preparation work`_ section." msgstr "" #: ../../workshops/scientific-computing.rst:122 -msgid "" -"The Variable Explorer is one of the most frequently used components in " -"this workshop. **This is the pane where we will observe the data and most" -" of the results of the scientific analysis, except for the plots**." +msgid "The Variable Explorer is one of the most frequently used components in this workshop. **This is the pane where we will observe the data and most of the results of the scientific analysis, except for the plots**." msgstr "" #: ../../workshops/scientific-computing.rst:128 -msgid "" -"The :doc:`Plots pane <../panes/plots>` shows all the static graphs and " -"images created in your IPython Console session. **All plots generated by " -"the code will appear in this component**. You will also be able to save " -"each graphic in a local file or copy it to the clipboard to share it with" -" other researchers." +msgid "The :doc:`Plots pane <../panes/plots>` shows all the static graphs and images created in your IPython Console session. **All plots generated by the code will appear in this component**. You will also be able to save each graphic in a local file or copy it to the clipboard to share it with other researchers." msgstr "" #: ../../workshops/scientific-computing.rst:132 @@ -3530,12 +2530,7 @@ msgid "Code Analysis (share a stylish code!)" msgstr "" #: ../../workshops/scientific-computing.rst:134 -msgid "" -"Wouldn't it be great to have a tool to be able to detect code errors, " -"stylistic problems, bad practices, inconsistencies and other issues? This" -" is precisely the task of the :doc:`Code Analysis<../panes/pylint>`. " -"Your code can run, but if you are going to share it with other " -"researchers it would be great if it is both readable and neat as well." +msgid "Wouldn't it be great to have a tool to be able to detect code errors, stylistic problems, bad practices, inconsistencies and other issues? This is precisely the task of the :doc:`Code Analysis<../panes/pylint>`. Your code can run, but if you are going to share it with other researchers it would be great if it is both readable and neat as well." msgstr "" #: ../../workshops/scientific-computing.rst:146 @@ -3543,12 +2538,7 @@ msgid "Setting up the Conda environment" msgstr "" #: ../../workshops/scientific-computing.rst:154 -msgid "" -"We recommend creating the virtual environment with `Anaconda " -"`_ (or `Miniconda " -"`_) as it integrates " -"seamlessly with Spyder. You can find installation instructions in " -"`Anaconda documentation`_." +msgid "We recommend creating the virtual environment with `Anaconda `_ (or `Miniconda `_) as it integrates seamlessly with Spyder. You can find installation instructions in `Anaconda documentation`_." msgstr "" #: ../../workshops/scientific-computing.rst:160 @@ -3556,25 +2546,15 @@ msgid "1. With commands" msgstr "" #: ../../workshops/scientific-computing.rst:162 -msgid "" -"Just run the following command in your Anaconda Prompt (Windows) or " -"terminal (other platforms), for a minimal install of Spyder into a new " -"environment called ``scientific-computing``:" +msgid "Just run the following command in your Anaconda Prompt (Windows) or terminal (other platforms), for a minimal install of Spyder into a new environment called ``scientific-computing``:" msgstr "" #: ../../workshops/scientific-computing.rst:168 -msgid "" -"To install Spyder's optional dependencies as well for full functionality," -" use the following command instead:" +msgid "To install Spyder's optional dependencies as well for full functionality, use the following command instead:" msgstr "" #: ../../workshops/scientific-computing.rst:176 -msgid "" -"Spyder now offers :ref:`install-standalone` for Windows and macOS, making" -" it easier to get up and running with the application without having to " -"download Anaconda or manually install it in your existing environment. If" -" you use the standalone installer, there is no need to install " -"``spyder=5`` with conda." +msgid "Spyder now offers :ref:`install-standalone` for Windows and macOS, making it easier to get up and running with the application without having to download Anaconda or manually install it in your existing environment. If you use the standalone installer, there is no need to install ``spyder=5`` with conda." msgstr "" #: ../../workshops/scientific-computing.rst:180 @@ -3582,11 +2562,7 @@ msgid "2. From an environment.yml file" msgstr "" #: ../../workshops/scientific-computing.rst:182 -msgid "" -"You can also install the virtual environment easily using the environment" -" file (``scientific-computing.yml``) that we share with you. Just run the" -" following command in the terminal (you must have the environment file in" -" the current directory):" +msgid "You can also install the virtual environment easily using the environment file (``scientific-computing.yml``) that we share with you. Just run the following command in the terminal (you must have the environment file in the current directory):" msgstr "" #: ../../workshops/scientific-computing.rst:190 @@ -3602,10 +2578,7 @@ msgid "Downloading the dataset" msgstr "" #: ../../workshops/scientific-computing.rst:202 -msgid "" -"We are going to work with a public dataset called OKCupid, collected by " -"Kirkegaard and Bjerrekaer. The dataset is composed of 68,371 records and " -"2,626 variables." +msgid "We are going to work with a public dataset called OKCupid, collected by Kirkegaard and Bjerrekaer. The dataset is composed of 68,371 records and 2,626 variables." msgstr "" #: ../../workshops/scientific-computing.rst:204 @@ -3617,11 +2590,7 @@ msgid "Setting up the working directory" msgstr "" #: ../../workshops/scientific-computing.rst:212 -msgid "" -"The virtual environment and the data file are now ready. The only thing " -"that remains is to create a directory to work in. In your operating " -"system, create a new directory with the name of your choice. Then copy " -"and unzip the dataset file there." +msgid "The virtual environment and the data file are now ready. The only thing that remains is to create a directory to work in. In your operating system, create a new directory with the name of your choice. Then copy and unzip the dataset file there." msgstr "" #: ../../workshops/scientific-computing.rst:214 @@ -3629,9 +2598,7 @@ msgid "Here is an example (on Linux or macOS):" msgstr "" #: ../../workshops/scientific-computing.rst:221 -msgid "" -"Keep in mind that in this new directory you must have the data file " -"unzipped." +msgid "Keep in mind that in this new directory you must have the data file unzipped." msgstr "" #: ../../workshops/scientific-computing.rst:223 @@ -3639,27 +2606,23 @@ msgid "Launch Spyder:" msgstr "" #: ../../workshops/scientific-computing.rst:229 -msgid "" -"Let's make sure Spyder is ready. First, check that the working directory " -"is correct. You should see in the upper right corner the path to the " -"directory where you have the dataset. Something like this:" +msgid "Let's make sure Spyder is ready. First, check that the working directory is correct. You should see in the upper right corner the path to the directory where you have the dataset. Something like this:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:231 +msgid "Spyder's Working Directory plugin showing the working directory of spyder-scientific" msgstr "" #: ../../workshops/scientific-computing.rst:234 -msgid "" -"Second, let's check that the virtual environment we created is enabled in" -" Spyder. Go to :guilabel:`Preferences` > :guilabel:`Python interpreter`, " -"and use the dropdown under :guilabel:`Use the following Python " -"interpreter` to select the path to your virtual environment. You should " -"see something like this:" +msgid "Second, let's check that the virtual environment we created is enabled in Spyder. Go to :guilabel:`Preferences` > :guilabel:`Python interpreter`, and use the dropdown under :guilabel:`Use the following Python interpreter` to select the path to your virtual environment. You should see something like this:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:236 +msgid "Set up environment in Spyder's Preferences" msgstr "" #: ../../workshops/scientific-computing.rst:245 -msgid "" -"Although the workshop is designed for you to write the code in the " -"IPython Console, we have created a file that you can :download:`download " -"`. This script provides all the code you will " -"write in this workshop, and you can use it as a guide if you get lost." +msgid "Although the workshop is designed for you to write the code in the IPython Console, we have created a file that you can :download:`download `. This script provides all the code you will write in this workshop, and you can use it as a guide if you get lost." msgstr "" #: ../../workshops/scientific-computing.rst:251 @@ -3667,41 +2630,27 @@ msgid "The dataset" msgstr "" #: ../../workshops/scientific-computing.rst:253 -msgid "" -"OKCupid is a dataset that gathers information obtained from the online " -"dating site OKCupid. It consists of 68,371 records collected " -"automatically employing a scraper that extracted public information." +msgid "OKCupid is a dataset that gathers information obtained from the online dating site OKCupid. It consists of 68,371 records collected automatically employing a scraper that extracted public information." msgstr "" #: ../../workshops/scientific-computing.rst:255 -msgid "" -"The dataset contains demographic data (e.g., gender, sexual orientation " -"and age). It also includes answers to general questions used by the " -"website's algorithm to calculate some personality indicators to help find" -" compatible matches." +msgid "The dataset contains demographic data (e.g., gender, sexual orientation and age). It also includes answers to general questions used by the website's algorithm to calculate some personality indicators to help find compatible matches." msgstr "" #: ../../workshops/scientific-computing.rst:257 -msgid "" -"If you want more information about how this dataset was collected and " -"what kind of information it contains you can get it in this paper: `The " -"OKCupid dataset`_." +msgid "If you want more information about how this dataset was collected and what kind of information it contains you can get it in this paper: `The OKCupid dataset`_." +msgstr "" + +#: ../../workshops/scientific-computing.rst:263 +msgid "IPython Console location in Spyder IDE" msgstr "" #: ../../workshops/scientific-computing.rst:266 -msgid "" -"You can also write your code or in the Editor (the pane that occupies the" -" entire left side of Spyder). If you use the Editor, you can run the code" -" by selecting it and pressing the :guilabel:`Run selection or current " -"line` button in the :guilabel:`Run toolbar` or by pressing the F9 button." +msgid "You can also write your code or in the Editor (the pane that occupies the entire left side of Spyder). If you use the Editor, you can run the code by selecting it and pressing the :guilabel:`Run selection or current line` button in the :guilabel:`Run toolbar` or by pressing the F9 button." msgstr "" #: ../../workshops/scientific-computing.rst:280 -msgid "" -"The data you downloaded earlier is in `parquet " -"`_ format. This format" -" is very convenient because it is smaller and faster than CSV or JSON " -"files." +msgid "The data you downloaded earlier is in `parquet `_ format. This format is very convenient because it is smaller and faster than CSV or JSON files." msgstr "" #: ../../workshops/scientific-computing.rst:282 @@ -3709,15 +2658,15 @@ msgid "Load data:" msgstr "" #: ../../workshops/scientific-computing.rst:288 -msgid "" -"You should now be able to see the data you have imported in the Variable " -"Explorer." +msgid "You should now be able to see the data you have imported in the Variable Explorer." +msgstr "" + +#: ../../workshops/scientific-computing.rst:290 +msgid "Dataset in the Variable Explorer" msgstr "" #: ../../workshops/scientific-computing.rst:293 -msgid "" -"You can see that the object is of type DataFrame and the number of rows " -"and columns of the object." +msgid "You can see that the object is of type DataFrame and the number of rows and columns of the object." msgstr "" #: ../../workshops/scientific-computing.rst:299 @@ -3729,122 +2678,95 @@ msgid "Age" msgstr "" #: ../../workshops/scientific-computing.rst:305 -msgid "" -"Now, let's explore one of the variables, in this case, the numeric " -"variable age (``d_age``)." +msgid "Now, let's explore one of the variables, in this case, the numeric variable age (``d_age``)." msgstr "" #: ../../workshops/scientific-computing.rst:309 -msgid "" -"In the OKCupid dataset, all demographic variables are prefixed with " -"\"d\\_\" and profile variables with \"p\\_\"." +msgid "In the OKCupid dataset, all demographic variables are prefixed with \"d\\_\" and profile variables with \"p\\_\"." +msgstr "" + +#: ../../workshops/scientific-computing.rst:315 +msgid "Console output for data.d_age.describe()" msgstr "" #: ../../workshops/scientific-computing.rst:318 -msgid "" -"What happened? We called the ``data`` object and used Python's dot " -"notation to pick the ``d_age`` column. This has a `Pandas Series " -"`_ type object. To this " -"object we pass the ``describe()`` method that shows a summary of some " -"indicators: count of values, mean, standard deviation, maximum value, " -"minimum value, among others. With these figures we can see that the " -"sample is mainly constituted of young people (the average is 31.65 years " -"old)." +msgid "What happened? We called the ``data`` object and used Python's dot notation to pick the ``d_age`` column. This has a `Pandas Series `_ type object. To this object we pass the ``describe()`` method that shows a summary of some indicators: count of values, mean, standard deviation, maximum value, minimum value, among others. With these figures we can see that the sample is mainly constituted of young people (the average is 31.65 years old)." msgstr "" #: ../../workshops/scientific-computing.rst:320 -msgid "" -"The return of a function, method or the attribute of an object can be " -"stored as a variable to have it at hand in the Variable Explorer:" +msgid "The return of a function, method or the attribute of an object can be stored as a variable to have it at hand in the Variable Explorer:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:327 +msgid "More variables in Variable Explorer" msgstr "" #: ../../workshops/scientific-computing.rst:330 -msgid "" -"The values are floats. The lowest age is 18.0 years and the highest is " -"100.0 years." +msgid "The values are floats. The lowest age is 18.0 years and the highest is 100.0 years." msgstr "" #: ../../workshops/scientific-computing.rst:334 -msgid "" -"Notice also that each type of variable has a different color to quickly " -"distinguish them." +msgid "Notice also that each type of variable has a different color to quickly distinguish them." msgstr "" #: ../../workshops/scientific-computing.rst:336 -msgid "" -"We already know the minimum and maximum age, and that the mean is around " -"32 years old. A good way to further explore this variable is to plot a " -"histogram, a type of graph that shows the frequency distributions. In " -"this way we can see if the groups of young people on the platform are " -"more numerous than the older ones." +msgid "We already know the minimum and maximum age, and that the mean is around 32 years old. A good way to further explore this variable is to plot a histogram, a type of graph that shows the frequency distributions. In this way we can see if the groups of young people on the platform are more numerous than the older ones." msgstr "" #: ../../workshops/scientific-computing.rst:338 -msgid "" -"We can plot a histogram directly from the dataframe. To do this we select" -" the variable (as we did with the ``.describe()``) and invoke the " -"``.plot.hist()`` method. In this method we will pass as arguments the " -"number of bins and the transparency of the plot (``alpha``)." +msgid "We can plot a histogram directly from the dataframe. To do this we select the variable (as we did with the ``.describe()``) and invoke the ``.plot.hist()`` method. In this method we will pass as arguments the number of bins and the transparency of the plot (``alpha``)." +msgstr "" + +#: ../../workshops/scientific-computing.rst:344 +msgid "Age histogram with Pandas" msgstr "" #: ../../workshops/scientific-computing.rst:348 -msgid "" -"Another way to generate a simple histogram in Spyder is to use a context " -"menu on an array in the Variable Explorer. But first we must store these " -"values in a list and call that variable ``age``." +msgid "Another way to generate a simple histogram in Spyder is to use a context menu on an array in the Variable Explorer. But first we must store these values in a list and call that variable ``age``." +msgstr "" + +#: ../../workshops/scientific-computing.rst:354 +msgid "Age histogram option from Variable Explorer" +msgstr "" + +#: ../../workshops/scientific-computing.rst:357 +msgid "Age histogram from Variable Explorer" msgstr "" #: ../../workshops/scientific-computing.rst:360 -msgid "" -"Frequency distributions come in different sizes and shapes. The shape of " -"a histogram reveals very interesting things about the data. A " -"symmetrical, bell-shaped histogram might indicate that the distribution " -"is normal (most of the scores are close to the center of the " -"distribution). In the age histogram, you can see that it has a \"tail\" " -"to the right (towards the older ages). Technically this is called " -"\"positively `skewed`_\". It is also noticeable that it is somewhat " -"pointy (positive `kurtosis`_ or leptokurtic). These two things could " -"suggest that age is not a random variable." +msgid "Frequency distributions come in different sizes and shapes. The shape of a histogram reveals very interesting things about the data. A symmetrical, bell-shaped histogram might indicate that the distribution is normal (most of the scores are close to the center of the distribution). In the age histogram, you can see that it has a \"tail\" to the right (towards the older ages). Technically this is called \"positively `skewed`_\". It is also noticeable that it is somewhat pointy (positive `kurtosis`_ or leptokurtic). These two things could suggest that age is not a random variable." msgstr "" #: ../../workshops/scientific-computing.rst:365 -msgid "" -"Although we can create the histogram directly from the dataframe, we are " -"going to use a Python library called Seaborn to do the same, because this" -" library will allow us to do more interesting things later." +msgid "Although we can create the histogram directly from the dataframe, we are going to use a Python library called Seaborn to do the same, because this library will allow us to do more interesting things later." msgstr "" #: ../../workshops/scientific-computing.rst:372 -msgid "" -"We call ``sns.histplot()`` with three arguments. The first one " -"(``data.d_age``) is a Pandas Series with the **quantitative** variable we" -" want to plot. The second (``kde=True``) adds a curve showing an ideal " -"model of the age distribution (using a method called *Kernel Density " -"Estimator*). And the third one (``bins=25``) indicates that we want 25 " -"bins in the graph." +msgid "We call ``sns.histplot()`` with three arguments. The first one (``data.d_age``) is a Pandas Series with the **quantitative** variable we want to plot. The second (``kde=True``) adds a curve showing an ideal model of the age distribution (using a method called *Kernel Density Estimator*). And the third one (``bins=25``) indicates that we want 25 bins in the graph." +msgstr "" + +#: ../../workshops/scientific-computing.rst:374 +msgid "Age histogram with Seaborn" msgstr "" #: ../../workshops/scientific-computing.rst:377 -msgid "" -"The second line (``plt.show()``) is intended to show all the figures not " -"displayed so far. If you have any doubts about how to utilize an object, " -"method or function, you can use the ``help()`` tool in the console. For " -"example:" +msgid "The second line (``plt.show()``) is intended to show all the figures not displayed so far. If you have any doubts about how to utilize an object, method or function, you can use the ``help()`` tool in the console. For example:" msgstr "" #: ../../workshops/scientific-computing.rst:383 -msgid "" -"Or you can also take advantage of the Help pane included in Spyder to get" -" on-screen help:" +msgid "Or you can also take advantage of the Help pane included in Spyder to get on-screen help:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:385 +msgid "plt.show() help in Spyder's Help pane" msgstr "" #: ../../workshops/scientific-computing.rst:388 -msgid "" -"With Seaborn, we can add a line representing the mean of the histogram. " -"To do this we will use the ``axvline()`` method and add a text with the " -"value of the mean where ``text()``, ``min_ylim`` and ``max_ylim`` are " -"used to mark the position of the text." +msgid "With Seaborn, we can add a line representing the mean of the histogram. To do this we will use the ``axvline()`` method and add a text with the value of the mean where ``text()``, ``min_ylim`` and ``max_ylim`` are used to mark the position of the text." +msgstr "" + +#: ../../workshops/scientific-computing.rst:400 +msgid "Age histogram with mean line" msgstr "" #: ../../workshops/scientific-computing.rst:405 @@ -3852,46 +2774,27 @@ msgid "Religion seriosity" msgstr "" #: ../../workshops/scientific-computing.rst:407 -msgid "" -"We know the extent of the dataframe and we have seen how to explore a " -"quantitative variable. Now let's move on to a qualitative variable. The " -"``columns`` attribute shows a list of column names in the dataframe. We " -"also know that demographic variables are prefixed with \"d\\_\", so we " -"can look for variable names that correspond to this prefix." +msgid "We know the extent of the dataframe and we have seen how to explore a quantitative variable. Now let's move on to a qualitative variable. The ``columns`` attribute shows a list of column names in the dataframe. We also know that demographic variables are prefixed with \"d\\_\", so we can look for variable names that correspond to this prefix." msgstr "" #: ../../workshops/scientific-computing.rst:413 -msgid "" -"In the Variable Explorer you will see a new variable ``demograph``. If " -"you double click on it you will see a list of the demographic variables " -"in the dataset. At the end of the list you will see a value " -"``d_religion_seriosity``. If you right click on it, several options will " -"appear on the screen. You can rename the column, delete it or insert a " -"new one. Let's click on :guilabel:`Copy` to copy the column name into " -"memory." +msgid "In the Variable Explorer you will see a new variable ``demograph``. If you double click on it you will see a list of the demographic variables in the dataset. At the end of the list you will see a value ``d_religion_seriosity``. If you right click on it, several options will appear on the screen. You can rename the column, delete it or insert a new one. Let's click on :guilabel:`Copy` to copy the column name into memory." msgstr "" #: ../../workshops/scientific-computing.rst:415 -msgid "" -"In the IPython Console, type ``data.`` and then copy the column name. " -"Type a period at the end (no spaces) and hit tab. You should see " -"something like the following:" +msgid "In the IPython Console, type ``data.`` and then copy the column name. Type a period at the end (no spaces) and hit tab. You should see something like the following:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:417 +msgid "IPython Console auto-completion" msgstr "" #: ../../workshops/scientific-computing.rst:420 -msgid "" -"You can then see a list of all relevant methods and attributes of the " -"class. Right at the end you will see ``value_counts`` that could be used " -"to summarize the variable. It is a method so it must end in parentheses:" +msgid "You can then see a list of all relevant methods and attributes of the class. Right at the end you will see ``value_counts`` that could be used to summarize the variable. It is a method so it must end in parentheses:" msgstr "" #: ../../workshops/scientific-computing.rst:432 -msgid "" -"In addition to demographic and profile variables, the dataset includes " -"responses to questions on a variety of topics. These questions are coded " -"with a prefix \"q\" followed by an integer. The text of the questions is " -"stored in a file called :file:`question_data.csv` (which you can download" -" as part of the `OKCupid dataset`_)." +msgid "In addition to demographic and profile variables, the dataset includes responses to questions on a variety of topics. These questions are coded with a prefix \"q\" followed by an integer. The text of the questions is stored in a file called :file:`question_data.csv` (which you can download as part of the `OKCupid dataset`_)." msgstr "" #: ../../workshops/scientific-computing.rst:434 @@ -3899,15 +2802,11 @@ msgid "We can examine this file in the Variable Explorer:" msgstr "" #: ../../workshops/scientific-computing.rst:440 -msgid "" -"Double click on \"question_data\" in the Variable Explorer to display " -"each question aligned with its code (\"q\" + number)." +msgid "Double click on \"question_data\" in the Variable Explorer to display each question aligned with its code (\"q\" + number)." msgstr "" #: ../../workshops/scientific-computing.rst:442 -msgid "" -"Now that we have learned how to explore the data we can ask interesting " -"questions and try to answer them with the help of the dataset and Spyder." +msgid "Now that we have learned how to explore the data we can ask interesting questions and try to answer them with the help of the dataset and Spyder." msgstr "" #: ../../workshops/scientific-computing.rst:448 @@ -3915,63 +2814,31 @@ msgid "Think of a theory and write a hypothesis" msgstr "" #: ../../workshops/scientific-computing.rst:450 -msgid "" -"A theory is nothing more than an explanation of something. For example, " -"we could get involved in the eternal conflict between cats and dogs. I, " -"as a dog person, might have a theory (unscientific, of course) that those" -" who prefer to have the companionship of a dog are smarter people than " -"those who prefer a wicked (but lovable) kitty. To test the support of a " -"theory, one can make a prediction based on it and see how this prediction" -" behaves in an experiment or a concrete situation. We call this " -"prediction a hypothesis." +msgid "A theory is nothing more than an explanation of something. For example, we could get involved in the eternal conflict between cats and dogs. I, as a dog person, might have a theory (unscientific, of course) that those who prefer to have the companionship of a dog are smarter people than those who prefer a wicked (but lovable) kitty. To test the support of a theory, one can make a prediction based on it and see how this prediction behaves in an experiment or a concrete situation. We call this prediction a hypothesis." msgstr "" #: ../../workshops/scientific-computing.rst:452 -msgid "" -"A hypothesis is a statement that can be tested employing the scientific " -"method. They must be verifiable using empirical evidence or data. For " -"example, *green is the best color* is not a hypothesis since it cannot be" -" proven or disproven." +msgid "A hypothesis is a statement that can be tested employing the scientific method. They must be verifiable using empirical evidence or data. For example, *green is the best color* is not a hypothesis since it cannot be proven or disproven." msgstr "" #: ../../workshops/scientific-computing.rst:454 -msgid "" -"Concerning the above theory of a person's pet preferences, to explore it " -"we should find two variables to relate. The first variable would be " -"related to a **self-identification as a cat person or dog person**. The " -"second variable would be related to a person's **ability to solve " -"problems and situations**." +msgid "Concerning the above theory of a person's pet preferences, to explore it we should find two variables to relate. The first variable would be related to a **self-identification as a cat person or dog person**. The second variable would be related to a person's **ability to solve problems and situations**." msgstr "" #: ../../workshops/scientific-computing.rst:456 -msgid "" -"The OKCupid dataset has useful variables that we can use to investigate " -"this theory. For example, question **q997** (*Are you a cat person or a " -"dog person?* ) provides information about a person's pet preferences. The" -" second variable is slightly more difficult to come up with, as it is " -"somewhat more complex. Fortunately, the researchers who collected the " -"dataset have also selected 14 questions that can serve as a proxy for a " -"cognitive ability test. This selection of questions can be found in the " -"file :file:`test_items.csv` in the `OKCupid dataset`_." +msgid "The OKCupid dataset has useful variables that we can use to investigate this theory. For example, question **q997** (*Are you a cat person or a dog person?* ) provides information about a person's pet preferences. The second variable is slightly more difficult to come up with, as it is somewhat more complex. Fortunately, the researchers who collected the dataset have also selected 14 questions that can serve as a proxy for a cognitive ability test. This selection of questions can be found in the file :file:`test_items.csv` in the `OKCupid dataset`_." msgstr "" #: ../../workshops/scientific-computing.rst:462 -msgid "" -"So, let's try to see if there is any evidence in the OKCupid dataset to " -"support the following hypothesis:" +msgid "So, let's try to see if there is any evidence in the OKCupid dataset to support the following hypothesis:" msgstr "" #: ../../workshops/scientific-computing.rst:464 -msgid "" -"*People who prefer dogs to cats would score higher on tests of cognitive " -"ability*." +msgid "*People who prefer dogs to cats would score higher on tests of cognitive ability*." msgstr "" #: ../../workshops/scientific-computing.rst:468 -msgid "" -"SPOILER ALERT: If you are a cat person, and feel you should immediately " -"leave this workshop, I suggest you stay. If you're not a cat person, stay" -" too." +msgid "SPOILER ALERT: If you are a cat person, and feel you should immediately leave this workshop, I suggest you stay. If you're not a cat person, stay too." msgstr "" #: ../../workshops/scientific-computing.rst:474 @@ -3979,10 +2846,7 @@ msgid "Build the test" msgstr "" #: ../../workshops/scientific-computing.rst:476 -msgid "" -"We already know which questions will be part of the cognitive ability " -"test. Now we are going to process this data to obtain the scores for each" -" person." +msgid "We already know which questions will be part of the cognitive ability test. Now we are going to process this data to obtain the scores for each person." msgstr "" #: ../../workshops/scientific-computing.rst:478 @@ -3990,9 +2854,7 @@ msgid "First, we make a copy of the original dataset:" msgstr "" #: ../../workshops/scientific-computing.rst:484 -msgid "" -"Then, we find the correct answer to each test question (these answers are" -" in ``test_items``)." +msgid "Then, we find the correct answer to each test question (these answers are in ``test_items``)." msgstr "" #: ../../workshops/scientific-computing.rst:493 @@ -4000,56 +2862,27 @@ msgid "The correct answers have been stored in the ``test_items`` dataframe." msgstr "" #: ../../workshops/scientific-computing.rst:495 -msgid "" -"Next, we will indicate, in the ``ca_test`` dataframe, whether the person " -"answered correctly to each question selected in the cognitive ability " -"test. These answers will be entered as a boolean in new variables with " -"the prefix \"resp\\_\" followed by the corresponding question code. The " -"Boolean is calculated with the function ``lambda row: row[q] == a, " -"axis=1``." +msgid "Next, we will indicate, in the ``ca_test`` dataframe, whether the person answered correctly to each question selected in the cognitive ability test. These answers will be entered as a boolean in new variables with the prefix \"resp\\_\" followed by the corresponding question code. The Boolean is calculated with the function ``lambda row: row[q] == a, axis=1``." msgstr "" #: ../../workshops/scientific-computing.rst:510 -msgid "" -"Some ``test_items`` questions are not in the data but don't worry about " -"that. We use a ``try... except`` block to ignore these errors. Answering " -"these questions was optional, so many OkCupid site users did not answer " -"all of them. So we have removed from the records the users who did not " -"answer the 14 questions we have chosen for the cognitive ability test. " -"This reduced the sample size considerably. There are other ways to avoid " -"this reduction, but they are outside the scope of this workshop." +msgid "Some ``test_items`` questions are not in the data but don't worry about that. We use a ``try... except`` block to ignore these errors. Answering these questions was optional, so many OkCupid site users did not answer all of them. So we have removed from the records the users who did not answer the 14 questions we have chosen for the cognitive ability test. This reduced the sample size considerably. There are other ways to avoid this reduction, but they are outside the scope of this workshop." msgstr "" #: ../../workshops/scientific-computing.rst:512 -msgid "" -"We want to sum the correct answers for each person, but some integer " -"results were stored as strings, so let's fix that:" +msgid "We want to sum the correct answers for each person, but some integer results were stored as strings, so let's fix that:" msgstr "" #: ../../workshops/scientific-computing.rst:524 -msgid "" -"Now that we have the correct answer for each test question, let's add up " -"each correct answer for each person. There are 14 questions, so the " -"maximum score will also be 14:" +msgid "Now that we have the correct answer for each test question, let's add up each correct answer for each person. There are 14 questions, so the maximum score will also be 14:" msgstr "" #: ../../workshops/scientific-computing.rst:531 -msgid "" -"How do we add up these responses? Remember that each answer was stored as" -" a boolean (True or False) with the prefix \"resp\\_\". So we search in " -"the ``ca_test`` dataframe for the answers of each column starting with " -"\"resp\" (we use the regular expression ``regex=\"^resp\"`` and the " -"method ``filter``) and sum the True values of each row with " -"``sum(axis=1)``. Then we store these results in the \"cognitive_score\" " -"column of the ``ca_test`` dataset." +msgid "How do we add up these responses? Remember that each answer was stored as a boolean (True or False) with the prefix \"resp\\_\". So we search in the ``ca_test`` dataframe for the answers of each column starting with \"resp\" (we use the regular expression ``regex=\"^resp\"`` and the method ``filter``) and sum the True values of each row with ``sum(axis=1)``. Then we store these results in the \"cognitive_score\" column of the ``ca_test`` dataset." msgstr "" #: ../../workshops/scientific-computing.rst:533 -msgid "" -"You can see the results of these operations by typing in the IPython " -"Console ``ca_test.cognitive_score.describe()``. If you do so, in *count* " -"you will see that the new number of records has been reduced to 479 (the " -"rest of the 68,371 users did not answer all of these questions)." +msgid "You can see the results of these operations by typing in the IPython Console ``ca_test.cognitive_score.describe()``. If you do so, in *count* you will see that the new number of records has been reduced to 479 (the rest of the 68,371 users did not answer all of these questions)." msgstr "" #: ../../workshops/scientific-computing.rst:537 @@ -4060,20 +2893,16 @@ msgstr "" msgid "Let's draw a histogram of this variable to see the frequency distribution." msgstr "" +#: ../../workshops/scientific-computing.rst:546 +msgid "Cognitive test score histogram" +msgstr "" + #: ../../workshops/scientific-computing.rst:549 -msgid "" -"As you can see, in this case, the distribution is not symmetrical but has" -" a long \"tail\" on the left (negatively skewed). This means that most of" -" the users who answered all the questions did quite well and that only a " -"few users answered most of the questions in the wrong way." +msgid "As you can see, in this case, the distribution is not symmetrical but has a long \"tail\" on the left (negatively skewed). This means that most of the users who answered all the questions did quite well and that only a few users answered most of the questions in the wrong way." msgstr "" #: ../../workshops/scientific-computing.rst:553 -msgid "" -"The values we have calculated in this section were already in the data " -"(``data.CA_items``). However, we have chosen to obtain these results " -"again using code because it is a good way to learn how to use the tools " -"provided by Python and Pandas for data manipulation." +msgid "The values we have calculated in this section were already in the data (``data.CA_items``). However, we have chosen to obtain these results again using code because it is a good way to learn how to use the tools provided by Python and Pandas for data manipulation." msgstr "" #: ../../workshops/scientific-computing.rst:559 @@ -4081,65 +2910,36 @@ msgid "Relate variables" msgstr "" #: ../../workshops/scientific-computing.rst:561 -msgid "" -"Remember that the hypothesis relates two variables: which pet do you " -"prefer and cognitive ability. The measurement of pet preferences will be " -"made from question **q997** (categorical or qualitative variable) and " -"cognitive ability will be measured from the sum of the correct answers on" -" the test (quantitative interval variable). With this type of variable we" -" can make some box plots to see if there are differences between the " -"means." +msgid "Remember that the hypothesis relates two variables: which pet do you prefer and cognitive ability. The measurement of pet preferences will be made from question **q997** (categorical or qualitative variable) and cognitive ability will be measured from the sum of the correct answers on the test (quantitative interval variable). With this type of variable we can make some box plots to see if there are differences between the means." msgstr "" #: ../../workshops/scientific-computing.rst:563 -msgid "" -"But first, let's change the standard Seaborn palette, to get prettier " -"plots." +msgid "But first, let's change the standard Seaborn palette, to get prettier plots." msgstr "" #: ../../workshops/scientific-computing.rst:573 -msgid "" -"Seaborn allows you to choose from different styles of graphics and color " -"palettes. More information is available at " -"https://seaborn.pydata.org/tutorial/color_palettes.html" +msgid "Seaborn allows you to choose from different styles of graphics and color palettes. More information is available at https://seaborn.pydata.org/tutorial/color_palettes.html" msgstr "" #: ../../workshops/scientific-computing.rst:575 -msgid "" -"Now, we are going to create box plots to observe the relationship between" -" variables. To do this, we will use the ``catplot`` class of Seaborn. The" -" first argument will be the x-axis, which in this case will be the " -"qualitative variable (question **q997**). The second argument will be the" -" y-axis, where we will place the quantitative variable (cognitive score)." -" With the parameter ``kind`` we indicate that it is a box plot. The " -"parameters ``height`` and ``aspect`` regulate the appearance of the " -"graph. The last parameter, ``data``, indicates where the data comes from." +msgid "Now, we are going to create box plots to observe the relationship between variables. To do this, we will use the ``catplot`` class of Seaborn. The first argument will be the x-axis, which in this case will be the qualitative variable (question **q997**). The second argument will be the y-axis, where we will place the quantitative variable (cognitive score). With the parameter ``kind`` we indicate that it is a box plot. The parameters ``height`` and ``aspect`` regulate the appearance of the graph. The last parameter, ``data``, indicates where the data comes from." +msgstr "" + +#: ../../workshops/scientific-computing.rst:583 +msgid "Pet preferences and cognitive score relationship (boxplot)" msgstr "" #: ../../workshops/scientific-computing.rst:586 #, python-format -msgid "" -"Box plots or box-whisker diagrams display, near the center of the box, " -"the **mean** of the data as a horizontal line. The lines bordering the " -"box represent **50% of the observations** (*interquartile range* ). " -"Outside the box, upwards and downwards, we find two whiskers: the lower " -"one represents the **mean of the values in the lower part of the " -"dataset**, and the upper one represents the **mean of the values in the " -"upper part of the dataset**. The points beyond the whiskers are " -"**outliers**." +msgid "Box plots or box-whisker diagrams display, near the center of the box, the **mean** of the data as a horizontal line. The lines bordering the box represent **50% of the observations** (*interquartile range* ). Outside the box, upwards and downwards, we find two whiskers: the lower one represents the **mean of the values in the lower part of the dataset**, and the upper one represents the **mean of the values in the upper part of the dataset**. The points beyond the whiskers are **outliers**." msgstr "" #: ../../workshops/scientific-computing.rst:590 -msgid "" -"An outlier is a value that is very different from the rest of the data " -"values. They must be taken into account because they can often create a " -"bias in the model we are trying to fit to the data." +msgid "An outlier is a value that is very different from the rest of the data values. They must be taken into account because they can often create a bias in the model we are trying to fit to the data." msgstr "" #: ../../workshops/scientific-computing.rst:592 -msgid "" -"The graph shows four boxes measuring cognitive ability for the following " -"groups:" +msgid "The graph shows four boxes measuring cognitive ability for the following groups:" msgstr "" #: ../../workshops/scientific-computing.rst:594 @@ -4159,41 +2959,23 @@ msgid "Those who like neither cats nor dogs." msgstr "" #: ../../workshops/scientific-computing.rst:599 -msgid "" -"The lowest mean is that of those who prefer dogs only, but by very " -"little. The box (and boundaries) representing dog lovers is also " -"\"wider,\" implying a larger variability in the individual test results " -"for this group. But this is not a very different dispersion from that of " -"those who prefer cats. All the means are within the limits of the other " -"boxes (interquartiles), which seems to indicate that, in fact, there are " -"not really important differences in the intelligence test scores for " -"these groups. This seems to undermine support for the initial hypothesis " -"we posed above." +msgid "The lowest mean is that of those who prefer dogs only, but by very little. The box (and boundaries) representing dog lovers is also \"wider,\" implying a larger variability in the individual test results for this group. But this is not a very different dispersion from that of those who prefer cats. All the means are within the limits of the other boxes (interquartiles), which seems to indicate that, in fact, there are not really important differences in the intelligence test scores for these groups. This seems to undermine support for the initial hypothesis we posed above." msgstr "" #: ../../workshops/scientific-computing.rst:603 -msgid "" -"If you want to see the figures, enter ``dog_or_cat = " -"ca_test.groupby(\"q997\")[\"cognitive_score\"].describe()`` in the " -"IPython Console and look at the results in the Variable Explorer. This " -"way you can see how many people prefer cats or dogs, and the means and " -"standard deviation of the cognitive ability test results for each group." +msgid "If you want to see the figures, enter ``dog_or_cat = ca_test.groupby(\"q997\")[\"cognitive_score\"].describe()`` in the IPython Console and look at the results in the Variable Explorer. This way you can see how many people prefer cats or dogs, and the means and standard deviation of the cognitive ability test results for each group." msgstr "" #: ../../workshops/scientific-computing.rst:605 -msgid "" -"To appreciate in context the real difference in the averages, let's " -"create some bar charts. We are now going to use Seaborn's barplot class. " -"On the x-axis we put again the qualitative variable (**q997**) and on the" -" y-axis the quantitative variable (cognitive_score). The data parameter " -"takes as argument the entire dataset." +msgid "To appreciate in context the real difference in the averages, let's create some bar charts. We are now going to use Seaborn's barplot class. On the x-axis we put again the qualitative variable (**q997**) and on the y-axis the quantitative variable (cognitive_score). The data parameter takes as argument the entire dataset." +msgstr "" + +#: ../../workshops/scientific-computing.rst:617 +msgid "Pet preferences and cognitive score mean representation (box graph)" msgstr "" #: ../../workshops/scientific-computing.rst:620 -msgid "" -"If the box plots indicated that the means did not show significant " -"differences (possibly due to chance), the bar plot confirms that these " -"differences are, in proportion, quite modest." +msgid "If the box plots indicated that the means did not show significant differences (possibly due to chance), the bar plot confirms that these differences are, in proportion, quite modest." msgstr "" #: ../../workshops/scientific-computing.rst:626 @@ -4201,36 +2983,19 @@ msgid "ANOVA test" msgstr "" #: ../../workshops/scientific-computing.rst:628 -msgid "" -"To make sure that the differences between the means are statistically " -"significant, we will perform an ANOVA (analysis of variance) because we " -"are going to compare the means of more than two groups." +msgid "To make sure that the differences between the means are statistically significant, we will perform an ANOVA (analysis of variance) because we are going to compare the means of more than two groups." msgstr "" #: ../../workshops/scientific-computing.rst:630 -msgid "" -"How does ANOVA work? This analysis tells us whether three or more means " -"are equal. If so, this would support the null hypothesis." +msgid "How does ANOVA work? This analysis tells us whether three or more means are equal. If so, this would support the null hypothesis." msgstr "" #: ../../workshops/scientific-computing.rst:634 -msgid "" -"The *null hypothesis* is an alternative prediction to the one we have " -"stated in our hypothesis. The null hypothesis simply states that the " -"observed differences in means are due to random variations that occur " -"when samples are collected." +msgid "The *null hypothesis* is an alternative prediction to the one we have stated in our hypothesis. The null hypothesis simply states that the observed differences in means are due to random variations that occur when samples are collected." msgstr "" #: ../../workshops/scientific-computing.rst:636 -msgid "" -"An ANOVA produces an *F-ratio* (also called F-statistic) that compares " -"the amount of systematic variation in the data (variation that can be " -"explained by the model or hypothesis) with the amount of unsystematic " -"variance (variation that cannot be explained by our hypothesis or model)." -" This means that F is the ratio of the model to its error. ANOVA also " -"produces a *p-value* that indicates the probability that the variation " -"can be attributed to the null hypothesis. The smaller the p-value, the " -"less likely it is that the observed variation is due to chance." +msgid "An ANOVA produces an *F-ratio* (also called F-statistic) that compares the amount of systematic variation in the data (variation that can be explained by the model or hypothesis) with the amount of unsystematic variance (variation that cannot be explained by our hypothesis or model). This means that F is the ratio of the model to its error. ANOVA also produces a *p-value* that indicates the probability that the variation can be attributed to the null hypothesis. The smaller the p-value, the less likely it is that the observed variation is due to chance." msgstr "" #: ../../workshops/scientific-computing.rst:640 @@ -4238,68 +3003,43 @@ msgid "Formatting the data" msgstr "" #: ../../workshops/scientific-computing.rst:642 -msgid "" -"To perform an ANOVA, let's start by pivoting the dataset with the " -"cognitive ability test results. The pet preferences values will now be " -"the column names, and each row will represent a person." +msgid "To perform an ANOVA, let's start by pivoting the dataset with the cognitive ability test results. The pet preferences values will now be the column names, and each row will represent a person." msgstr "" #: ../../workshops/scientific-computing.rst:646 -msgid "" -"To perform an ANOVA, certain requirements or assumptions must be met. For" -" example, the distributions of the residuals must be normal. This is not " -"the case here. There are more appropriate statistical tests for this " -"example, and the possibility of performing certain transformations on the" -" data in order to apply ANOVA in this case. However, we use ANOVA because" -" it is a fairly popular test, and because the purpose of this workshop is" -" to serve as an introduction to scientific computing with Spyder. We do " -"not intend here to obtain scientific results for publication." +msgid "To perform an ANOVA, certain requirements or assumptions must be met. For example, the distributions of the residuals must be normal. This is not the case here. There are more appropriate statistical tests for this example, and the possibility of performing certain transformations on the data in order to apply ANOVA in this case. However, we use ANOVA because it is a fairly popular test, and because the purpose of this workshop is to serve as an introduction to scientific computing with Spyder. We do not intend here to obtain scientific results for publication." msgstr "" #: ../../workshops/scientific-computing.rst:652 -msgid "" -"You will see that one of the columns includes the answers to the test " -"made by people who did not specify their preferences towards pets. Let's " -"delete that column." +msgid "You will see that one of the columns includes the answers to the test made by people who did not specify their preferences towards pets. Let's delete that column." +msgstr "" + +#: ../../workshops/scientific-computing.rst:658 +msgid "Pet preferences pivot table for ANOVA analysis." msgstr "" #: ../../workshops/scientific-computing.rst:661 -msgid "" -"Now let's rename the column names (for simplicity) and remove the records" -" that have missing values (with ``dropna``). The argument " -"``inplace=True`` allows you to directly modify a dataframe without having" -" to create a new one." +msgid "Now let's rename the column names (for simplicity) and remove the records that have missing values (with ``dropna``). The argument ``inplace=True`` allows you to directly modify a dataframe without having to create a new one." msgstr "" #: ../../workshops/scientific-computing.rst:671 -msgid "" -"In the variable ``dog_or_cat_col_names`` we have stored the names of the " -"values in order. This implies that: A = Both, B = Cats, C = Dogs, and D =" -" Neither." +msgid "In the variable ``dog_or_cat_col_names`` we have stored the names of the values in order. This implies that: A = Both, B = Cats, C = Dogs, and D = Neither." msgstr "" #: ../../workshops/scientific-computing.rst:673 -msgid "" -"To perform ANOVA, we are going to use a Python library called \"stats\", " -"in particular the ``f_oneway`` function. You can find more information " -"about this library by typing ``stats`` in the Help Pane or learn more " -"about the function by typing ``stats.f_oneway``." +msgid "To perform ANOVA, we are going to use a Python library called \"stats\", in particular the ``f_oneway`` function. You can find more information about this library by typing ``stats`` in the Help Pane or learn more about the function by typing ``stats.f_oneway``." +msgstr "" + +#: ../../workshops/scientific-computing.rst:675 +msgid "stats.f_oneway() help in Spyder's Help pane" msgstr "" #: ../../workshops/scientific-computing.rst:678 -msgid "" -"The help notes that this function requires an array-like with the " -"measurements for each group as an input (in our case, one sample for A, " -"one for B, one for C, and one for D). Since we have empty cells in each " -"column, let's remove them from each column (the ``f_oneway`` function " -"does not support missing values)." +msgid "The help notes that this function requires an array-like with the measurements for each group as an input (in our case, one sample for A, one for B, one for C, and one for D). Since we have empty cells in each column, let's remove them from each column (the ``f_oneway`` function does not support missing values)." msgstr "" #: ../../workshops/scientific-computing.rst:684 -msgid "" -"In the above line of code we are creating a list with 4 elements: the " -"test results of each column A, B, C, and D, without the missing values " -"(they are removed with ``dropna()``)." +msgid "In the above line of code we are creating a list with 4 elements: the test results of each column A, B, C, and D, without the missing values (they are removed with ``dropna()``)." msgstr "" #: ../../workshops/scientific-computing.rst:688 @@ -4307,56 +3047,27 @@ msgid "Run ANOVA" msgstr "" #: ../../workshops/scientific-computing.rst:690 -msgid "" -"Now, let's run ANOVA and store the output in two variables: ``f_value`` " -"and ``p_value``. Notice that since ``dog_or_cat_samples`` is a list, we " -"must pass the argument with an asterisk (``*dog_or_cat_samples``)." +msgid "Now, let's run ANOVA and store the output in two variables: ``f_value`` and ``p_value``. Notice that since ``dog_or_cat_samples`` is a list, we must pass the argument with an asterisk (``*dog_or_cat_samples``)." msgstr "" #: ../../workshops/scientific-computing.rst:696 -msgid "" -"With the help of ``stats.f_oneway`` in the Help Pane you can read a " -"description of the output of this function, some interesting notes about " -"the test, and some references that you can use to better understand the " -"nature of this analysis." +msgid "With the help of ``stats.f_oneway`` in the Help Pane you can read a description of the output of this function, some interesting notes about the test, and some references that you can use to better understand the nature of this analysis." msgstr "" #: ../../workshops/scientific-computing.rst:700 -msgid "" -"In the Help pane you will read that ANOVA requires certain assumptions to" -" be satisfied. In this workshop we have not checked those assumptions " -"because our goal is merely to show some Spyder functions that make the " -"research work easier. Thus, the results obtained in this example with " -"ANOVA should not be taken too rigorously." +msgid "In the Help pane you will read that ANOVA requires certain assumptions to be satisfied. In this workshop we have not checked those assumptions because our goal is merely to show some Spyder functions that make the research work easier. Thus, the results obtained in this example with ANOVA should not be taken too rigorously." msgstr "" #: ../../workshops/scientific-computing.rst:702 -msgid "" -"In the Variable Explorer you can find these two new variables: " -"``f_value`` and ``p_value``. ``p_value`` (0.6275) is well over 0.05, " -"which gives support to the null hypothesis (detracting support from our " -"hypothesis). To know if the F value obtained is greater than the " -"theoretically expected value, a **F critical value** must be calculated. " -"This can be estimated using the ``stats`` library, a significance level " -"(*q* ), and the degrees of freedom (*df* ) for the number of groups and " -"the number of observations:" +msgid "In the Variable Explorer you can find these two new variables: ``f_value`` and ``p_value``. ``p_value`` (0.6275) is well over 0.05, which gives support to the null hypothesis (detracting support from our hypothesis). To know if the F value obtained is greater than the theoretically expected value, a **F critical value** must be calculated. This can be estimated using the ``stats`` library, a significance level (*q* ), and the degrees of freedom (*df* ) for the number of groups and the number of observations:" msgstr "" #: ../../workshops/scientific-computing.rst:713 -msgid "" -"The value of ``f_critical`` (2.6241) is larger than that of ``f_value`` " -"(0.5813). This means that the variance between the means of these groups " -"is not significantly different. Since the *p* value indicates that we " -"cannot rule out random variations, then we have to discard our " -"hypothesis." +msgid "The value of ``f_critical`` (2.6241) is larger than that of ``f_value`` (0.5813). This means that the variance between the means of these groups is not significantly different. Since the *p* value indicates that we cannot rule out random variations, then we have to discard our hypothesis." msgstr "" #: ../../workshops/scientific-computing.rst:715 -msgid "" -"What is the conclusion of all this? There seems to be little or no " -"evidence in our data to think that there is indeed a correlation between " -"a person's pet preferences and his or her ability to solve practical or " -"abstract problems. Cat and dog owners, rejoice!" +msgid "What is the conclusion of all this? There seems to be little or no evidence in our data to think that there is indeed a correlation between a person's pet preferences and his or her ability to solve practical or abstract problems. Cat and dog owners, rejoice!" msgstr "" #: ../../workshops/scientific-computing.rst:721 @@ -4364,11 +3075,7 @@ msgid "Report and share" msgstr "" #: ../../workshops/scientific-computing.rst:723 -msgid "" -"In science, sharing results, good and bad, is critical. Today, in " -"scientific computing, it is also crucial to share data, and the code used" -" to process and analyze it. To help with this, we will use Spyder's Code " -"Analysis." +msgid "In science, sharing results, good and bad, is critical. Today, in scientific computing, it is also crucial to share data, and the code used to process and analyze it. To help with this, we will use Spyder's Code Analysis." msgstr "" #: ../../workshops/scientific-computing.rst:727 @@ -4376,18 +3083,15 @@ msgid "Code Analysis" msgstr "" #: ../../workshops/scientific-computing.rst:729 -msgid "" -"When you share code, you want it to be readable, clean, and not overly " -"complex. The Code Analysis component can help us detect these issues and " -"even bugs that can affect the performance of our code." +msgid "When you share code, you want it to be readable, clean, and not overly complex. The Code Analysis component can help us detect these issues and even bugs that can affect the performance of our code." msgstr "" #: ../../workshops/scientific-computing.rst:731 -msgid "" -"To see an example, you can open the :download:`scientific-computing-" -"astro.py ` file and run the " -":guilabel:`Code Analysis` (open the file in the pane and click on the " -"green triangular button in the upper right corner)." +msgid "To see an example, you can open the :download:`scientific-computing-astro.py ` file and run the :guilabel:`Code Analysis` (open the file in the pane and click on the green triangular button in the upper right corner)." +msgstr "" + +#: ../../workshops/scientific-computing.rst:733 +msgid "Code Analysis pane Example for astrological sign and cognitive ability" msgstr "" #: ../../workshops/scientific-computing.rst:736 @@ -4411,39 +3115,23 @@ msgid "Error: probable bugs in the code" msgstr "" #: ../../workshops/scientific-computing.rst:743 -msgid "" -"Each of these categories indicates the type of alert and the line on " -"which the potential issue occurs. For example, it tells us that line 129 " -"is too long, or that we imported numpy but did not use it at all in the " -"code." +msgid "Each of these categories indicates the type of alert and the line on which the potential issue occurs. For example, it tells us that line 129 is too long, or that we imported numpy but did not use it at all in the code." msgstr "" #: ../../workshops/scientific-computing.rst:745 -msgid "" -"These suggestions can contribute to sharing clean code. We recommend " -"using this panel to polish your code before publishing it." +msgid "These suggestions can contribute to sharing clean code. We recommend using this panel to polish your code before publishing it." msgstr "" #: ../../workshops/scientific-computing.rst:753 -msgid "" -"In this workshop we have taken the first steps to use Spyder for " -"scientific computing. We have seen how from a question or doubt a " -"hypothesis is raised. This question can also emerge from the exploration " -"of some data, which can be done by calculating some measures (such as " -"mean, median, standard deviation) or by drawing some plots." +msgid "In this workshop we have taken the first steps to use Spyder for scientific computing. We have seen how from a question or doubt a hypothesis is raised. This question can also emerge from the exploration of some data, which can be done by calculating some measures (such as mean, median, standard deviation) or by drawing some plots." msgstr "" #: ../../workshops/scientific-computing.rst:755 -msgid "" -"Often, in order to answer the question, we must process some data (for " -"example, for the construction of a cognitive ability test)." +msgid "Often, in order to answer the question, we must process some data (for example, for the construction of a cognitive ability test)." msgstr "" #: ../../workshops/scientific-computing.rst:757 -msgid "" -"Finally, we try to establish a relationship between variables with some " -"statistical tests. The results of these tests will support or not our " -"initial hypothesis." +msgid "Finally, we try to establish a relationship between variables with some statistical tests. The results of these tests will support or not our initial hypothesis." msgstr "" #: ../../workshops/scientific-computing.rst:762 @@ -4471,32 +3159,19 @@ msgid "Improve code readability with Code Analysis." msgstr "" #: ../../workshops/scientific-computing.rst:772 -msgid "" -"Spyder has many features that can help you do data analysis. You can find" -" more information in our `official documentation `_." +msgid "Spyder has many features that can help you do data analysis. You can find more information in our `official documentation `_." msgstr "" #: ../../workshops/scientific-computing.rst:782 -msgid "" -"If you want to check what you have learned, we suggest you analyze the " -"data to try to answer the following question: *Do the different zodiac " -"signs influence the results of a cognitive ability test?,* you can check " -"the Python script :download:`scientific-computing-astro.py ` if you have any doubts." +msgid "If you want to check what you have learned, we suggest you analyze the data to try to answer the following question: *Do the different zodiac signs influence the results of a cognitive ability test?,* you can check the Python script :download:`scientific-computing-astro.py ` if you have any doubts." msgstr "" #: ../../workshops/scientific-computing.rst:790 -msgid "" -"For a description of the dataset used, see the following `paper " -"`__:" +msgid "For a description of the dataset used, see the following `paper `__:" msgstr "" #: ../../workshops/scientific-computing.rst:792 -msgid "" -"Kirkegaard, E. O. W., & Bjerrekær, J. D. (2016). *The OKCupid dataset: A " -"very large public dataset of dating site users*. Open Differential " -"Psychology. doi:10.26775/odp.2016.11.03*" +msgid "Kirkegaard, E. O. W., & Bjerrekær, J. D. (2016). *The OKCupid dataset: A very large public dataset of dating site users*. Open Differential Psychology. doi:10.26775/odp.2016.11.03*" msgstr "" #: ../../workshops/scientific-computing.rst:794 @@ -4504,8 +3179,6 @@ msgid "A very fun book for learning statistics with R is the following:" msgstr "" #: ../../workshops/scientific-computing.rst:796 -msgid "" -"Field, A., Miles, J., & Field, Z. (2012). *Discovering statistics using " -"R*. SAGE Publications." +msgid "Field, A., Miles, J., & Field, Z. (2012). *Discovering statistics using R*. SAGE Publications." msgstr "" diff --git a/doc/locales/pot/faq.pot b/doc/locales/pot/faq.pot index 6902e00b..0a83fdf0 100644 --- a/doc/locales/pot/faq.pot +++ b/doc/locales/pot/faq.pot @@ -1,19 +1,19 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../faq.rst:3 @@ -24,39 +24,32 @@ msgstr "" msgid "Installing and updating" msgstr "" +#: ../../faq.rst:0 +msgid "Q: How do I install Spyder?" +msgstr "" + #: ../../faq.rst:12 -msgid "" -"The easiest way to install Spyder is with the Anaconda Python " -"distribution, which comes with everything you need to get started in an " -"all-in-one package. Download it from its `webpage`_." +msgid "The easiest way to install Spyder is with the Anaconda Python distribution, which comes with everything you need to get started in an all-in-one package. Download it from its `webpage`_." msgstr "" #: ../../faq.rst:17 msgid "For more information, visit our :doc:`/installation`." msgstr "" +#: ../../faq.rst:0 +msgid "Q: How do I install Spyder on Windows Subsystem for Linux 2 (WSL2)?" +msgstr "" + #: ../../faq.rst:23 -msgid "" -"If you already installed Spyder on your Windows machine, you do not need " -"to reinstall it on a WSL2-based Linux environment if your code must run " -"there." +msgid "If you already installed Spyder on your Windows machine, you do not need to reinstall it on a WSL2-based Linux environment if your code must run there." msgstr "" #: ../../faq.rst:25 -msgid "" -"Instead, just install `Miniconda`_ inside WSL2 and create a new conda " -"environment (or use an existing conda- or virtualenv), then install " -"Spyder-Kernels into that environment with e.g. ``conda install spyder-" -"kernels``. You must manually install ``ipython_genutils`` with e.g. " -"``conda install ipython_genutils``." +msgid "Instead, just install `Miniconda`_ inside WSL2 and create a new conda environment (or use an existing conda- or virtualenv), then install Spyder-Kernels into that environment with e.g. ``conda install spyder-kernels``. You must manually install ``ipython_genutils`` with e.g. ``conda install ipython_genutils``." msgstr "" #: ../../faq.rst:30 -msgid "" -"Windows creates a network path located at ``\\\\wsl$`` that points to the" -" partitions of your WSL2 machines, e.g. ``\\\\wsl$\\Ubuntu-20.04``. You " -"**must** map a network drive letter to your machine path, e.g. ``W:``, " -"for Spyder to correctly see its files and folders." +msgid "Windows creates a network path located at ``\\\\wsl$`` that points to the partitions of your WSL2 machines, e.g. ``\\\\wsl$\\Ubuntu-20.04``. You **must** map a network drive letter to your machine path, e.g. ``W:``, for Spyder to correctly see its files and folders." msgstr "" #: ../../faq.rst:33 @@ -64,22 +57,15 @@ msgid "To start a Spyder kernel, from your Linux terminal run" msgstr "" #: ../../faq.rst:39 -msgid "" -"It will run the kernel as a subprocess and create a file named " -":file:`remotemachine.json` in your WSL home folder." +msgid "It will run the kernel as a subprocess and create a file named :file:`remotemachine.json` in your WSL home folder." msgstr "" #: ../../faq.rst:41 -msgid "" -"Finally, under the options menu of Spyder's :doc:`panes/ipythonconsole`, " -"select :guilabel:`Connect to an existing kernel` as described in :ref" -":`connecting-external-kernel`. Insert the absolute path of " -":file:`remotemachine.json` into the :guilabel:`Connection file` field. If" -" you mapped ``W:`` as mentioned in above note, the path should be " -":file:`W:/home/{username}/remotemachine.json`. A new console will open in" -" Spyder, running in the Linux environment. Try running ``os.system('ls " -"-la')`` and see if it lists your WSL home folder. If you run ``exit()`` " -"from Spyder, the kernel running on Linux will be stopped." +msgid "Finally, under the options menu of Spyder's :doc:`panes/ipythonconsole`, select :guilabel:`Connect to an existing kernel` as described in :ref:`connecting-external-kernel`. Insert the absolute path of :file:`remotemachine.json` into the :guilabel:`Connection file` field. If you mapped ``W:`` as mentioned in above note, the path should be :file:`W:/home/{username}/remotemachine.json`. A new console will open in Spyder, running in the Linux environment. Try running ``os.system('ls -la')`` and see if it lists your WSL home folder. If you run ``exit()`` from Spyder, the kernel running on Linux will be stopped." +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: How do I update Spyder using conda?" msgstr "" #: ../../faq.rst:52 @@ -87,62 +73,67 @@ msgid "From the command line (or Anaconda prompt on Windows), run:" msgstr "" #: ../../faq.rst:59 -msgid "" -"If this results in an error or does not update Spyder to the latest " -"version, try:" +msgid "If this results in an error or does not update Spyder to the latest version, try:" +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: How do update I Spyder using Anaconda Navigator?" msgstr "" #: ../../faq.rst:69 -msgid "" -"Open the \"gear\" menu in Spyder's section under :guilabel:`Home` in " -"Navigator. Go to :guilabel:`Install specific version` and select the " -"version of Spyder you want to use. We strongly recommend the latest " -"available, to benefit from new features, bug fixes, performance " -"improvements and usability enhancements." +msgid "Open the \"gear\" menu in Spyder's section under :guilabel:`Home` in Navigator. Go to :guilabel:`Install specific version` and select the version of Spyder you want to use. We strongly recommend the latest available, to benefit from new features, bug fixes, performance improvements and usability enhancements." +msgstr "" + +#: ../../faq.rst:73 +msgid "Navigator showing installing specific version of Spyder" msgstr "" #: ../../faq.rst:80 msgid "Running Spyder" msgstr "" +#: ../../faq.rst:0 +msgid "Q: How do I run Spyder?" +msgstr "" + #: ../../faq.rst:85 msgid "You can launch it in any of the following ways:" msgstr "" #: ../../faq.rst:87 -msgid "" -"**From the command line**: Type ``spyder`` in your terminal (or Anaconda " -"prompt on Windows)." +msgid "**From the command line**: Type ``spyder`` in your terminal (or Anaconda prompt on Windows)." msgstr "" #: ../../faq.rst:89 -msgid "" -"**From Anaconda Navigator**: Scroll to :guilabel:`Spyder` under " -":guilabel:`Home`, and click :guilabel:`Launch`." +msgid "**From Anaconda Navigator**: Scroll to :guilabel:`Spyder` under :guilabel:`Home`, and click :guilabel:`Launch`." +msgstr "" + +#: ../../faq.rst:91 +msgid "Navigator showing running a specific version of Spyder" msgstr "" #: ../../faq.rst:94 msgid "***Windows Only***: Launch it via the Start menu shortcut." msgstr "" +#: ../../faq.rst:96 +msgid "Spyder shortcut in the Windows Start menu" +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: Can I try Spyder without installing it?" +msgstr "" + #: ../../faq.rst:103 -msgid "" -"Yes! With `Binder`_, you can work with a fully functional copy of Spyder " -"that runs right in your web browser. Try it `here`_." +msgid "Yes! With `Binder`_, you can work with a fully functional copy of Spyder that runs right in your web browser. Try it `here`_." +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: What are the system requirements for Spyder? How resource-intensive is it?" msgstr "" #: ../../faq.rst:114 -msgid "" -"Spyder works on modern versions of Windows, macOS and Linux (see the " -"table below for recommended versions) via Anaconda, as well as other " -"methods. It typically uses relatively minimal CPU when idle, and 0.5 GB -" -" 1 GB of RAM, depending on how long you've been using it and how many " -"files, projects, panes and consoles you have open. It should work on any " -"system with a dual-core or better x64 processor and at least 4 GB of RAM," -" although 8 GB is *strongly* recommended for best performance when " -"running other applications. However, the code you run, such as scientific" -" computation and deep learning models, may require additional resources " -"beyond this baseline for Spyder itself." +msgid "Spyder works on modern versions of Windows, macOS and Linux (see the table below for recommended versions) via Anaconda, as well as other methods. It typically uses relatively minimal CPU when idle, and 0.5 GB - 1 GB of RAM, depending on how long you've been using it and how many files, projects, panes and consoles you have open. It should work on any system with a dual-core or better x64 processor and at least 4 GB of RAM, although 8 GB is *strongly* recommended for best performance when running other applications. However, the code you run, such as scientific computation and deep learning models, may require additional resources beyond this baseline for Spyder itself." msgstr "" #: ../../faq.rst:122 @@ -177,18 +168,24 @@ msgstr "" msgid "Ubuntu 16.04" msgstr "" +#: ../../faq.rst:0 +msgid "Q: How do I run Spyder installed in a conda environment using Anaconda Navigator?" +msgstr "" + #: ../../faq.rst:133 -msgid "" -"Select the environment you want to launch Spyder from under " -":guilabel:`Applications on`. If Spyder is installed in this environment, " -"you will see it in Navigator's :guilabel:`Home` window. Click " -":guilabel:`Launch` to start Spyder in your selected environment." +msgid "Select the environment you want to launch Spyder from under :guilabel:`Applications on`. If Spyder is installed in this environment, you will see it in Navigator's :guilabel:`Home` window. Click :guilabel:`Launch` to start Spyder in your selected environment." +msgstr "" + +#: ../../faq.rst:137 +msgid "Navigator showing running Spyder in a specific environment" +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: How do I run Spyder installed in a conda environment using the command line?" msgstr "" #: ../../faq.rst:144 -msgid "" -"Activate your conda environment by typing the following in your terminal " -"(or Anaconda Prompt on Windows):" +msgid "Activate your conda environment by typing the following in your terminal (or Anaconda Prompt on Windows):" msgstr "" #: ../../faq.rst:150 @@ -199,279 +196,237 @@ msgstr "" msgid "Using Spyder" msgstr "" +#: ../../faq.rst:0 +msgid "Q: How do I install Python packages to use within Spyder if I installed Spyder with conda?" +msgstr "" + #: ../../faq.rst:163 -msgid "" -"The first approach for installing a package should be using conda. In " -"your system terminal (or Anaconda Prompt on Windows), type:" +msgid "The first approach for installing a package should be using conda. In your system terminal (or Anaconda Prompt on Windows), type:" msgstr "" #: ../../faq.rst:170 -msgid "" -"If your installation is not successful, follow steps 3 through 5 of Part " -"2 in our video on solving and avoiding problems with pip, Conda and " -"Conda-Forge." +msgid "If your installation is not successful, follow steps 3 through 5 of Part 2 in our video on solving and avoiding problems with pip, Conda and Conda-Forge." +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: How do I get Spyder to work with my existing Python packages/environment?" +msgstr "" + +#: ../../faq.rst:182 +msgid "To work with an existing environment in Spyder, change the default Python interpreter for new :doc:`/panes/ipythonconsole`\\s to point to this environment." msgstr "" #: ../../faq.rst:184 -msgid "" -"To work with an existing environment in Spyder, change the default Python" -" interpreter for new :doc:`/panes/ipythonconsole`\\s to point to this " -"environment." +msgid "To do so, open the :guilabel:`Python interpreter` section of Spyder's preferences (:menuselection:`Tools --> Preferences`, or :menuselection:`Spyder --> Preferences` on macOS). Here, select the option :guilabel:`Use the following Python interpreter`, and use the dropdown below to select your preferred environment. If it's not listed, see :ref:`the note below `." msgstr "" -#: ../../faq.rst:186 -msgid "" -"To do so, open the :guilabel:`Python interpreter` section of Spyder's " -"preferences (:menuselection:`Tools --> Preferences`, or " -":menuselection:`Spyder --> Preferences` on macOS). Here, select the " -"option :guilabel:`Use the following Python interpreter`, and use the " -"dropdown below to select your preferred environment. If it's not listed, " -"see :ref:`the note below `." +#: ../../faq.rst:188 +msgid "Preferences showing changing Python interpreter" +msgstr "" + +#: ../../faq.rst:195 +msgid "If you installed Miniconda (or another Conda-based distribution) to a non-default path, or are using a virtual environment managed by a tool other than ``pyenv``, your environments likely won't be listed." msgstr "" #: ../../faq.rst:197 -msgid "" -"If you installed Miniconda (or another Conda-based distribution) to a " -"non-default path, or are using a virtual environment managed by a tool " -"other than ``pyenv``, your environments likely won't be listed." +msgid "Instead, use the text box or the :guilabel:`Select file` button to enter the path to the Python interpreter you want to use. You can find this path by activating the venv or Conda env you want to use in your terminal (Anaconda Prompt on Windows), and running the command:" msgstr "" -#: ../../faq.rst:199 -msgid "" -"Instead, use the text box or the :guilabel:`Select file` button to enter " -"the path to the Python interpreter you want to use. You can find this " -"path by activating the venv or Conda env you want to use in your terminal" -" (Anaconda Prompt on Windows), and running the command:" +#: ../../faq.rst:204 +msgid "Finally, click :guilabel:`Restart kernel` in the :guilabel:`Consoles` menu for this change to take effect. If ``spyder-kernels`` is not already installed, the :doc:`/panes/ipythonconsole` will display instructions on how to install the right version. Execute the given command in your terminal (the Anaconda Prompt on Windows) with the environment activated, and finally restart the kernel once more." msgstr "" -#: ../../faq.rst:206 -msgid "" -"Finally, click :guilabel:`Restart kernel` in the :guilabel:`Consoles` " -"menu for this change to take effect. If ``spyder-kernels`` is not already" -" installed, the :doc:`/panes/ipythonconsole` will display instructions on" -" how to install the right version. Execute the given command in your " -"terminal (the Anaconda Prompt on Windows) with the environment activated," -" and finally restart the kernel once more." +#: ../../faq.rst:0 +msgid "Q: How do I install Python packages to use within Spyder if I downloaded Spyder from the standalone installers?" msgstr "" -#: ../../faq.rst:216 -msgid "" -"Watch our video on using additional packages or follow the instructions " -"below." +#: ../../faq.rst:212 +msgid "Watch our video on using additional packages or follow the instructions below." msgstr "" -#: ../../faq.rst:224 -msgid "" -"If you want to use other packages in Spyder that don't come with our " -"installer, you need to have your own Python distribution installed; we " -"recommend `Miniconda`_ or another Conda-based option. For Spyder to " -"recognize it automatically, you should use a Conda-based distribution " -"with its default install path." +#: ../../faq.rst:220 +msgid "If you want to use other packages in Spyder that don't come with our installer, you need to have your own Python distribution installed; we recommend `Miniconda`_ or another Conda-based option. For Spyder to recognize it automatically, you should use a Conda-based distribution with its default install path." msgstr "" -#: ../../faq.rst:229 -msgid "" -"Create a new conda environment containing ``spyder-kernels`` and the " -"packages that you want to use. For example, if you want to use ``scikit-" -"learn``, open your terminal (or Anaconda prompt on Windows) and run the " -"following command:" +#: ../../faq.rst:225 +msgid "Create a new conda environment containing ``spyder-kernels`` and the packages that you want to use. For example, if you want to use ``scikit-learn``, open your terminal (or Anaconda prompt on Windows) and run the following command:" msgstr "" -#: ../../faq.rst:236 -msgid "" -"Finally, connect Spyder to this ``my-env`` environment by changing " -"Spyder's default Python interpreter, following the instructions in " -":ref:`the above answer `." +#: ../../faq.rst:232 +msgid "Finally, connect Spyder to this ``my-env`` environment by changing Spyder's default Python interpreter, following the instructions in :ref:`the above answer `." msgstr "" -#: ../../faq.rst:242 -msgid "" -"Either use the :guilabel:`Reset Spyder to factory defaults` under " -":guilabel:`Tools` in Spyder's menu bar, the :guilabel:`Reset Spyder " -"settings` Start menu shortcut (Windows), or run ``spyder --reset`` in " -"your system terminal (Anaconda prompt on Windows)." +#: ../../faq.rst:0 +msgid "Q: How do I reset Spyder's preferences to the defaults?" msgstr "" -#: ../../faq.rst:251 -msgid "" -"Under :guilabel:`General` in Spyder's :guilabel:`Preferences`, go to the " -":guilabel:`Advanced settings` tab and select your language from the " -"options displayed under :guilabel:`Language`." +#: ../../faq.rst:238 +msgid "Either use the :guilabel:`Reset Spyder to factory defaults` under :guilabel:`Tools` in Spyder's menu bar, the :guilabel:`Reset Spyder settings` Start menu shortcut (Windows), or run ``spyder --reset`` in your system terminal (Anaconda prompt on Windows)." +msgstr "" + +#: ../../faq.rst:240 +msgid "Spyder reset button in tools" +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: How do I change Spyder's language?" +msgstr "" + +#: ../../faq.rst:247 +msgid "Under :guilabel:`General` in Spyder's :guilabel:`Preferences`, go to the :guilabel:`Advanced settings` tab and select your language from the options displayed under :guilabel:`Language`." +msgstr "" + +#: ../../faq.rst:249 +msgid "Spyder change language in preferences." +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: How do I use code cells in Spyder?" +msgstr "" + +#: ../../faq.rst:256 +msgid "To create a cell in Spyder's :doc:`/panes/editor`, type ``#%%`` in your script. Each ``#%%`` will make a new cell. To run a cell, press :kbd:`Shift-Enter` (while your cursor is focused on it) or use the :guilabel:`Run current cell` button in Spyder's toolbar." msgstr "" #: ../../faq.rst:260 -#, python-format -msgid "" -"To create a cell in Spyder's :doc:`/panes/editor`, type ``#%%`` in your " -"script. Each ``#%%`` will make a new cell. To run a cell, press :kbd" -":`Shift-Enter` (while your cursor is focused on it) or use the " -":guilabel:`Run current cell` button in Spyder's toolbar." +#: ../../faq.rst:295 +#: ../../faq.rst:304 +#: ../../faq.rst:313 +msgid "Spyder showing cell generation." msgstr "" -#: ../../faq.rst:271 -msgid "" -"Spyder plugins are available in the ``conda-forge`` conda channel. To " -"install one, type on the command line (or Anaconda Prompt on Windows):" +#: ../../faq.rst:0 +msgid "Q: How do I use plugins with Spyder (e.g. Spyder-Notebook, Spyder-Terminal, Spyder-Unittest)?" msgstr "" -#: ../../faq.rst:278 -msgid "" -"Replace ```` with the name of the plugin you want to use. For " -"more information on a specific plugin, go to the its repository:" +#: ../../faq.rst:267 +msgid "Spyder plugins are available in the ``conda-forge`` conda channel. To install one, type on the command line (or Anaconda Prompt on Windows):" msgstr "" -#: ../../faq.rst:281 +#: ../../faq.rst:274 +msgid "Replace ```` with the name of the plugin you want to use. For more information on a specific plugin, go to the its repository:" +msgstr "" + +#: ../../faq.rst:277 msgid "`spyder-unittest`_" msgstr "" -#: ../../faq.rst:282 +#: ../../faq.rst:278 msgid "`spyder-terminal`_" msgstr "" -#: ../../faq.rst:283 +#: ../../faq.rst:279 msgid "`spyder-notebook`_" msgstr "" -#: ../../faq.rst:284 +#: ../../faq.rst:280 msgid "`spyder-memory-profiler`_" msgstr "" -#: ../../faq.rst:285 +#: ../../faq.rst:281 msgid "`spyder-line-profiler`_" msgstr "" -#: ../../faq.rst:297 -msgid "" -"Check the option :guilabel:`Remove all variables before execution` in the" -" :guilabel:`Configuration per file...` dialog under the :guilabel:`Run` " -"menu." +#: ../../faq.rst:0 +msgid "Q: How do I clear all variables before executing my code?" msgstr "" -#: ../../faq.rst:306 -msgid "" -"Select the appropriate option in the :guilabel:`Configuration per " -"file...` dialog under the :guilabel:`Run` menu." +#: ../../faq.rst:293 +msgid "Check the option :guilabel:`Remove all variables before execution` in the :guilabel:`Configuration per file...` dialog under the :guilabel:`Run` menu." msgstr "" -#: ../../faq.rst:315 -msgid "" -"Go to :guilabel:`Preferences` and select the theme you want under " -":guilabel:`Syntax highlighting theme` in the :guilabel:`Appearance` " -"section." +#: ../../faq.rst:0 +msgid "Q: How do I run my code in a dedicated console or an external system terminal?" +msgstr "" + +#: ../../faq.rst:302 +msgid "Select the appropriate option in the :guilabel:`Configuration per file...` dialog under the :guilabel:`Run` menu." +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: How do I change the syntax highlighting theme in the Editor?" +msgstr "" + +#: ../../faq.rst:311 +msgid "Go to :guilabel:`Preferences` and select the theme you want under :guilabel:`Syntax highlighting theme` in the :guilabel:`Appearance` section." msgstr "" -#: ../../faq.rst:324 +#: ../../faq.rst:320 msgid "Troubleshooting" msgstr "" -#: ../../faq.rst:329 -msgid "" -"You should first follow the steps in our :doc:`troubleshooting " -"guide`. If you can't solve your problem, " -"open an issue by following the instructions in our " -":doc:`/troubleshooting/submit-a-report` section." +#: ../../faq.rst:0 +msgid "Q: I've found a bug or issue with Spyder. What do I do?" msgstr "" -#: ../../faq.rst:336 -msgid "" -"First, make sure the error you are seeing is not a bug in your code. To " -"confirm this, try running it in any standard Python interpreter. If the " -"error still occurs, the problem is likely with your code and a site like " -"`Stack Overflow`_ might be the best place to start. Otherwise, start at " -"the :doc:`/troubleshooting/basic-first-aid` section of our " -"troubleshooting guide." +#: ../../faq.rst:325 +msgid "You should first follow the steps in our :doc:`troubleshooting guide`. If you can't solve your problem, open an issue by following the instructions in our :doc:`/troubleshooting/submit-a-report` section." msgstr "" -#: ../../faq.rst:347 -msgid "" -"If nothing is displayed in the calltip, hover hint or :doc:`/panes/help` " -"pane, make sure the object you are inspecting has a docstring, and try " -"executing your code in the :doc:`/panes/ipythonconsole` to get help and " -"completions there. If this doesn't work, try restarting PyLS by right-" -"clicking the :guilabel:`LSP Python` label item in the statusbar at the " -"bottom of Spyder's main window, and selecting the :guilabel:`Restart " -"Python Language Server` option." +#: ../../faq.rst:0 +msgid "Q: I get an error in the IPython console running my code! Help!" msgstr "" -#: ../../faq.rst:350 -msgid "" -"For more information, go to the :ref:`code-completion-problems-ref` " -"section in the :doc:`/troubleshooting/common-illnesses` page of our " -"troubleshooting guide." +#: ../../faq.rst:332 +msgid "First, make sure the error you are seeing is not a bug in your code. To confirm this, try running it in any standard Python interpreter. If the error still occurs, the problem is likely with your code and a site like `Stack Overflow`_ might be the best place to start. Otherwise, start at the :doc:`/troubleshooting/basic-first-aid` section of our troubleshooting guide." msgstr "" -#: ../../faq.rst:356 -msgid "" -"First, make sure your version of Spyder-Kernels is compatible with that " -"of Spyder. See the table in the :ref:`spyder-kernels-version-ref` section" -" of the troubleshooting guide to check." +#: ../../faq.rst:0 +msgid "Q: Code completion/help doesn't work; what can I do?" msgstr "" -#: ../../faq.rst:359 -msgid "" -"To install the right version, type the following on the command line (or " -"Anaconda Prompt on Windows)" +#: ../../faq.rst:343 +msgid "If nothing is displayed in the calltip, hover hint or :doc:`/panes/help` pane, make sure the object you are inspecting has a docstring, and try executing your code in the :doc:`/panes/ipythonconsole` to get help and completions there. If this doesn't work, try restarting PyLS by right-clicking the :guilabel:`LSP Python` label item in the statusbar at the bottom of Spyder's main window, and selecting the :guilabel:`Restart Python Language Server` option." msgstr "" -#: ../../faq.rst:365 -msgid "" -"For more information, go to the :ref:`starting-kernel-problems-ref` " -"section in the :doc:`/troubleshooting/common-illnesses` page of our " -"troubleshooting guide." +#: ../../faq.rst:346 +msgid "For more information, go to the :ref:`code-completion-problems-ref` section in the :doc:`/troubleshooting/common-illnesses` page of our troubleshooting guide." msgstr "" -#: ../../faq.rst:371 -msgid "" -"Spyder is in the final stages of being updated for full compatibility " -"with macOS 11 Big Sur, which will be released by the end of 2020 as part " -"of version 4.2.1. However, you can get it working right now with the " -"workaround below. Make sure you have the Anaconda or Miniconda " -"distribution installed, and run the following commands in the Terminal to" -" install Spyder from Conda-Forge in a clean environment:" +#: ../../faq.rst:0 +msgid "Q: I get the message \"An error occurred while starting the kernel\". How do I fix this?" msgstr "" -#: ../../faq.rst:381 -msgid "" -"Then, whenever you want to start Spyder, run the following from the " -"Terminal:" +#: ../../faq.rst:352 +msgid "First, make sure your version of Spyder-Kernels is compatible with that of Spyder. See the table in the :ref:`spyder-kernels-version-ref` section of the troubleshooting guide to check." msgstr "" -#: ../../faq.rst:393 +#: ../../faq.rst:355 +msgid "To install the right version, type the following on the command line (or Anaconda Prompt on Windows)" +msgstr "" + +#: ../../faq.rst:361 +msgid "For more information, go to the :ref:`starting-kernel-problems-ref` section in the :doc:`/troubleshooting/common-illnesses` page of our troubleshooting guide." +msgstr "" + +#: ../../faq.rst:0 +msgid "Q: Spyder doesn't launch or is slow on macOS Big Sur. How can I get it working?" +msgstr "" + +#: ../../faq.rst:367 +msgid "Spyder is in the final stages of being updated for full compatibility with macOS 11 Big Sur, which will be released by the end of 2020 as part of version 4.2.1. However, you can get it working right now with the workaround below. Make sure you have the Anaconda or Miniconda distribution installed, and run the following commands in the Terminal to install Spyder from Conda-Forge in a clean environment:" +msgstr "" + +#: ../../faq.rst:377 +msgid "Then, whenever you want to start Spyder, run the following from the Terminal:" +msgstr "" + +#: ../../faq.rst:389 msgid "About Spyder" msgstr "" -#: ../../faq.rst:398 -#, python-format -msgid "" -"Spyder is 100% free and open source; there is no paid version or " -"prohibition on commercial use. It is developed by its international user " -"community, and supported by its users through `OpenCollective`_ and by " -"its generous sponsoring organizations, including `Quansight`_ and " -"`NumFOCUS`_. Our source code, standalone installers and most of our " -"distribution methods (Pip/PyPI, Linux distros, MacPorts, WinPython, etc) " -"can be freely redistributed, used and modified by anyone, for any " -"purpose, including commercial use. For more details about the situation " -"with Anaconda, see `that question`_." -msgstr "" - -#: ../../faq.rst:412 -#, python-format -msgid "" -"If you use Spyder with the Anaconda distribution, they `recently " -"changed`_ their `Terms of Service`_ to add restrictions on large (> 200 " -"employee) for-profit companies using Anaconda on a large scale. However, " -"these terms only apply to the package infrastructure (the full Anaconda " -"distribution and the ``defaults`` conda channel). Instead, you can simply" -" download the similar `Miniforge distribution`_, which is 100% open " -"source and identical to full Anaconda (aside from not bundling the Python" -" packages installed by default in the Anaconda ``base`` environment, " -"which we recommend you avoid using anyway given any problems here can " -"break your whole installation). Then, simply install the packages you " -"need (including Spyder, if you aren't using our recommended :ref" -":`install-standalone`) with ``conda`` as you usually do. Miniforge will " -"automatically use the community-maintained Conda-Forge repository, which " -"has a much wider variety of packages and is generally more up to date " -"than the Anaconda equivalent, in addition to being free of any commercial" -" restrictions. For more, see our :doc:`/installation`." +#: ../../faq.rst:0 +msgid "Q: What's Spyder's licensing situation? Is commercial use allowed?" +msgstr "" + +#: ../../faq.rst:394 +msgid "Spyder is 100% free and open source; there is no paid version or prohibition on commercial use. It is developed by its international user community, and supported by its users through `OpenCollective`_ and by its generous sponsoring organizations, including `Quansight`_ and `NumFOCUS`_. Our source code, standalone installers and most of our distribution methods (Pip/PyPI, Linux distros, MacPorts, WinPython, etc) can be freely redistributed, used and modified by anyone, for any purpose, including commercial use. For more details about the situation with Anaconda, see `that question`_." msgstr "" +#: ../../faq.rst:0 +msgid "Q: What do the Anaconda licensing changes mean for Spyder?" +msgstr "" + +#: ../../faq.rst:408 +msgid "If you use Spyder with the Anaconda distribution, they `recently changed`_ their `Terms of Service`_ to add restrictions on large (> 200 employee) for-profit companies using Anaconda on a large scale. However, these terms only apply to the package infrastructure (the full Anaconda distribution and the ``defaults`` conda channel). Instead, you can simply download the similar `Miniforge distribution`_, which is 100% open source and identical to full Anaconda (aside from not bundling the Python packages installed by default in the Anaconda ``base`` environment, which we recommend you avoid using anyway given any problems here can break your whole installation). Then, simply install the packages you need (including Spyder, if you aren't using our recommended :ref:`install-standalone`) with ``conda`` as you usually do. Miniforge will automatically use the community-maintained Conda-Forge repository, which has a much wider variety of packages and is generally more up to date than the Anaconda equivalent, in addition to being free of any commercial restrictions. For more, see our :doc:`/installation`." +msgstr "" diff --git a/doc/locales/pot/index.pot b/doc/locales/pot/index.pot index 3ea9ec84..d195a964 100644 --- a/doc/locales/pot/index.pot +++ b/doc/locales/pot/index.pot @@ -1,26 +1,22 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#: ../../index.rst:137 -msgid "Welcome" -msgstr "" - -#: ../../index.rst:137 +#: ../../index.rst:153 msgid "FAQ" msgstr "" @@ -28,14 +24,12 @@ msgstr "" msgid "Welcome to Spyder's Documentation" msgstr "" +#: ../../index.rst:5 +msgid "Screenshot of the Spyder main window, with the default panel layout" +msgstr "" + #: ../../index.rst:9 -msgid "" -"Spyder is a powerful scientific environment written in Python, for " -"Python, and designed by and for scientists, engineers and data analysts. " -"It features a unique combination of the advanced editing, analysis, " -"debugging, and profiling functionality of a comprehensive development " -"tool with the data exploration, interactive execution, deep inspection, " -"and beautiful visualization capabilities of a scientific package." +msgid "Spyder is a powerful scientific environment written in Python, for Python, and designed by and for scientists, engineers and data analysts. It features a unique combination of the advanced editing, analysis, debugging, and profiling functionality of a comprehensive development tool with the data exploration, interactive execution, deep inspection, and beautiful visualization capabilities of a scientific package." msgstr "" #: ../../index.rst:18 @@ -43,109 +37,73 @@ msgid "Where to go now?" msgstr "" #: ../../index.rst:20 -msgid "" -"Spyder's documentation provides a variety of resources that will help you" -" learn how to use the application and explore each one of its panes. " -"These include video tutorials, in-depth descriptions and how-to guides " -"covering a wide range of needs and experience levels with Spyder." +msgid "Spyder's documentation provides a variety of resources that will help you learn how to use the application and explore each one of its panes. These include video tutorials, in-depth descriptions and how-to guides covering a wide range of needs and experience levels with Spyder." msgstr "" -#: ../../index.rst:33 -msgid "" -"If you are looking for a summary of its features and interface, check out" -" the :doc:`quickstart`." +#: ../../index.rst:34 +msgid "If you are looking for a summary of its features and interface, check out the :doc:`quickstart`." msgstr "" -#: ../../index.rst:41 -msgid "" -"If you don't have Spyder installed and want to get started, follow the " -":doc:`/installation`." +#: ../../index.rst:45 +msgid "If you don't have Spyder installed and want to get started, follow the :doc:`/installation`." msgstr "" -#: ../../index.rst:49 -msgid "" -"If you are completely new to Spyder, watch our basic tutorial series, " -":doc:`videos/first-steps-with-spyder`." +#: ../../index.rst:56 +msgid "If you are completely new to Spyder, watch our basic tutorial series, :doc:`videos/first-steps-with-spyder`." msgstr "" -#: ../../index.rst:57 -msgid "" -"If you are familiar with Spyder and want to explore the functionality of " -"its panes in more detail, go to :doc:`panes/index`." +#: ../../index.rst:67 +msgid "If you are familiar with Spyder and want to explore the functionality of its panes in more detail, go to :doc:`panes/index`." msgstr "" -#: ../../index.rst:65 -msgid "" -"If you've run into a Spyder problem and need help solving it, take a look" -" at our :doc:`troubleshooting guide`." +#: ../../index.rst:78 +msgid "If you've run into a Spyder problem and need help solving it, take a look at our :doc:`troubleshooting guide`." msgstr "" -#: ../../index.rst:73 +#: ../../index.rst:89 msgid "If you have a question about Spyder, visit the :doc:`faq` section." msgstr "" -#: ../../index.rst:81 +#: ../../index.rst:97 msgid "Join our community" msgstr "" -#: ../../index.rst:83 -msgid "" -"Spyder is open source software, which means that is free for everyone to " -"use and anyone can contribute to it. We encourage everyone to become a " -"part of our community and help develop Spyder!" +#: ../../index.rst:99 +msgid "Spyder is open source software, which means that is free for everyone to use and anyone can contribute to it. We encourage everyone to become a part of our community and help develop Spyder!" msgstr "" -#: ../../index.rst:90 +#: ../../index.rst:106 msgid "Looking to contribute your code?" msgstr "" -#: ../../index.rst:92 -msgid "" -"Spyder is written in the same Python language that you use it to develop," -" so its easy to get started contributing to it. You can follow our " -"`contributing guide`_ to set up a development environment, and you can " -"get involved with the project through our `Github repository`_. The " -"easiest way to get started is helping us resolve items on our `issue " -"tracker`_, either by fixing bugs in Spyder, or helping users troubleshoot" -" their problems (which doesn't require writing any code)." +#: ../../index.rst:108 +msgid "Spyder is written in the same Python language that you use it to develop, so its easy to get started contributing to it. You can follow our `contributing guide`_ to set up a development environment, and you can get involved with the project through our `Github repository`_. The easiest way to get started is helping us resolve items on our `issue tracker`_, either by fixing bugs in Spyder, or helping users troubleshoot their problems (which doesn't require writing any code)." msgstr "" -#: ../../index.rst:106 +#: ../../index.rst:122 msgid "Want to help writing docs?" msgstr "" -#: ../../index.rst:108 -msgid "" -"We welcome your contributions of corrections, additions and enhancements " -"to these docs. Check out the `docs contributing guide`_ to learn how to " -"submit a PR with your changes on our `docs repo`_." +#: ../../index.rst:124 +msgid "We welcome your contributions of corrections, additions and enhancements to these docs. Check out the `docs contributing guide`_ to learn how to submit a PR with your changes on our `docs repo`_." msgstr "" -#: ../../index.rst:119 +#: ../../index.rst:135 msgid "Interested in translating Spyder?" msgstr "" -#: ../../index.rst:121 -msgid "" -"In order to reach more users around the world in need of a powerful " -"scientific Python environment, we welcome your help translating the " -"documentation and the interface into different languages." +#: ../../index.rst:137 +msgid "In order to reach more users around the world in need of a powerful scientific Python environment, we welcome your help translating the documentation and the interface into different languages." msgstr "" -#: ../../index.rst:123 -msgid "" -"For this purpose we use `Crowdin`_, which provides a simple web based " -"interface for translators, proofreaders and managers, so everyone can " -"help us translate Spyder into any language." +#: ../../index.rst:139 +msgid "For this purpose we use `Crowdin`_, which provides a simple web based interface for translators, proofreaders and managers, so everyone can help us translate Spyder into any language." msgstr "" -#: ../../index.rst:131 +#: ../../index.rst:147 msgid "Want to be part of our social media?" msgstr "" -#: ../../index.rst:133 -msgid "" -"Connect with Spyder through our social media channels to stay up to date " -"with our current developments!" +#: ../../index.rst:149 +msgid "Connect with Spyder through our social media channels to stay up to date with our current developments!" msgstr "" - diff --git a/doc/locales/pot/installation.pot b/doc/locales/pot/installation.pot index 86d572bc..f85cb82a 100644 --- a/doc/locales/pot/installation.pot +++ b/doc/locales/pot/installation.pot @@ -1,50 +1,35 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../installation.rst:5 -msgid "Installation Guide" +msgid "Install Guide" msgstr "" #: ../../installation.rst:7 -msgid "" -"Spyder is relatively easy to install on Windows, Linux and macOS. Just " -"make sure to read and follow these instructions with care." +msgid "Spyder is relatively easy to install on Windows, Linux and macOS. Just make sure to read and follow these instructions with care." msgstr "" #: ../../installation.rst:10 -msgid "" -"If you run into problems, before posting a report, *please* consult our " -"comprehensive :doc:`troubleshooting guide` " -"and search the `issue tracker`_ for your error message and problem " -"description. These methods generally fix or isolate the great majority of" -" install-related difficulties. Thanks!" +msgid "If you run into problems, before posting a report, *please* consult our comprehensive :doc:`troubleshooting guide` and search the `issue tracker`_ for your error message and problem description. These methods generally fix or isolate the great majority of install-related difficulties. Thanks!" msgstr "" #: ../../installation.rst:18 -msgid "" -"For most users on Windows and macOS, we recommend our :ref:`install-" -"standalone` as the most straightforward and robust option to obtain " -"Spyder. For users needing Linux support, third-party Spyder plugins or " -"Variable Explorer compatibility with custom-installed packages—all " -"capabilities which the standalone installers currently do not yet " -"provide—we advise using a :ref:`install-conda`. Linux, plugin and " -"package/environment management support in the standalone installers are " -"currently under active development for future Spyder versions." +msgid "For most users on Windows and macOS, we recommend our :ref:`install-standalone` as the most straightforward and robust option to obtain Spyder. For users needing Linux support, third-party Spyder plugins or Variable Explorer compatibility with custom-installed packages—all capabilities which the standalone installers currently do not yet provide—we advise using a :ref:`install-conda`. Linux, plugin and package/environment management support in the standalone installers are currently under active development for future Spyder versions." msgstr "" #: ../../installation.rst:27 @@ -52,11 +37,11 @@ msgid "Try Spyder online" msgstr "" #: ../../installation.rst:29 -msgid "" -"Want to try out Spyder without installing it? With `Binder`_ you can work" -" with a fully functional copy of Spyder online that runs right in your " -"web browser, no installation needed. Visit the `Spyder Binder`_ to get " -"started using Spyder." +msgid "Want to try out Spyder without installing it? With `Binder`_ you can work with a fully functional copy of Spyder online that runs right in your web browser, no installation needed. Visit the `Spyder Binder`_ to get started using Spyder." +msgstr "" + +#: ../../installation.rst:36 +msgid "Spyder running on Binder" msgstr "" #: ../../installation.rst:45 @@ -64,34 +49,15 @@ msgid "Standalone installers" msgstr "" #: ../../installation.rst:47 -msgid "" -"The standalone installers are our recommended method for most users on " -"Windows and macOS, with experimental Linux support under active " -"development. They work like any other IDE, where Spyder can be installed " -"and updated independently of the Python environments you use to run your " -"code. This avoids the problems with incompatible packages and broken " -"installations users often face when mixing Spyder with the (Conda, etc) " -"environments they use to run their code." +msgid "The standalone installers are our recommended method for most users on Windows and macOS, with experimental Linux support under active development. They work like any other IDE, where Spyder can be installed and updated independently of the Python environments you use to run your code. This avoids the problems with incompatible packages and broken installations users often face when mixing Spyder with the (Conda, etc) environments they use to run their code." msgstr "" #: ../../installation.rst:51 -msgid "" -"The installers include a built-in Python environment with the most common" -" scientific libraries (e.g. NumPy, Pandas, Matpotlib, etc), which can be " -"used out of the box for basic data analysis tasks. However, to manage " -"your own packages and environments, you'll currently need to connect an " -"external Python distribution (such as `Anaconda`_, `Miniconda`_, " -"`Miniforge/Mambaforge`_, `WinPython`_ or `Python.org `__) to " -"your standalone copy of Spyder. For more information on this, see our " -":ref:`FAQ entry on the subject `." +msgid "The installers include a built-in Python environment with the most common scientific libraries (e.g. NumPy, Pandas, Matpotlib, etc), which can be used out of the box for basic data analysis tasks. However, to manage your own packages and environments, you'll currently need to connect an external Python distribution (such as `Anaconda`_, `Miniconda`_, `Miniforge/Mambaforge`_, `WinPython`_ or `Python.org `__) to your standalone copy of Spyder. For more information on this, see our :ref:`FAQ entry on the subject `." msgstr "" #: ../../installation.rst:57 -msgid "" -"The standalone installers do not yet support installing third-party " -"Spyder plugins not already bundled with them, though this feature is " -"currently under development. For now, if you need this capability, we " -"recommend a :ref:`install-conda`." +msgid "The standalone installers do not yet support installing third-party Spyder plugins not already bundled with them, though this feature is currently under development. For now, if you need this capability, we recommend a :ref:`install-conda`." msgstr "" #: ../../installation.rst:64 @@ -99,495 +65,353 @@ msgid "Downloading and installing" msgstr "" #: ../../installation.rst:66 -msgid "" -"To download the supported Spyder installer for your platform, simply " -"click the appropriate link below (for Linux, see the :ref:`install-conda`" -" section). Then, double-click the downloaded file to open the installer. " -"If a security warning pops up, you may need to click :guilabel:`Yes`, " -":guilabel:`OK`, :guilabel:`Open`, :guilabel:`Allow` or similar." +msgid "To download the supported Spyder installer for your platform, simply click the appropriate link below (for Linux, see the :ref:`install-conda` section). Then, double-click the downloaded file to open the installer. If a security warning pops up, you may need to click :guilabel:`Yes`, :guilabel:`OK`, :guilabel:`Open`, :guilabel:`Allow` or similar." msgstr "" #: ../../installation.rst:70 -msgid "" -"On Windows, if a \"SmartScreen\" dialog appears, click :guilabel:`More " -"info` followed by :guilabel:`Run anyway`, and then proceed through the " -"steps in the installer." +msgid "On Windows, if a \"SmartScreen\" dialog appears, click :guilabel:`More info` followed by :guilabel:`Run anyway`, and then proceed through the steps in the installer." msgstr "" #: ../../installation.rst:72 -msgid "" -"On macOS, open the disk image and drag Spyder to your " -":guilabel:`Applications` folder." +msgid "On macOS, open the disk image and drag Spyder to your :guilabel:`Applications` folder." msgstr "" #: ../../installation.rst:79 -msgid "`Windows Installer`_" +msgid "`Windows`_" msgstr "" #: ../../installation.rst:79 -msgid "`macOS Installer`_" +msgid "`macOS M1`_" msgstr "" -#: ../../installation.rst:87 -msgid "" -"\"Lite\" versions of both installers are also available from the " -"`releases page`_, which are somewhat smaller than the full installers. " -"These lack a number of optional but recommended dependencies, such as " -"NumPy, SciPy and Pandas, meaning that a few " -":doc:`/panes/variableexplorer` features, including graphical data import " -"wizards and support for rich display and editing of NumPy arrays and " -"Pandas DataFrames, will not be available. Given this only saves a modest " -"amount of space while missing out on significant features, we recommend " -"using the full installers unless minimizing download/install size and " -"memory usage is a priority." -msgstr "" - -#: ../../installation.rst:97 -msgid "Running from a standalone install" +#: ../../installation.rst:79 +msgid "`macOS Intel`_" +msgstr "" + +#: ../../installation.rst:79 +msgid "`Linux`_" +msgstr "" + +#: ../../installation.rst:89 +msgid "\"Lite\" versions of both installers are also available from the `releases page`_, which are somewhat smaller than the full installers. These lack a number of optional but recommended dependencies, such as NumPy, SciPy and Pandas, meaning that a few :doc:`/panes/variableexplorer` features, including graphical data import wizards and support for rich display and editing of NumPy arrays and Pandas DataFrames, will not be available. Given this only saves a modest amount of space while missing out on significant features, we recommend using the full installers unless minimizing download/install size and memory usage is a priority." msgstr "" #: ../../installation.rst:99 -msgid "" -"To run Spyder when installed standalone, you can simply use your " -"operating system's typical method of launching applications, such as " -"opening it from the :guilabel:`Start` menu on Windows (or the Taskbar, if" -" you've pinned it there), or from Launchpad, Spotlight or the " -":guilabel:`Applications` folder on macOS (or the Dock, if you've added it" -" there)." +msgid "Running from a standalone install" msgstr "" -#: ../../installation.rst:105 -msgid "Updating a standalone install" +#: ../../installation.rst:101 +msgid "To run Spyder when installed standalone, you can simply use your operating system's typical method of launching applications, such as opening it from the :guilabel:`Start` menu on Windows (or the Taskbar, if you've pinned it there), or from Launchpad, Spotlight or the :guilabel:`Applications` folder on macOS (or the Dock, if you've added it there)." msgstr "" #: ../../installation.rst:107 -msgid "" -"By default, Spyder checks for updates automatically on startup, and you " -"can also check manually with :menuselection:`Help --> Check for updates`." -" The standalone installers for Spyder 5.4.0+ include update functionality" -" built right into Spyder, which after checking for updates will display a" -" prompt to automatically download and install the current version. On " -"earlier versions, you'll need to manually download and install the latest" -" release (if on Windows, make sure to remove the old version first from " -"Control Panel/System Settings)." +msgid "Updating a standalone install" msgstr "" -#: ../../installation.rst:117 -msgid "Conda-based distributions" +#: ../../installation.rst:109 +msgid "By default, Spyder checks for updates automatically on startup, and you can also check manually with :menuselection:`Help --> Check for updates`. The standalone installers for Spyder 5.4.0+ include update functionality built right into Spyder, which after checking for updates will display a prompt to automatically download and install the current version. On earlier versions, you'll need to manually download and install the latest release (if on Windows, make sure to remove the old version first from Control Panel/System Settings)." msgstr "" #: ../../installation.rst:119 -msgid "" -"Spyder is included by default in the `Anaconda`_ Python distribution, " -"which comes with everything you need to get started in an all-in-one " -"package. It can also be easily installed in the much lighter-weight " -"`Miniconda`_ and `Miniforge/Mambaforge`_, which include just Python and " -"the Conda/Mamba package and environment manager by default (with " -"Miniforge defaulting to the Conda-Forge channel, and Mambaforge using " -"Mamba, a much faster alternative to Conda). This is our recommended " -"installation method on Linux and for users with third-party Spyder " -"plugins, as support for both of these in our standalone installers is " -"still under active development." -msgstr "" - -#: ../../installation.rst:131 -msgid "Conda environment" +msgid "Conda-based distributions" +msgstr "" + +#: ../../installation.rst:121 +msgid "Spyder is included by default in the `Anaconda`_ Python distribution, which comes with everything you need to get started in an all-in-one package. It can also be easily installed in the much lighter-weight `Miniconda`_ and `Miniforge/Mambaforge`_, which include just Python and the Conda/Mamba package and environment manager by default (with Miniforge defaulting to the Conda-Forge channel, and Mambaforge using Mamba, a much faster alternative to Conda). This is our recommended installation method on Linux and for users with third-party Spyder plugins, as support for both of these in our standalone installers is still under active development." msgstr "" #: ../../installation.rst:133 -msgid "" -"With Miniconda/Miniforge/Mambaforge, or to get a more reliable and up-to-" -"date Spyder version with Anaconda, we strongly recommend installing " -"Spyder into its own dedicated Conda environment." +msgid "Conda environment" msgstr "" -#: ../../installation.rst:137 -msgid "" -"If using Mamba/Mambaforge, substitute ``mamba`` for ``conda`` in the " -"following commands." +#: ../../installation.rst:135 +msgid "With Miniconda/Miniforge/Mambaforge, or to get a more reliable and up-to-date Spyder version with Anaconda, we strongly recommend installing Spyder into its own dedicated Conda environment." msgstr "" -#: ../../installation.rst:143 -msgid "Installing with Conda" +#: ../../installation.rst:139 +msgid "If using Mamba/Mambaforge, substitute ``mamba`` for ``conda`` in the following commands." msgstr "" #: ../../installation.rst:145 -msgid "" -"For a full install of Spyder and all optional dependencies, run the " -"following command in your Anaconda Prompt (Windows) or terminal:" +msgid "Installing with Conda" msgstr "" -#: ../../installation.rst:151 -msgid "" -"For a minimal install without the optional functionality and integration " -"with the above packages, you can instead run:" +#: ../../installation.rst:147 +msgid "For a full install of Spyder and all optional dependencies, run the following command in your Anaconda Prompt (Windows) or terminal:" msgstr "" -#: ../../installation.rst:157 -msgid "" -"This installs Spyder into a new environment called ``spyder-env``, using " -"the more up-to-date, community-run Conda-Forge channel. To make sure " -"future installs/updates in this environment also use Conda-Forge and are " -"faster and more reliable, make sure to set it as your environment's " -"default channel with strict channel priority enabled, if this isn't the " -"case already (as it is with Miniforge/Mambaforge or if you've manually " -"configured it):" +#: ../../installation.rst:153 +msgid "For a minimal install without the optional functionality and integration with the above packages, you can instead run:" +msgstr "" + +#: ../../installation.rst:159 +msgid "This installs Spyder into a new environment called ``spyder-env``, using the more up-to-date, community-run Conda-Forge channel. To make sure future installs/updates in this environment also use Conda-Forge and are faster and more reliable, make sure to set it as your environment's default channel with strict channel priority enabled, if this isn't the case already (as it is with Miniforge/Mambaforge or if you've manually configured it):" msgstr "" -#: ../../installation.rst:166 +#: ../../installation.rst:168 msgid "Here's a summary of the main steps." msgstr "" -#: ../../installation.rst:175 -msgid "Running with Conda" +#: ../../installation.rst:170 +msgid "Running Spyder installation with conda" msgstr "" #: ../../installation.rst:177 -msgid "" -"You can then run Spyder by the same methods :ref:`as with Anaconda " -"`, except that you need to make sure to launch " -"the Start menu shortcut with ``(spyder-env)`` in the name, select the " -"``spyder-env`` environment on the left before launching it with " -"Navigator, or type ``conda activate spyder-env`` before launching it on " -"the command line." +msgid "Running with Conda" msgstr "" #: ../../installation.rst:179 -msgid "" -"See :ref:`our FAQ question ` for more " -"information about how to use Spyder with your existing Conda " -"environments." +msgid "You can then run Spyder by the same methods :ref:`as with Anaconda `, except that you need to make sure to launch the Start menu shortcut with ``(spyder-env)`` in the name, select the ``spyder-env`` environment on the left before launching it with Navigator, or type ``conda activate spyder-env`` before launching it on the command line." msgstr "" -#: ../../installation.rst:185 -msgid "Updating with Conda" +#: ../../installation.rst:181 +msgid "See :ref:`our FAQ question ` for more information about how to use Spyder with your existing Conda environments." msgstr "" #: ../../installation.rst:187 -msgid "" -"With any Conda-based distribution and Spyder installed in its own " -"environment (recommended), update Conda itself, active the environment, " -"and finally update Spyder. In your system terminal (or Anaconda Prompt if" -" on Windows), run:" +msgid "Updating with Conda" msgstr "" -#: ../../installation.rst:196 -msgid "" -"In case you get an error trying to update, just remove the existing " -"environment (if using one other than ``base``):" +#: ../../installation.rst:189 +msgid "With any Conda-based distribution and Spyder installed in its own environment (recommended), update Conda itself, active the environment, and finally update Spyder. In your system terminal (or Anaconda Prompt if on Windows), run:" +msgstr "" + +#: ../../installation.rst:198 +msgid "In case you get an error trying to update, just remove the existing environment (if using one other than ``base``):" msgstr "" -#: ../../installation.rst:202 +#: ../../installation.rst:204 msgid "And then :ref:`recreate a fresh one `." msgstr "" -#: ../../installation.rst:208 +#: ../../installation.rst:210 msgid "Anaconda base" msgstr "" -#: ../../installation.rst:210 -msgid "" -"While we recommend always using a dedicated environment, with Anaconda " -"you can also run the bundled copy of Spyder from the built-in ``base`` " -"environment." +#: ../../installation.rst:212 +msgid "While we recommend always using a dedicated environment, with Anaconda you can also run the bundled copy of Spyder from the built-in ``base`` environment." msgstr "" -#: ../../installation.rst:214 -msgid "" -"The bundled Spyder version can often be quite out of date, missing new " -"features and bug fixes from the latest version, and if you install, " -"change or remove other packages, there is a significant chance of " -"dependency conflicts or a broken Spyder installation. Therefore, we " -"recommend :ref:`installing Spyder into a new Conda environment ` to avoid all these issues." +#: ../../installation.rst:216 +msgid "The bundled Spyder version can often be quite out of date, missing new features and bug fixes from the latest version, and if you install, change or remove other packages, there is a significant chance of dependency conflicts or a broken Spyder installation. Therefore, we recommend :ref:`installing Spyder into a new Conda environment ` to avoid all these issues." msgstr "" -#: ../../installation.rst:221 +#: ../../installation.rst:223 msgid "Running with Anaconda" msgstr "" -#: ../../installation.rst:223 -msgid "" -"To run the bundled version of Spyder after installing it with Anaconda, " -"the recommended method on Windows is to launch it via the Start menu " -"shortcut. On other platforms, open Anaconda Navigator, scroll to Spyder " -"under :guilabel:`Home` and click :guilabel:`Launch`." +#: ../../installation.rst:225 +msgid "To run the bundled version of Spyder after installing it with Anaconda, the recommended method on Windows is to launch it via the Start menu shortcut. On other platforms, open Anaconda Navigator, scroll to Spyder under :guilabel:`Home` and click :guilabel:`Launch`." msgstr "" -#: ../../installation.rst:229 -msgid "" -"If Spyder does not start via this method or you prefer to use the command" -" line, open Anaconda Prompt (Windows) or your terminal (other platforms)," -" type ``conda activate base`` then ``spyder``." +#: ../../installation.rst:228 +msgid "Anaconda Navigator showing Spyder" msgstr "" -#: ../../installation.rst:235 -msgid "Updating with Anaconda" +#: ../../installation.rst:231 +msgid "If Spyder does not start via this method or you prefer to use the command line, open Anaconda Prompt (Windows) or your terminal (other platforms), type ``conda activate base`` then ``spyder``." msgstr "" #: ../../installation.rst:237 -msgid "" -"With Spyder installed in Anaconda's ``base`` environment, first update " -"the ``anaconda`` meta-package, and then Spyder itself (in case there is a" -" newer version than that pinned to the ``anaconda`` metapackage). In your" -" system terminal (or Anaconda Prompt if on Windows), run:" +msgid "Updating with Anaconda" msgstr "" -#: ../../installation.rst:247 -msgid "" -"These commands also update all your other packages, which is one reason " -"we strongly recommend you use an isolated conda environment to avoid any " -"potential unintended effects on other installed packages." +#: ../../installation.rst:239 +msgid "With Spyder installed in Anaconda's ``base`` environment, first update the ``anaconda`` meta-package, and then Spyder itself (in case there is a newer version than that pinned to the ``anaconda`` metapackage). In your system terminal (or Anaconda Prompt if on Windows), run:" msgstr "" #: ../../installation.rst:249 -msgid "" -"In case you get an error resolving dependencies, try uninstalling Spyder " -"and re-installing it:" +msgid "These commands also update all your other packages, which is one reason we strongly recommend you use an isolated conda environment to avoid any potential unintended effects on other installed packages." msgstr "" -#: ../../installation.rst:262 -msgid "Using pip" +#: ../../installation.rst:251 +msgid "In case you get an error resolving dependencies, try uninstalling Spyder and re-installing it:" msgstr "" -#: ../../installation.rst:266 -msgid "" -"While this installation method is a viable option for experienced users, " -"installing Spyder (and other PyData-stack packages) with pip can " -"sometimes lead to tricky issues, particularly on Windows and macOS. While" -" you are welcome to try it on your own, we are typically not able to " -"provide individual support for installation problems with pip, except to " -"recommend our :ref:`install-standalone` (Windows and macOS) or a :ref" -":`install-conda`." +#: ../../installation.rst:264 +msgid "Using pip" msgstr "" -#: ../../installation.rst:269 -msgid "" -"You can install Spyder with the pip package manager, which is included by" -" default with most Python installations. Before installing Spyder itself " -"by this method, you need to download the `Python`_ programming language." +#: ../../installation.rst:268 +msgid "While this installation method is a viable option for experienced users, installing Spyder (and other PyData-stack packages) with pip can sometimes lead to tricky issues, particularly on Windows and macOS. While you are welcome to try it on your own, we are typically not able to provide individual support for installation problems with pip, except to recommend our :ref:`install-standalone` (Windows and macOS) or a :ref:`install-conda`." msgstr "" -#: ../../installation.rst:276 -msgid "" -"Due to a known issue with some DEB-based Linux distributions (Debian, " -"Ubuntu, Mint), you might also need to install the ``pyqt5-dev-tools`` " -"package first, with ``sudo apt install pyqt5-dev-tools``." +#: ../../installation.rst:271 +msgid "You can install Spyder with the pip package manager, which is included by default with most Python installations. Before installing Spyder itself by this method, you need to download the `Python`_ programming language." msgstr "" #: ../../installation.rst:278 -msgid "" -"You'll first want to create and activate a virtual environment in which " -"to install Spyder, via one of the following methods." +msgid "Due to a known issue with some DEB-based Linux distributions (Debian, Ubuntu, Mint), you might also need to install the ``pyqt5-dev-tools`` package first, with ``sudo apt install pyqt5-dev-tools``." msgstr "" #: ../../installation.rst:280 +msgid "You'll first want to create and activate a virtual environment in which to install Spyder, via one of the following methods." +msgstr "" + +#: ../../installation.rst:282 msgid "With ``virtualenvwrapper``:" msgstr "" -#: ../../installation.rst:287 +#: ../../installation.rst:289 msgid "Otherwise, on macOS/Linux/Unix:" msgstr "" -#: ../../installation.rst:294 +#: ../../installation.rst:296 msgid "or on Windows:" msgstr "" -#: ../../installation.rst:301 -msgid "" -"After activating your environment, to install Spyder and its optional " -"dependencies, run:" +#: ../../installation.rst:303 +msgid "After activating your environment, to install Spyder and its optional dependencies, run:" msgstr "" -#: ../../installation.rst:307 +#: ../../installation.rst:309 msgid "Or for a minimal installation, run:" msgstr "" -#: ../../installation.rst:316 -msgid "" -"To launch Spyder after installing it, ensure your environment is " -"activated and run the ``spyder`` or ``spyder3`` command." +#: ../../installation.rst:315 +msgid "Running Spyder installation with pip" msgstr "" #: ../../installation.rst:318 -msgid "And to update Spyder, with your Spyder environment activated, run:" +msgid "To launch Spyder after installing it, ensure your environment is activated and run the ``spyder`` or ``spyder3`` command." msgstr "" -#: ../../installation.rst:330 -msgid "Alternative methods" +#: ../../installation.rst:320 +msgid "And to update Spyder, with your Spyder environment activated, run:" msgstr "" -#: ../../installation.rst:334 -msgid "" -"While we describe alternative Spyder installation options for users who " -"prefer them, as these are third-party distributions that we have no " -"direct involvement in, we are usually not able to offer useful individual" -" assistance for problems specific to installing via these alternative " -"methods." +#: ../../installation.rst:332 +msgid "Alternative methods" msgstr "" #: ../../installation.rst:336 -msgid "" -"Also, the Spyder versions they install may be out of date relative to the" -" current release, and thus be missing the latest features and bug fixes." +msgid "While we describe alternative Spyder installation options for users who prefer them, as these are third-party distributions that we have no direct involvement in, we are usually not able to offer useful individual assistance for problems specific to installing via these alternative methods." msgstr "" #: ../../installation.rst:338 -msgid "" -"Therefore, we recommend you switch to our :ref:`install-standalone` " -"(Windows and macOS) or a :ref:`install-conda` if you encounter " -"installation issues you are unable to solve on your own." +msgid "Also, the Spyder versions they install may be out of date relative to the current release, and thus be missing the latest features and bug fixes." msgstr "" -#: ../../installation.rst:344 -msgid "Windows" +#: ../../installation.rst:340 +msgid "Therefore, we recommend you switch to our :ref:`install-standalone` (Windows and macOS) or a :ref:`install-conda` if you encounter installation issues you are unable to solve on your own." msgstr "" #: ../../installation.rst:346 -msgid "" -"Spyder is included in the `WinPython`_ scientific Python distribution, " -"along with many other common numerical computing and data analysis " -"packages. You can use Spyder immediately after installing, similar to " -"Anaconda." +msgid "Windows" msgstr "" -#: ../../installation.rst:355 -msgid "macOS" +#: ../../installation.rst:348 +msgid "Spyder is included in the `WinPython`_ scientific Python distribution, along with many other common numerical computing and data analysis packages. You can use Spyder immediately after installing, similar to Anaconda." msgstr "" #: ../../installation.rst:357 +msgid "macOS" +msgstr "" + +#: ../../installation.rst:359 msgid "Spyder is available as `a cask`_ through `Homebrew`_." msgstr "" -#: ../../installation.rst:362 +#: ../../installation.rst:364 msgid "To install it using the ``brew`` package manager, run:" msgstr "" -#: ../../installation.rst:368 +#: ../../installation.rst:370 msgid "It is also available as a `a port`_ through `MacPorts`_." msgstr "" -#: ../../installation.rst:373 +#: ../../installation.rst:375 msgid "To install it using the ``port`` package manager, run:" msgstr "" -#: ../../installation.rst:383 +#: ../../installation.rst:385 msgid "Linux" msgstr "" -#: ../../installation.rst:385 -msgid "" -"Spyder can be installed via third-party distro packages on most common " -"Linux distributions." +#: ../../installation.rst:387 +msgid "Spyder can be installed via third-party distro packages on most common Linux distributions." msgstr "" -#: ../../installation.rst:387 -msgid "" -"Running Spyder installed this way will generally be the same as any other" -" distro-installed application. Alternatively, it can be launched from the" -" terminal with ``spyder`` (or ``spyder3``, on older versions of some " -"distros)." +#: ../../installation.rst:389 +msgid "Running Spyder installed this way will generally be the same as any other distro-installed application. Alternatively, it can be launched from the terminal with ``spyder`` (or ``spyder3``, on older versions of some distros)." msgstr "" -#: ../../installation.rst:394 +#: ../../installation.rst:396 msgid "Ubuntu/Debian" msgstr "" -#: ../../installation.rst:396 +#: ../../installation.rst:398 msgid "Spyder is available as `a Ubuntu package`_ and `a Debian package`_." msgstr "" -#: ../../installation.rst:401 +#: ../../installation.rst:403 msgid "To install it using the ``apt`` package manager, run:" msgstr "" -#: ../../installation.rst:411 +#: ../../installation.rst:413 msgid "Other distributions" msgstr "" -#: ../../installation.rst:413 +#: ../../installation.rst:415 msgid "Spyder is also available in other GNU/Linux distributions, including:" msgstr "" -#: ../../installation.rst:415 +#: ../../installation.rst:417 msgid "`Arch Linux`_" msgstr "" -#: ../../installation.rst:416 +#: ../../installation.rst:418 msgid "`Fedora`_" msgstr "" -#: ../../installation.rst:417 +#: ../../installation.rst:419 msgid "`Gentoo`_" msgstr "" -#: ../../installation.rst:418 +#: ../../installation.rst:420 msgid "`openSUSE`_" msgstr "" -#: ../../installation.rst:425 -msgid "" -"Please refer to the links or your distribution's documentation for how to" -" install Spyder." +#: ../../installation.rst:427 +msgid "Please refer to the links or your distribution's documentation for how to install Spyder." msgstr "" -#: ../../installation.rst:433 +#: ../../installation.rst:435 msgid "Development builds" msgstr "" -#: ../../installation.rst:435 -msgid "" -"If you want to try the next Spyder version before it is released, you " -"can! You may want to do this for fixing bugs in Spyder, adding new " -"features, learning how Spyder works or just getting a taste of what the " -"IDE can do. For more information, please see the `Contributing Guide`_ " -"included with the Spyder source or on Github, and for further detail " -"consult the `Spyder development wiki`_." +#: ../../installation.rst:437 +msgid "If you want to try the next Spyder version before it is released, you can! You may want to do this for fixing bugs in Spyder, adding new features, learning how Spyder works or just getting a taste of what the IDE can do. For more information, please see the `Contributing Guide`_ included with the Spyder source or on Github, and for further detail consult the `Spyder development wiki`_." msgstr "" -#: ../../installation.rst:450 +#: ../../installation.rst:452 msgid "Additional help" msgstr "" -#: ../../installation.rst:454 -msgid "" -"*Run in to a problem installing or running Spyder?* Read our " -"`Troubleshooting Guide and FAQ`_." +#: ../../installation.rst:456 +msgid "*Run in to a problem installing or running Spyder?* Read our :ref:`Troubleshooting Guide `." msgstr "" -#: ../../installation.rst:458 -msgid "" -"*Looking for general information about Spyder and its ecosystem?* See our" -" `main website`_." +#: ../../installation.rst:460 +msgid "*Looking for general information about Spyder and its ecosystem?* See our `main website`_." msgstr "" -#: ../../installation.rst:462 -msgid "" -"*Need to submit a bug report or feature request?* Check out our `Github " -"repository`_." +#: ../../installation.rst:464 +msgid "*Need to submit a bug report or feature request?* Check out our `Github repository`_." msgstr "" -#: ../../installation.rst:466 -msgid "" -"*Want development-oriented help and information?* Consult our `Github " -"wiki`_." +#: ../../installation.rst:468 +msgid "*Want development-oriented help and information?* Consult our `Github wiki`_." msgstr "" -#: ../../installation.rst:470 -msgid "" -"*Have a help request or discussion topic?* Subscribe to our `Google " -"Group`_." +#: ../../installation.rst:472 +msgid "*Have a help request or discussion topic?* Subscribe to our `Google Group`_." msgstr "" -#: ../../installation.rst:474 -msgid "" -"*Asking a quick question or want to chat with the dev team?* Stop by our " -"`Gitter chatroom`_." +#: ../../installation.rst:476 +msgid "*Asking a quick question or want to chat with the dev team?* Stop by our `Gitter chatroom`_." msgstr "" -#: ../../installation.rst:478 -msgid "" -"*Seeking personalized help from expert Spyder consultants?* Visit " -"`OpenTeams`_." +#: ../../installation.rst:480 +msgid "*Seeking personalized help from expert Spyder consultants?* Visit `OpenTeams`_." msgstr "" - diff --git a/doc/locales/pot/panes.pot b/doc/locales/pot/panes.pot index e304b2a3..1f575f18 100644 --- a/doc/locales/pot/panes.pot +++ b/doc/locales/pot/panes.pot @@ -1,19 +1,19 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../panes/debugging.rst:3 @@ -21,12 +21,11 @@ msgid "Debugger" msgstr "" #: ../../panes/debugging.rst:5 -msgid "" -"**Debugging** in Spyder is supported through integration with the " -"enhanced ``ipdb`` debugger in the :doc:`ipythonconsole`. This allows " -"breakpoints and the execution flow to be viewed and controlled right from" -" the Spyder GUI, as well as with all the familiar IPython console " -"commands." +msgid "**Debugging** in Spyder is supported through integration with the enhanced ``ipdb`` debugger in the :doc:`ipythonconsole`. This allows breakpoints and the execution flow to be viewed and controlled right from the Spyder GUI, as well as with all the familiar IPython console commands." +msgstr "" + +#: ../../panes/debugging.rst:8 +msgid "A Spyder IPython console window, showing the ipdb debugger in action" msgstr "" #: ../../panes/debugging.rst:15 @@ -34,45 +33,47 @@ msgid "Debugging with ipdb" msgstr "" #: ../../panes/debugging.rst:17 -msgid "" -"You can fully control debugger execution from the :guilabel:`Debug` menu," -" :guilabel:`Debug toolbar` and via configurable keyboard shortcuts, along" -" with the standard ``ipdb`` `console commands`_." +msgid "You can fully control debugger execution from the :guilabel:`Debug` menu, :guilabel:`Debug toolbar` and via configurable keyboard shortcuts, along with the standard ``ipdb`` `console commands`_." +msgstr "" + +#: ../../panes/debugging.rst:19 +msgid "A Spyder IPython console window, showing debugging from toolbar" msgstr "" #: ../../panes/debugging.rst:22 -msgid "" -"Additionally, the :doc:`editor` shows the line of code the debugger is " -"currently stopped on with an arrow." +msgid "Additionally, the :doc:`editor` shows the line of code the debugger is currently stopped on with an arrow." +msgstr "" + +#: ../../panes/debugging.rst:26 +msgid "Spyder Editor showing the debugging panel" msgstr "" #: ../../panes/debugging.rst:29 -msgid "" -"Spyder's debugger offers syntax highlighting, code completion and command" -" history, which work exactly like they do in the normal interactive " -"interpreter." +msgid "Spyder's debugger offers syntax highlighting, code completion and command history, which work exactly like they do in the normal interactive interpreter." msgstr "" #: ../../panes/debugging.rst:31 -msgid "" -"Use the up and down arrows to recall previous commands, and press " -":kbd:`Tab` to trigger autocomplete suggestions." +msgid "Use the up and down arrows to recall previous commands, and press :kbd:`Tab` to trigger autocomplete suggestions." +msgstr "" + +#: ../../panes/debugging.rst:33 +msgid "A Spyder IPython console window, showing autocompletion when debugging" msgstr "" #: ../../panes/debugging.rst:36 -#, python-format -msgid "" -"Furthermore, IPython's `magic functions`_ are available in debugging " -"mode. You can, for example, run ``%ls`` to list the contents of your " -"current working directory or ``%timeit`` to check how fast a given " -"snippet of code is." +msgid "Furthermore, IPython's `magic functions`_ are available in debugging mode. You can, for example, run ``%ls`` to list the contents of your current working directory or ``%timeit`` to check how fast a given snippet of code is." +msgstr "" + +#: ../../panes/debugging.rst:41 +msgid "Ipython console in debug mode showing timeit magic" msgstr "" #: ../../panes/debugging.rst:44 -msgid "" -"Finally, you can enter and execute multiline statements in Spyder's " -"debugger just like with the regular IPython prompt, to easily run complex" -" code." +msgid "Finally, you can enter and execute multiline statements in Spyder's debugger just like with the regular IPython prompt, to easily run complex code." +msgstr "" + +#: ../../panes/debugging.rst:46 +msgid "Debugger showing multiline debugger" msgstr "" #: ../../panes/debugging.rst:54 @@ -80,11 +81,11 @@ msgid "Breakpoints" msgstr "" #: ../../panes/debugging.rst:56 -msgid "" -"Spyder's debugger is integrated with the :guilabel:`Breakpoints` pane, " -"which lists the file, line, and condition (if any) of every breakpoint " -"defined. To open it, select :menuselection:`Debug --> List breakpoints`, " -"or press :kbd:`Ctrl-Shift-B` (:kbd:`Cmd-Shift-B` on macOS)." +msgid "Spyder's debugger is integrated with the :guilabel:`Breakpoints` pane, which lists the file, line, and condition (if any) of every breakpoint defined. To open it, select :menuselection:`Debug --> List breakpoints`, or press :kbd:`Ctrl-Shift-B` (:kbd:`Cmd-Shift-B` on macOS)." +msgstr "" + +#: ../../panes/debugging.rst:59 +msgid "Spyder's Breakpoints panel, with a number of examples showing file, line number and an optional condition" msgstr "" #: ../../panes/debugging.rst:62 @@ -96,15 +97,11 @@ msgid "With the :guilabel:`Set/clear breakpoint` option in the Debug menu." msgstr "" #: ../../panes/debugging.rst:65 -msgid "" -"Through pressing the configurable keyboard shortcut (:kbd:`F12` for " -"normal, or :kbd:`Shift-F12` for conditional breakpoints by default)." +msgid "Through pressing the configurable keyboard shortcut (:kbd:`F12` for normal, or :kbd:`Shift-F12` for conditional breakpoints by default)." msgstr "" #: ../../panes/debugging.rst:66 -msgid "" -"By clicking to the left of the line number in an open file in the Editor " -"(adding :kbd:`Shift` for a conditional breakpoint)." +msgid "By clicking to the left of the line number in an open file in the Editor (adding :kbd:`Shift` for a conditional breakpoint)." msgstr "" #: ../../panes/debugging.rst:67 @@ -115,10 +112,16 @@ msgstr "" msgid "Interactively, using the ``b`` command in a debugging session." msgstr "" +#: ../../panes/debugging.rst:70 +msgid "Spyder showing setting conditional breakpoint" +msgstr "" + #: ../../panes/debugging.rst:73 -msgid "" -"You can access and edit local and global variables at each breakpoint " -"through the :doc:`variableexplorer`." +msgid "You can access and edit local and global variables at each breakpoint through the :doc:`variableexplorer`." +msgstr "" + +#: ../../panes/debugging.rst:75 +msgid "Spyder's console and variable explorer showing local and global variables when debugging" msgstr "" #: ../../panes/debugging.rst:82 @@ -126,30 +129,27 @@ msgid "Advanced features" msgstr "" #: ../../panes/debugging.rst:84 -msgid "" -"You can avoid stepping through other Python packages while debugging by " -"enabling the new :guilabel:`Ignore Python libraries while debugging` " -"option in Spyder's preferences, under :menuselection:`IPython Console -->" -" Debugger --> Debug`. This will skip all the built-in and third-party " -"Python modules you have installed." +msgid "You can avoid stepping through other Python packages while debugging by enabling the new :guilabel:`Ignore Python libraries while debugging` option in Spyder's preferences, under :menuselection:`IPython Console --> Debugger --> Debug`. This will skip all the built-in and third-party Python modules you have installed." +msgstr "" + +#: ../../panes/debugging.rst:87 +msgid "Spyder's preferences showing Ignore Python libraries while debugging options" msgstr "" #: ../../panes/debugging.rst:90 -msgid "" -"If your code has variables with the same names as Pdb commands (e.g. " -"``b`` or ``step``), you can still refer to them as normal while " -"debugging. To call the respective Pdb command, just add an exclamation " -"point before it (e.g. ``!b`` or ``!step``)." +msgid "If your code has variables with the same names as Pdb commands (e.g. ``b`` or ``step``), you can still refer to them as normal while debugging. To call the respective Pdb command, just add an exclamation point before it (e.g. ``!b`` or ``!step``)." +msgstr "" + +#: ../../panes/debugging.rst:93 +msgid "Spyder's IPython console showing Pdb commands" msgstr "" #: ../../panes/debugging.rst:96 -msgid "" -"You can have Spyder automatically execute a custom snippet of code every " -"time the debugger stops. For example, you can use this to set specific " -"variables, or import commonly-used modules so they are always available " -"while debugging. To set this up, go to :menuselection:`Preferences --> " -"IPython Console --> Debugger --> Run code while debugging`, and enter the" -" code that you want to be executed with each step." +msgid "You can have Spyder automatically execute a custom snippet of code every time the debugger stops. For example, you can use this to set specific variables, or import commonly-used modules so they are always available while debugging. To set this up, go to :menuselection:`Preferences --> IPython Console --> Debugger --> Run code while debugging`, and enter the code that you want to be executed with each step." +msgstr "" + +#: ../../panes/debugging.rst:100 +msgid "Spyder's preferenes with debugging snippet" msgstr "" #: ../../panes/debugging.rst:107 @@ -157,47 +157,57 @@ msgid "Matplotlib support" msgstr "" #: ../../panes/debugging.rst:109 -msgid "" -"Generating Matplotlib figures is fully supported while the debugger is " -"active, including all the different graphics backends. Use the " -"``%matplotlib`` magic to change to an interactive backend (e.g. " -"``%matplotlib qt5``) to pan, zoom and adjust your plots in a separate " -"window, or switch back to the default ``inline`` (``%matplotlib inline``)" -" to see them displayed right in the :doc:`plots` pane." +msgid "Generating Matplotlib figures is fully supported while the debugger is active, including all the different graphics backends. Use the ``%matplotlib`` magic to change to an interactive backend (e.g. ``%matplotlib qt5``) to pan, zoom and adjust your plots in a separate window, or switch back to the default ``inline`` (``%matplotlib inline``) to see them displayed right in the :doc:`plots` pane." +msgstr "" + +#: ../../panes/debugging.rst:112 +msgid "Debugger showing matplotlib interactive backend" msgstr "" #: ../../panes/debugging.rst:116 -msgid "" -"To avoid showing plots while debugging, deactivate the :guilabel:`Process" -" execute events while debugging` option in :menuselection:`Preferences " -"--> IPython console --> Debugger`." -msgstr "" - -#: ../../panes/debugging.rst:122 ../../panes/editor.rst:313 -#: ../../panes/fileexplorer.rst:99 ../../panes/findinfiles.rst:65 -#: ../../panes/help.rst:80 ../../panes/historylog.rst:51 -#: ../../panes/ipythonconsole.rst:185 ../../panes/onlinehelp.rst:86 -#: ../../panes/outline.rst:54 ../../panes/plots.rst:85 -#: ../../panes/profiler.rst:99 ../../panes/projects.rst:62 -#: ../../panes/pylint.rst:91 ../../panes/variableexplorer.rst:194 +msgid "To avoid showing plots while debugging, deactivate the :guilabel:`Process execute events while debugging` option in :menuselection:`Preferences --> IPython console --> Debugger`." +msgstr "" + +#: ../../panes/debugging.rst:122 +#: ../../panes/editor.rst:313 +#: ../../panes/fileexplorer.rst:99 +#: ../../panes/findinfiles.rst:65 +#: ../../panes/help.rst:80 +#: ../../panes/historylog.rst:51 +#: ../../panes/ipythonconsole.rst:185 +#: ../../panes/onlinehelp.rst:86 +#: ../../panes/outline.rst:54 +#: ../../panes/plots.rst:85 +#: ../../panes/profiler.rst:99 +#: ../../panes/projects.rst:62 +#: ../../panes/pylint.rst:91 +#: ../../panes/variableexplorer.rst:194 msgid "Related panes" msgstr "" -#: ../../panes/debugging.rst:124 ../../panes/fileexplorer.rst:101 -#: ../../panes/findinfiles.rst:67 ../../panes/help.rst:82 -#: ../../panes/ipythonconsole.rst:188 ../../panes/outline.rst:56 -#: ../../panes/projects.rst:64 ../../panes/pylint.rst:93 +#: ../../panes/debugging.rst:124 +#: ../../panes/fileexplorer.rst:101 +#: ../../panes/findinfiles.rst:67 +#: ../../panes/help.rst:82 +#: ../../panes/ipythonconsole.rst:188 +#: ../../panes/outline.rst:56 +#: ../../panes/projects.rst:64 +#: ../../panes/pylint.rst:93 msgid ":doc:`editor`" msgstr "" -#: ../../panes/debugging.rst:125 ../../panes/editor.rst:317 -#: ../../panes/help.rst:83 ../../panes/historylog.rst:53 -#: ../../panes/plots.rst:87 ../../panes/profiler.rst:101 +#: ../../panes/debugging.rst:125 +#: ../../panes/editor.rst:317 +#: ../../panes/help.rst:83 +#: ../../panes/historylog.rst:53 +#: ../../panes/plots.rst:87 +#: ../../panes/profiler.rst:101 #: ../../panes/variableexplorer.rst:197 msgid ":doc:`ipythonconsole`" msgstr "" -#: ../../panes/debugging.rst:126 ../../panes/ipythonconsole.rst:191 +#: ../../panes/debugging.rst:126 +#: ../../panes/ipythonconsole.rst:191 #: ../../panes/plots.rst:88 msgid ":doc:`variableexplorer`" msgstr "" @@ -207,13 +217,11 @@ msgid "Editor" msgstr "" #: ../../panes/editor.rst:5 -msgid "" -"Spyder's multi-language **Editor** pane is the key element of the IDE, " -"where you can create, open, and modify source files. The Editor offers a " -"variety of core features, such as autocompletion, real-time analysis, " -"syntax highlighting, horizontal and vertical splitting, and much more. In" -" addition, it integrates a number of powerful tools for an easy to use, " -"efficient editing experience." +msgid "Spyder's multi-language **Editor** pane is the key element of the IDE, where you can create, open, and modify source files. The Editor offers a variety of core features, such as autocompletion, real-time analysis, syntax highlighting, horizontal and vertical splitting, and much more. In addition, it integrates a number of powerful tools for an easy to use, efficient editing experience." +msgstr "" + +#: ../../panes/editor.rst:9 +msgid "Spyder's Editor pane, split horizontally and with style analysis" msgstr "" #: ../../panes/editor.rst:16 @@ -224,12 +232,12 @@ msgstr "" msgid "The Editor pane consists of the following areas:" msgstr "" +#: ../../panes/editor.rst:20 +msgid "Spyder's Editor pane, showing its different areas (described below)" +msgstr "" + #: ../../panes/editor.rst:23 -msgid "" -"The left sidebar shows line numbers and displays any code analysis " -"warnings that exist in the current file. Clicking a line number selects " -"the text on that line, and clicking to the right of it sets a " -":ref:`breakpoint `." +msgid "The left sidebar shows line numbers and displays any code analysis warnings that exist in the current file. Clicking a line number selects the text on that line, and clicking to the right of it sets a :ref:`breakpoint `." msgstr "" #: ../../panes/editor.rst:25 @@ -237,28 +245,19 @@ msgid "The scrollbars allow vertical and horizontal navigation in a file." msgstr "" #: ../../panes/editor.rst:26 -msgid "" -"The context (right-click) menu displays actions relevant to whatever was " -"clicked." +msgid "The context (right-click) menu displays actions relevant to whatever was clicked." msgstr "" #: ../../panes/editor.rst:27 -msgid "" -"The options menu (\"Hamburger\" icon at top right) includes useful " -"settings and actions relevant to the Editor." +msgid "The options menu (\"Hamburger\" icon at top right) includes useful settings and actions relevant to the Editor." msgstr "" #: ../../panes/editor.rst:28 -msgid "" -"The location bar at the top of the Editor pane shows the full path of the" -" current file." +msgid "The location bar at the top of the Editor pane shows the full path of the current file." msgstr "" #: ../../panes/editor.rst:29 -msgid "" -"The tab bar displays the names of all opened files. It also has a " -":guilabel:`Browse tabs` button (at left) to show every open tab and " -"switch between them—which comes in handy if many are open." +msgid "The tab bar displays the names of all opened files. It also has a :guilabel:`Browse tabs` button (at left) to show every open tab and switch between them—which comes in handy if many are open." msgstr "" #: ../../panes/editor.rst:36 @@ -270,17 +269,19 @@ msgid "Tabs" msgstr "" #: ../../panes/editor.rst:41 -msgid "" -"You can browse and navigate between open files in the Editor with tabs. " -"Click the :guilabel:`Browse tabs` button on the left of the tab bar to " -"display a list of open files, with the active tab checked." +msgid "You can browse and navigate between open files in the Editor with tabs. Click the :guilabel:`Browse tabs` button on the left of the tab bar to display a list of open files, with the active tab checked." +msgstr "" + +#: ../../panes/editor.rst:44 +msgid "Spyder's Editor pane, showing the tabs browser" msgstr "" #: ../../panes/editor.rst:47 -msgid "" -"Reorder files by dragging and dropping, or with :guilabel:`Sort tabs " -"alphabetically` in the options menu, which also allows closing all tabs " -"to the right of, or all tabs but the active one." +msgid "Reorder files by dragging and dropping, or with :guilabel:`Sort tabs alphabetically` in the options menu, which also allows closing all tabs to the right of, or all tabs but the active one." +msgstr "" + +#: ../../panes/editor.rst:49 +msgid "Spyder's Editor pane, showing how to browse and sort open tabs alphabetically" msgstr "" #: ../../panes/editor.rst:54 @@ -288,18 +289,19 @@ msgid "File switcher" msgstr "" #: ../../panes/editor.rst:56 -msgid "" -"The Editor features a file switcher, which enables you to navigate and " -"switch between multiple open files. The file switcher is helpful for " -"locating any file when there are several files opened." +msgid "The Editor features a file switcher, which enables you to navigate and switch between multiple open files. The file switcher is helpful for locating any file when there are several files opened." +msgstr "" + +#: ../../panes/editor.rst:59 +msgid "Spyder's Editor pane, showing the file switcher" msgstr "" #: ../../panes/editor.rst:62 -msgid "" -"It can be accessed from the :menuselection:`File --> File Switcher` menu " -"or :kbd:`Ctrl-P`, and includes a search function. You can type in any " -"part of an open file's name and—if exists—it can be switched to by " -"pressing :kbd:`Enter`." +msgid "It can be accessed from the :menuselection:`File --> File Switcher` menu or :kbd:`Ctrl-P`, and includes a search function. You can type in any part of an open file's name and—if exists—it can be switched to by pressing :kbd:`Enter`." +msgstr "" + +#: ../../panes/editor.rst:65 +msgid "Spyder's Editor pane, showing searching and switching to an existing file" msgstr "" #: ../../panes/editor.rst:70 @@ -307,25 +309,19 @@ msgid "Split panels" msgstr "" #: ../../panes/editor.rst:72 -msgid "" -"The Editor can be split horizontally and vertically into as many distinct" -" panels as desired. This allows viewing and editing the contents of " -"several files (or different parts of the same file) at the same time." +msgid "The Editor can be split horizontally and vertically into as many distinct panels as desired. This allows viewing and editing the contents of several files (or different parts of the same file) at the same time." +msgstr "" + +#: ../../panes/editor.rst:75 +msgid "Spyder's Editor pane, showing how to split panels" msgstr "" #: ../../panes/editor.rst:78 -msgid "" -"Split the Editor with the :guilabel:`Split vertically` (:kbd:`Ctrl-" -"Shift-{`) and :guilabel:`Split horizontally` (:kbd:`Ctrl-Shift--`) " -"commands in the options menu, and use :guilabel:`Close this panel` (:kbd" -":`Alt-Shift-W`) to close the selected split panel." +msgid "Split the Editor with the :guilabel:`Split vertically` (:kbd:`Ctrl-Shift-{`) and :guilabel:`Split horizontally` (:kbd:`Ctrl-Shift--`) commands in the options menu, and use :guilabel:`Close this panel` (:kbd:`Alt-Shift-W`) to close the selected split panel." msgstr "" #: ../../panes/editor.rst:80 -msgid "" -":menuselection:`Close this panel` closes a split panel, while " -":menuselection:`Close` hides the entire Editor *pane* (including all " -"splits, which are restored when the Editor is re-opened)." +msgid ":menuselection:`Close this panel` closes a split panel, while :menuselection:`Close` hides the entire Editor *pane* (including all splits, which are restored when the Editor is re-opened)." msgstr "" #: ../../panes/editor.rst:86 @@ -337,27 +333,19 @@ msgid "Syntax highlighting" msgstr "" #: ../../panes/editor.rst:91 -msgid "" -"To improve the readability of your code, Spyder has a syntax highlighting" -" feature that determines the color and style of text in the Editor, as " -"well as in the :doc:`ipythonconsole`." +msgid "To improve the readability of your code, Spyder has a syntax highlighting feature that determines the color and style of text in the Editor, as well as in the :doc:`ipythonconsole`." msgstr "" #: ../../panes/editor.rst:93 -msgid "" -"You can configure and preview syntax highlighting themes and fonts under " -":menuselection:`Preferences --> Appearance`. The :guilabel:`Syntax " -"highlighting theme` section allows you to change the color and style of " -"the syntax elements and background to match your preferences. You can " -"switch between available themes in the drop-down menu, modify the " -"selected theme, create a new theme, and more. The :guilabel:`Fonts` " -"section lets you change the text font and size." +msgid "You can configure and preview syntax highlighting themes and fonts under :menuselection:`Preferences --> Appearance`. The :guilabel:`Syntax highlighting theme` section allows you to change the color and style of the syntax elements and background to match your preferences. You can switch between available themes in the drop-down menu, modify the selected theme, create a new theme, and more. The :guilabel:`Fonts` section lets you change the text font and size." +msgstr "" + +#: ../../panes/editor.rst:98 +msgid "Spyder's Editor pane, showing how to switch between syntax highlighting themes" msgstr "" #: ../../panes/editor.rst:101 -msgid "" -"Changes made to the syntax highlighting theme and font settings are " -"common to all source files, regardless of their language." +msgid "Changes made to the syntax highlighting theme and font settings are common to all source files, regardless of their language." msgstr "" #: ../../panes/editor.rst:105 @@ -365,12 +353,11 @@ msgid "Code cells" msgstr "" #: ../../panes/editor.rst:107 -msgid "" -"A \"code cell\" in Spyder is a block of lines, typically in a script, " -"that can be easily executed all at once in the current " -":doc:`ipythonconsole`. This is similar to \"cell\" behavior in Jupyter " -"Notebook and MATLAB. You can divide your scripts into as many cells as " -"needed, or none at all—the choice is yours." +msgid "A \"code cell\" in Spyder is a block of lines, typically in a script, that can be easily executed all at once in the current :doc:`ipythonconsole`. This is similar to \"cell\" behavior in Jupyter Notebook and MATLAB. You can divide your scripts into as many cells as needed, or none at all—the choice is yours." +msgstr "" + +#: ../../panes/editor.rst:111 +msgid "Spyder's Editor pane, showing an example of a code cell" msgstr "" #: ../../panes/editor.rst:114 @@ -378,7 +365,6 @@ msgid "You can separate cells by lines starting with either:" msgstr "" #: ../../panes/editor.rst:116 -#, python-format msgid "``# %%`` (standard cell separator), or" msgstr "" @@ -387,29 +373,19 @@ msgid "``# `` (IPython notebook cell separator)" msgstr "" #: ../../panes/editor.rst:119 -#, python-format -msgid "" -"Providing a description to the right of the separator will give that cell" -" its own name in the :doc:`outline`. You can also create \"subsections\" " -"by adding more ``%`` signs to the cell separator, e.g. ``# %%%`` to " -"create a level 2 subsection, ``# %%%%`` for level 3, etc. This displays " -"multiple levels in the :doc:`outline` pane." +msgid "Providing a description to the right of the separator will give that cell its own name in the :doc:`outline`. You can also create \"subsections\" by adding more ``%`` signs to the cell separator, e.g. ``# %%%`` to create a level 2 subsection, ``# %%%%`` for level 3, etc. This displays multiple levels in the :doc:`outline` pane." +msgstr "" + +#: ../../panes/editor.rst:123 +msgid "Spyder outline pane, showing an example of sub sections" msgstr "" #: ../../panes/editor.rst:126 -msgid "" -"This only affects how the cell is displayed in the :doc:`outline`, and " -"doesn't affect running it in the Editor." +msgid "This only affects how the cell is displayed in the :doc:`outline`, and doesn't affect running it in the Editor." msgstr "" #: ../../panes/editor.rst:128 -msgid "" -"To run the code in a cell, use :menuselection:`Run --> Run cell`, the " -":guilabel:`Run cell` button in the toolbar or the keyboard shortcut (:kbd" -":`Ctrl-Enter`/:kbd:`Cmd-Return` by default). You can also run a cell and " -"then jump to the next one, letting you quickly step through multiple " -"cells, using :menuselection:`Run --> Run cell and advance` (:kbd:`Shift-" -"Enter` by default)." +msgid "To run the code in a cell, use :menuselection:`Run --> Run cell`, the :guilabel:`Run cell` button in the toolbar or the keyboard shortcut (:kbd:`Ctrl-Enter`/:kbd:`Cmd-Return` by default). You can also run a cell and then jump to the next one, letting you quickly step through multiple cells, using :menuselection:`Run --> Run cell and advance` (:kbd:`Shift-Enter` by default)." msgstr "" #: ../../panes/editor.rst:133 @@ -417,22 +393,19 @@ msgid "Automatic formatting" msgstr "" #: ../../panes/editor.rst:135 -msgid "" -"The Editor has built-in support for automatically formatting your code " -"using several popular tools, including `Autopep8 " -"`_ and `Black " -"`_. The :guilabel:`Format file " -"or selection with {tool}` command in the :guilabel:`Source` or context " -"menu will format either the selected fragment (if text is selected) or " -"the entire active file." +msgid "The Editor has built-in support for automatically formatting your code using several popular tools, including `Autopep8 `_ and `Black `_. The :guilabel:`Format file or selection with {tool}` command in the :guilabel:`Source` or context menu will format either the selected fragment (if text is selected) or the entire active file." +msgstr "" + +#: ../../panes/editor.rst:138 +msgid "Spyder Editor pane, showing an example of code selection formatting" msgstr "" #: ../../panes/editor.rst:141 -msgid "" -"You can have the Editor automatically autoformat a file every time you " -"save your work. To set this up, go to :menuselection:`Preferences --> " -"Completion and linting --> Code style and formatting --> Code formatting`" -" and check the :guilabel:`Autoformat files on save` option." +msgid "You can have the Editor automatically autoformat a file every time you save your work. To set this up, go to :menuselection:`Preferences --> Completion and linting --> Code style and formatting --> Code formatting` and check the :guilabel:`Autoformat files on save` option." +msgstr "" + +#: ../../panes/editor.rst:144 +msgid "Spyder's preferences dialog, showing checking the autoformat files on save setting" msgstr "" #: ../../panes/editor.rst:151 @@ -440,9 +413,7 @@ msgid "Running code" msgstr "" #: ../../panes/editor.rst:153 -msgid "" -"The Editor lets you run an entire file as well as specific lines, " -"selections or cells." +msgid "The Editor lets you run an entire file as well as specific lines, selections or cells." msgstr "" #: ../../panes/editor.rst:155 @@ -454,9 +425,7 @@ msgid "The :doc:`ipythonconsole` will display output and errors." msgstr "" #: ../../panes/editor.rst:158 -msgid "" -"The :doc:`variableexplorer` allows you to browse and interact with the " -"objects generated." +msgid "The :doc:`variableexplorer` allows you to browse and interact with the objects generated." msgstr "" #: ../../panes/editor.rst:159 @@ -468,11 +437,7 @@ msgid "Run file" msgstr "" #: ../../panes/editor.rst:165 -msgid "" -"Run an entire Editor file using the :menuselection:`Run --> Run` menu " -"item, the :guilabel:`Run file` toolbar button or the :kbd:`F5` key. Use " -":menuselection:`Run --> Re-Run last script` to re-run the most recent " -"file executed with the above." +msgid "Run an entire Editor file using the :menuselection:`Run --> Run` menu item, the :guilabel:`Run file` toolbar button or the :kbd:`F5` key. Use :menuselection:`Run --> Re-Run last script` to re-run the most recent file executed with the above." msgstr "" #: ../../panes/editor.rst:170 @@ -480,14 +445,7 @@ msgid "Run line/selection" msgstr "" #: ../../panes/editor.rst:172 -msgid "" -"You can execute the current line—or multiple selected lines—using the " -":guilabel:`Run selection or current line` option from the toolbar or the " -":menuselection:`Run` menu, as well as with the :kbd:`F9` key. After " -"running the current line, the cursor automatically advances to the next " -"one, so you can step through your code line by line. Unlike " -":guilabel:`Run file`, the executed lines are shown in the " -":doc:`ipythonconsole`." +msgid "You can execute the current line—or multiple selected lines—using the :guilabel:`Run selection or current line` option from the toolbar or the :menuselection:`Run` menu, as well as with the :kbd:`F9` key. After running the current line, the cursor automatically advances to the next one, so you can step through your code line by line. Unlike :guilabel:`Run file`, the executed lines are shown in the :doc:`ipythonconsole`." msgstr "" #: ../../panes/editor.rst:178 @@ -495,13 +453,7 @@ msgid "Run cell" msgstr "" #: ../../panes/editor.rst:180 -msgid "" -"To run a cell, place your cursor inside it and use the " -":menuselection:`Run --> Run cell` menu item, the :guilabel:`Run current " -"cell` toolbar button or the :kbd:`Ctrl-Enter` / :kbd:`Cmd-Return` " -"keyboard shortcut. Use :guilabel:`Run cell and advance` in the " -":guilabel:`Run` menu/toolbar or :kbd:`Shift-Enter` to jump to the next " -"cell after running, useful for stepping through cells quickly." +msgid "To run a cell, place your cursor inside it and use the :menuselection:`Run --> Run cell` menu item, the :guilabel:`Run current cell` toolbar button or the :kbd:`Ctrl-Enter` / :kbd:`Cmd-Return` keyboard shortcut. Use :guilabel:`Run cell and advance` in the :guilabel:`Run` menu/toolbar or :kbd:`Shift-Enter` to jump to the next cell after running, useful for stepping through cells quickly." msgstr "" #: ../../panes/editor.rst:185 @@ -509,17 +461,15 @@ msgid "Run configuration" msgstr "" #: ../../panes/editor.rst:187 -msgid "" -"You can use the :guilabel:`Run configuration per file` dialog to set each" -" file's working directory, console mode (current, dedicated or external)," -" command line arguments, execution options (clear all variables, run in " -"an existing/empty namespace, debug on error), and more." +msgid "You can use the :guilabel:`Run configuration per file` dialog to set each file's working directory, console mode (current, dedicated or external), command line arguments, execution options (clear all variables, run in an existing/empty namespace, debug on error), and more." +msgstr "" + +#: ../../panes/editor.rst:189 +msgid "Spyder's Editor pane, showing the Run Configuration dialog" msgstr "" #: ../../panes/editor.rst:192 -msgid "" -"To access it, click :menuselection:`Run --> Configuration per file...` or" -" press :kbd:`Ctrl-F6` / :kbd:`Cmd-F6`." +msgid "To access it, click :menuselection:`Run --> Configuration per file...` or press :kbd:`Ctrl-F6` / :kbd:`Cmd-F6`." msgstr "" #: ../../panes/editor.rst:198 @@ -531,19 +481,11 @@ msgid "Find and replace" msgstr "" #: ../../panes/editor.rst:203 -msgid "" -"To search for text in the current file, use :menuselection:`Search --> " -"Find text` or :kbd:`Ctrl-F` / :kbd:`Cmd-F`, and to replace it, use " -":menuselection:`Search --> Replace text` or :kbd:`Ctrl-R` / :kbd:`Cmd-R`." -" Typing your search string in the resulting panel below the Editor " -"highlights each result and counts the total. Navigate between matches " -"with the :guilabel:`Find Previous` and :guilabel:`Find Next` buttons in " -"the find/replace panel, their corresponding entries in the " -":guilabel:`Search` menu, or use the :kbd:`F2` and :kbd:`F3` keys. Use the" -" :guilabel:`.*` button to process search text as a `regular expression " -"`_, :guilabel:`Aa` to treat it" -" as case-sensitive and :guilabel:`[–]` to only match whole words (e.g. " -"for ``data``, match ``data()`` but not ``dataframe``)." +msgid "To search for text in the current file, use :menuselection:`Search --> Find text` or :kbd:`Ctrl-F` / :kbd:`Cmd-F`, and to replace it, use :menuselection:`Search --> Replace text` or :kbd:`Ctrl-R` / :kbd:`Cmd-R`. Typing your search string in the resulting panel below the Editor highlights each result and counts the total. Navigate between matches with the :guilabel:`Find Previous` and :guilabel:`Find Next` buttons in the find/replace panel, their corresponding entries in the :guilabel:`Search` menu, or use the :kbd:`F2` and :kbd:`F3` keys. Use the :guilabel:`.*` button to process search text as a `regular expression `_, :guilabel:`Aa` to treat it as case-sensitive and :guilabel:`[–]` to only match whole words (e.g. for ``data``, match ``data()`` but not ``dataframe``)." +msgstr "" + +#: ../../panes/editor.rst:208 +msgid "Spyder's Editor pane, showing the find and replace panel" msgstr "" #: ../../panes/editor.rst:213 @@ -551,11 +493,11 @@ msgid "Go to line" msgstr "" #: ../../panes/editor.rst:215 -msgid "" -"The :guilabel:`Go to line` dialog allows jumping to a specific line in " -"the active file. Open it with :menuselection:`Search --> Go to line` or " -":kbd:`Ctrl-L` / :kbd:`Cmd-L`, type the line number you want to scroll to " -"and press :kbd:`Enter` (or click :guilabel:`OK`)." +msgid "The :guilabel:`Go to line` dialog allows jumping to a specific line in the active file. Open it with :menuselection:`Search --> Go to line` or :kbd:`Ctrl-L` / :kbd:`Cmd-L`, type the line number you want to scroll to and press :kbd:`Enter` (or click :guilabel:`OK`)." +msgstr "" + +#: ../../panes/editor.rst:218 +msgid "Spyder's Editor pane, showing the go to line feature" msgstr "" #: ../../panes/editor.rst:221 @@ -567,12 +509,11 @@ msgid "Class/function selector" msgstr "" #: ../../panes/editor.rst:227 -msgid "" -"This panel, activated under :menuselection:`Source --> Show selector for " -"classes and functions`, displays (as applicable) the name of the cell, " -"function/method and class the Editor cursor is located inside. Use its " -"dropdowns to view and jump to the functions, methods and classes in the " -"current file." +msgid "This panel, activated under :menuselection:`Source --> Show selector for classes and functions`, displays (as applicable) the name of the cell, function/method and class the Editor cursor is located inside. Use its dropdowns to view and jump to the functions, methods and classes in the current file." +msgstr "" + +#: ../../panes/editor.rst:230 +msgid "Spyder's Editor pane, showing the class and function selector panel" msgstr "" #: ../../panes/editor.rst:237 @@ -580,27 +521,15 @@ msgid "Code analysis and completions" msgstr "" #: ../../panes/editor.rst:239 -msgid "" -"Spyder uses the `Language Server Protocol `_ (LSP) to provide code completion and " -"linting for the Editor, similar to VSCode, Neovim, and other popular " -"editors/IDEs." +msgid "Spyder uses the `Language Server Protocol `_ (LSP) to provide code completion and linting for the Editor, similar to VSCode, Neovim, and other popular editors/IDEs." msgstr "" #: ../../panes/editor.rst:243 -msgid "" -"Many issues with completion and linting are outside of Spyder's control, " -"and are either limitations with the LSP or the code that is being " -"introspected, but some can be worked around. See :ref:`code-completion-" -"problems-ref` for troubleshooting steps." +msgid "Many issues with completion and linting are outside of Spyder's control, and are either limitations with the LSP or the code that is being introspected, but some can be worked around. See :ref:`code-completion-problems-ref` for troubleshooting steps." msgstr "" #: ../../panes/editor.rst:246 -msgid "" -"Python is supported out of the box, and advanced users can add completion" -" and linting support for other languages by setting up LSP servers for " -"them under :menuselection:`Preferences --> Completion and Linting --> " -"Other languages`." +msgid "Python is supported out of the box, and advanced users can add completion and linting support for other languages by setting up LSP servers for them under :menuselection:`Preferences --> Completion and Linting --> Other languages`." msgstr "" #: ../../panes/editor.rst:250 @@ -608,24 +537,15 @@ msgid "Code completion" msgstr "" #: ../../panes/editor.rst:252 -msgid "" -"Automatic code completion as you type is enabled by default in the " -"Editor, and can also be triggered manually with :kbd:`Ctrl-Space`/:kbd" -":`Cmd-Space`, showing you possible completions (with pop-up help for " -"each) and available code snippets. For example, typing ``cla`` will " -"display the keyword ``class``, the decorator ``classmethod`` and two " -"built-in snippets with class templates. Select the desired completion " -"with the arrow keys and :kbd:`Enter`, or by double clicking." +msgid "Automatic code completion as you type is enabled by default in the Editor, and can also be triggered manually with :kbd:`Ctrl-Space`/:kbd:`Cmd-Space`, showing you possible completions (with pop-up help for each) and available code snippets. For example, typing ``cla`` will display the keyword ``class``, the decorator ``classmethod`` and two built-in snippets with class templates. Select the desired completion with the arrow keys and :kbd:`Enter`, or by double clicking." +msgstr "" + +#: ../../panes/editor.rst:256 +msgid "Spyder's Editor pane, showing a code completion example" msgstr "" #: ../../panes/editor.rst:259 -msgid "" -"You can enable or disable on-the-fly code completion, as well as modify " -"when it is triggered and what results are shown, under " -":menuselection:`Preferences --> Completion and Linting --> General --> " -"Completions`. Spyder also allows you to define custom completion snippets" -" to use, in addition to the ones offered by the LSP, under " -":menuselection:`Preferences --> Completion and Linting --> Advanced`." +msgid "You can enable or disable on-the-fly code completion, as well as modify when it is triggered and what results are shown, under :menuselection:`Preferences --> Completion and Linting --> General --> Completions`. Spyder also allows you to define custom completion snippets to use, in addition to the ones offered by the LSP, under :menuselection:`Preferences --> Completion and Linting --> Advanced`." msgstr "" #: ../../panes/editor.rst:264 @@ -633,30 +553,27 @@ msgid "Linting and code style" msgstr "" #: ../../panes/editor.rst:266 -msgid "" -"Spyder can optionally highlight syntax errors, style issues, and other " -"potential problems with your code in the Editor, which can help you spot " -"bugs quickly and make your code easier to read and understand." +msgid "Spyder can optionally highlight syntax errors, style issues, and other potential problems with your code in the Editor, which can help you spot bugs quickly and make your code easier to read and understand." +msgstr "" + +#: ../../panes/editor.rst:268 +msgid "Spyder's Editor pane, showing an example of a highlighted code error" msgstr "" #: ../../panes/editor.rst:271 -msgid "" -"The Editor's basic linting, powered by `Pyflakes " -"`_, warns of syntax errors and likely " -"bugs in your code. It is on by default, and can be disabled or customized" -" under :menuselection:`Preferences --> Completion and Linting --> " -"Linting`." +msgid "The Editor's basic linting, powered by `Pyflakes `_, warns of syntax errors and likely bugs in your code. It is on by default, and can be disabled or customized under :menuselection:`Preferences --> Completion and Linting --> Linting`." +msgstr "" + +#: ../../panes/editor.rst:274 +msgid "Spyder's preferences dialog, showing linting settings" msgstr "" #: ../../panes/editor.rst:277 -msgid "" -"Code style analysis, powered by `Pycodestyle " -"`_, flags deviations from the " -"style conventions in :pep:`8`. It is not active by default, but you can " -"enable it and customize the `Pycodestyle error codes " -"`_ shown " -"with the options under :menuselection:`Preferences --> Completion and " -"Linting --> Code style and formatting --> Code Style`." +msgid "Code style analysis, powered by `Pycodestyle `_, flags deviations from the style conventions in :pep:`8`. It is not active by default, but you can enable it and customize the `Pycodestyle error codes `_ shown with the options under :menuselection:`Preferences --> Completion and Linting --> Code style and formatting --> Code Style`." +msgstr "" + +#: ../../panes/editor.rst:280 +msgid "Spyder's preferences dialog, showing code style and formatting settings" msgstr "" #: ../../panes/editor.rst:285 @@ -664,27 +581,23 @@ msgid "Introspection features" msgstr "" #: ../../panes/editor.rst:287 -msgid "" -"If there's a function, class or variable for which you would like to " -"check its definition, you need to :kbd:`Ctrl`/:kbd:`Cmd`-click its name " -"in the Editor (or click its name and press :kbd:`Ctrl-G` / :kbd:`Cmd-G` " -"to jump to the file and line where it is declared." +msgid "If there's a function, class or variable for which you would like to check its definition, you need to :kbd:`Ctrl`/:kbd:`Cmd`-click its name in the Editor (or click its name and press :kbd:`Ctrl-G` / :kbd:`Cmd-G` to jump to the file and line where it is declared." +msgstr "" + +#: ../../panes/editor.rst:289 +msgid "Spyder's Editor pane, showing the go to definition feature" msgstr "" #: ../../panes/editor.rst:292 -msgid "" -"You can hover over the name of an object for pop-up help, as " -":ref:`described in the Help pane docs `." +msgid "You can hover over the name of an object for pop-up help, as :ref:`described in the Help pane docs `." +msgstr "" + +#: ../../panes/editor.rst:294 +msgid "Spyder's Editor pane, showing an example of a hover hint" msgstr "" #: ../../panes/editor.rst:297 -msgid "" -"Finally, if you type the name of a function, method or class constructor " -"and then an open parenthesis, a calltip will pop up which shows the " -"function's parameters as you type them, as well as a summary of its " -"documentation. These features can be enabled and customized under " -":menuselection:`Preferences --> Completion and Linting --> " -"Introspection`." +msgid "Finally, if you type the name of a function, method or class constructor and then an open parenthesis, a calltip will pop up which shows the function's parameters as you type them, as well as a summary of its documentation. These features can be enabled and customized under :menuselection:`Preferences --> Completion and Linting --> Introspection`." msgstr "" #: ../../panes/editor.rst:304 @@ -692,28 +605,29 @@ msgid "Keyboard shortcuts" msgstr "" #: ../../panes/editor.rst:306 -msgid "" -"To view the Editor's primary keyboard shortcuts, consult its section " -"under :menuselection:`Help --> Shortcuts Summary`. The full list can be " -"browsed, searched and customized (on double-click) in " -":menuselection:`Preferences --> Keyboard shortcuts`." +msgid "To view the Editor's primary keyboard shortcuts, consult its section under :menuselection:`Help --> Shortcuts Summary`. The full list can be browsed, searched and customized (on double-click) in :menuselection:`Preferences --> Keyboard shortcuts`." msgstr "" -#: ../../panes/editor.rst:315 ../../panes/findinfiles.rst:68 -#: ../../panes/outline.rst:57 ../../panes/projects.rst:65 +#: ../../panes/editor.rst:315 +#: ../../panes/findinfiles.rst:68 +#: ../../panes/outline.rst:57 +#: ../../panes/projects.rst:65 msgid ":doc:`fileexplorer`" msgstr "" -#: ../../panes/editor.rst:316 ../../panes/fileexplorer.rst:102 +#: ../../panes/editor.rst:316 +#: ../../panes/fileexplorer.rst:102 msgid ":doc:`findinfiles`" msgstr "" -#: ../../panes/editor.rst:318 ../../panes/fileexplorer.rst:103 +#: ../../panes/editor.rst:318 +#: ../../panes/fileexplorer.rst:103 #: ../../panes/outline.rst:58 msgid ":doc:`projects`" msgstr "" -#: ../../panes/editor.rst:319 ../../panes/profiler.rst:102 +#: ../../panes/editor.rst:319 +#: ../../panes/profiler.rst:102 msgid ":doc:`pylint`" msgstr "" @@ -722,11 +636,11 @@ msgid "Files" msgstr "" #: ../../panes/fileexplorer.rst:5 -msgid "" -"The **Files** pane is a filesystem and directory browser built right into" -" Spyder. You can view and filter files according to their type and " -"extension, open them with the :doc:`editor` or an external tool, and " -"perform many common operations." +msgid "The **Files** pane is a filesystem and directory browser built right into Spyder. You can view and filter files according to their type and extension, open them with the :doc:`editor` or an external tool, and perform many common operations." +msgstr "" + +#: ../../panes/fileexplorer.rst:8 +msgid "Spyder Files pane, showing a tree view of files and metadata" msgstr "" #: ../../panes/fileexplorer.rst:17 @@ -734,28 +648,27 @@ msgid "File operations" msgstr "" #: ../../panes/fileexplorer.rst:19 -msgid "" -"To browse the files on your system, use the arrows at the top of the " -"pane. You can expand/collapse the folders in the pane to display the " -"files and subdirectories hierarchically. Double-clicking a folder will " -"open it, showing the files inside and making it your working directory." +msgid "To browse the files on your system, use the arrows at the top of the pane. You can expand/collapse the folders in the pane to display the files and subdirectories hierarchically. Double-clicking a folder will open it, showing the files inside and making it your working directory." +msgstr "" + +#: ../../panes/fileexplorer.rst:23 +msgid "Spyder Files pane showing browsing directories" msgstr "" #: ../../panes/fileexplorer.rst:26 -msgid "" -"To open a file in the :guilabel:`Editor` from the :guilabel:`Files` pane," -" double-click its name. If you right-click over it, you will see a " -"context menu that allows you to access a number of functions, including " -"running scripts; creating, renaming, moving, deleting files; and opening " -"them in your computer's file manager." +msgid "To open a file in the :guilabel:`Editor` from the :guilabel:`Files` pane, double-click its name. If you right-click over it, you will see a context menu that allows you to access a number of functions, including running scripts; creating, renaming, moving, deleting files; and opening them in your computer's file manager." +msgstr "" + +#: ../../panes/fileexplorer.rst:29 +msgid "Spyder Files pane showing context menu" msgstr "" #: ../../panes/fileexplorer.rst:32 -msgid "" -"You can copy and paste one or several files to and from the pane, and " -"copy their absolute or relative paths to the clipboard as text. If " -"copying the paths for multiple files, they will be automatically " -"formatted so you can paste them directly into a Python list." +msgid "You can copy and paste one or several files to and from the pane, and copy their absolute or relative paths to the clipboard as text. If copying the paths for multiple files, they will be automatically formatted so you can paste them directly into a Python list." +msgstr "" + +#: ../../panes/fileexplorer.rst:35 +msgid "Spyder Files pane showing copying absolute path to Editor" msgstr "" #: ../../panes/fileexplorer.rst:44 @@ -763,53 +676,48 @@ msgid "Version control support" msgstr "" #: ../../panes/fileexplorer.rst:46 -msgid "" -"The :guilabel:`Files` pane allows you to perform basic operations with " -"the `Git`_ distributed version control system, like committing your " -"changes and browsing the repository a given file or folder is part of. " -"This is :ref:`particularly useful` when you're working in " -"Spyder :doc:`projects`." +msgid "The :guilabel:`Files` pane allows you to perform basic operations with the `Git`_ distributed version control system, like committing your changes and browsing the repository a given file or folder is part of. This is :ref:`particularly useful` when you're working in Spyder :doc:`projects`." +msgstr "" + +#: ../../panes/fileexplorer.rst:51 +msgid "Spyder Files pane showing committing change of file" msgstr "" -#: ../../panes/fileexplorer.rst:58 ../../panes/ipythonconsole.rst:65 -#: ../../panes/outline.rst:16 ../../panes/plots.rst:20 -#: ../../panes/pylint.rst:50 ../../panes/variableexplorer.rst:103 +#: ../../panes/fileexplorer.rst:58 +#: ../../panes/ipythonconsole.rst:65 +#: ../../panes/outline.rst:16 +#: ../../panes/plots.rst:20 +#: ../../panes/pylint.rst:50 +#: ../../panes/variableexplorer.rst:103 msgid "Options menu" msgstr "" #: ../../panes/fileexplorer.rst:60 -msgid "" -"The options menu in the top right of the :guilabel:`Files` pane offers " -"several ways to customize how your files are displayed." +msgid "The options menu in the top right of the :guilabel:`Files` pane offers several ways to customize how your files are displayed." msgstr "" #: ../../panes/fileexplorer.rst:62 -msgid "" -"By default, the pane displays the contents of your working directory " -"without filtering. However, it can filter the list to show only files " -"matching the patterns set under :guilabel:`Show filenames with these " -"extensions...`, if you toggle the :guilabel:`Filter filenames` button in " -"the pane toolbar." +msgid "By default, the pane displays the contents of your working directory without filtering. However, it can filter the list to show only files matching the patterns set under :guilabel:`Show filenames with these extensions...`, if you toggle the :guilabel:`Filter filenames` button in the pane toolbar." +msgstr "" + +#: ../../panes/fileexplorer.rst:65 +msgid "Spyder Files pane showing filtering files" msgstr "" #: ../../panes/fileexplorer.rst:68 -msgid "" -"You can also activate the :guilabel:`Show hidden files` option, which " -"will display files that are invisible by default in your operating " -"system." +msgid "You can also activate the :guilabel:`Show hidden files` option, which will display files that are invisible by default in your operating system." msgstr "" #: ../../panes/fileexplorer.rst:70 -msgid "" -"Additionally, you can change which file attributes you want to see by " -"hiding or displaying the :guilabel:`Type`, :guilabel:`Size` and " -":guilabel:`Date Modified` columns using the corresponding menu options." +msgid "Additionally, you can change which file attributes you want to see by hiding or displaying the :guilabel:`Type`, :guilabel:`Size` and :guilabel:`Date Modified` columns using the corresponding menu options." +msgstr "" + +#: ../../panes/fileexplorer.rst:72 +msgid "Spyder Files pane showing columns checked and shown" msgstr "" #: ../../panes/fileexplorer.rst:75 -msgid "" -"The menu also gives you the option to open files and directories with a " -"single instead of a double click, to suit your preferences." +msgid "The menu also gives you the option to open files and directories with a single instead of a double click, to suit your preferences." msgstr "" #: ../../panes/fileexplorer.rst:81 @@ -817,21 +725,19 @@ msgid "File associations" msgstr "" #: ../../panes/fileexplorer.rst:83 -msgid "" -":guilabel:`Files` allows you to associate different external applications" -" with specific file extensions they can open. Under the :guilabel:`File " -"associations` tab of the :guilabel:`Files` preferences pane, you can add " -"file types and set the external program used to open each of them by " -"default." +msgid ":guilabel:`Files` allows you to associate different external applications with specific file extensions they can open. Under the :guilabel:`File associations` tab of the :guilabel:`Files` preferences pane, you can add file types and set the external program used to open each of them by default." +msgstr "" + +#: ../../panes/fileexplorer.rst:86 +msgid "Spyder Files pane showing files associations" msgstr "" #: ../../panes/fileexplorer.rst:89 -msgid "" -"Once you've set this up, files will automatically launch in the " -"associated application when opened from Spyder's :guilabel:`Files` pane. " -"Additionally, when you right-click a file, you will find an " -":guilabel:`Open with...` option that will allow you to select from the " -"applications associated with this extension." +msgid "Once you've set this up, files will automatically launch in the associated application when opened from Spyder's :guilabel:`Files` pane. Additionally, when you right-click a file, you will find an :guilabel:`Open with...` option that will allow you to select from the applications associated with this extension." +msgstr "" + +#: ../../panes/fileexplorer.rst:92 +msgid "Spyder Files pane showing opening file with associated program" msgstr "" #: ../../panes/findinfiles.rst:3 @@ -839,9 +745,11 @@ msgid "Find" msgstr "" #: ../../panes/findinfiles.rst:5 -msgid "" -"The **Find** pane allows you to search the content of text files in a " -"user-defined location, with advanced features to filter your results." +msgid "The **Find** pane allows you to search the content of text files in a user-defined location, with advanced features to filter your results." +msgstr "" + +#: ../../panes/findinfiles.rst:7 +msgid "Spyder Find in Files panel, with search results shown per-file" msgstr "" #: ../../panes/findinfiles.rst:14 @@ -849,23 +757,19 @@ msgid "Using the Find pane" msgstr "" #: ../../panes/findinfiles.rst:16 -msgid "" -"To search for text in the Find pane, enter it in the field in the top " -"left and press the search button. This will allow you to view and " -"navigate through all the occurrences of your search text in your working " -"directory. You can expand or collapse the search results to view the " -"matches in each file. Clicking on a match will automatically open the " -"file and highlight the line where the text was found." +msgid "To search for text in the Find pane, enter it in the field in the top left and press the search button. This will allow you to view and navigate through all the occurrences of your search text in your working directory. You can expand or collapse the search results to view the matches in each file. Clicking on a match will automatically open the file and highlight the line where the text was found." +msgstr "" + +#: ../../panes/findinfiles.rst:21 +msgid "Spyder Find pane showing search and going to a file" msgstr "" #: ../../panes/findinfiles.rst:24 -msgid "" -"If you want to change the scope of your search, select another directory," -" project or file in the :guilabel:`Search in` menu. The locations that " -"you select for your search will be stored in the list so you can access " -"them easily in the future. To erase all of these saved directories, " -"select the :guilabel:`Clear the list` option from the dropdown menu in " -"the :guilabel:`Search in` field." +msgid "If you want to change the scope of your search, select another directory, project or file in the :guilabel:`Search in` menu. The locations that you select for your search will be stored in the list so you can access them easily in the future. To erase all of these saved directories, select the :guilabel:`Clear the list` option from the dropdown menu in the :guilabel:`Search in` field." +msgstr "" + +#: ../../panes/findinfiles.rst:28 +msgid "Spyder Find pane showing choosing new directory and directory stored in the list" msgstr "" #: ../../panes/findinfiles.rst:35 @@ -873,35 +777,39 @@ msgid "Choosing search options" msgstr "" #: ../../panes/findinfiles.rst:37 -msgid "" -"You can select from a number of options to enable searches as broad or " -"refined as you need." +msgid "You can select from a number of options to enable searches as broad or refined as you need." msgstr "" #: ../../panes/findinfiles.rst:39 -msgid "" -"To enable case sensitivity, which only returns matches with identical " -"capitalization to your search text, toggle the :guilabel:`Aa` button on." +msgid "To enable case sensitivity, which only returns matches with identical capitalization to your search text, toggle the :guilabel:`Aa` button on." +msgstr "" + +#: ../../panes/findinfiles.rst:41 +msgid "Spyder Find pane showing search with case sensitive activated" msgstr "" #: ../../panes/findinfiles.rst:44 -msgid "" -"To parse your search string as a `regular expression`_, enable the " -":guilabel:`.*` button." +msgid "To parse your search string as a `regular expression`_, enable the :guilabel:`.*` button." +msgstr "" + +#: ../../panes/findinfiles.rst:48 +msgid "Spyder Find pane showing regular expression search" msgstr "" #: ../../panes/findinfiles.rst:51 -msgid "" -"To exclude certain filenames, extensions or directories from your search," -" click the :guilabel:`Plus` button to display the advanced options for " -"the pane, and then enter them in the :guilabel:`Exclude` text box." +msgid "To exclude certain filenames, extensions or directories from your search, click the :guilabel:`Plus` button to display the advanced options for the pane, and then enter them in the :guilabel:`Exclude` text box." +msgstr "" + +#: ../../panes/findinfiles.rst:53 +msgid "Spyder Find pane showing search excluding several file-types" msgstr "" #: ../../panes/findinfiles.rst:56 -msgid "" -"Finally, to change the number of matches displayed, select the " -":guilabel:`Set maximum number of results` option under the pane's Options" -" menu in the top right." +msgid "Finally, to change the number of matches displayed, select the :guilabel:`Set maximum number of results` option under the pane's Options menu in the top right." +msgstr "" + +#: ../../panes/findinfiles.rst:58 +msgid "Spyder Find pane showing window with maximum results dialog open" msgstr "" #: ../../panes/help.rst:3 @@ -909,17 +817,19 @@ msgid "Help" msgstr "" #: ../../panes/help.rst:5 -msgid "" -"You can use the **Help** pane to find, render and display rich " -"documentation for any object with a docstring, including modules, " -"classes, functions and methods. This allows you to access documentation " -"easily directly from Spyder, without having to interrupt your workflow." +msgid "You can use the **Help** pane to find, render and display rich documentation for any object with a docstring, including modules, classes, functions and methods. This allows you to access documentation easily directly from Spyder, without having to interrupt your workflow." +msgstr "" + +#: ../../panes/help.rst:8 +msgid "Spyder main window showing getting help for numpy arrays from editor" msgstr "" #: ../../panes/help.rst:11 -msgid "" -"You can also access Spyder's tutorial from here, which will guide you " -"through some basic steps for using its key features." +msgid "You can also access Spyder's tutorial from here, which will guide you through some basic steps for using its key features." +msgstr "" + +#: ../../panes/help.rst:13 +msgid "Spyder Help pane showing the link for the Spyder's tutorial" msgstr "" #: ../../panes/help.rst:21 @@ -927,29 +837,27 @@ msgid "Getting help" msgstr "" #: ../../panes/help.rst:23 -msgid "" -"Help can be retrieved both by static analysis of open files in the " -":doc:`editor`, or by dynamically inspecting an object in an " -":doc:`ipythonconsole`. You can trigger help manually by pressing the " -"configurable help shortcut (:kbd:`Ctrl-I` by default)." +msgid "Help can be retrieved both by static analysis of open files in the :doc:`editor`, or by dynamically inspecting an object in an :doc:`ipythonconsole`. You can trigger help manually by pressing the configurable help shortcut (:kbd:`Ctrl-I` by default)." +msgstr "" + +#: ../../panes/help.rst:26 +msgid "Spyder Editor and Help panes, with the latter displaying documentation for an object selected in the former." msgstr "" #: ../../panes/help.rst:29 -msgid "" -"You can also manually enter the object's name into the :guilabel:`Object`" -" textbox at the top of the pane, if :guilabel:`Console` is selected as " -"the :guilabel:`Source`." +msgid "You can also manually enter the object's name into the :guilabel:`Object` textbox at the top of the pane, if :guilabel:`Console` is selected as the :guilabel:`Source`." +msgstr "" + +#: ../../panes/help.rst:31 +msgid "Spyder Help pane, displaying documentation for an object whose name was written in the object text box" msgstr "" #: ../../panes/help.rst:34 -msgid "" -"Automatic help can be individually enabled for both the " -":guilabel:`Editor` and the :guilabel:`Console` under " -":menuselection:`Preferences --> Help --> Automatic Connections`, and " -"turned on and off dynamically via the lock icon in the top right corner " -"of the :guilabel:`Help` pane. If enabled, simply typing a left " -"parenthesis (``(``) after a function or method name will show its " -"associated help." +msgid "Automatic help can be individually enabled for both the :guilabel:`Editor` and the :guilabel:`Console` under :menuselection:`Preferences --> Help --> Automatic Connections`, and turned on and off dynamically via the lock icon in the top right corner of the :guilabel:`Help` pane. If enabled, simply typing a left parenthesis (``(``) after a function or method name will show its associated help." +msgstr "" + +#: ../../panes/help.rst:37 +msgid "Spyder console and help pane showing automatic help with parenthesis" msgstr "" #: ../../panes/help.rst:44 @@ -957,19 +865,15 @@ msgid "Understanding help modes" msgstr "" #: ../../panes/help.rst:46 -msgid "" -"You can use the options menu (:guilabel:`Hamburger` icon) in the top " -"right of the :guilabel:`Help` pane to toggle the help display mode." +msgid "You can use the options menu (:guilabel:`Hamburger` icon) in the top right of the :guilabel:`Help` pane to toggle the help display mode." msgstr "" #: ../../panes/help.rst:48 -msgid "" -":guilabel:`Rich Text` mode renders the object's docstrings with " -"``Sphinx``, :guilabel:`Plain Text` mode displays the docstring without " -"formatting while :guilabel:`Show Source` displays the docstring inline " -"with the code for the selected object, or any Python portion of it (if " -"the object is not pure Python). The latter can be useful when docstrings " -"are not available or insufficient to document the object." +msgid ":guilabel:`Rich Text` mode renders the object's docstrings with ``Sphinx``, :guilabel:`Plain Text` mode displays the docstring without formatting while :guilabel:`Show Source` displays the docstring inline with the code for the selected object, or any Python portion of it (if the object is not pure Python). The latter can be useful when docstrings are not available or insufficient to document the object." +msgstr "" + +#: ../../panes/help.rst:51 +msgid "Spyder help pane showing different modes" msgstr "" #: ../../panes/help.rst:59 @@ -977,10 +881,11 @@ msgid "Getting help by hovering" msgstr "" #: ../../panes/help.rst:61 -msgid "" -"You can also get summary help for objects by hovering over them in the " -":guilabel:`Editor`. Clicking the hover popup will open the full " -"documentation in the :guilabel:`Help` pane." +msgid "You can also get summary help for objects by hovering over them in the :guilabel:`Editor`. Clicking the hover popup will open the full documentation in the :guilabel:`Help` pane." +msgstr "" + +#: ../../panes/help.rst:64 +msgid "Editor pane showing help of an object from hover" msgstr "" #: ../../panes/help.rst:71 @@ -988,13 +893,7 @@ msgid "Control automatic import" msgstr "" #: ../../panes/help.rst:73 -msgid "" -"When you get help in the :guilabel:`IPython Console` for an object that " -"has not been previously imported, it is automatically loaded in Spyder's " -"own internal interpreter so that documentation can be shown when " -"available. This can be disabled in the :guilabel:`Help` pane's top-right " -"options menu so that only documentation from imported objects is " -"displayed." +msgid "When you get help in the :guilabel:`IPython Console` for an object that has not been previously imported, it is automatically loaded in Spyder's own internal interpreter so that documentation can be shown when available. This can be disabled in the :guilabel:`Help` pane's top-right options menu so that only documentation from imported objects is displayed." msgstr "" #: ../../panes/help.rst:84 @@ -1006,10 +905,11 @@ msgid "History" msgstr "" #: ../../panes/historylog.rst:5 -msgid "" -"With the **History** pane, you can view the recent code and commands " -"you've entered into any :doc:`ipythonconsole`, along with their " -"timestamp." +msgid "With the **History** pane, you can view the recent code and commands you've entered into any :doc:`ipythonconsole`, along with their timestamp." +msgstr "" + +#: ../../panes/historylog.rst:7 +msgid "Spyder History Log, displaying a list of previously executed commands" msgstr "" #: ../../panes/historylog.rst:14 @@ -1017,14 +917,7 @@ msgid "Using the History pane" msgstr "" #: ../../panes/historylog.rst:16 -msgid "" -"Navigating the :guilabel:`History` pane is very straightforward. Each " -"Spyder session is marked by a date and timestamp, making it easy to " -"remember when you executed a certain command. Statements can be selected " -"and copied from the context menu or with the normal system shortcuts. " -"Just like in the Editor, selecting a word or phrase displays all other " -"occurrences, and full syntax highlighting is also supported. The last " -"≈1000 lines entered are stored in the pane." +msgid "Navigating the :guilabel:`History` pane is very straightforward. Each Spyder session is marked by a date and timestamp, making it easy to remember when you executed a certain command. Statements can be selected and copied from the context menu or with the normal system shortcuts. Just like in the Editor, selecting a word or phrase displays all other occurrences, and full syntax highlighting is also supported. The last ≈1000 lines entered are stored in the pane." msgstr "" #: ../../panes/historylog.rst:26 @@ -1032,11 +925,11 @@ msgid "Options Menu" msgstr "" #: ../../panes/historylog.rst:28 -msgid "" -"The top-right options menu (:guilabel:`Hamburger` icon) allows you to " -"toggle wrapping of long lines (:guilabel:`Wrap lines`), and whether the " -"line number is displayed to the left of the text (:guilabel:`Show line " -"numbers`)." +msgid "The top-right options menu (:guilabel:`Hamburger` icon) allows you to toggle wrapping of long lines (:guilabel:`Wrap lines`), and whether the line number is displayed to the left of the text (:guilabel:`Show line numbers`)." +msgstr "" + +#: ../../panes/historylog.rst:30 +msgid "Spyder History Log, displaying wrapping lines and showing line number" msgstr "" #: ../../panes/historylog.rst:37 @@ -1044,24 +937,19 @@ msgid "Advanced usage" msgstr "" #: ../../panes/historylog.rst:39 -msgid "" -"The list of commands shown in the :guilabel:`History` pane are stored in " -":file:`history.py` in the :file:`.spyder-py3` directory in your user home" -" folder (by default, :file:`C:/Users/{username}` on Windows, " -":file:`/Users/{username}` for macOS, and typically " -":file:`/home/{username}` on GNU/Linux). You might need to show invisible " -"files in order to see it on a non-Windows operating system." +msgid "The list of commands shown in the :guilabel:`History` pane are stored in :file:`history.py` in the :file:`.spyder-py3` directory in your user home folder (by default, :file:`C:/Users/{username}` on Windows, :file:`/Users/{username}` for macOS, and typically :file:`/home/{username}` on GNU/Linux). You might need to show invisible files in order to see it on a non-Windows operating system." +msgstr "" + +#: ../../panes/historylog.rst:42 +msgid "Spyder History Log file" msgstr "" #: ../../panes/historylog.rst:45 -msgid "" -"While there is currently no built-in way to clear history from the Spyder" -" interface aside from resetting preferences, you can do so by closing " -"Spyder, deleting this file and restarting Spyder again." +msgid "While there is currently no built-in way to clear history from the Spyder interface aside from resetting preferences, you can do so by closing Spyder, deleting this file and restarting Spyder again." msgstr "" #: ../../panes/index.rst:3 -msgid "Panes in Depth" +msgid "Panes" msgstr "" #: ../../panes/ipythonconsole.rst:3 @@ -1069,28 +957,23 @@ msgid "IPython Console" msgstr "" #: ../../panes/ipythonconsole.rst:5 -msgid "" -"The **IPython Console** allows you to execute commands and interact with " -"data inside `IPython`_ interpreters." +msgid "The **IPython Console** allows you to execute commands and interact with data inside `IPython`_ interpreters." +msgstr "" + +#: ../../panes/ipythonconsole.rst:9 +msgid "Spyder IPython Console with code, inline plots, and the In prompt" msgstr "" #: ../../panes/ipythonconsole.rst:12 -msgid "" -"To launch a new IPython instance, go to :guilabel:`New console (default " -"settings)` under the :guilabel:`Consoles` menu, or use the keyboard " -"shortcut :kbd:`Ctrl-T` (:kbd:`Cmd-T` on macOS) when the console is " -"focused." +msgid "To launch a new IPython instance, go to :guilabel:`New console (default settings)` under the :guilabel:`Consoles` menu, or use the keyboard shortcut :kbd:`Ctrl-T` (:kbd:`Cmd-T` on macOS) when the console is focused." +msgstr "" + +#: ../../panes/ipythonconsole.rst:14 +msgid "Spyder showing opening a new Ipython Console" msgstr "" #: ../../panes/ipythonconsole.rst:17 -msgid "" -"From the same menu, you can stop currently executing code with " -":guilabel:`Interrupt kernel`, clear a console's namespace with " -":guilabel:`Remove all variables`, or relaunch a fresh one with " -":guilabel:`Restart kernel`. As each console is executed in a separate " -"process, this won't affect any others you've opened, and you will be able" -" to easily test your code in a clean environment without disrupting your " -"primary session." +msgid "From the same menu, you can stop currently executing code with :guilabel:`Interrupt kernel`, clear a console's namespace with :guilabel:`Remove all variables`, or relaunch a fresh one with :guilabel:`Restart kernel`. As each console is executed in a separate process, this won't affect any others you've opened, and you will be able to easily test your code in a clean environment without disrupting your primary session." msgstr "" #: ../../panes/ipythonconsole.rst:26 @@ -1098,9 +981,7 @@ msgid "Supported features" msgstr "" #: ../../panes/ipythonconsole.rst:28 -msgid "" -"Any :guilabel:`IPython Console`, whether :ref:`external` or started by Spyder, supports:" +msgid "Any :guilabel:`IPython Console`, whether :ref:`external` or started by Spyder, supports:" msgstr "" #: ../../panes/ipythonconsole.rst:30 @@ -1116,24 +997,19 @@ msgid "Full GUI integration with the enhanced Spyder :doc:`Debugger`. msgstr "" #: ../../panes/ipythonconsole.rst:33 -msgid "" -"The :doc:`variableexplorer`, with GUI-based editors for many built-in and" -" third-party Python objects." +msgid "The :doc:`variableexplorer`, with GUI-based editors for many built-in and third-party Python objects." msgstr "" #: ../../panes/ipythonconsole.rst:34 -msgid "" -"Display of Matplotlib graphics in Spyder's :doc:`plots` pane, if the " -":guilabel:`Inline` backend is selected under :menuselection:`Preferences " -"--> IPython console --> Graphics --> Graphics backend`, and inline in the" -" console if :guilabel:`Mute inline plotting` is unchecked under the " -":guilabel:`Plots` pane's options menu." +msgid "Display of Matplotlib graphics in Spyder's :doc:`plots` pane, if the :guilabel:`Inline` backend is selected under :menuselection:`Preferences --> IPython console --> Graphics --> Graphics backend`, and inline in the console if :guilabel:`Mute inline plotting` is unchecked under the :guilabel:`Plots` pane's options menu." +msgstr "" + +#: ../../panes/ipythonconsole.rst:36 +msgid "Spyder IPython Console, with a popup list of code completion guesses" msgstr "" #: ../../panes/ipythonconsole.rst:39 -msgid "" -"For information on the features, commands and capabilities built into " -"IPython itself, see the `IPython documentation`_." +msgid "For information on the features, commands and capabilities built into IPython itself, see the `IPython documentation`_." msgstr "" #: ../../panes/ipythonconsole.rst:47 @@ -1141,30 +1017,27 @@ msgid "Special consoles" msgstr "" #: ../../panes/ipythonconsole.rst:49 -msgid "" -"Spyder also supports several types of specialized consoles. A `Sympy " -"console`_ enables creating and displaying symbolic math expressions right" -" inside Spyder. A `Cython console`_ allows you to use the Cython language" -" to speed up your code and call C functions directly from Python. " -"Finally, a `Pylab console`_ loads common Numpy and Matplotlib functions " -"by default; while this is deprecated and strongly discouraged for new " -"code, it can still be used if necessary for legacy scripts that need it." +msgid "Spyder also supports several types of specialized consoles. A `Sympy console`_ enables creating and displaying symbolic math expressions right inside Spyder. A `Cython console`_ allows you to use the Cython language to speed up your code and call C functions directly from Python. Finally, a `Pylab console`_ loads common Numpy and Matplotlib functions by default; while this is deprecated and strongly discouraged for new code, it can still be used if necessary for legacy scripts that need it." +msgstr "" + +#: ../../panes/ipythonconsole.rst:58 +msgid "Spyder showing opening a new special Console" msgstr "" #: ../../panes/ipythonconsole.rst:67 -msgid "" -"The options menu allows you to inspect your current environment variables" -" (:guilabel:`Show environment variables`), and the contents of your " -"system's ``PATH`` (:guilabel:`Show sys.path contents`). In addition, you " -"can have each console display how long it has been running with " -":guilabel:`Show elapsed time`." +msgid "The options menu allows you to inspect your current environment variables (:guilabel:`Show environment variables`), and the contents of your system's ``PATH`` (:guilabel:`Show sys.path contents`). In addition, you can have each console display how long it has been running with :guilabel:`Show elapsed time`." +msgstr "" + +#: ../../panes/ipythonconsole.rst:70 +msgid "Spyder IPython Console with options menu" msgstr "" #: ../../panes/ipythonconsole.rst:73 -msgid "" -"You can also change the name of the current :guilabel:`IPython console` " -"tab with the :guilabel:`Rename tab` option, or by simply double-clicking " -"it." +msgid "You can also change the name of the current :guilabel:`IPython console` tab with the :guilabel:`Rename tab` option, or by simply double-clicking it." +msgstr "" + +#: ../../panes/ipythonconsole.rst:75 +msgid "Spyder IPython Console showing renaming console" msgstr "" #: ../../panes/ipythonconsole.rst:84 @@ -1172,13 +1045,11 @@ msgid "Using external kernels" msgstr "" #: ../../panes/ipythonconsole.rst:86 -msgid "" -"You can connect to external local and remote kernels (including those " -"managed by Jupyter Notebook or QtConsole) through the :guilabel:`Connect " -"to an existing kernel` dialog under the :guilabel:`Consoles` menu. For " -"this feature to work, a compatible version of the ``spyder-kernels`` " -"package :ref:`must be installed ` in the " -"environment or machine in which the external kernel is running." +msgid "You can connect to external local and remote kernels (including those managed by Jupyter Notebook or QtConsole) through the :guilabel:`Connect to an existing kernel` dialog under the :guilabel:`Consoles` menu. For this feature to work, a compatible version of the ``spyder-kernels`` package :ref:`must be installed ` in the environment or machine in which the external kernel is running." +msgstr "" + +#: ../../panes/ipythonconsole.rst:89 +msgid "Connect to external kernel dialog of the Spyder IPython console" msgstr "" #: ../../panes/ipythonconsole.rst:94 @@ -1186,37 +1057,37 @@ msgid "Connect to a local kernel" msgstr "" #: ../../panes/ipythonconsole.rst:96 -msgid "" -"To connect to a local kernel that is already running (e.g. one started by" -" Jupyter notebook)," +msgid "To connect to a local kernel that is already running (e.g. one started by Jupyter notebook)," msgstr "" #: ../../panes/ipythonconsole.rst:98 -#, python-format -msgid "" -"Run ``%connect_info`` in the notebook or console you want to connect to, " -"and copy the name of its kernel connection file, shown after ``jupyter " -" --existing``." +msgid "Run ``%connect_info`` in the notebook or console you want to connect to, and copy the name of its kernel connection file, shown after ``jupyter --existing``." +msgstr "" + +#: ../../panes/ipythonconsole.rst:100 +msgid "Running connect_info in a Jupyter notebook" msgstr "" #: ../../panes/ipythonconsole.rst:103 -msgid "" -"In Spyder, click :guilabel:`Connect to an existing kernel` from the " -":guilabel:`Consoles` menu, and paste the name of the " -":guilabel:`Connection file` from the previous step." +msgid "In Spyder, click :guilabel:`Connect to an existing kernel` from the :guilabel:`Consoles` menu, and paste the name of the :guilabel:`Connection file` from the previous step." msgstr "" #: ../../panes/ipythonconsole.rst:105 -msgid "" -"As a convenience, kernel ID numbers (e.g. ``1234``) entered in the " -"connection file path field will be expanded to the full path of the file," -" i.e. :file:`{jupyter/runtime/dir/path}/kernal-{id}.json`." +msgid "As a convenience, kernel ID numbers (e.g. ``1234``) entered in the connection file path field will be expanded to the full path of the file, i.e. :file:`{jupyter/runtime/dir/path}/kernal-{id}.json`." +msgstr "" + +#: ../../panes/ipythonconsole.rst:107 +msgid "Copying the connection filename into Spyder's dialog" msgstr "" #: ../../panes/ipythonconsole.rst:110 msgid "Click :guilabel:`OK` to connect to the kernel." msgstr "" +#: ../../panes/ipythonconsole.rst:112 +msgid "Connecting to the kernel and running basic commands." +msgstr "" + #: ../../panes/ipythonconsole.rst:117 msgid "Connect to a remote kernel" msgstr "" @@ -1226,69 +1097,59 @@ msgid "To connect to a kernel on a remote machine," msgstr "" #: ../../panes/ipythonconsole.rst:121 -msgid "" -"Launch a Spyder kernel on the remote host if one is not already running, " -"with ``python -m spyder_kernels.console``." +msgid "Launch a Spyder kernel on the remote host if one is not already running, with ``python -m spyder_kernels.console``." +msgstr "" + +#: ../../panes/ipythonconsole.rst:123 +msgid "Staring a Spyder kernel on a remote machine" msgstr "" #: ../../panes/ipythonconsole.rst:126 -msgid "" -"Copy the kernel's connection file " -"(:file:`{jupyter/runtime/dir/path}/kernel-{pid}.json`) to the machine " -"you're running Spyder on." +msgid "Copy the kernel's connection file (:file:`{jupyter/runtime/dir/path}/kernel-{pid}.json`) to the machine you're running Spyder on." msgstr "" #: ../../panes/ipythonconsole.rst:128 -msgid "" -"You can get :file:`{jupyter/runtime/dir/path}` by executing ``jupyter " -"--runtime-dir`` in the same Python environment as the kernel. Usually, " -"the connection file you are looking for will be one of the newest in this" -" directory, corresponding to the time you started the external kernel." +msgid "You can get :file:`{jupyter/runtime/dir/path}` by executing ``jupyter --runtime-dir`` in the same Python environment as the kernel. Usually, the connection file you are looking for will be one of the newest in this directory, corresponding to the time you started the external kernel." +msgstr "" + +#: ../../panes/ipythonconsole.rst:131 +msgid "Using SCP to copy the connection file to the local machine" msgstr "" #: ../../panes/ipythonconsole.rst:134 -msgid "" -"Click :guilabel:`Connect to an existing kernel` from the " -":guilabel:`Consoles` menu, and browse for or enter the path to the " -"connection file from the previous step." +msgid "Click :guilabel:`Connect to an existing kernel` from the :guilabel:`Consoles` menu, and browse for or enter the path to the connection file from the previous step." msgstr "" #: ../../panes/ipythonconsole.rst:136 -msgid "" -"As a convenience, kernel ID numbers (e.g. ``1234``) entered in the " -"connection file path field will be expanded to " -":file:`{jupyter/runtime/dir/path}/kernal-{id}.json` on your local " -"machine, if you've copied the connection file there." +msgid "As a convenience, kernel ID numbers (e.g. ``1234``) entered in the connection file path field will be expanded to :file:`{jupyter/runtime/dir/path}/kernal-{id}.json` on your local machine, if you've copied the connection file there." +msgstr "" + +#: ../../panes/ipythonconsole.rst:138 +msgid "Opening the connect to kernel dialog and browsing for the path" msgstr "" #: ../../panes/ipythonconsole.rst:141 -msgid "" -"Check the :guilabel:`This is a remote kernel (via SSH)` box and enter the" -" :guilabel:`Hostname` or IP address, username and port to connect to on " -"the remote machine. Then, enter *either* :file:`{username}`'s password on" -" the remote machine, or browse to an SSH keyfile (typically in the " -":file:`.ssh` directory in your home folder on the local machine, often " -"called :file:`id_rsa` or similar) registered on it; only one is needed to" -" connect. If you check :guilabel:`Save connection settings`, these " -"details will be remembered and filled for you automatically next time you" -" open the dialog." +msgid "Check the :guilabel:`This is a remote kernel (via SSH)` box and enter the :guilabel:`Hostname` or IP address, username and port to connect to on the remote machine. Then, enter *either* :file:`{username}`'s password on the remote machine, or browse to an SSH keyfile (typically in the :file:`.ssh` directory in your home folder on the local machine, often called :file:`id_rsa` or similar) registered on it; only one is needed to connect. If you check :guilabel:`Save connection settings`, these details will be remembered and filled for you automatically next time you open the dialog." msgstr "" #: ../../panes/ipythonconsole.rst:145 -msgid "" -"Note that :guilabel:`Port` is the port number on your remote machine that" -" the SSH daemon (``sshd``) is listening on, typically 22 unless you or " -"your administrator has configured it otherwise." +msgid "Note that :guilabel:`Port` is the port number on your remote machine that the SSH daemon (``sshd``) is listening on, typically 22 unless you or your administrator has configured it otherwise." +msgstr "" + +#: ../../panes/ipythonconsole.rst:147 +msgid "Entering pre-filled SSH details into the connection dialog" msgstr "" #: ../../panes/ipythonconsole.rst:150 msgid "Click :guilabel:`OK` to connect to the remote kernel" msgstr "" +#: ../../panes/ipythonconsole.rst:152 +msgid "Connecting to the remote kernel and running basic commands" +msgstr "" + #: ../../panes/ipythonconsole.rst:155 -msgid "" -"For more technical details about connecting to remote kernels, see the " -"`Connecting to a remote kernel`_ page in the IPython Cookbook." +msgid "For more technical details about connecting to remote kernels, see the `Connecting to a remote kernel`_ page in the IPython Cookbook." msgstr "" #: ../../panes/ipythonconsole.rst:165 @@ -1296,33 +1157,32 @@ msgid "Reload changed modules" msgstr "" #: ../../panes/ipythonconsole.rst:167 -msgid "" -"When working in an interactive session, Python only loads a module from " -"its source file once, the first time it is imported." +msgid "When working in an interactive session, Python only loads a module from its source file once, the first time it is imported." msgstr "" #: ../../panes/ipythonconsole.rst:169 -msgid "" -"Spyder's :guilabel:`User Module Reloader` (UMR) automatically reloads " -"modules right in your existing IPython consoles whenever they are " -"modified and re-imported. With the UMR enabled, you can test changes to " -"your code without restarting the kernel." +msgid "Spyder's :guilabel:`User Module Reloader` (UMR) automatically reloads modules right in your existing IPython consoles whenever they are modified and re-imported. With the UMR enabled, you can test changes to your code without restarting the kernel." +msgstr "" + +#: ../../panes/ipythonconsole.rst:172 +msgid "Spyder showing reloading modules in console" msgstr "" #: ../../panes/ipythonconsole.rst:175 -msgid "" -"UMR is enabled by default, and it will provide you with a red ``Reloaded " -"modules:`` message in the console listing the files it has refreshed when" -" it is activated. If desired, you can turn it on or off, and prevent " -"specific modules from being reloaded, under :menuselection:`Preferences " -"--> Python interpreter --> User Module Reloader (UMR)`." +msgid "UMR is enabled by default, and it will provide you with a red ``Reloaded modules:`` message in the console listing the files it has refreshed when it is activated. If desired, you can turn it on or off, and prevent specific modules from being reloaded, under :menuselection:`Preferences --> Python interpreter --> User Module Reloader (UMR)`." msgstr "" -#: ../../panes/ipythonconsole.rst:187 ../../panes/variableexplorer.rst:196 +#: ../../panes/ipythonconsole.rst:178 +msgid "Spyder preferences showing option to use module reloader" +msgstr "" + +#: ../../panes/ipythonconsole.rst:187 +#: ../../panes/variableexplorer.rst:196 msgid ":doc:`debugging`" msgstr "" -#: ../../panes/ipythonconsole.rst:189 ../../panes/onlinehelp.rst:88 +#: ../../panes/ipythonconsole.rst:189 +#: ../../panes/onlinehelp.rst:88 msgid ":doc:`help`" msgstr "" @@ -1335,10 +1195,11 @@ msgid "Online Help" msgstr "" #: ../../panes/onlinehelp.rst:5 -msgid "" -"The **Online Help** pane provides a built-in web browser to explore " -"dynamically generated Python documentation on installed modules—including" -" your own—rendered by a `pydoc`_ server running in the background." +msgid "The **Online Help** pane provides a built-in web browser to explore dynamically generated Python documentation on installed modules—including your own—rendered by a `pydoc`_ server running in the background." +msgstr "" + +#: ../../panes/onlinehelp.rst:9 +msgid "Spyder Online Help pane on the index page, a list of builtin modules" msgstr "" #: ../../panes/onlinehelp.rst:16 @@ -1346,42 +1207,51 @@ msgid "Using the Online Help" msgstr "" #: ../../panes/onlinehelp.rst:18 -msgid "" -"The Online Help's home shows an index where you can browse the " -"documentation of standard library modules, third party packages installed" -" in your Python environment, and your own local code. Click on the name " -"of any module to open its documentation." +msgid "The Online Help's home shows an index where you can browse the documentation of standard library modules, third party packages installed in your Python environment, and your own local code. Click on the name of any module to open its documentation." +msgstr "" + +#: ../../panes/onlinehelp.rst:21 +msgid "Spyder Online Help pane showing module browsing" msgstr "" #: ../../panes/onlinehelp.rst:24 -msgid "" -"Enter the name of the item you'd like help on in the :guilabel:`Package` " -"field to load its documentation directly." +msgid "Enter the name of the item you'd like help on in the :guilabel:`Package` field to load its documentation directly." +msgstr "" + +#: ../../panes/onlinehelp.rst:26 +msgid "Spyder Online Help pane showing module browsing by name" msgstr "" #: ../../panes/onlinehelp.rst:29 -msgid "" -"The module's file location is linked to the right of the doc's title, " -"which you can click to view its source code." +msgid "The module's file location is linked to the right of the doc's title, which you can click to view its source code." +msgstr "" + +#: ../../panes/onlinehelp.rst:31 +msgid "Spyder Online Help pane showing source code clicking module's path" msgstr "" #: ../../panes/onlinehelp.rst:34 -msgid "" -"Standard library modules also have a link to the corresponding `Python " -"docs`_, which can be viewed right inside of the pane." +msgid "Standard library modules also have a link to the corresponding `Python docs`_, which can be viewed right inside of the pane." +msgstr "" + +#: ../../panes/onlinehelp.rst:38 +msgid "Spyder Online Help pane showing python docs embedded in pane" msgstr "" #: ../../panes/onlinehelp.rst:41 -msgid "" -"If you're not sure of the name of the object you want help on, or are " -"looking for a specific keyword, use the :guilabel:`Search` field to get a" -" list of results." +msgid "If you're not sure of the name of the object you want help on, or are looking for a specific keyword, use the :guilabel:`Search` field to get a list of results." +msgstr "" + +#: ../../panes/onlinehelp.rst:43 +msgid "Spyder Online Help pane showing search of a keyword" msgstr "" #: ../../panes/onlinehelp.rst:46 -msgid "" -"Links above the search field provide an index of topics with general help" -" and a list of Python keywords linked to their corresponding docs." +msgid "Links above the search field provide an index of topics with general help and a list of Python keywords linked to their corresponding docs." +msgstr "" + +#: ../../panes/onlinehelp.rst:48 +msgid "Spyder Online Help pane on the topics page" msgstr "" #: ../../panes/onlinehelp.rst:55 @@ -1389,38 +1259,43 @@ msgid "Toolbar items" msgstr "" #: ../../panes/onlinehelp.rst:57 -msgid "" -"Just like in a web browser, the forward and back buttons move through the" -" pages you have visited, and the home button (house icon) returns you to " -"the module index." +msgid "Just like in a web browser, the forward and back buttons move through the pages you have visited, and the home button (house icon) returns you to the module index." +msgstr "" + +#: ../../panes/onlinehelp.rst:59 +msgid "Spyder Online Help pane showing navigation with arrows" msgstr "" #: ../../panes/onlinehelp.rst:62 -msgid "" -"Perform a realtime search within a page's content with the " -":guilabel:`Find` button (magnifying glass icon top left) or " -":kbd:`Ctrl-F`, navigate through matches with the Up and Down buttons, and" -" make matching case sensitive with the :guilabel:`Aa` button." +msgid "Perform a realtime search within a page's content with the :guilabel:`Find` button (magnifying glass icon top left) or :kbd:`Ctrl-F`, navigate through matches with the Up and Down buttons, and make matching case sensitive with the :guilabel:`Aa` button." +msgstr "" + +#: ../../panes/onlinehelp.rst:64 +msgid "Spyder Online Help pane showing finding a word on a module" msgstr "" #: ../../panes/onlinehelp.rst:67 -msgid "" -"You can view and re-run previous searches from the drop-down menu in the " -":guilabel:`Package` field." +msgid "You can view and re-run previous searches from the drop-down menu in the :guilabel:`Package` field." +msgstr "" + +#: ../../panes/onlinehelp.rst:69 +msgid "Spyder Online Help pane showing previous searches" msgstr "" #: ../../panes/onlinehelp.rst:72 -msgid "" -"You can also use the zoom in/out buttons (:guilabel:`-` and " -":guilabel:`+`, top right) to change the font size to suit your " -"preferences." +msgid "You can also use the zoom in/out buttons (:guilabel:`-` and :guilabel:`+`, top right) to change the font size to suit your preferences." +msgstr "" + +#: ../../panes/onlinehelp.rst:74 +msgid "Spyder Online Help pane showing changing the font" msgstr "" #: ../../panes/onlinehelp.rst:77 -msgid "" -"To cancel searching or page loading, click the stop button (red square), " -"and to reload the page (such as when you change your own package's " -"documentation), press the refresh button (circular arrow)." +msgid "To cancel searching or page loading, click the stop button (red square), and to reload the page (such as when you change your own package's documentation), press the refresh button (circular arrow)." +msgstr "" + +#: ../../panes/onlinehelp.rst:79 +msgid "Spyder Online Help pane showing refreshing pane when updating docs" msgstr "" #: ../../panes/outline.rst:3 @@ -1428,20 +1303,19 @@ msgid "Outline" msgstr "" #: ../../panes/outline.rst:5 -msgid "" -"The **Outline** pane allows you to view and navigate the functions, " -"classes, methods, cells and comments in open Python files. To show or " -"hide the Outline pane, use :menuselection:`View --> Panes --> Outline` or" -" :kbd:`Ctrl-Shift-O` / :kbd:`Cmd-Shift-O`. Click an entry in the outline " -"to jump to its source file location, and use the :guilabel:`Go to cursor " -"position` toolbar button to highlight the item corresponding to the " -"current :doc:`editor` position." +msgid "The **Outline** pane allows you to view and navigate the functions, classes, methods, cells and comments in open Python files. To show or hide the Outline pane, use :menuselection:`View --> Panes --> Outline` or :kbd:`Ctrl-Shift-O` / :kbd:`Cmd-Shift-O`. Click an entry in the outline to jump to its source file location, and use the :guilabel:`Go to cursor position` toolbar button to highlight the item corresponding to the current :doc:`editor` position." +msgstr "" + +#: ../../panes/outline.rst:9 +msgid "Outline pane" msgstr "" #: ../../panes/outline.rst:18 -msgid "" -"The options menu in the top-right of the pane allows customizing how the " -"outline is displayed." +msgid "The options menu in the top-right of the pane allows customizing how the outline is displayed." +msgstr "" + +#: ../../panes/outline.rst:20 +msgid "Outline options menu" msgstr "" #: ../../panes/outline.rst:23 @@ -1449,48 +1323,31 @@ msgid "These customization settings include:" msgstr "" #: ../../panes/outline.rst:25 -msgid "" -":guilabel:`Show absolute path`: Display the full path to each file " -"instead of just the name." +msgid ":guilabel:`Show absolute path`: Display the full path to each file instead of just the name." msgstr "" #: ../../panes/outline.rst:26 -msgid "" -":guilabel:`Show all files`: List every open file rather than just the " -"current one. This allows using the Outline as a file switcher." +msgid ":guilabel:`Show all files`: List every open file rather than just the current one. This allows using the Outline as a file switcher." msgstr "" #: ../../panes/outline.rst:28 -msgid "" -":guilabel:`Group code cells`: Group code cells in multiple nested levels " -"in the outline rather than showing all cells in one level. You can create" -" subsections by adding more ``%`` signs to the cell separator." +msgid ":guilabel:`Group code cells`: Group code cells in multiple nested levels in the outline rather than showing all cells in one level. You can create subsections by adding more ``%`` signs to the cell separator." msgstr "" #: ../../panes/outline.rst:30 -msgid "" -":guilabel:`Display variables and attributes`: Display top-level " -"variable/constant definitions and class attributes in the outline." +msgid ":guilabel:`Display variables and attributes`: Display top-level variable/constant definitions and class attributes in the outline." msgstr "" #: ../../panes/outline.rst:31 -msgid "" -":guilabel:`Follow cursor position`: Automatically highlight and expand " -"the entry corresponding to the current cursor position in the " -":doc:`editor`." +msgid ":guilabel:`Follow cursor position`: Automatically highlight and expand the entry corresponding to the current cursor position in the :doc:`editor`." msgstr "" #: ../../panes/outline.rst:32 -msgid "" -":guilabel:`Show special comments`: List special comments in the outline, " -"which start with ``# ----``." +msgid ":guilabel:`Show special comments`: List special comments in the outline, which start with ``# ----``." msgstr "" #: ../../panes/outline.rst:33 -msgid "" -":guilabel:`Sort files alphabetically`: Sort the file list in alphabetical" -" order. When disabled, all tabs will be sorted by the tab order of the " -"currently selected Editor panel." +msgid ":guilabel:`Sort files alphabetically`: Sort the file list in alphabetical order. When disabled, all tabs will be sorted by the tab order of the currently selected Editor panel." msgstr "" #: ../../panes/outline.rst:40 @@ -1526,26 +1383,23 @@ msgid "Plots" msgstr "" #: ../../panes/plots.rst:5 -msgid "" -"The **Plots** pane shows the static figures and images created during " -"your session. It will show you plots from the :doc:`ipythonconsole`, " -"produced by your code in the :doc:`editor` or generated by the " -":doc:`variableexplorer` allowing you to interact with them in several " -"ways." +msgid "The **Plots** pane shows the static figures and images created during your session. It will show you plots from the :doc:`ipythonconsole`, produced by your code in the :doc:`editor` or generated by the :doc:`variableexplorer` allowing you to interact with them in several ways." +msgstr "" + +#: ../../panes/plots.rst:8 +msgid "Spyder main window showing execution for the Plots pane" msgstr "" #: ../../panes/plots.rst:11 -msgid "" -"The figures shown in the Plots pane are those associated with the " -"currently active :guilabel:`Console` tab; if you switch consoles, the " -"list of plots displayed (or none at all, if a new console) will change " -"accordingly." +msgid "The figures shown in the Plots pane are those associated with the currently active :guilabel:`Console` tab; if you switch consoles, the list of plots displayed (or none at all, if a new console) will change accordingly." +msgstr "" + +#: ../../panes/plots.rst:13 +msgid "Spyder's plots pane and console showing switching consoles" msgstr "" #: ../../panes/plots.rst:22 -msgid "" -"The options menu in the top right of the :guilabel:`Plots` pane offers " -"several ways to customize how your plots are displayed." +msgid "The options menu in the top right of the :guilabel:`Plots` pane offers several ways to customize how your plots are displayed." msgstr "" #: ../../panes/plots.rst:26 @@ -1553,10 +1407,11 @@ msgid "Mute inline plotting" msgstr "" #: ../../panes/plots.rst:28 -msgid "" -"The :guilabel:`Mute inline plotting` option is enabled by default, " -"preventing your plots from appearing in the Console. If you deactivate " -"this option, figures will display in both the Plots pane and the Console." +msgid "The :guilabel:`Mute inline plotting` option is enabled by default, preventing your plots from appearing in the Console. If you deactivate this option, figures will display in both the Plots pane and the Console." +msgstr "" + +#: ../../panes/plots.rst:31 +msgid "Spyder's plots pane and console showing plots in the console" msgstr "" #: ../../panes/plots.rst:36 @@ -1564,10 +1419,11 @@ msgid "Show plot outline" msgstr "" #: ../../panes/plots.rst:38 -msgid "" -"The :guilabel:`Show plot outline` option, off by default, shows a thin " -"stroke surrounding the area of the figure area, which will also appear in" -" the exported images." +msgid "The :guilabel:`Show plot outline` option, off by default, shows a thin stroke surrounding the area of the figure area, which will also appear in the exported images." +msgstr "" + +#: ../../panes/plots.rst:40 +msgid "Spyder's plots pane showing a plot's outline" msgstr "" #: ../../panes/plots.rst:45 @@ -1575,11 +1431,11 @@ msgid "Fit plots to window" msgstr "" #: ../../panes/plots.rst:47 -msgid "" -"The :guilabel:`Fit plots to Window` option, also enabled by default, " -"sizes the figures to match the pane. Disabling it will display plots at " -"their native size, and allow you use the zoom buttons at the top of the " -"pane to scale them manually." +msgid "The :guilabel:`Fit plots to Window` option, also enabled by default, sizes the figures to match the pane. Disabling it will display plots at their native size, and allow you use the zoom buttons at the top of the pane to scale them manually." +msgstr "" + +#: ../../panes/plots.rst:50 +msgid "Spyder main window showing plots zoom" msgstr "" #: ../../panes/plots.rst:57 @@ -1587,32 +1443,35 @@ msgid "Toolbar options" msgstr "" #: ../../panes/plots.rst:59 -msgid "" -"The toolbar at the top of the Plots pane provides several useful features" -" that allow you to interact with your figures. For example, you can cycle" -" sequentially through the plot list with the forward and back arrows." +msgid "The toolbar at the top of the Plots pane provides several useful features that allow you to interact with your figures. For example, you can cycle sequentially through the plot list with the forward and back arrows." +msgstr "" + +#: ../../panes/plots.rst:62 +msgid "Spyder main window showing plot navigation using arrows." msgstr "" #: ../../panes/plots.rst:65 -msgid "" -"You can also save one or all the plots in the pane to file(s) by clicking" -" the respective \"save\"/\"save all\" icons in the toolbar. Plots are " -"rendered and saved as PNG by default, but SVG can be selected as an " -"option under :menuselection:`Preferences --> IPython console --> Graphics" -" --> Inline backend --> Format`." +msgid "You can also save one or all the plots in the pane to file(s) by clicking the respective \"save\"/\"save all\" icons in the toolbar. Plots are rendered and saved as PNG by default, but SVG can be selected as an option under :menuselection:`Preferences --> IPython console --> Graphics --> Inline backend --> Format`." +msgstr "" + +#: ../../panes/plots.rst:68 +msgid "Spyder plots pane showing saving a plot." msgstr "" #: ../../panes/plots.rst:71 -msgid "" -"Additionally, if you want to use a figure in another document, you can " -"click the \"copy to clipboard\" button and paste your plot wherever you " -"want, such as a word processor." +msgid "Additionally, if you want to use a figure in another document, you can click the \"copy to clipboard\" button and paste your plot wherever you want, such as a word processor." +msgstr "" + +#: ../../panes/plots.rst:73 +msgid "Spyder Plots pane showing pasting plot in LibreOffice." msgstr "" #: ../../panes/plots.rst:76 -msgid "" -"Finally, you can use the \"remove\" and \"remove all\" buttons in the " -"toolbar to clear plots from the list." +msgid "Finally, you can use the \"remove\" and \"remove all\" buttons in the toolbar to clear plots from the list." +msgstr "" + +#: ../../panes/plots.rst:78 +msgid "Spyder plots pane showing pasting plot in LibreOffice." msgstr "" #: ../../panes/profiler.rst:3 @@ -1620,13 +1479,13 @@ msgid "Profiler" msgstr "" #: ../../panes/profiler.rst:5 -msgid "" -"The **Profiler** pane recursively determines the run time and number of " -"calls for every function and method called in a file, breaking down each " -"procedure into its smallest individual units. This allows you to easily " -"identify the bottlenecks in your code, points you toward the exact " -"statements most critical for optimization, and measures the performance " -"delta after followup changes." +msgid "The **Profiler** pane recursively determines the run time and number of calls for every function and method called in a file, breaking down each procedure into its smallest individual units. This allows you to easily identify the bottlenecks in your code, points you toward the exact statements most critical for optimization, and measures the performance delta after followup changes." +msgstr "" + +#: ../../panes/profiler.rst:8 +#: ../../panes/profiler.rst:84 +#: ../../panes/profiler.rst:92 +msgid "Spyder Profiler pane, displaying a list of functions and their execution time" msgstr "" #: ../../panes/profiler.rst:15 @@ -1634,60 +1493,56 @@ msgid "Running the Profiler" msgstr "" #: ../../panes/profiler.rst:17 -msgid "" -"You can browse for a file using the open button to the right of the " -"Profiler's path box (top left of the pane), which will run profiling over" -" this file automatically." +msgid "You can browse for a file using the open button to the right of the Profiler's path box (top left of the pane), which will run profiling over this file automatically." +msgstr "" + +#: ../../panes/profiler.rst:19 +msgid "Spyder Profiler pane, showing browsing a file and running profiler" msgstr "" #: ../../panes/profiler.rst:22 -msgid "" -"You can manually enter the path in the pane's path box and then run the " -"analysis on the file by pressing :guilabel:`Profile` in the Profiler " -"pane." +msgid "You can manually enter the path in the pane's path box and then run the analysis on the file by pressing :guilabel:`Profile` in the Profiler pane." msgstr "" #: ../../panes/profiler.rst:24 -msgid "" -"You can also run profiling for the file that is currently open in the " -":doc:`editor` by clicking :menuselection:`&Run --> Profile` in the menu " -"bar, or by using a configurable shortcut (:kbd:`F10` by default)." +msgid "You can also run profiling for the file that is currently open in the :doc:`editor` by clicking :menuselection:`&Run --> Profile` in the menu bar, or by using a configurable shortcut (:kbd:`F10` by default)." +msgstr "" + +#: ../../panes/profiler.rst:27 +#: ../../panes/profiler.rst:51 +msgid "Spyder Profiler pane, showing running profiler from menu bar" msgstr "" #: ../../panes/profiler.rst:30 -msgid "" -"If you'd like to cancel an in-progress run, click the :guilabel:`Stop` " -"button in the top right, and if profiling fails for any reason, the " -":guilabel:`Output` dialog will be displayed, indicating the error that " -"occurred." +msgid "If you'd like to cancel an in-progress run, click the :guilabel:`Stop` button in the top right, and if profiling fails for any reason, the :guilabel:`Output` dialog will be displayed, indicating the error that occurred." msgstr "" #: ../../panes/profiler.rst:32 -msgid "" -"By double-clicking an item in the Profiler, you will be taken to the file" -" and line in the :doc:`editor` where it was called." +msgid "By double-clicking an item in the Profiler, you will be taken to the file and line in the :doc:`editor` where it was called." +msgstr "" + +#: ../../panes/profiler.rst:34 +msgid "Spyder Profiler pane, showing opening a file when clicking on its analysis" msgstr "" #: ../../panes/profiler.rst:37 -msgid "" -"You can increase the number of levels displayed for a particular object " -"by clicking the dropdown arrows to the left of the name, and " -"expand/collapse all the items with the buttons in the top left." +msgid "You can increase the number of levels displayed for a particular object by clicking the dropdown arrows to the left of the name, and expand/collapse all the items with the buttons in the top left." +msgstr "" + +#: ../../panes/profiler.rst:39 +msgid "Spyder Profiler pane, showing dropdown arrows and buttons for expanding and collapsing" msgstr "" #: ../../panes/profiler.rst:42 -msgid "" -"By clicking the dropdown or press the :kbd:`Down Arrow` key in the " -"filename field, you can recall paths of previous profiled files." +msgid "By clicking the dropdown or press the :kbd:`Down Arrow` key in the filename field, you can recall paths of previous profiled files." +msgstr "" + +#: ../../panes/profiler.rst:44 +msgid "Spyder Profiler pane, showing dropdown of previous profiled files" msgstr "" #: ../../panes/profiler.rst:47 -msgid "" -"Finally, you can save the data for a given run to disk as a file with the" -" ``.Result`` extension using the :guilabel:`Save data` button. This can " -"be loaded to compare with a previous run of the same file using the " -":guilabel:`Load data` button. To remove the loaded data, click the " -":guilabel:`Clear comparison` button." +msgid "Finally, you can save the data for a given run to disk as a file with the ``.Result`` extension using the :guilabel:`Save data` button. This can be loaded to compare with a previous run of the same file using the :guilabel:`Load data` button. To remove the loaded data, click the :guilabel:`Clear comparison` button." msgstr "" #: ../../panes/profiler.rst:58 @@ -1695,31 +1550,15 @@ msgid "Interpreting the results" msgstr "" #: ../../panes/profiler.rst:60 -msgid "" -"Results are broken down by function/method/statement, with each sub-" -"element listed hierarchically under the top-level item that called them. " -":guilabel:`Total Time` is that taken by the specified item and every " -"function \"underneath\" (*i.e.* called by) it, while :guilabel:`Local " -"Time` only counts the time spent in the particular callable object's own " -"scope. The :guilabel:`Calls` column displays the total number of times " -"the specified object was called at that level inside its parent calling " -"function (or within the ``__main__`` scope, if a top-level object). " -"Finally, the numbers in the :guilabel:`Diff` columns for each of the " -"three appear if a comparison is loaded, and indicate the deltas between " -"each measurement." +msgid "Results are broken down by function/method/statement, with each sub-element listed hierarchically under the top-level item that called them. :guilabel:`Total Time` is that taken by the specified item and every function \"underneath\" (*i.e.* called by) it, while :guilabel:`Local Time` only counts the time spent in the particular callable object's own scope. The :guilabel:`Calls` column displays the total number of times the specified object was called at that level inside its parent calling function (or within the ``__main__`` scope, if a top-level object). Finally, the numbers in the :guilabel:`Diff` columns for each of the three appear if a comparison is loaded, and indicate the deltas between each measurement." +msgstr "" + +#: ../../panes/profiler.rst:65 +msgid "Profiler with a comparison loaded, displaying the time deltas between two runs" msgstr "" #: ../../panes/profiler.rst:68 -msgid "" -"For example, suppose you ran the :guilabel:`Profiler` on a file calling a" -" function ``sleep_wrapper()`` that in turn called the ``sleep()`` " -"function, and the ``sleep_wrapper()`` function took a total of 3.87 ms to" -" run, with 3.86 ms of that spent executing the ``sleep()`` function " -"inside it. Therefore, if ``sleep()`` called nothing else itself, its " -":guilabel:`Total Time` and :guilabel:`Local Time` would both be " -"identical, at 3.87 ms. Meanwhile, :guilabel:`Total Time` for " -"``sleep_wrapper()`` would be 3.86 ms, but :guilabel:`Local Time` only " -"0.01 ms as the rest was spent inside the ``sleep()`` function it called." +msgid "For example, suppose you ran the :guilabel:`Profiler` on a file calling a function ``sleep_wrapper()`` that in turn called the ``sleep()`` function, and the ``sleep_wrapper()`` function took a total of 3.87 ms to run, with 3.86 ms of that spent executing the ``sleep()`` function inside it. Therefore, if ``sleep()`` called nothing else itself, its :guilabel:`Total Time` and :guilabel:`Local Time` would both be identical, at 3.87 ms. Meanwhile, :guilabel:`Total Time` for ``sleep_wrapper()`` would be 3.86 ms, but :guilabel:`Local Time` only 0.01 ms as the rest was spent inside the ``sleep()`` function it called." msgstr "" #: ../../panes/profiler.rst:76 @@ -1727,17 +1566,11 @@ msgid "Profiler plugins" msgstr "" #: ../../panes/profiler.rst:78 -msgid "" -"There are two additional plugins that you can install to enable other " -"types of profiling in Spyder. First, Spyder Line Profiler allows you to " -"benchmark each line of your code individually. To learn more, visit the " -"`spyder-line-profiler git repository`_." +msgid "There are two additional plugins that you can install to enable other types of profiling in Spyder. First, Spyder Line Profiler allows you to benchmark each line of your code individually. To learn more, visit the `spyder-line-profiler git repository`_." msgstr "" #: ../../panes/profiler.rst:87 -msgid "" -"Second, Spyder Memory Profiler measures the memory usage of your code. " -"For more information, go to the `spyder-memory-profiler git repository`_." +msgid "Second, Spyder Memory Profiler measures the memory usage of your code. For more information, go to the `spyder-memory-profiler git repository`_." msgstr "" #: ../../panes/projects.rst:3 @@ -1745,28 +1578,19 @@ msgid "Projects" msgstr "" #: ../../panes/projects.rst:5 -msgid "" -"Spyder allows you to associate a given directory with a **Project**, " -"which automatically saves and restores the files you have open in the " -":doc:`editor` from the last time you opened that project. With the " -":ref:`Project ` pane, you can browse all your project's" -" files, regardless of your current working directory or " -":doc:`fileexplorer` location." +msgid "Spyder allows you to associate a given directory with a **Project**, which automatically saves and restores the files you have open in the :doc:`editor` from the last time you opened that project. With the :ref:`Project ` pane, you can browse all your project's files, regardless of your current working directory or :doc:`fileexplorer` location." +msgstr "" + +#: ../../panes/projects.rst:8 +msgid "Spyder showing Project Explorer and projects menu" msgstr "" #: ../../panes/projects.rst:11 -msgid "" -"In addition, your project's root folder is used to set your working " -"directory, and automatically added to the ``PYTHONPATH``, so you can " -"easily ``import`` and work with any modules and packages you create " -"inside of it." +msgid "In addition, your project's root folder is used to set your working directory, and automatically added to the ``PYTHONPATH``, so you can easily ``import`` and work with any modules and packages you create inside of it." msgstr "" #: ../../panes/projects.rst:15 -msgid "" -"Projects are completely optional and not imposed on users. All of Spyder'" -" functionality (code completion, session saving, File Explorer, working " -"directory, etc) is available without creating a :guilabel:`Project`." +msgid "Projects are completely optional and not imposed on users. All of Spyder' functionality (code completion, session saving, File Explorer, working directory, etc) is available without creating a :guilabel:`Project`." msgstr "" #: ../../panes/projects.rst:22 @@ -1774,11 +1598,11 @@ msgid "Creating a Project" msgstr "" #: ../../panes/projects.rst:24 -msgid "" -"To create a :guilabel:`Project`, click the :guilabel:`New Project` entry " -"in the :guilabel:`Projects` menu, choose whether you'd like to associate " -"a :guilabel:`Project` with an existing directory or make a new one, and " -"enter the :guilabel:`Project`'s name and path." +msgid "To create a :guilabel:`Project`, click the :guilabel:`New Project` entry in the :guilabel:`Projects` menu, choose whether you'd like to associate a :guilabel:`Project` with an existing directory or make a new one, and enter the :guilabel:`Project`'s name and path." +msgstr "" + +#: ../../panes/projects.rst:26 +msgid "Spyder showing opening a new project" msgstr "" #: ../../panes/projects.rst:35 @@ -1786,11 +1610,11 @@ msgid "Using the Projects Pane" msgstr "" #: ../../panes/projects.rst:37 -msgid "" -"Once a :guilabel:`Project` is opened, the :guilabel:`Project` pane is " -"shown, presenting a tree view of the current :guilabel:`Project`'s files " -"and directories. It allows you to perform all the same :ref:`operations" -"` as Spyder's :doc:`fileexplorer` pane." +msgid "Once a :guilabel:`Project` is opened, the :guilabel:`Project` pane is shown, presenting a tree view of the current :guilabel:`Project`'s files and directories. It allows you to perform all the same :ref:`operations` as Spyder's :doc:`fileexplorer` pane." +msgstr "" + +#: ../../panes/projects.rst:40 +msgid "Spyder Project Explorer, displaying a directory tree of project files" msgstr "" #: ../../panes/projects.rst:49 @@ -1798,18 +1622,11 @@ msgid "Working with version control" msgstr "" #: ../../panes/projects.rst:51 -msgid "" -"The :guilabel:`Project` pane has basic integration with the `Git`_ " -"distributed version control system, just like :ref:`in the Files pane" -"`. You can commit or browse a file, directory or the " -"entire repository via the commands in the context menu." +msgid "The :guilabel:`Project` pane has basic integration with the `Git`_ distributed version control system, just like :ref:`in the Files pane`. You can commit or browse a file, directory or the entire repository via the commands in the context menu." msgstr "" #: ../../panes/projects.rst:56 -msgid "" -"To use this functionality, the :guilabel:`Project` must be located in a " -"``git`` repository and the ``git`` and ``gitk`` commands must be on the " -"system path." +msgid "To use this functionality, the :guilabel:`Project` must be located in a ``git`` repository and the ``git`` and ``gitk`` commands must be on the system path." msgstr "" #: ../../panes/pylint.rst:3 @@ -1817,14 +1634,11 @@ msgid "Code Analysis" msgstr "" #: ../../panes/pylint.rst:5 -msgid "" -"The **Code Analysis** pane detects style issues, bad practices, potential" -" bugs, and other quality problems in your code, all without having to " -"actually execute it. Based on these results, it also gives your code an " -"overall quality score. Spyder's code analyzer is powered by the best-in-" -"class `Pylint`_ back-end, which can intelligently detect an enormous and " -"customizable range of potential errors, bad practices, quality issues, " -"style violations, and more." +msgid "The **Code Analysis** pane detects style issues, bad practices, potential bugs, and other quality problems in your code, all without having to actually execute it. Based on these results, it also gives your code an overall quality score. Spyder's code analyzer is powered by the best-in-class `Pylint`_ back-end, which can intelligently detect an enormous and customizable range of potential errors, bad practices, quality issues, style violations, and more." +msgstr "" + +#: ../../panes/pylint.rst:11 +msgid "Spyder Pylint pane, showing numerous issues discovered in a file" msgstr "" #: ../../panes/pylint.rst:18 @@ -1832,52 +1646,51 @@ msgid "Using the code analyzer" msgstr "" #: ../../panes/pylint.rst:20 -msgid "" -"You can select the desired file to analyze directly in the :doc:`editor` " -"by clicking anywhere within it. To run the analysis, press the " -"configurable shortcut (:kbd:`F8` by default), select " -":menuselection:`Source --> Run code analysis` from the menu bar or click " -"the :guilabel:`Analyze` button in the Code Analysis pane. If the Code " -"Analysis pane is not visible, you can open it under :menuselection:`View " -"--> Panes --> Code Analysis`. All standard checks are run by default. To " -"go directly to a line in the :doc:`editor` highlighted by a failed check," -" just click its name." +msgid "You can select the desired file to analyze directly in the :doc:`editor` by clicking anywhere within it. To run the analysis, press the configurable shortcut (:kbd:`F8` by default), select :menuselection:`Source --> Run code analysis` from the menu bar or click the :guilabel:`Analyze` button in the Code Analysis pane. If the Code Analysis pane is not visible, you can open it under :menuselection:`View --> Panes --> Code Analysis`. All standard checks are run by default. To go directly to a line in the :doc:`editor` highlighted by a failed check, just click its name." +msgstr "" + +#: ../../panes/pylint.rst:26 +msgid "Spyder Pylint pane, showing running analysis and clicking failed check" msgstr "" #: ../../panes/pylint.rst:29 -msgid "" -"You can also manually enter the path of a file you'd like it to check in " -"the path entry box in the pane's toolbar. The analyzer works with both " -"individual scripts and whole Python packages (directories containing an " -":file:`__init__.py` file)." +msgid "You can also manually enter the path of a file you'd like it to check in the path entry box in the pane's toolbar. The analyzer works with both individual scripts and whole Python packages (directories containing an :file:`__init__.py` file)." +msgstr "" + +#: ../../panes/pylint.rst:32 +msgid "Spyder Pylint pane, showing running analysis browsing file" msgstr "" #: ../../panes/pylint.rst:35 -msgid "" -"Cancel analyzing a file with the :guilabel:`Stop` button, and if analysis" -" fails, click the :guilabel:`Output` button to find out why. If Pylint " -"does succeed, the :guilabel:`Output` will show the raw plain text " -"analysis results on the selected file, allowing you to easily browse and " -"copy/paste the full message names and descriptions." +msgid "Cancel analyzing a file with the :guilabel:`Stop` button, and if analysis fails, click the :guilabel:`Output` button to find out why. If Pylint does succeed, the :guilabel:`Output` will show the raw plain text analysis results on the selected file, allowing you to easily browse and copy/paste the full message names and descriptions." +msgstr "" + +#: ../../panes/pylint.rst:38 +msgid "Spyder Pylint pane, showing output" msgstr "" #: ../../panes/pylint.rst:41 -msgid "" -"Finally, you can click the dropdown or press the dropdown arrow in the " -"filename field to view results of previous analyses." +msgid "Finally, you can click the dropdown or press the dropdown arrow in the filename field to view results of previous analyses." +msgstr "" + +#: ../../panes/pylint.rst:43 +msgid "Spyder Pylint pane, showing history" msgstr "" #: ../../panes/pylint.rst:52 -msgid "" -"The number of recent runs Spyder should remember can be customized in the" -" :guilabel:`History` dialog, available from the Code Analysis options " -"menu." +msgid "The number of recent runs Spyder should remember can be customized in the :guilabel:`History` dialog, available from the Code Analysis options menu." +msgstr "" + +#: ../../panes/pylint.rst:54 +msgid "Spyder Pylint pane, customizing history dialog" msgstr "" #: ../../panes/pylint.rst:57 -msgid "" -"You can also expand or collapse one or all the sections in the pane by " -"using the corresponding options in the options menu." +msgid "You can also expand or collapse one or all the sections in the pane by using the corresponding options in the options menu." +msgstr "" + +#: ../../panes/pylint.rst:59 +msgid "Spyder Pylint pane, expanding and collapsing sections" msgstr "" #: ../../panes/pylint.rst:66 @@ -1885,23 +1698,19 @@ msgid "Advanced options" msgstr "" #: ../../panes/pylint.rst:68 -msgid "" -"You can turn certain messages off at the line, block or file/module level" -" by adding a ``# pylint: disable=MESSAGE-NAMES`` comment at the " -"respective `scope`_, where ``MESSAGE_NAMES`` should be replaced with a " -"comma-separated list (or single value) of `Pylint message names`_. For " -"example, a directive might look like ``# pylint: disable=invalid-name``, " -"or ``# pylint: disable=fixme, line-too-long``." +msgid "You can turn certain messages off at the line, block or file/module level by adding a ``# pylint: disable=MESSAGE-NAMES`` comment at the respective `scope`_, where ``MESSAGE_NAMES`` should be replaced with a comma-separated list (or single value) of `Pylint message names`_. For example, a directive might look like ``# pylint: disable=invalid-name``, or ``# pylint: disable=fixme, line-too-long``." +msgstr "" + +#: ../../panes/pylint.rst:75 +msgid "Spyder Pylint pane, showing disabling a message locally" msgstr "" #: ../../panes/pylint.rst:78 -msgid "" -"Or, you can globally suppress specific messages and adjust other Pylint " -"settings by editing the :file:`.pylintrc` configuration file in your user" -" folder. If it doesn't exist, you can generate it by running ``pylint " -"--generate-rcfile > .pylintrc`` in your user directory, from Anaconda " -"Prompt (on Windows) or your terminal (macOS/Linux). For more details on " -"configuring Pylint, see the `Pylint documentation`_." +msgid "Or, you can globally suppress specific messages and adjust other Pylint settings by editing the :file:`.pylintrc` configuration file in your user folder. If it doesn't exist, you can generate it by running ``pylint --generate-rcfile > .pylintrc`` in your user directory, from Anaconda Prompt (on Windows) or your terminal (macOS/Linux). For more details on configuring Pylint, see the `Pylint documentation`_." +msgstr "" + +#: ../../panes/pylint.rst:84 +msgid "Spyder Pylint pane, disabling a message globally in the .pylintrc" msgstr "" #: ../../panes/pylint.rst:94 @@ -1913,24 +1722,27 @@ msgid "Variable Explorer" msgstr "" #: ../../panes/variableexplorer.rst:5 -msgid "" -"The **Variable Explorer** allows you to interactively browse and manage " -"the objects generated running your code." +msgid "The **Variable Explorer** allows you to interactively browse and manage the objects generated running your code." +msgstr "" + +#: ../../panes/variableexplorer.rst:7 +msgid "Spyder Variable Explorer execution with a variable of type list" msgstr "" #: ../../panes/variableexplorer.rst:10 -msgid "" -"It shows the namespace contents (including all global objects, variables," -" class instances and more) of the currently selected " -":doc:`ipythonconsole` session, and allows you to add, remove, and edit " -"their values through a variety of GUI-based editors." +msgid "It shows the namespace contents (including all global objects, variables, class instances and more) of the currently selected :doc:`ipythonconsole` session, and allows you to add, remove, and edit their values through a variety of GUI-based editors." +msgstr "" + +#: ../../panes/variableexplorer.rst:12 +msgid "Spyder Variable Explorer, with a list of variables and their contents" msgstr "" #: ../../panes/variableexplorer.rst:15 -msgid "" -"The Variable Explorer gives you information on the name, size, type and " -"value of each object. To modify a scalar variable, like an number, string" -" or boolean, simply double click it in the pane and type its new value." +msgid "The Variable Explorer gives you information on the name, size, type and value of each object. To modify a scalar variable, like an number, string or boolean, simply double click it in the pane and type its new value." +msgstr "" + +#: ../../panes/variableexplorer.rst:18 +msgid "Spyder Variable Explorer modifying value of a variable" msgstr "" #: ../../panes/variableexplorer.rst:25 @@ -1938,11 +1750,7 @@ msgid "Object viewers" msgstr "" #: ../../panes/variableexplorer.rst:27 -msgid "" -"Spyder's :guilabel:`Variable Explorer` offers built in support for " -"editing lists, strings, dictionaries, NumPy arrays, Pandas DataFrames, " -"Series and more; as well as being able to plot and visualize them with " -"one click." +msgid "Spyder's :guilabel:`Variable Explorer` offers built in support for editing lists, strings, dictionaries, NumPy arrays, Pandas DataFrames, Series and more; as well as being able to plot and visualize them with one click." msgstr "" #: ../../panes/variableexplorer.rst:31 @@ -1950,9 +1758,11 @@ msgid "Strings" msgstr "" #: ../../panes/variableexplorer.rst:33 -msgid "" -"When a string variable is longer than forty characters, you can double " -"click it to see its value in a text editor to more easily modify it." +msgid "When a string variable is longer than forty characters, you can double click it to see its value in a text editor to more easily modify it." +msgstr "" + +#: ../../panes/variableexplorer.rst:35 +msgid "Variable Explorer text editor, displaying a long string in a window" msgstr "" #: ../../panes/variableexplorer.rst:41 @@ -1960,11 +1770,11 @@ msgid "Dictionaries" msgstr "" #: ../../panes/variableexplorer.rst:43 -msgid "" -"Double-clicking on dictionaries will show a viewer displaying each of its" -" keys with its associated value. You can double click any of the values " -"to modify them, which will open a new viewer if the value is itself an " -"object." +msgid "Double-clicking on dictionaries will show a viewer displaying each of its keys with its associated value. You can double click any of the values to modify them, which will open a new viewer if the value is itself an object." +msgstr "" + +#: ../../panes/variableexplorer.rst:46 +msgid "Dictionary editor displaying keys and their types, sizes, and values" msgstr "" #: ../../panes/variableexplorer.rst:52 @@ -1972,11 +1782,11 @@ msgid "Lists" msgstr "" #: ../../panes/variableexplorer.rst:54 -msgid "" -"For lists, the main Variable Explorer displays a preview of the first ten" -" values. To see them all, double click the list to open a viewer that " -"will display the index, type, size and value of each element of the list." -" Just like dictionaries, you can double-click values to edit them." +msgid "For lists, the main Variable Explorer displays a preview of the first ten values. To see them all, double click the list to open a viewer that will display the index, type, size and value of each element of the list. Just like dictionaries, you can double-click values to edit them." +msgstr "" + +#: ../../panes/variableexplorer.rst:58 +msgid "List editor displaying a list, showing one being edited" msgstr "" #: ../../panes/variableexplorer.rst:64 @@ -1984,29 +1794,23 @@ msgid "Numpy arrays" msgstr "" #: ../../panes/variableexplorer.rst:66 -msgid "" -"Like lists, for Numpy arrays the Variable Explorer shows a preview of " -"their values. Double-clicking them will open a viewer displaying the " -"array values in a \"heat map\", with each value in a grid cell colored " -"based on its numeric quantity. You can deactivate the background color by" -" unchecking the appropriate option in the viewer, which will happen " -"automatically if the array is too large to improve performance." +msgid "Like lists, for Numpy arrays the Variable Explorer shows a preview of their values. Double-clicking them will open a viewer displaying the array values in a \"heat map\", with each value in a grid cell colored based on its numeric quantity. You can deactivate the background color by unchecking the appropriate option in the viewer, which will happen automatically if the array is too large to improve performance." +msgstr "" + +#: ../../panes/variableexplorer.rst:70 +msgid "Array editor array, displaying a \"heatmap\" of its values" msgstr "" #: ../../panes/variableexplorer.rst:73 -msgid "" -"If supported by the datatype, you can also change the format of the " -"array's values, choosing the number of decimals that you want the array " -"to display. For this, click the :guilabel:`Format` button and and set the" -" desired formatting in the dialog that appears, using standard `Printf-" -"style syntax`_." +msgid "If supported by the datatype, you can also change the format of the array's values, choosing the number of decimals that you want the array to display. For this, click the :guilabel:`Format` button and and set the desired formatting in the dialog that appears, using standard `Printf-style syntax`_." msgstr "" #: ../../panes/variableexplorer.rst:78 -msgid "" -"Additionally, you can adjust the size of the rows and columns of the " -"array by expanding or contracting their headers. Clicking the " -":guilabel:`Resize` button will set it automatically." +msgid "Additionally, you can adjust the size of the rows and columns of the array by expanding or contracting their headers. Clicking the :guilabel:`Resize` button will set it automatically." +msgstr "" + +#: ../../panes/variableexplorer.rst:81 +msgid "Array editor with a 2D int array, showing resizing of columns" msgstr "" #: ../../panes/variableexplorer.rst:86 @@ -2014,29 +1818,35 @@ msgid "DataFrames" msgstr "" #: ../../panes/variableexplorer.rst:88 -msgid "" -"DataFrames, like Numpy arrays, display in a viewer where you can show or " -"hide \"heatmap\" colors, change the format and resize the rows and " -"columns either manually or automatically." +msgid "DataFrames, like Numpy arrays, display in a viewer where you can show or hide \"heatmap\" colors, change the format and resize the rows and columns either manually or automatically." +msgstr "" + +#: ../../panes/variableexplorer.rst:90 +msgid "Dataframe editor showing data frame \"heatmap\"" msgstr "" #: ../../panes/variableexplorer.rst:93 -msgid "" -"Additionally, starting in Spyder 4, the Variable Explorer has MultiIndex " -"support in its DataFrame inspector, including for multi-level and multi-" -"dimensional indices." +msgid "Additionally, starting in Spyder 4, the Variable Explorer has MultiIndex support in its DataFrame inspector, including for multi-level and multi-dimensional indices." +msgstr "" + +#: ../../panes/variableexplorer.rst:96 +msgid "Dataframe editor showing multi-index support" msgstr "" #: ../../panes/variableexplorer.rst:105 -msgid "" -"The options menu in the top right of the Variable Explorer pane allows " -"you filter the objects shown by a number of different criteria." +msgid "The options menu in the top right of the Variable Explorer pane allows you filter the objects shown by a number of different criteria." +msgstr "" + +#: ../../panes/variableexplorer.rst:107 +msgid "Spyder Variable Explorer, with options menu" msgstr "" #: ../../panes/variableexplorer.rst:110 -msgid "" -"It also allows you to display the min and max of Numpy arrays instead of " -"a preview of their values." +msgid "It also allows you to display the min and max of Numpy arrays instead of a preview of their values." +msgstr "" + +#: ../../panes/variableexplorer.rst:112 +msgid "Variable Explorer showing max and min values of numpy array" msgstr "" #: ../../panes/variableexplorer.rst:120 @@ -2044,35 +1854,27 @@ msgid "Toolbar buttons" msgstr "" #: ../../panes/variableexplorer.rst:122 -msgid "" -"The Variable Explorer's toolbar includes several useful features that " -"affect the entire namespace. For example, you can save the current " -"session's data as a ``.spydata`` file, which can be loaded later to " -"recover all the variables stored." +msgid "The Variable Explorer's toolbar includes several useful features that affect the entire namespace. For example, you can save the current session's data as a ``.spydata`` file, which can be loaded later to recover all the variables stored." +msgstr "" + +#: ../../panes/variableexplorer.rst:125 +msgid "Variable Explorer showing how to save and import data" msgstr "" #: ../../panes/variableexplorer.rst:130 -msgid "" -"You should **not** load any ``.spydata`` file from any source you don't " -"fully trust (ideally, only those files you've saved yourself). Like with " -"any `Python pickle`_, it is inherently not secure against malicious code," -" as it can load any Python object and can execute arbitrary code on your " -"machine. Additionally, it is not guaranteed to work reliably across all " -"Python environments other than the one it was created in, so it should be" -" only used as a local persistence format, not for interchange." +msgid "You should **not** load any ``.spydata`` file from any source you don't fully trust (ideally, only those files you've saved yourself). Like with any `Python pickle`_, it is inherently not secure against malicious code, as it can load any Python object and can execute arbitrary code on your machine. Additionally, it is not guaranteed to work reliably across all Python environments other than the one it was created in, so it should be only used as a local persistence format, not for interchange." msgstr "" #: ../../panes/variableexplorer.rst:136 -msgid "" -"There is also a button to remove all displayed variables, and a search " -"box to find objects by name or type." +msgid "There is also a button to remove all displayed variables, and a search box to find objects by name or type." +msgstr "" + +#: ../../panes/variableexplorer.rst:138 +msgid "Variable Explorer showing how to search variables" msgstr "" #: ../../panes/variableexplorer.rst:141 -msgid "" -"Finally, there is a button to refresh the Variable Explorer's contents, " -"which will update it to show the current state of the code running in the" -" IPython console." +msgid "Finally, there is a button to refresh the Variable Explorer's contents, which will update it to show the current state of the code running in the IPython console." msgstr "" #: ../../panes/variableexplorer.rst:147 @@ -2080,59 +1882,57 @@ msgid "Advanced functionality" msgstr "" #: ../../panes/variableexplorer.rst:149 -msgid "" -"The context menu, available by right-clicking any variable, provides " -"numerous additional options to interact with objects of various types. " -"These include renaming, removing or editing existing variables, as well " -"as the :guilabel:`duplicate` option to create a new copy of one of them " -"under a new name you enter in the resulting dialog box." +msgid "The context menu, available by right-clicking any variable, provides numerous additional options to interact with objects of various types. These include renaming, removing or editing existing variables, as well as the :guilabel:`duplicate` option to create a new copy of one of them under a new name you enter in the resulting dialog box." +msgstr "" + +#: ../../panes/variableexplorer.rst:152 +msgid "Variable Explorer showing duplicating a variable" msgstr "" #: ../../panes/variableexplorer.rst:155 -msgid "" -"Furthermore, you can copy and paste the value of a variable, saving it in" -" the Variable Explorer with any name that you choose. This allows you to " -"change the type of the variable that you are pasting which can be very " -"useful, allowing you to, for example, easily copy the elements of a list " -"into an array." +msgid "Furthermore, you can copy and paste the value of a variable, saving it in the Variable Explorer with any name that you choose. This allows you to change the type of the variable that you are pasting which can be very useful, allowing you to, for example, easily copy the elements of a list into an array." +msgstr "" + +#: ../../panes/variableexplorer.rst:158 +msgid "Variable Explorer showing copying list into array" msgstr "" #: ../../panes/variableexplorer.rst:161 -msgid "" -"Additionally, you can create an object from scratch directly in the " -"Variable Explorer with the :guilabel:`Insert` option, which allows you to" -" type the key (which should be in quotation marks) and the value for the " -"item that you want to insert. In addition to adding a new top-level " -"variable, this feature also allows you to create a new key in a " -"dictionary, a new element in a list, and much more." +msgid "Additionally, you can create an object from scratch directly in the Variable Explorer with the :guilabel:`Insert` option, which allows you to type the key (which should be in quotation marks) and the value for the item that you want to insert. In addition to adding a new top-level variable, this feature also allows you to create a new key in a dictionary, a new element in a list, and much more." +msgstr "" + +#: ../../panes/variableexplorer.rst:164 +msgid "Variable Explorer showing insertion of a new variable" msgstr "" #: ../../panes/variableexplorer.rst:167 -msgid "" -"For lists and Numpy arrays, more advanced options are available, " -"including generating plots and histograms of their values appropriate to " -"their type and dimensions." +msgid "For lists and Numpy arrays, more advanced options are available, including generating plots and histograms of their values appropriate to their type and dimensions." +msgstr "" + +#: ../../panes/variableexplorer.rst:169 +msgid "Plot window showing a plot, generated via the previous options" msgstr "" #: ../../panes/variableexplorer.rst:172 -msgid "" -"You can even save an array to a ``.npy`` file by simply clicking the " -"appropriate option, which can later be loaded by Spyder or in your code " -"via ``numpy.load()``." +msgid "You can even save an array to a ``.npy`` file by simply clicking the appropriate option, which can later be loaded by Spyder or in your code via ``numpy.load()``." +msgstr "" + +#: ../../panes/variableexplorer.rst:174 +msgid "Context menu for an int array, with the Show image option selected" msgstr "" #: ../../panes/variableexplorer.rst:178 -msgid "" -"For two-dimensional arrays, you can also display them as images, treating" -" their values as RGB colors. For this, Spyder uses Matplotlib's " -"colormaps, which can be `easily changed to match your preferences`_." +msgid "For two-dimensional arrays, you can also display them as images, treating their values as RGB colors. For this, Spyder uses Matplotlib's colormaps, which can be `easily changed to match your preferences`_." +msgstr "" + +#: ../../panes/variableexplorer.rst:182 +msgid "Interactive image based on the array's data" msgstr "" #: ../../panes/variableexplorer.rst:185 -msgid "" -"Finally, we added a context-menu action to open any object using the new " -"Object Explorer even if they already have a builtin viewer (DataFrames, " -"arrays, etc), allowing for deeper inspection of the inner workings of " -"these datatypes." +msgid "Finally, we added a context-menu action to open any object using the new Object Explorer even if they already have a builtin viewer (DataFrames, arrays, etc), allowing for deeper inspection of the inner workings of these datatypes." msgstr "" +#: ../../panes/variableexplorer.rst:187 +msgid "Object explorer showing dataframe" +msgstr "" diff --git a/doc/locales/pot/plugins.pot b/doc/locales/pot/plugins.pot index 16476989..35e70fb6 100644 --- a/doc/locales/pot/plugins.pot +++ b/doc/locales/pot/plugins.pot @@ -1,23 +1,23 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../plugins/index.rst:3 -msgid "Spyder Plugins" +msgid "Plugins" msgstr "" #: ../../plugins/lineprofiler.rst:3 @@ -25,10 +25,11 @@ msgid "Spyder Line Profiler" msgstr "" #: ../../plugins/lineprofiler.rst:5 -msgid "" -"**Spyder-Line-Profiler** is a plugin to run the Python `line profiler`_. " -"This package profiles the time that individual lines of code take to " -"execute." +msgid "**Spyder-Line-Profiler** is a plugin to run the Python `line profiler`_. This package profiles the time that individual lines of code take to execute." +msgstr "" + +#: ../../plugins/lineprofiler.rst:10 +msgid "Spyder with the Line Profiler pane open" msgstr "" #: ../../plugins/lineprofiler.rst:17 @@ -36,20 +37,15 @@ msgid "Installing the Line Profiler" msgstr "" #: ../../plugins/lineprofiler.rst:19 -msgid "" -"If you installed Spyder using conda, the best way to obtain Spyder-Line-" -"Profiler is to run the following command in your terminal (or Anaconda " -"prompt on Windows):" +msgid "If you installed Spyder using conda, the best way to obtain Spyder-Line-Profiler is to run the following command in your terminal (or Anaconda prompt on Windows):" msgstr "" #: ../../plugins/lineprofiler.rst:27 -msgid "" -"At the moment it is not possible to use this plugin with the Spyder :ref" -":`install-standalone` for Windows and macOS. We're working to add support" -" for them in the future." +msgid "At the moment it is not possible to use this plugin with the Spyder :ref:`install-standalone` for Windows and macOS. We're working to add support for them in the future." msgstr "" -#: ../../plugins/lineprofiler.rst:30 ../../plugins/notebook.rst:26 +#: ../../plugins/lineprofiler.rst:30 +#: ../../plugins/notebook.rst:26 #: ../../plugins/terminal.rst:27 msgid "Restart Spyder in order to be able to use the plugin." msgstr "" @@ -59,32 +55,35 @@ msgid "Using the Line Profiler" msgstr "" #: ../../plugins/lineprofiler.rst:38 -msgid "" -"When the Line Profiler is installed, it will be available under the menu " -"item :menuselection:`View --> Panes --> Line Profiler`." +msgid "When the Line Profiler is installed, it will be available under the menu item :menuselection:`View --> Panes --> Line Profiler`." +msgstr "" + +#: ../../plugins/lineprofiler.rst:40 +msgid "Spyder showing View Panes Line Profiler" msgstr "" #: ../../plugins/lineprofiler.rst:43 -msgid "" -"You will see it then as a tab next to the :guilabel:`Files` tab. For the " -"Line Profiler to work, you must place the ``@profile`` decorator on the " -"line above any functions that you wish to profile." +msgid "You will see it then as a tab next to the :guilabel:`Files` tab. For the Line Profiler to work, you must place the ``@profile`` decorator on the line above any functions that you wish to profile." +msgstr "" + +#: ../../plugins/lineprofiler.rst:46 +msgid "Adding 'profile' decorators to script to profile it line by line." msgstr "" #: ../../plugins/lineprofiler.rst:49 -msgid "" -"Now that the decorators have been added, you can then either select a " -"script with the button present in the pane or run the profiler from " -":menuselection:`Run --> Profile line by line`. Your file will then be " -"profiled line by line." +msgid "Now that the decorators have been added, you can then either select a script with the button present in the pane or run the profiler from :menuselection:`Run --> Profile line by line`. Your file will then be profiled line by line." +msgstr "" + +#: ../../plugins/lineprofiler.rst:52 +msgid "Spyder showing the line profiler button in the Run menu" msgstr "" #: ../../plugins/lineprofiler.rst:55 -msgid "" -"After running the profiler, either from the button in the pane or the " -":menuselection:`Run` menu, the results are shown in the :guilabel:`Line " -"Profiler` pane. The path displayed there is that of the file being " -"profiled." +msgid "After running the profiler, either from the button in the pane or the :menuselection:`Run` menu, the results are shown in the :guilabel:`Line Profiler` pane. The path displayed there is that of the file being profiled." +msgstr "" + +#: ../../plugins/lineprofiler.rst:58 +msgid "Running the line profiler and inspecting the results." msgstr "" #: ../../plugins/lineprofiler.rst:61 @@ -100,9 +99,7 @@ msgid "``Hits:`` how many times that line is hit in the scope." msgstr "" #: ../../plugins/lineprofiler.rst:65 -msgid "" -"``Time (ms):`` time spent running the line in total for all hits, in " -"milliseconds." +msgid "``Time (ms):`` time spent running the line in total for all hits, in milliseconds." msgstr "" #: ../../plugins/lineprofiler.rst:66 @@ -126,16 +123,15 @@ msgid "Spyder Notebook" msgstr "" #: ../../plugins/notebook.rst:5 -msgid "" -"**Spyder-notebook** is a plugin that allows you to open, edit and " -"interact with Jupyter Notebooks right inside Spyder." +msgid "**Spyder-notebook** is a plugin that allows you to open, edit and interact with Jupyter Notebooks right inside Spyder." +msgstr "" + +#: ../../plugins/notebook.rst:7 +msgid "Spyder Notebook in Spyder" msgstr "" #: ../../plugins/notebook.rst:10 -msgid "" -"Using notebooks inside Spyder allows you to take advantage of their web " -"interface alongside Spyder’s powerful features such as the Variable " -"explorer, console and debugger." +msgid "Using notebooks inside Spyder allows you to take advantage of their web interface alongside Spyder’s powerful features such as the Variable explorer, console and debugger." msgstr "" #: ../../plugins/notebook.rst:14 @@ -143,17 +139,12 @@ msgid "Installing the Notebook" msgstr "" #: ../../plugins/notebook.rst:16 -msgid "" -"If you installed Spyder using conda, the best way to install Spyder-" -"notebook is to run the following command in your terminal or Anaconda " -"prompt on Windows:" +msgid "If you installed Spyder using conda, the best way to install Spyder-notebook is to run the following command in your terminal or Anaconda prompt on Windows:" msgstr "" -#: ../../plugins/notebook.rst:24 ../../plugins/terminal.rst:25 -msgid "" -"At the moment it is not possible to use this plugin with the Spyder :ref" -":`install-standalone` for Windows and macOS. We're working to make that " -"possible in the future." +#: ../../plugins/notebook.rst:24 +#: ../../plugins/terminal.rst:25 +msgid "At the moment it is not possible to use this plugin with the Spyder :ref:`install-standalone` for Windows and macOS. We're working to make that possible in the future." msgstr "" #: ../../plugins/notebook.rst:30 @@ -161,49 +152,47 @@ msgid "Using the Notebook" msgstr "" #: ../../plugins/notebook.rst:32 -msgid "" -"When the Notebook is installed, it will be available under the menu item " -":menuselection:`View --> Panes --> Notebook`." +msgid "When the Notebook is installed, it will be available under the menu item :menuselection:`View --> Panes --> Notebook`." +msgstr "" + +#: ../../plugins/notebook.rst:34 +msgid "Spyder showing view panes Notebook" msgstr "" #: ../../plugins/notebook.rst:37 -msgid "" -"You will see it then as a tab in the bottom of the editor area. When " -"switching to it, a welcome screen will be displayed, from where you can " -"create a new notebook by right-clicking it and selecting :guilabel:`New " -"notebook`." +msgid "You will see it then as a tab in the bottom of the editor area. When switching to it, a welcome screen will be displayed, from where you can create a new notebook by right-clicking it and selecting :guilabel:`New notebook`." +msgstr "" + +#: ../../plugins/notebook.rst:39 +msgid "Spyder with context menu showing new notebook option" msgstr "" #: ../../plugins/notebook.rst:42 -msgid "" -"You can also click the :guilabel:`Plus` button at the top right of the " -"pane. A new Jupyter Notebook will be opened as a tab, ready for user " -"input in a temporary file. This can serve as a scratch pad where you can " -"do quick calculations and plots." +msgid "You can also click the :guilabel:`Plus` button at the top right of the pane. A new Jupyter Notebook will be opened as a tab, ready for user input in a temporary file. This can serve as a scratch pad where you can do quick calculations and plots." +msgstr "" + +#: ../../plugins/notebook.rst:44 +msgid "Spyder showing a new notebook" msgstr "" #: ../../plugins/notebook.rst:47 -msgid "" -"To save this notebook go to the options menu at the top right of the pane" -" and click the :guilabel:`Save as...` option. This will store your " -"notebook locally with the ``ipynb`` extension, which will allow you to " -"open it then as a Jupyter Notebook outside of Spyder." +msgid "To save this notebook go to the options menu at the top right of the pane and click the :guilabel:`Save as...` option. This will store your notebook locally with the ``ipynb`` extension, which will allow you to open it then as a Jupyter Notebook outside of Spyder." +msgstr "" + +#: ../../plugins/notebook.rst:49 +msgid "Gif showing save as" msgstr "" #: ../../plugins/notebook.rst:52 -msgid "" -"You can also open any Jupyter Notebook inside Spyder. For this go to the " -"options menu at the top right of the pane and click :guilabel:`Open`, " -"which will allow you to look for ``ipynb`` files in your computer. Click " -"any notebook that you want to open inside Spyder and you will be able to " -"see it as a new tab in the Notebook pane." +msgid "You can also open any Jupyter Notebook inside Spyder. For this go to the options menu at the top right of the pane and click :guilabel:`Open`, which will allow you to look for ``ipynb`` files in your computer. Click any notebook that you want to open inside Spyder and you will be able to see it as a new tab in the Notebook pane." +msgstr "" + +#: ../../plugins/notebook.rst:54 +msgid "Gif showing opening a Jupyter notebook inside Spyder" msgstr "" #: ../../plugins/notebook.rst:57 -msgid "" -"The :guilabel:`Open recent` option displays a list of the recent " -"notebooks you opened in Spyder, from which you can select them and open " -"them again in Spyder." +msgid "The :guilabel:`Open recent` option displays a list of the recent notebooks you opened in Spyder, from which you can select them and open them again in Spyder." msgstr "" #: ../../plugins/notebook.rst:61 @@ -211,14 +200,11 @@ msgid "Connecting an IPython Console" msgstr "" #: ../../plugins/notebook.rst:63 -msgid "" -"You can connect an :doc:`/panes/ipythonconsole` to your notebook, which " -"will allow you to view your variables in the " -":doc:`/panes/variableexplorer`. To do so, go to the options menu and " -"click the :guilabel:`Open console` option. This will open a new console " -"with the same name of your notebook and display the variables of the " -"cells that you have executed previously in your Notebook. If you don't " -"see them, press :kbd:`Enter` in the console." +msgid "You can connect an :doc:`/panes/ipythonconsole` to your notebook, which will allow you to view your variables in the :doc:`/panes/variableexplorer`. To do so, go to the options menu and click the :guilabel:`Open console` option. This will open a new console with the same name of your notebook and display the variables of the cells that you have executed previously in your Notebook. If you don't see them, press :kbd:`Enter` in the console." +msgstr "" + +#: ../../plugins/notebook.rst:65 +msgid "Gif showing connecting console and displaying variables" msgstr "" #: ../../plugins/notebook.rst:68 @@ -226,10 +212,7 @@ msgid "You can view, modify and create new ones in the console too." msgstr "" #: ../../plugins/notebook.rst:70 -msgid "" -"Since the Variable Explorer is associated to each console, closing the " -"notebook's console will immediately hide the variables from the Variable " -"Explorer." +msgid "Since the Variable Explorer is associated to each console, closing the notebook's console will immediately hide the variables from the Variable Explorer." msgstr "" #: ../../plugins/notebook.rst:74 @@ -237,21 +220,27 @@ msgid "Additional Options" msgstr "" #: ../../plugins/notebook.rst:76 -msgid "" -"The context menu, available by right-clicking the pane area outside the " -"notebook, allows you to zoom your notebook in or out." +msgid "The context menu, available by right-clicking the pane area outside the notebook, allows you to zoom your notebook in or out." +msgstr "" + +#: ../../plugins/notebook.rst:78 +msgid "Gif zooming in and out the notebook." msgstr "" #: ../../plugins/notebook.rst:81 -msgid "" -"You can also select the code from your Notebook and copy it on your " -"clipboard to paste this code anywhere you want." +msgid "You can also select the code from your Notebook and copy it on your clipboard to paste this code anywhere you want." +msgstr "" + +#: ../../plugins/notebook.rst:83 +msgid "Gif copying and pasting" msgstr "" #: ../../plugins/notebook.rst:86 -msgid "" -"Finally, you can see all the server information of your notebook by " -"clicking the :guilabel:`Server info` option in the context menu." +msgid "Finally, you can see all the server information of your notebook by clicking the :guilabel:`Server info` option in the context menu." +msgstr "" + +#: ../../plugins/notebook.rst:88 +msgid "Server info for notebook in Spyder" msgstr "" #: ../../plugins/terminal.rst:3 @@ -259,17 +248,15 @@ msgid "Spyder Terminal" msgstr "" #: ../../plugins/terminal.rst:5 -msgid "" -"**Spyder-terminal** is a plugin that allows you to have integrated system" -" terminals inside Spyder." +msgid "**Spyder-terminal** is a plugin that allows you to have integrated system terminals inside Spyder." +msgstr "" + +#: ../../plugins/terminal.rst:7 +msgid "Spyder Terminal in Spyder" msgstr "" #: ../../plugins/terminal.rst:10 -msgid "" -"Spyder-terminal allows you to use any system shell installed in your " -"system (e.g. Bash, Zsh or Powershell) rather than just the IPython " -"console. You can use it to issue commands, interact with version control " -"or to run programs." +msgid "Spyder-terminal allows you to use any system shell installed in your system (e.g. Bash, Zsh or Powershell) rather than just the IPython console. You can use it to issue commands, interact with version control or to run programs." msgstr "" #: ../../plugins/terminal.rst:15 @@ -277,10 +264,7 @@ msgid "Installing the Terminal" msgstr "" #: ../../plugins/terminal.rst:17 -msgid "" -"If you installed Spyder using conda, the best way to install Spyder-" -"terminal is to run the following command in your Terminal or Anaconda " -"prompt on Windows:" +msgid "If you installed Spyder using conda, the best way to install Spyder-terminal is to run the following command in your Terminal or Anaconda prompt on Windows:" msgstr "" #: ../../plugins/terminal.rst:31 @@ -288,31 +272,35 @@ msgid "Using the Terminal" msgstr "" #: ../../plugins/terminal.rst:33 -msgid "" -"When the Terminal is installed, it will be available under the menu item " -":menuselection:`View --> Panes --> Terminal`." +msgid "When the Terminal is installed, it will be available under the menu item :menuselection:`View --> Panes --> Terminal`." +msgstr "" + +#: ../../plugins/terminal.rst:35 +msgid "Spyder showing view panes Terminal" msgstr "" #: ../../plugins/terminal.rst:38 -msgid "" -"You will see it then as a tab at the bottom of the console area. When " -"switching to it, a new terminal tab will be created. You can also create " -"more terminals by clicking in the :guilabel:`+` button at the upper right" -" corner of the terminal area." +msgid "You will see it then as a tab at the bottom of the console area. When switching to it, a new terminal tab will be created. You can also create more terminals by clicking in the :guilabel:`+` button at the upper right corner of the terminal area." +msgstr "" + +#: ../../plugins/terminal.rst:40 +msgid "Spyder showing the new terminal button" msgstr "" #: ../../plugins/terminal.rst:43 -msgid "" -"Clicking the :guilabel:`Options` button next to the :guilabel:`+` button " -"will allow you to rename terminals, undock the terminal, and open a " -"terminal in the directory of the current Editor file." +msgid "Clicking the :guilabel:`Options` button next to the :guilabel:`+` button will allow you to rename terminals, undock the terminal, and open a terminal in the directory of the current Editor file." +msgstr "" + +#: ../../plugins/terminal.rst:45 +msgid "Spyder showing the terminal Options menu" msgstr "" #: ../../plugins/terminal.rst:48 -msgid "" -"If you right click the terminal area, it's possible to issue commands " -"such as :guilabel:`Clear Terminal`, :guilabel:`Zoom In/Out` and " -":guilabel:`Copy/Paste Text`." +msgid "If you right click the terminal area, it's possible to issue commands such as :guilabel:`Clear Terminal`, :guilabel:`Zoom In/Out` and :guilabel:`Copy/Paste Text`." +msgstr "" + +#: ../../plugins/terminal.rst:50 +msgid "Spyder showing the terminal context menu" msgstr "" #: ../../plugins/terminal.rst:55 @@ -320,10 +308,9 @@ msgid "Terminal Preferences" msgstr "" #: ../../plugins/terminal.rst:57 -msgid "" -"It's also possible to customize the Terminal by going to " -":menuselection:`python --> Preferences...` and then clicking on the " -"Terminal tab on the menu to the left. You can select the shell " -"interpreter, set the buffer limit and the type of cursor." +msgid "It's also possible to customize the Terminal by going to :menuselection:`python --> Preferences...` and then clicking on the Terminal tab on the menu to the left. You can select the shell interpreter, set the buffer limit and the type of cursor." msgstr "" +#: ../../plugins/terminal.rst:60 +msgid "Preferences of the Terminal plugin" +msgstr "" diff --git a/doc/locales/pot/quickstart.pot b/doc/locales/pot/quickstart.pot index 1e5624aa..0526ee80 100644 --- a/doc/locales/pot/quickstart.pot +++ b/doc/locales/pot/quickstart.pot @@ -1,31 +1,25 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../quickstart.rst:3 -msgid "Quickstart" +msgid "Tour" msgstr "" #: ../../quickstart.rst:5 -msgid "" -"Welcome to our Quickstart! Here you will find an interactive tour that " -"will guide you through Spyder's interface. You'll get familiar with the " -"most important parts of the IDE, especially those we'll be mentioning " -"throughout our docs. Finally, you'll get to walk through some of Spyder's" -" key panes and functionality." +msgid "Welcome to our Quickstart! Here you will find an interactive tour that will guide you through Spyder's interface. You'll get familiar with the most important parts of the IDE, especially those we'll be mentioning throughout our docs. Finally, you'll get to walk through some of Spyder's key panes and functionality." msgstr "" - diff --git a/doc/locales/pot/troubleshooting.pot b/doc/locales/pot/troubleshooting.pot index 62425f64..1a52d91c 100644 --- a/doc/locales/pot/troubleshooting.pot +++ b/doc/locales/pot/troubleshooting.pot @@ -1,19 +1,19 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../troubleshooting/basic-first-aid.rst:3 @@ -21,9 +21,7 @@ msgid "Basic First Aid" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:5 -msgid "" -"These suggestions, while more of a shotgun approach, tend to fix the " -"majority of reported issues just on their own." +msgid "These suggestions, while more of a shotgun approach, tend to fix the majority of reported issues just on their own." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:11 @@ -35,77 +33,48 @@ msgid "**Restart Spyder**, and try what you were doing before again." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:15 -msgid "" -"**Upgrade Spyder** to the latest release, and you might find your issue " -"is resolved (along with new features, enhancements, and other bug fixes)." -" Minor releases come out every couple months, so unless you've updated " -"recently, there is a good chance your version isn't the latest. You can " -"find out with the :guilabel:`Check for updates` command under the " -":guilabel:`Help` menu." +msgid "**Upgrade Spyder** to the latest release, and you might find your issue is resolved (along with new features, enhancements, and other bug fixes). Minor releases come out every couple months, so unless you've updated recently, there is a good chance your version isn't the latest. You can find out with the :guilabel:`Check for updates` command under the :guilabel:`Help` menu." +msgstr "" + +#: ../../troubleshooting/basic-first-aid.rst:19 +#: ../../troubleshooting/first-steps.rst:25 +msgid "Spyder showing view internal console option" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:22 -msgid "" -"To perform the update with Conda (strongly recommended), from your " -"terminal (or Anaconda Prompt on Windows) run:" +msgid "To perform the update with Conda (strongly recommended), from your terminal (or Anaconda Prompt on Windows) run:" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:29 -msgid "" -"**Update Spyder's dependencies and environment**, either by installing " -"the latest version of your distribution (e.g. the recommended Anaconda), " -"or with the relevant \"update all\" command in your terminal (or Anaconda" -" Prompt on Windows). To get the latest stable version of everything using" -" Conda, you can run:" +msgid "**Update Spyder's dependencies and environment**, either by installing the latest version of your distribution (e.g. the recommended Anaconda), or with the relevant \"update all\" command in your terminal (or Anaconda Prompt on Windows). To get the latest stable version of everything using Conda, you can run:" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:36 -msgid "" -"**Restart your machine**, in case the problem lies with a lingering " -"process or another such issue." +msgid "**Restart your machine**, in case the problem lies with a lingering process or another such issue." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:38 -msgid "" -"**Restore Spyder's config files** to their defaults, which solves a huge " -"variety of Spyder issues. From your terminal (or Anaconda Prompt on " -"Windows), run:" +msgid "**Restore Spyder's config files** to their defaults, which solves a huge variety of Spyder issues. From your terminal (or Anaconda Prompt on Windows), run:" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:47 -msgid "" -"This will reset your preferences, as well as any custom keyboard " -"shortcuts or syntax highlighting schemes. If you particularly care about " -"any of those, you should make a copy of the :file:`.spyder-py3` folder in" -" your user home directory (:file:`C:/Users/YOUR_USERNAME` on Windows, " -":file:`/Users/YOUR_USERNAME` on macOS, or :file:`/home/YOUR_USERNAME` on " -"Linux), and restore it afterwards if this doesn't solve the problem." +msgid "This will reset your preferences, as well as any custom keyboard shortcuts or syntax highlighting schemes. If you particularly care about any of those, you should make a copy of the :file:`.spyder-py3` folder in your user home directory (:file:`C:/Users/YOUR_USERNAME` on Windows, :file:`/Users/YOUR_USERNAME` on macOS, or :file:`/home/YOUR_USERNAME` on Linux), and restore it afterwards if this doesn't solve the problem." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:50 -msgid "" -"**Try installing Spyder into a new Conda environment** (recommended) or " -"``virtualenv``/``venv``, and see if the issue reoccurs." +msgid "**Try installing Spyder into a new Conda environment** (recommended) or ``virtualenv``/``venv``, and see if the issue reoccurs." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:52 -msgid "" -"In your system terminal (or Anaconda Prompt on Windows), run the " -"following commands to create an a fresh, clean environment and start " -"Spyder in it:" +msgid "In your system terminal (or Anaconda Prompt on Windows), run the following commands to create an a fresh, clean environment and start Spyder in it:" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:60 -msgid "" -"If this fixes the issue, the problem was likely due to another package " -"installed on your system, particularly if done with pip, which can cause " -"many problems and should be avoided if at all possible." +msgid "If this fixes the issue, the problem was likely due to another package installed on your system, particularly if done with pip, which can cause many problems and should be avoided if at all possible." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:62 -msgid "" -"**Watch our video** on solving and avoiding problems with pip, Conda and " -"Conda-Forge, and follow its instructions." +msgid "**Watch our video** on solving and avoiding problems with pip, Conda and Conda-Forge, and follow its instructions." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:75 @@ -113,35 +82,23 @@ msgid "Reinstalling Spyder" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:77 -msgid "" -"If none of the previous steps solve your issue, you should do a full " -"uninstall of Spyder by whatever means you originally installed it." +msgid "If none of the previous steps solve your issue, you should do a full uninstall of Spyder by whatever means you originally installed it." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:79 -msgid "" -"For Anaconda, follow all the steps under Option B in the `Anaconda " -"uninstall guide`_, delete the Anaconda directory wherever it was " -"originally installed, and (on Windows) remove the " -":file:`%appdata%/python` directory if it exists." +msgid "For Anaconda, follow all the steps under Option B in the `Anaconda uninstall guide`_, delete the Anaconda directory wherever it was originally installed, and (on Windows) remove the :file:`%appdata%/python` directory if it exists." +msgstr "" + +#: ../../troubleshooting/basic-first-aid.rst:81 +msgid "Deleting appdata/python directory" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:84 -msgid "" -"Then, do a clean install of the latest version of the `Anaconda " -"distribution`_ which is how we recommend you install Spyder and keep it " -"up to date." +msgid "Then, do a clean install of the latest version of the `Anaconda distribution`_ which is how we recommend you install Spyder and keep it up to date." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:88 -msgid "" -"While you are welcome to get Spyder working on your own by one of the " -"many other means we offer, we are only able to provide individual support" -" for install-related issues for users of the Anaconda distribution. In " -"particular, pip installation, while doable, is only really for experts, " -"as there are many pitfalls involved and different issues specific to your" -" setup, which is why we recommend using Conda whenever possible. For " -"further information, please visit our :doc:`/installation`." +msgid "While you are welcome to get Spyder working on your own by one of the many other means we offer, we are only able to provide individual support for install-related issues for users of the Anaconda distribution. In particular, pip installation, while doable, is only really for experts, as there are many pitfalls involved and different issues specific to your setup, which is why we recommend using Conda whenever possible. For further information, please visit our :doc:`/installation`." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:99 @@ -149,68 +106,39 @@ msgid "Isolating problems" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:101 -msgid "" -"If you get an error while running a specific line, block, or " -"script/program, it may not be an issue with Spyder, but rather something " -"lower down in the packages it depends on. Try running it in the following" -" in order if and until it starts working as you expect. If you manage to " -"isolate the bug, report it to the last one it *doesn't* work in." +msgid "If you get an error while running a specific line, block, or script/program, it may not be an issue with Spyder, but rather something lower down in the packages it depends on. Try running it in the following in order if and until it starts working as you expect. If you manage to isolate the bug, report it to the last one it *doesn't* work in." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:105 -msgid "" -"**Spyder** itself, of course! Make sure you can reproduce the error after" -" closing and reopening it, if possible." +msgid "**Spyder** itself, of course! Make sure you can reproduce the error after closing and reopening it, if possible." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:108 -msgid "" -"**A bare QtConsole instance**, e.g. launched from Anaconda navigator or " -"from the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux) with " -"``jupyter qtconsole``." +msgid "**A bare QtConsole instance**, e.g. launched from Anaconda navigator or from the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux) with ``jupyter qtconsole``." +msgstr "" + +#: ../../troubleshooting/basic-first-aid.rst:110 +msgid "Anaconda navigator showing qtconsole" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:113 -msgid "" -"QtConsole is the GUI console backend Spyder depends on to run its code, " -"so most issues involving Spyder's :doc:`/panes/ipythonconsole` are " -"actually something with QtConsole instead, and can be reported to their " -"`issue tracker`_." +msgid "QtConsole is the GUI console backend Spyder depends on to run its code, so most issues involving Spyder's :doc:`/panes/ipythonconsole` are actually something with QtConsole instead, and can be reported to their `issue tracker`_." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:115 -msgid "" -"**An IPython command line shell**, launched with e.g. ``ipython`` from " -"the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). " -"Reproducible bugs can be reported to their `Github page`_, though make " -"sure to read their guidelines and docs first." +msgid "**An IPython command line shell**, launched with e.g. ``ipython`` from the Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). Reproducible bugs can be reported to their `Github page`_, though make sure to read their guidelines and docs first." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:118 -msgid "" -"**A standard Python interpreter**, either run as a script file with " -"``python path/to/your/file.py`` or launched interactively with ``python``" -" from your Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). " -"While it is not impossible that you've found Python bug, it is much more " -"likely to be an issue with the code itself or a package you are using, so" -" your best sources are the `Python docs`_ and the other resources listed " -"above." +msgid "**A standard Python interpreter**, either run as a script file with ``python path/to/your/file.py`` or launched interactively with ``python`` from your Anaconda Prompt/Terminal/command line (Windows/Mac/Linux). While it is not impossible that you've found Python bug, it is much more likely to be an issue with the code itself or a package you are using, so your best sources are the `Python docs`_ and the other resources listed above." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:127 -msgid "" -"If the problem reoccurs in a similar or identical way with any of these " -"methods (other than only Spyder itself), then it is almost certainly not " -"an issue with Spyder, and would be best handled elsewhere. As we usually " -"aren't able to do much about issues not related to Spyder, a forum like " -"`Stack Overflow`_ or the relevant package's docs is a much better place " -"to get help or report the issue." +msgid "If the problem reoccurs in a similar or identical way with any of these methods (other than only Spyder itself), then it is almost certainly not an issue with Spyder, and would be best handled elsewhere. As we usually aren't able to do much about issues not related to Spyder, a forum like `Stack Overflow`_ or the relevant package's docs is a much better place to get help or report the issue." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:132 -msgid "" -"See the :doc:`call-for-help` section for other places to look for " -"information and assistance." +msgid "See the :doc:`call-for-help` section for other places to look for information and assistance." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:138 @@ -218,25 +146,19 @@ msgid "Debugging and patching" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:140 -msgid "" -"If you know your way around Python, you can often diagnose and even fix " -"Spyder issues yourself, since the IDE is written in the same language you" -" use in it. You can explore the error messages you're receiving and " -"Spyder's inner workings with the :guilabel:`Internal Console`, available " -"under the menu item :menuselection:`View --> Panes --> Internal Console`." +msgid "If you know your way around Python, you can often diagnose and even fix Spyder issues yourself, since the IDE is written in the same language you use in it. You can explore the error messages you're receiving and Spyder's inner workings with the :guilabel:`Internal Console`, available under the menu item :menuselection:`View --> Panes --> Internal Console`." +msgstr "" + +#: ../../troubleshooting/basic-first-aid.rst:143 +msgid "Spyder showing Internal console" msgstr "" #: ../../troubleshooting/basic-first-aid.rst:146 -msgid "" -"For more detailed debug output, start Spyder from the command line " -"(Anaconda Prompt on Windows) with ``spyder --debug-info verbose``." +msgid "For more detailed debug output, start Spyder from the command line (Anaconda Prompt on Windows) with ``spyder --debug-info verbose``." msgstr "" #: ../../troubleshooting/basic-first-aid.rst:148 -msgid "" -"Even if you don't manage to fix the problem yourself, this output can be " -"very helpful in aiding us to quickly narrow down and solve your issue for" -" you." +msgid "Even if you don't manage to fix the problem yourself, this output can be very helpful in aiding us to quickly narrow down and solve your issue for you." msgstr "" #: ../../troubleshooting/call-for-help.rst:3 @@ -244,12 +166,7 @@ msgid "Calling for Help" msgstr "" #: ../../troubleshooting/call-for-help.rst:5 -msgid "" -"Aside from this troubleshooting guide, there are a number of other " -"sources of documentation and troubleshooting information you can check " -"before submitting an issue, as they might already offer an answer, or at " -"least help you better understand the problem. Even if we aren't able to " -"help you, these places might." +msgid "Aside from this troubleshooting guide, there are a number of other sources of documentation and troubleshooting information you can check before submitting an issue, as they might already offer an answer, or at least help you better understand the problem. Even if we aren't able to help you, these places might." msgstr "" #: ../../troubleshooting/call-for-help.rst:14 @@ -261,9 +178,7 @@ msgid "Spyder's FAQ section" msgstr "" #: ../../troubleshooting/call-for-help.rst:21 -msgid "" -"Spyder's documentation has a FAQ section, where you might find the " -"answers that you are looking for." +msgid "Spyder's documentation has a FAQ section, where you might find the answers that you are looking for." msgstr "" #: ../../troubleshooting/call-for-help.rst:27 @@ -271,10 +186,7 @@ msgid "Spyder's YouTube channel" msgstr "" #: ../../troubleshooting/call-for-help.rst:29 -msgid "" -"Our `YouTube channel`_ contains helpful videos that will guide you " -"through many of Spyder's features, and provide a starting point for newer" -" users." +msgid "Our `YouTube channel`_ contains helpful videos that will guide you through many of Spyder's features, and provide a starting point for newer users." msgstr "" #: ../../troubleshooting/call-for-help.rst:37 @@ -282,10 +194,7 @@ msgid "Spyder Gitter" msgstr "" #: ../../troubleshooting/call-for-help.rst:39 -msgid "" -"We have a public `Gitter room`_ where you can chat directly with the " -"Spyder developers. If you've got a quick question to ask the team and are" -" looking for a quick answer, this is a great place to go." +msgid "We have a public `Gitter room`_ where you can chat directly with the Spyder developers. If you've got a quick question to ask the team and are looking for a quick answer, this is a great place to go." msgstr "" #: ../../troubleshooting/call-for-help.rst:48 @@ -293,9 +202,7 @@ msgid "Spyder Google Group" msgstr "" #: ../../troubleshooting/call-for-help.rst:50 -msgid "" -"Our `Google Group`_ is great for help-related questions, particularly " -"those you aren't sure are a full-on Spyder issue." +msgid "Our `Google Group`_ is great for help-related questions, particularly those you aren't sure are a full-on Spyder issue." msgstr "" #: ../../troubleshooting/call-for-help.rst:58 @@ -303,9 +210,7 @@ msgid "Spyder website" msgstr "" #: ../../troubleshooting/call-for-help.rst:60 -msgid "" -"The `Spyder site`_ contains basic information about the IDE and links to " -"many other helpful resources." +msgid "The `Spyder site`_ contains basic information about the IDE and links to many other helpful resources." msgstr "" #: ../../troubleshooting/call-for-help.rst:68 @@ -313,13 +218,7 @@ msgid "Stack Overflow tag" msgstr "" #: ../../troubleshooting/call-for-help.rst:70 -msgid "" -"`Stack Overflow`_ is a great place to start searching and posting, " -"particularly if your question is more programming-related, or has to do " -"with something specific to your own code. It has an vibrant Spyder " -"community as well, with new questions posted every day, and the " -"developers (especially Carlos Cordoba, the lead maintainer) are active in" -" answering them." +msgid "`Stack Overflow`_ is a great place to start searching and posting, particularly if your question is more programming-related, or has to do with something specific to your own code. It has an vibrant Spyder community as well, with new questions posted every day, and the developers (especially Carlos Cordoba, the lead maintainer) are active in answering them." msgstr "" #: ../../troubleshooting/call-for-help.rst:79 @@ -327,11 +226,7 @@ msgid "OpenTeams support" msgstr "" #: ../../troubleshooting/call-for-help.rst:81 -msgid "" -"On `OpenTeams`_, you can get help from expert Spyder consultants. " -"OpenTeams offers services from Spyder experts ranging from a brief " -"consultation to an experienced team to help you with a large scale " -"implementation project." +msgid "On `OpenTeams`_, you can get help from expert Spyder consultants. OpenTeams offers services from Spyder experts ranging from a brief consultation to an experienced team to help you with a large scale implementation project." msgstr "" #: ../../troubleshooting/call-for-help.rst:91 @@ -343,10 +238,7 @@ msgid "Official Python help page" msgstr "" #: ../../troubleshooting/call-for-help.rst:98 -msgid "" -"The `Python help page`_ is a great resource that lists a number of places" -" you can get assistance, support and learning resources for the language " -"and its packages." +msgid "The `Python help page`_ is a great resource that lists a number of places you can get assistance, support and learning resources for the language and its packages." msgstr "" #: ../../troubleshooting/call-for-help.rst:106 @@ -354,10 +246,7 @@ msgid "Python documentation" msgstr "" #: ../../troubleshooting/call-for-help.rst:108 -msgid "" -"The `Python docs`_ can help you understand a number of issues that can be" -" caused by quirks in the language itself, or misunderstandings as to how " -"it behaves." +msgid "The `Python docs`_ can help you understand a number of issues that can be caused by quirks in the language itself, or misunderstandings as to how it behaves." msgstr "" #: ../../troubleshooting/call-for-help.rst:116 @@ -365,10 +254,7 @@ msgid "Python subreddits" msgstr "" #: ../../troubleshooting/call-for-help.rst:118 -msgid "" -"`r/python`_ and `r/learnpython`_ are resources you can use to ask about " -"and discuss issues with Python and its packages. The former is aimed more" -" at general Python usage, and the latter more specifically at beginners." +msgid "`r/python`_ and `r/learnpython`_ are resources you can use to ask about and discuss issues with Python and its packages. The former is aimed more at general Python usage, and the latter more specifically at beginners." msgstr "" #: ../../troubleshooting/call-for-help.rst:130 @@ -380,11 +266,7 @@ msgid "Anaconda help" msgstr "" #: ../../troubleshooting/call-for-help.rst:138 -msgid "" -"The `Anaconda docs`_ site offers free community help and documentation " -"for the Anaconda applications, installing the Anaconda distribution, and " -"using the Conda package and environment manager; along with paid support " -"options." +msgid "The `Anaconda docs`_ site offers free community help and documentation for the Anaconda applications, installing the Anaconda distribution, and using the Conda package and environment manager; along with paid support options." msgstr "" #: ../../troubleshooting/call-for-help.rst:145 @@ -392,11 +274,7 @@ msgid "SciPy.org website" msgstr "" #: ../../troubleshooting/call-for-help.rst:147 -msgid "" -"The `Scipy website`_ is the the central home of the SciPy stack, with " -"information, documentation, help, and bug tracking for many of the core " -"packages used with Spyder, including NumPy, SciPy, Matplotlib, Pandas, " -"Sympy and IPython." +msgid "The `Scipy website`_ is the the central home of the SciPy stack, with information, documentation, help, and bug tracking for many of the core packages used with Spyder, including NumPy, SciPy, Matplotlib, Pandas, Sympy and IPython." msgstr "" #: ../../troubleshooting/call-for-help.rst:155 @@ -404,9 +282,7 @@ msgid "Project Jupyter" msgstr "" #: ../../troubleshooting/call-for-help.rst:157 -msgid "" -"`Jupyter`_ is the development hub for IPython, Spyder's QtConsole, " -"Jupyter notebooks used with the `Spyder-Notebook`_ plugin, and more." +msgid "`Jupyter`_ is the development hub for IPython, Spyder's QtConsole, Jupyter notebooks used with the `Spyder-Notebook`_ plugin, and more." msgstr "" #: ../../troubleshooting/call-for-help.rst:166 @@ -414,9 +290,7 @@ msgid "Data Science Stack Exchange" msgstr "" #: ../../troubleshooting/call-for-help.rst:168 -msgid "" -"The `Data Science`_ site in Stack Exchange can be very useful for " -"questions that relate more to data science than programming specifically." +msgid "The `Data Science`_ site in Stack Exchange can be very useful for questions that relate more to data science than programming specifically." msgstr "" #: ../../troubleshooting/common-illnesses.rst:3 @@ -424,9 +298,7 @@ msgid "Common Illnesses" msgstr "" #: ../../troubleshooting/common-illnesses.rst:5 -msgid "" -"Beyond the general troubleshooting steps, some frequently-reported " -"problems require more specialized solutions." +msgid "Beyond the general troubleshooting steps, some frequently-reported problems require more specialized solutions." msgstr "" #: ../../troubleshooting/common-illnesses.rst:13 @@ -434,12 +306,7 @@ msgid "Errors starting the kernel" msgstr "" #: ../../troubleshooting/common-illnesses.rst:15 -msgid "" -"If you receive the message ``An error occurred while starting the " -"kernel`` in the :doc:`/panes/ipythonconsole`, Spyder was unable to launch" -" a new Python interpreter in the current working environment to run your " -"code. There are a number of problems that can cause this, but most can be" -" fixed fairly quickly with a few easy steps." +msgid "If you receive the message ``An error occurred while starting the kernel`` in the :doc:`/panes/ipythonconsole`, Spyder was unable to launch a new Python interpreter in the current working environment to run your code. There are a number of problems that can cause this, but most can be fixed fairly quickly with a few easy steps." msgstr "" #: ../../troubleshooting/common-illnesses.rst:22 @@ -447,22 +314,19 @@ msgid "Spyder-Kernels not installed/incompatible" msgstr "" #: ../../troubleshooting/common-illnesses.rst:24 -msgid "" -"Spyder requires a supported version of the ``spyder-kernels`` package to " -"be present in the working environment you want to run your console in." +msgid "Spyder requires a supported version of the ``spyder-kernels`` package to be present in the working environment you want to run your console in." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:26 +msgid "Kernel version error dialog" msgstr "" #: ../../troubleshooting/common-illnesses.rst:29 -msgid "" -"It is included by default with Anaconda, but if you want to run your code" -" in another Python environment or installation, you'll need to make sure " -"it's installed and updated to the latest version." +msgid "It is included by default with Anaconda, but if you want to run your code in another Python environment or installation, you'll need to make sure it's installed and updated to the latest version." msgstr "" #: ../../troubleshooting/common-illnesses.rst:31 -msgid "" -"Check the required version of spyder-kernels for your version of Spyder " -"in the following table:" +msgid "Check the required version of spyder-kernels for your version of Spyder in the following table:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:33 @@ -574,21 +438,15 @@ msgid "2.4.3" msgstr "" #: ../../troubleshooting/common-illnesses.rst:52 -msgid "" -"To do so, activate the environment, then install ``spyder-kernels``. If " -"using Anaconda, open a terminal (Anaconda Prompt on Windows) and run:" +msgid "To do so, activate the environment, then install ``spyder-kernels``. If using Anaconda, open a terminal (Anaconda Prompt on Windows) and run:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:60 -msgid "" -"Otherwise, activate your environment by whatever means you created it, " -"and execute:" +msgid "Otherwise, activate your environment by whatever means you created it, and execute:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:66 -msgid "" -"For both of the previous commands, replace ```` with the " -"corresponding version in the table." +msgid "For both of the previous commands, replace ```` with the corresponding version in the table." msgstr "" #: ../../troubleshooting/common-illnesses.rst:70 @@ -596,12 +454,7 @@ msgid "Issue with another dependency" msgstr "" #: ../../troubleshooting/common-illnesses.rst:72 -msgid "" -"If the kernel displays a long error traceback that mentions other " -"packages like ``ipython``, ``ipykernel``, ``jupyter_client``, " -"``traitlets`` or ``pyzmq``, the problem may be an out of date or " -"incompatible version of a dependency package. To fix this, activate the " -"environment and update the key dependencies." +msgid "If the kernel displays a long error traceback that mentions other packages like ``ipython``, ``ipykernel``, ``jupyter_client``, ``traitlets`` or ``pyzmq``, the problem may be an out of date or incompatible version of a dependency package. To fix this, activate the environment and update the key dependencies." msgstr "" #: ../../troubleshooting/common-illnesses.rst:75 @@ -609,9 +462,7 @@ msgid "In an Anaconda environment:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:82 -msgid "" -"Otherwise, activate your environment by whatever means you created it, " -"and run:" +msgid "Otherwise, activate your environment by whatever means you created it, and run:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:90 @@ -619,22 +470,15 @@ msgid "AttributeError/ImportError" msgstr "" #: ../../troubleshooting/common-illnesses.rst:92 -msgid "" -"Check the last few lines of the error message, and see if its an " -"``AttributeError`` or ``ImportError``, or refers to a file you created in" -" your current working directory or your home folder " -"(:file:`C:/Users/YOUR_USERNAME` on Windows, :file:`/Users/YOUR_USERNAME` " -"on macOS, or :file:`/home/YOUR_USERNAME` on Linux)." +msgid "Check the last few lines of the error message, and see if its an ``AttributeError`` or ``ImportError``, or refers to a file you created in your current working directory or your home folder (:file:`C:/Users/YOUR_USERNAME` on Windows, :file:`/Users/YOUR_USERNAME` on macOS, or :file:`/home/YOUR_USERNAME` on Linux)." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:94 +msgid "Spyder's AtributeError dialog" msgstr "" #: ../../troubleshooting/common-illnesses.rst:97 -msgid "" -"If so, the the error is likely due to your file being named the same as a" -" Python standard library module, such as ``string.py`` or ``time.py``, " -"which overrides the built-in module that Spyder-Kernels is trying to " -"load. To fix this, simply rename your file to something other than one of" -" these names, and try restarting the kernel. To check the names of these " -"modules, see the list in the `Python standard library documentation`_." +msgid "If so, the the error is likely due to your file being named the same as a Python standard library module, such as ``string.py`` or ``time.py``, which overrides the built-in module that Spyder-Kernels is trying to load. To fix this, simply rename your file to something other than one of these names, and try restarting the kernel. To check the names of these modules, see the list in the `Python standard library documentation`_." msgstr "" #: ../../troubleshooting/common-illnesses.rst:109 @@ -642,13 +486,7 @@ msgid "Completion/help not working" msgstr "" #: ../../troubleshooting/common-illnesses.rst:111 -msgid "" -"To provide code completions, help and real-time analysis in the Editor, " -"Spyder uses the Python Language Server (PyLS), an implementation of the " -"Language Server Protocol specification used by VSCode, Atom and other " -"popular editors/IDEs. Most help and completion issues lie outside of " -"Spyder's control, and are either limitations with PyLS or the code that " -"is being introspected, but some can be worked around." +msgid "To provide code completions, help and real-time analysis in the Editor, Spyder uses the Python Language Server (PyLS), an implementation of the Language Server Protocol specification used by VSCode, Atom and other popular editors/IDEs. Most help and completion issues lie outside of Spyder's control, and are either limitations with PyLS or the code that is being introspected, but some can be worked around." msgstr "" #: ../../troubleshooting/common-illnesses.rst:116 @@ -656,15 +494,15 @@ msgid "Object missing docstring" msgstr "" #: ../../troubleshooting/common-illnesses.rst:118 -msgid "" -"If nothing is displayed in the calltip, hover hint or help pane, the " -"object you're trying to introspect may not have a docstring." +msgid "If nothing is displayed in the calltip, hover hint or help pane, the object you're trying to introspect may not have a docstring." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:120 +msgid "Docstring not found in help pane" msgstr "" #: ../../troubleshooting/common-illnesses.rst:124 -msgid "" -"In this case, the only solution is to add one in the source code of the " -"original function, method or class." +msgid "In this case, the only solution is to add one in the source code of the original function, method or class." msgstr "" #: ../../troubleshooting/common-illnesses.rst:128 @@ -672,16 +510,15 @@ msgid "Object cannot be found" msgstr "" #: ../../troubleshooting/common-illnesses.rst:130 -msgid "" -"Some objects, whether due to being written in C, Cython or another " -"language; generated dynamically at runtime; or being a method of an " -"object you create, cannot be easily found without executing the code." +msgid "Some objects, whether due to being written in C, Cython or another language; generated dynamically at runtime; or being a method of an object you create, cannot be easily found without executing the code." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:132 +msgid "Object not found in help pane" msgstr "" #: ../../troubleshooting/common-illnesses.rst:136 -msgid "" -"However, once you run your code in the :doc:`/panes/ipythonconsole`, you " -"might be able to get help and completions on the object there." +msgid "However, once you run your code in the :doc:`/panes/ipythonconsole`, you might be able to get help and completions on the object there." msgstr "" #: ../../troubleshooting/common-illnesses.rst:140 @@ -689,12 +526,11 @@ msgid "LSP has stopped working" msgstr "" #: ../../troubleshooting/common-illnesses.rst:142 -msgid "" -"Occasionally, especially after using Spyder for a while, code completion," -" help and analysis may stop working. If this is the case, you can check " -"LSP status with the :guilabel:`LSP Python` item in Spyder's status bar at" -" the bottom of the screen, and restart it by right-clicking it and " -"selecting the :guilabel:`Restart Python Language Server` item." +msgid "Occasionally, especially after using Spyder for a while, code completion, help and analysis may stop working. If this is the case, you can check LSP status with the :guilabel:`LSP Python` item in Spyder's status bar at the bottom of the screen, and restart it by right-clicking it and selecting the :guilabel:`Restart Python Language Server` item." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:145 +msgid "Spyder with LSP restart dialog" msgstr "" #: ../../troubleshooting/common-illnesses.rst:150 @@ -702,17 +538,11 @@ msgid "Spyder bug/dependency issue" msgstr "" #: ../../troubleshooting/common-illnesses.rst:152 -msgid "" -"Given the variety of dependencies involved in making LSP work, an " -"incompatible or out of date version in your environment can result in " -"error messages, incomplete results, or help/analysis not working at all." +msgid "Given the variety of dependencies involved in making LSP work, an incompatible or out of date version in your environment can result in error messages, incomplete results, or help/analysis not working at all." msgstr "" #: ../../troubleshooting/common-illnesses.rst:154 -msgid "" -"To address this, first try updating Anaconda and Spyder as described in " -":doc:`basic-first-aid`. If the issue still isn't resolved, update the " -"various relevant dependencies with:" +msgid "To address this, first try updating Anaconda and Spyder as described in :doc:`basic-first-aid`. If the issue still isn't resolved, update the various relevant dependencies with:" msgstr "" #: ../../troubleshooting/common-illnesses.rst:165 @@ -724,29 +554,19 @@ msgid "Plugin does not work at all" msgstr "" #: ../../troubleshooting/common-illnesses.rst:170 -msgid "" -"If you have installed a Spyder plugin, but you can't see it, go to the " -":guilabel:`Panes` submenu of the :guilabel:`View` menu and select the " -"plugin's name, which should make its pane visible. If you don't see the " -"plugin there, select the :guilabel:`Dependencies` item under the " -":guilabel:`Help` menu and see if the plugin appears at the bottom." +msgid "If you have installed a Spyder plugin, but you can't see it, go to the :guilabel:`Panes` submenu of the :guilabel:`View` menu and select the plugin's name, which should make its pane visible. If you don't see the plugin there, select the :guilabel:`Dependencies` item under the :guilabel:`Help` menu and see if the plugin appears at the bottom." +msgstr "" + +#: ../../troubleshooting/common-illnesses.rst:173 +msgid "Dependencies dialog showing Unittest plugin" msgstr "" #: ../../troubleshooting/common-illnesses.rst:176 -msgid "" -"If the plugin with the problem is not listed in the dependencies dialog, " -"check that you installed it in the same environment as Spyder. If you " -"have, then the problem may well be caused by a dependency issue. Test " -"whether you can import the plug-in manually by opening a Python console " -"in the same environment as Spyder and typing, for instance, ``import " -"spyder_unittest`` to test the Spyder-Unittest` plug-in; this command " -"should run without errors." +msgid "If the plugin with the problem is not listed in the dependencies dialog, check that you installed it in the same environment as Spyder. If you have, then the problem may well be caused by a dependency issue. Test whether you can import the plug-in manually by opening a Python console in the same environment as Spyder and typing, for instance, ``import spyder_unittest`` to test the Spyder-Unittest` plug-in; this command should run without errors." msgstr "" #: ../../troubleshooting/common-illnesses.rst:180 -msgid "" -"If none of this helps you to resolve the problem, then continue to the " -"next section." +msgid "If none of this helps you to resolve the problem, then continue to the next section." msgstr "" #: ../../troubleshooting/common-illnesses.rst:184 @@ -754,25 +574,15 @@ msgid "Other issues" msgstr "" #: ../../troubleshooting/common-illnesses.rst:186 -msgid "" -"If you get an error which mentions or involves a Spyder plugin, such as " -"``spyder-unittest``, ``spyder-terminal`` or ``spyder-notebook``, or if " -"you encounter any other problem with a Spyder plugin, then the first " -"approach should be to update Spyder and the plugin to their latest " -"versions." +msgid "If you get an error which mentions or involves a Spyder plugin, such as ``spyder-unittest``, ``spyder-terminal`` or ``spyder-notebook``, or if you encounter any other problem with a Spyder plugin, then the first approach should be to update Spyder and the plugin to their latest versions." msgstr "" #: ../../troubleshooting/common-illnesses.rst:188 -msgid "" -"If this doesn't fix the problem, you should check the plugin's website or" -" repository to see if it is compatible with your version of Spyder." +msgid "If this doesn't fix the problem, you should check the plugin's website or repository to see if it is compatible with your version of Spyder." msgstr "" #: ../../troubleshooting/common-illnesses.rst:190 -msgid "" -"Finally, if compatibility doesn't seem to be the problem, please check " -"those repositories to see if an issue was already opened, and report it " -"there if not." +msgid "Finally, if compatibility doesn't seem to be the problem, please check those repositories to see if an issue was already opened, and report it there if not." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:3 @@ -780,9 +590,7 @@ msgid "Emergency CPR" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:5 -msgid "" -"Is Spyder not launching at all? The steps on this section should " -"hopefully get it back up and running in no time." +msgid "Is Spyder not launching at all? The steps on this section should hopefully get it back up and running in no time." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:12 @@ -790,48 +598,31 @@ msgid "Common solutions" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:14 -msgid "" -"Try :doc:`basic-first-aid` first, which usually resolves most Spyder " -"install-related issues." +msgid "Try :doc:`basic-first-aid` first, which usually resolves most Spyder install-related issues." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:16 -msgid "" -"**Make sure Spyder isn't already running** and no Spyder related windows " -"(*e.g.* :doc:`/panes/variableexplorer` dialogs) are left open, and check " -"that the preference setting :menuselection:`Application --> Advanced " -"Settings --> Use a single instance` isn't checked." +msgid "**Make sure Spyder isn't already running** and no Spyder related windows (*e.g.* :doc:`/panes/variableexplorer` dialogs) are left open, and check that the preference setting :menuselection:`Application --> Advanced Settings --> Use a single instance` isn't checked." +msgstr "" + +#: ../../troubleshooting/emergency-cpr.rst:18 +msgid "Spyder showing Use a single instance setting" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:21 -msgid "" -"Try **starting Spyder via a different means**, such as from a shortcut, " -"Anaconda navigator, or your command line (or Anaconda Prompt on Windows) " -"by simply typing ``spyder`` then :kbd:`Enter`/:kbd:`Return`, and see if " -"any of those work. If so, then something's wrong with your install, not " -"Spyder itself, and so we recommend following :ref:`troubleshooting-" -"reinstalling-spyder-ref` to uninstall and reinstall Anaconda." +msgid "Try **starting Spyder via a different means**, such as from a shortcut, Anaconda navigator, or your command line (or Anaconda Prompt on Windows) by simply typing ``spyder`` then :kbd:`Enter`/:kbd:`Return`, and see if any of those work. If so, then something's wrong with your install, not Spyder itself, and so we recommend following :ref:`troubleshooting-reinstalling-spyder-ref` to uninstall and reinstall Anaconda." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:24 -msgid "" -"**Disable any security software** you may be using, such as a firewall or" -" antivirus, as these products can occasionally interfere with Spyder or " -"its related packages. Make sure to re-enable it if it doesn't fix the " -"problem, and if it does, add a rule or exception for Spyder or Python." +msgid "**Disable any security software** you may be using, such as a firewall or antivirus, as these products can occasionally interfere with Spyder or its related packages. Make sure to re-enable it if it doesn't fix the problem, and if it does, add a rule or exception for Spyder or Python." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:27 -msgid "" -"If it is currently installed \"for just you\", **try uninstalling and " -"reinstalling Anaconda \"for all users\" instead**, and vice versa, as " -"some systems can have issues with one or the other installation method." +msgid "If it is currently installed \"for just you\", **try uninstalling and reinstalling Anaconda \"for all users\" instead**, and vice versa, as some systems can have issues with one or the other installation method." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:29 -msgid "" -"**Check and repair/reset permissions**, your disk, and OS if all else " -"fails." +msgid "**Check and repair/reset permissions**, your disk, and OS if all else fails." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:35 @@ -839,18 +630,11 @@ msgid "Advanced tricks" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:37 -msgid "" -"If none of the above solves the problem, you can try starting Spyder " -"directly from its Python source files which may either get it running, or" -" at least provide useful information to help debug the issue further." +msgid "If none of the above solves the problem, you can try starting Spyder directly from its Python source files which may either get it running, or at least provide useful information to help debug the issue further." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:39 -msgid "" -"This technique consists of starting Spyder from your terminal (or " -"Anaconda Prompt on Windows) by manually running the Spyder startup " -"routine ( :guilabel:`start.py` ) with a known good Python interpreter, " -"and observing the results." +msgid "This technique consists of starting Spyder from your terminal (or Anaconda Prompt on Windows) by manually running the Spyder startup routine ( :guilabel:`start.py` ) with a known good Python interpreter, and observing the results." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:41 @@ -858,9 +642,7 @@ msgid "To do so, you'll need to:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:43 -msgid "" -"Find the path to the Spyder :file:`app` directory from the command line. " -"For this, run:" +msgid "Find the path to the Spyder :file:`app` directory from the command line. For this, run:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:50 @@ -868,23 +650,19 @@ msgid "Go to the output path of the above command on your command line:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:56 -msgid "" -"Once inside the :file:`app` directory, run ``python start.py`` to launch " -"Spyder." +msgid "Once inside the :file:`app` directory, run ``python start.py`` to launch Spyder." +msgstr "" + +#: ../../troubleshooting/emergency-cpr.rst:58 +msgid "Command line showing python start to launch Spyder" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:62 -msgid "" -"#. If it doesn't start successfully, then you should see an error " -"traceback printed; carefully copy that for future reference. Also run " -"``python mainwindow.py``, and record your results as well." +msgid "#. If it doesn't start successfully, then you should see an error traceback printed; carefully copy that for future reference. Also run ``python mainwindow.py``, and record your results as well." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:65 -msgid "" -"(*Windows only*) In case the command window disappears immediately after " -"the error, create a ``.bat`` file in the :file:`app` directory with the " -"following content:" +msgid "(*Windows only*) In case the command window disappears immediately after the error, create a ``.bat`` file in the :file:`app` directory with the following content:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:73 @@ -892,115 +670,71 @@ msgid "Replace ```` with the output of:" msgstr "" #: ../../troubleshooting/emergency-cpr.rst:79 -msgid "" -"Then, double click the batch file to run it, and you should see the error" -" information you need." +msgid "Then, double click the batch file to run it, and you should see the error information you need." msgstr "" #: ../../troubleshooting/emergency-cpr.rst:81 -msgid "" -"If reading the output (particularly the last line) doesn't help you solve" -" the problem, then record all of it carefully, and post it as part of " -"your bug report as described under the :doc:`submit-a-report` section." +msgid "If reading the output (particularly the last line) doesn't help you solve the problem, then record all of it carefully, and post it as part of your bug report as described under the :doc:`submit-a-report` section." msgstr "" -#: ../../troubleshooting/first-steps.rst:3 +#: ../../troubleshooting/first-steps.rst:6 msgid "First Steps" msgstr "" -#: ../../troubleshooting/first-steps.rst:5 -msgid "" -"If Spyder crashes or you receive an error message, please read the " -"following troubleshooting steps before opening a new issue. There's a " -"good chance that someone else has already experienced the same problem, " -"so checking for an existing solution will likely get Spyder working again" -" for you as quickly as possible." +#: ../../troubleshooting/first-steps.rst:8 +msgid "If Spyder crashes or you receive an error message, please read the following troubleshooting steps before opening a new issue. There's a good chance that someone else has already experienced the same problem, so checking for an existing solution will likely get Spyder working again for you as quickly as possible." msgstr "" -#: ../../troubleshooting/first-steps.rst:9 -msgid "" -"To make sure you're getting the most relevant help for your problem, " -"please make sure the issue is actually related to Spyder:" +#: ../../troubleshooting/first-steps.rst:12 +msgid "To make sure you're getting the most relevant help for your problem, please make sure the issue is actually related to Spyder:" msgstr "" -#: ../../troubleshooting/first-steps.rst:11 -msgid "" -"If the problem appears to be a result of *your own code*, `Stack " -"Overflow`_ is a better place to start." +#: ../../troubleshooting/first-steps.rst:14 +msgid "If the problem appears to be a result of *your own code*, `Stack Overflow`_ is a better place to start." msgstr "" -#: ../../troubleshooting/first-steps.rst:12 -msgid "" -"If the bug also occurs in the *standard Python, IPython, or QtConsole* " -"environments, or only with *a specific package*, it is unlikely to be " -"something in Spyder, and you should report it to those sources instead." +#: ../../troubleshooting/first-steps.rst:15 +msgid "If the bug also occurs in the *standard Python, IPython, or QtConsole* environments, or only with *a specific package*, it is unlikely to be something in Spyder, and you should report it to those sources instead." msgstr "" -#: ../../troubleshooting/first-steps.rst:13 -msgid "" -"If the problem lies with *your specific install*, uninstalling and clean-" -"reinstalling the `Anaconda`_ distribution is strongly recommended. As the" -" other methods of installing Spyder can result in tricky user-specific " -"problems, we generally aren't able to give individual support for install" -" issues." +#: ../../troubleshooting/first-steps.rst:16 +msgid "If the problem lies with *your specific install*, uninstalling and clean-reinstalling the `Anaconda`_ distribution is strongly recommended. As the other methods of installing Spyder can result in tricky user-specific problems, we generally aren't able to give individual support for install issues." msgstr "" -#: ../../troubleshooting/first-steps.rst:19 -msgid "" -"Just like the programs you code in it, Spyder is written in Python, so " -"you can often figure out many problems just by reading the last line of " -"the traceback or error message. To view it, simply click :guilabel:`Show " -"details` in the Spyder error dialog." +#: ../../troubleshooting/first-steps.rst:22 +msgid "Just like the programs you code in it, Spyder is written in Python, so you can often figure out many problems just by reading the last line of the traceback or error message. To view it, simply click :guilabel:`Show details` in the Spyder error dialog." msgstr "" -#: ../../troubleshooting/first-steps.rst:25 -msgid "" -"Often, that alone will tell you how to fix the problem on your own, but " -"if not, we're here to help." +#: ../../troubleshooting/first-steps.rst:28 +msgid "Often, that alone will tell you how to fix the problem on your own, but if not, we're here to help." msgstr "" -#: ../../troubleshooting/first-steps.rst:31 +#: ../../troubleshooting/first-steps.rst:34 msgid "Where to go from here" msgstr "" -#: ../../troubleshooting/first-steps.rst:33 -msgid "" -"If you check out our list of issue categories and problem descriptions " -"and see a question, error message or traceback that looks familiar, the " -"relevant sub-section will likely be of the most specific help solving " -"your issue as quickly as possible." +#: ../../troubleshooting/first-steps.rst:36 +msgid "If you check out our list of issue categories and problem descriptions and see a question, error message or traceback that looks familiar, the relevant sub-section will likely be of the most specific help solving your issue as quickly as possible." msgstr "" -#: ../../troubleshooting/first-steps.rst:37 -msgid "" -"As a first step to solving your issue, you can try some :doc:`basic-" -"first-aid`." +#: ../../troubleshooting/first-steps.rst:40 +msgid "As a first step to solving your issue, you can try some :doc:`basic-first-aid`." msgstr "" -#: ../../troubleshooting/first-steps.rst:41 -msgid "" -"If Spyder won't launch, check the :doc:`emergency-cpr` section and see if" -" that clears it up." +#: ../../troubleshooting/first-steps.rst:44 +msgid "If Spyder won't launch, check the :doc:`emergency-cpr` section and see if that clears it up." msgstr "" -#: ../../troubleshooting/first-steps.rst:45 -msgid "" -"If your problem is related to the kernel not starting, autocompletion or " -"a plugin go to :doc:`common-illnesses` section." +#: ../../troubleshooting/first-steps.rst:48 +msgid "If your problem is related to the kernel not starting, autocompletion or a plugin go to :doc:`common-illnesses` section." msgstr "" -#: ../../troubleshooting/first-steps.rst:49 -msgid "" -"If you still can't get it to work, and the problem is indeed Spyder-" -"related, you should consult the the :doc:`call-for-help` section for " -"other resources to explore." +#: ../../troubleshooting/first-steps.rst:52 +msgid "If you still can't get it to work, and the problem is indeed Spyder-related, you should consult the the :doc:`call-for-help` section for other resources to explore." msgstr "" -#: ../../troubleshooting/first-steps.rst:53 -msgid "" -"Finally, if you couldn't solve your problem and want to submit an issue " -"to our Github issue tracker, so the bug can hopefully be fixed for " -"everyone, :doc:`submit-a-report`." +#: ../../troubleshooting/first-steps.rst:56 +msgid "Finally, if you couldn't solve your problem and want to submit an issue to our Github issue tracker, so the bug can hopefully be fixed for everyone, :doc:`submit-a-report`." msgstr "" #: ../../troubleshooting/index.rst:3 @@ -1012,19 +746,17 @@ msgid "Submit a Report" msgstr "" #: ../../troubleshooting/submit-a-report.rst:5 -msgid "" -"If you can't fix your issue with any of the troubleshooting steps, then " -"you'll want to submit it to our issue tracker so our team can take a look" -" at it for you. You'll need a `Github account`_ to do this, so make sure " -"you have one before you begin (a good idea anyway)." +msgid "If you can't fix your issue with any of the troubleshooting steps, then you'll want to submit it to our issue tracker so our team can take a look at it for you. You'll need a `Github account`_ to do this, so make sure you have one before you begin (a good idea anyway)." +msgstr "" + +#: ../../troubleshooting/submit-a-report.rst:8 +#: ../../troubleshooting/submit-a-report.rst:32 +#: ../../troubleshooting/submit-a-report.rst:39 +msgid "Github page on Spyder's issue tracker" msgstr "" #: ../../troubleshooting/submit-a-report.rst:13 -msgid "" -"Before you submit an issue, make sure you've searched a description of " -"the problem and a relevant portion of the error traceback, on both Google" -" and Spyder's `issue tracker`_ to make sure it hasn't been submitted " -"before. If that's the case, your issue will be closed as a duplicate." +msgid "Before you submit an issue, make sure you've searched a description of the problem and a relevant portion of the error traceback, on both Google and Spyder's `issue tracker`_ to make sure it hasn't been submitted before. If that's the case, your issue will be closed as a duplicate." msgstr "" #: ../../troubleshooting/submit-a-report.rst:23 @@ -1032,44 +764,27 @@ msgid "Ways to submit an issue" msgstr "" #: ../../troubleshooting/submit-a-report.rst:25 -msgid "" -"There are several ways to submit an issue, either from Spyder or GitHub " -"directly. In order of preference and difficulty:" +msgid "There are several ways to submit an issue, either from Spyder or GitHub directly. In order of preference and difficulty:" msgstr "" #: ../../troubleshooting/submit-a-report.rst:28 -msgid "" -"**If Spyder presents an error dialog** you can submit an issue directly " -"from it. You will have to fill out a title for your issue, specify the " -"steps that lead to this problem and click :guilabel:`submit to Github`. " -"This will prefill an error report with your environment details, key " -"versions and dependencies and automatically insert the error/traceback " -"for you." +msgid "**If Spyder presents an error dialog** you can submit an issue directly from it. You will have to fill out a title for your issue, specify the steps that lead to this problem and click :guilabel:`submit to Github`. This will prefill an error report with your environment details, key versions and dependencies and automatically insert the error/traceback for you." msgstr "" #: ../../troubleshooting/submit-a-report.rst:36 -msgid "" -"**If Spyder opens and your issue does not involve an error dialog**, the " -"best way to do so is to simply select :guilabel:`Report issue` from the " -":guilabel:`Help` menu, which manually brings up the issue report form and" -" fills in the key information about your Spyder installation. Describe " -"the issue you're experiencing (including any error/traceback information)" -" along with a descriptive title, and click :guilabel:`Submit to Github`." +msgid "**If Spyder opens and your issue does not involve an error dialog**, the best way to do so is to simply select :guilabel:`Report issue` from the :guilabel:`Help` menu, which manually brings up the issue report form and fills in the key information about your Spyder installation. Describe the issue you're experiencing (including any error/traceback information) along with a descriptive title, and click :guilabel:`Submit to Github`." msgstr "" #: ../../troubleshooting/submit-a-report.rst:42 -msgid "" -"**If Spyder won't launch**, you can submit a report manually at our " -"issues page on `Github`_. Unlike the above, you'll need to manually " -"provide the versions of everything (Spyder, Python, OS, Qt/PyQt, " -"Anaconda, and Spyder's dependencies) as listed in the error report " -"template; see below for more on that." +msgid "**If Spyder won't launch**, you can submit a report manually at our issues page on `Github`_. Unlike the above, you'll need to manually provide the versions of everything (Spyder, Python, OS, Qt/PyQt, Anaconda, and Spyder's dependencies) as listed in the error report template; see below for more on that." +msgstr "" + +#: ../../troubleshooting/submit-a-report.rst:45 +msgid "Github page on Spyder's issue template" msgstr "" #: ../../troubleshooting/submit-a-report.rst:50 -msgid "" -"Once you submit your report, our team will try to get back to you as soon" -" as possible, often within 24 hours or less, to try to help you fix it." +msgid "Once you submit your report, our team will try to get back to you as soon as possible, often within 24 hours or less, to try to help you fix it." msgstr "" #: ../../troubleshooting/submit-a-report.rst:55 @@ -1077,10 +792,7 @@ msgid "What to include in your report" msgstr "" #: ../../troubleshooting/submit-a-report.rst:57 -msgid "" -"**Please include as much as possible of the following in your report** to" -" maximize your chances of getting relevant help and our ability to " -"diagnose, reproduce and solve your issue." +msgid "**Please include as much as possible of the following in your report** to maximize your chances of getting relevant help and our ability to diagnose, reproduce and solve your issue." msgstr "" #: ../../troubleshooting/submit-a-report.rst:59 @@ -1088,105 +800,69 @@ msgid "The key items, in order of priority:" msgstr "" #: ../../troubleshooting/submit-a-report.rst:61 -msgid "" -"The full, **complete error message or traceback** copy/pasted or " -"automatically entered exactly as displayed by Spyder:" +msgid "The full, **complete error message or traceback** copy/pasted or automatically entered exactly as displayed by Spyder:" msgstr "" #: ../../troubleshooting/submit-a-report.rst:63 -msgid "" -"Auto-generated reports directly from the error dialog should include this" -" automatically, but double check to make sure." +msgid "Auto-generated reports directly from the error dialog should include this automatically, but double check to make sure." msgstr "" #: ../../troubleshooting/submit-a-report.rst:64 -msgid "" -"You can copy and paste this from the the :guilabel:`Show Details` section" -" of the error dialog." +msgid "You can copy and paste this from the the :guilabel:`Show Details` section of the error dialog." msgstr "" #: ../../troubleshooting/submit-a-report.rst:65 -msgid "" -"If not present, or a dialog is not displayed, you can also find it " -"printed to Spyder's :guilabel:`Internal Console`, located under the " -":guilabel:`View` menu at :menuselection:`Panes --> Internal Console`." +msgid "If not present, or a dialog is not displayed, you can also find it printed to Spyder's :guilabel:`Internal Console`, located under the :guilabel:`View` menu at :menuselection:`Panes --> Internal Console`." msgstr "" #: ../../troubleshooting/submit-a-report.rst:66 -msgid "" -"If you prefer, or if Spyder won't start, you can start Spyder from your " -"command line (or Anaconda prompt on windows) with ``spyder`` and copy the" -" output printed there." +msgid "If you prefer, or if Spyder won't start, you can start Spyder from your command line (or Anaconda prompt on windows) with ``spyder`` and copy the output printed there." msgstr "" #: ../../troubleshooting/submit-a-report.rst:70 -msgid "" -"If you are reporting a specific behavior rather than an error, or the " -"message does not fully explain what occurs, please describe in detail " -"what actually happened, and what you expected Spyder to do." +msgid "If you are reporting a specific behavior rather than an error, or the message does not fully explain what occurs, please describe in detail what actually happened, and what you expected Spyder to do." msgstr "" #: ../../troubleshooting/submit-a-report.rst:72 -msgid "" -"A **detailed, step by step description of exactly what you did** leading " -"up to the error occurring, complete with sample code that triggers it, if" -" applicable." +msgid "A **detailed, step by step description of exactly what you did** leading up to the error occurring, complete with sample code that triggers it, if applicable." msgstr "" #: ../../troubleshooting/submit-a-report.rst:74 -msgid "" -"**Information about Spyder and its environment** as listed in the error " -"report template, which you can find under :guilabel:`About Spyder` in the" -" :guilabel:`Help` menu; along with its key dependencies, shown in the " -"dialog under :menuselection:`Help --> Dependencies` (there's a button to " -"copy-paste them)." +msgid "**Information about Spyder and its environment** as listed in the error report template, which you can find under :guilabel:`About Spyder` in the :guilabel:`Help` menu; along with its key dependencies, shown in the dialog under :menuselection:`Help --> Dependencies` (there's a button to copy-paste them)." +msgstr "" + +#: ../../troubleshooting/submit-a-report.rst:76 +msgid "Spyder showing Spyder's info and dependencies" msgstr "" #: ../../troubleshooting/submit-a-report.rst:79 -msgid "" -"If Spyder won't launch, paste the output of ``conda list`` from your " -"command line (or Anaconda prompt on Windows) in the " -":guilabel:`Dependencies` section of the issue template." +msgid "If Spyder won't launch, paste the output of ``conda list`` from your command line (or Anaconda prompt on Windows) in the :guilabel:`Dependencies` section of the issue template." +msgstr "" + +#: ../../troubleshooting/submit-a-report.rst:81 +msgid "Command line showing output of conda list" msgstr "" #: ../../troubleshooting/submit-a-report.rst:85 -msgid "" -"**How you installed Spyder** and any other relevant packages, *e.g.* " -"Anaconda, MacPorts or pip and **whether Spyder has worked before** since " -"you installed it." +msgid "**How you installed Spyder** and any other relevant packages, *e.g.* Anaconda, MacPorts or pip and **whether Spyder has worked before** since you installed it." msgstr "" #: ../../troubleshooting/submit-a-report.rst:87 -msgid "" -"**What else you've tried to fix it**, *e.g.* from this guide or elsewhere" -" on the web, and if you've **tried to reproduce it in standalone " -"QtConsole, IPython, and/or the plain Python** interpreter." +msgid "**What else you've tried to fix it**, *e.g.* from this guide or elsewhere on the web, and if you've **tried to reproduce it in standalone QtConsole, IPython, and/or the plain Python** interpreter." msgstr "" #: ../../troubleshooting/submit-a-report.rst:89 -msgid "" -"**Whether the problem occurred consistently before** in similar " -"situations or if this is the first time you've observed it." +msgid "**Whether the problem occurred consistently before** in similar situations or if this is the first time you've observed it." msgstr "" #: ../../troubleshooting/submit-a-report.rst:91 -msgid "" -"**Anything else special or unusual** about your system, environment, " -"packages, or specific usage that might have anything to do with the " -"problem" +msgid "**Anything else special or unusual** about your system, environment, packages, or specific usage that might have anything to do with the problem" msgstr "" #: ../../troubleshooting/submit-a-report.rst:95 -msgid "" -"If including block(s) of code in your report, be sure to precede and " -"follow it with a line of three backticks \\`\\`\\` to get a code block " -"like this:" +msgid "If including block(s) of code in your report, be sure to precede and follow it with a line of three backticks \\`\\`\\` to get a code block like this:" msgstr "" #: ../../troubleshooting/submit-a-report.rst:101 -msgid "" -"Otherwise, your code will likely contain random formatting or missing " -"indentation, making it difficult to examine and run it to reproduce and " -"fix your issue." +msgid "Otherwise, your code will likely contain random formatting or missing indentation, making it difficult to examine and run it to reproduce and fix your issue." msgstr "" - diff --git a/doc/locales/pot/videos.pot b/doc/locales/pot/videos.pot index ce258414..163c7ef6 100644 --- a/doc/locales/pot/videos.pot +++ b/doc/locales/pot/videos.pot @@ -1,19 +1,19 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../videos/first-steps-with-spyder.rst:3 @@ -21,11 +21,7 @@ msgid "First Steps with Spyder" msgstr "" #: ../../videos/first-steps-with-spyder.rst:5 -msgid "" -"The videos in this section provide a starting point for new users who " -"have never opened Spyder before. You'll get familiar with opening Spyder " -"in different ways, working with the four main panes and customizing the " -"Spyder to your heart's content." +msgid "The videos in this section provide a starting point for new users who have never opened Spyder before. You'll get familiar with opening Spyder in different ways, working with the four main panes and customizing the Spyder to your heart's content." msgstr "" #: ../../videos/first-steps-with-spyder.rst:12 @@ -33,9 +29,7 @@ msgid "Getting started" msgstr "" #: ../../videos/first-steps-with-spyder.rst:14 -msgid "" -"Discover the basics of using the Spyder interface and get an introduction" -" to its four main panes, along with a quick look at the others." +msgid "Discover the basics of using the Spyder interface and get an introduction to its four main panes, along with a quick look at the others." msgstr "" #: ../../videos/first-steps-with-spyder.rst:16 @@ -54,76 +48,41 @@ msgstr "" msgid "Explore the other default panes" msgstr "" +#: ../../videos/first-steps-with-spyder.rst:0 +#: ../../videos/working-with-spyder.rst:0 +msgid "Transcript" +msgstr "" + #: ../../videos/first-steps-with-spyder.rst:33 -msgid "" -"Hello everyone! I'm Juanita, and in this video I'm going to show you how " -"to open Spyder and go over the basics of Spyder's interface. We will " -"learn about Spyder's four panes that you'll likely be using most often, " -"as well as briefly explore the others that are open by default. If you " -"don't have Spyder installed and would like to follow along, you can " -"`download it here`_." +msgid "Hello everyone! I'm Juanita, and in this video I'm going to show you how to open Spyder and go over the basics of Spyder's interface. We will learn about Spyder's four panes that you'll likely be using most often, as well as briefly explore the others that are open by default. If you don't have Spyder installed and would like to follow along, you can `download it here`_." msgstr "" #: ../../videos/first-steps-with-spyder.rst:37 -msgid "" -"The easiest way to open Spyder is by opening Anaconda Navigator and " -"clicking on the Spyder application. In case you have an older version of " -"Spyder in Anaconda, open the command line (or the Anaconda Prompt in the " -"case of Windows) and type the commands:" +msgid "The easiest way to open Spyder is by opening Anaconda Navigator and clicking on the Spyder application. In case you have an older version of Spyder in Anaconda, open the command line (or the Anaconda Prompt in the case of Windows) and type the commands:" msgstr "" #: ../../videos/first-steps-with-spyder.rst:44 -msgid "" -"To launch Spyder without opening Navigator, open your command line and " -"type ``spyder``. If you followed the :doc:`/installation`, you should " -"have everything necessary to open Spyder 4." +msgid "To launch Spyder without opening Navigator, open your command line and type ``spyder``. If you followed the :doc:`/installation`, you should have everything necessary to open Spyder 4." msgstr "" #: ../../videos/first-steps-with-spyder.rst:46 -msgid "" -"This is what Spyder 4 looks like in its default configuration, though you" -" can thoroughly customize it, which we'll get to in a later tutorial. You" -" can see that it is divided into three sections showing three different " -"panes: the Editor, the IPython Console and the Help viewer. These three, " -"along with the Variable Explorer, are the four core panes you'll work " -"with the most in Spyder." +msgid "This is what Spyder 4 looks like in its default configuration, though you can thoroughly customize it, which we'll get to in a later tutorial. You can see that it is divided into three sections showing three different panes: the Editor, the IPython Console and the Help viewer. These three, along with the Variable Explorer, are the four core panes you'll work with the most in Spyder." msgstr "" #: ../../videos/first-steps-with-spyder.rst:48 -msgid "" -"On the left we have the Editor, where you can open, edit and run files. " -"Bottom right is the IPython Console, which you can use both interactively" -" and to run your code in the Editor. It shows you which version of Python" -" you are using. Above it, you'll find the Help pane, where you can get " -"more information and documentation for any object in the Editor or " -"Console by pressing :kbd:`Ctrl-I` (or :kbd:`Cmd-I` on macOS). We'll see " -"how to do this in our next video." +msgid "On the left we have the Editor, where you can open, edit and run files. Bottom right is the IPython Console, which you can use both interactively and to run your code in the Editor. It shows you which version of Python you are using. Above it, you'll find the Help pane, where you can get more information and documentation for any object in the Editor or Console by pressing :kbd:`Ctrl-I` (or :kbd:`Cmd-I` on macOS). We'll see how to do this in our next video." msgstr "" #: ../../videos/first-steps-with-spyder.rst:50 -msgid "" -"For the two sections on the right, you can switch tabs to see the other " -"panes that are open by default when launching Spyder. In the top section," -" you can switch to the Variable Explorer, which shows you the name, type," -" size and value of the variables that you have previously defined in the " -"Editor or the Console. You can also modify the value of these variables " -"directly from this pane by double clicking them under the Value column. " -"The Plots pane will show you the figures you generate with Matplotlib and" -" other libraries, and the Files pane allows you to browse the files on " -"your computer and open them in the Editor with just a click." +msgid "For the two sections on the right, you can switch tabs to see the other panes that are open by default when launching Spyder. In the top section, you can switch to the Variable Explorer, which shows you the name, type, size and value of the variables that you have previously defined in the Editor or the Console. You can also modify the value of these variables directly from this pane by double clicking them under the Value column. The Plots pane will show you the figures you generate with Matplotlib and other libraries, and the Files pane allows you to browse the files on your computer and open them in the Editor with just a click." msgstr "" #: ../../videos/first-steps-with-spyder.rst:52 -msgid "" -"Finally, in the bottom section you can also access the History pane, " -"which shows you the commands you have entered in the Console, including " -"those from previous sessions." +msgid "Finally, in the bottom section you can also access the History pane, which shows you the commands you have entered in the Console, including those from previous sessions." msgstr "" #: ../../videos/first-steps-with-spyder.rst:54 -msgid "" -"I hope you're now familiar with the basics of using the Spyder interface." -" In the next video, we will start working with Spyder's core panes." +msgid "I hope you're now familiar with the basics of using the Spyder interface. In the next video, we will start working with Spyder's core panes." msgstr "" #: ../../videos/first-steps-with-spyder.rst:56 @@ -151,9 +110,7 @@ msgid "Execute basic Python commands in the IPython Console" msgstr "" #: ../../videos/first-steps-with-spyder.rst:69 -msgid "" -"Define variables in the Editor and modify their values in the IPython " -"Console" +msgid "Define variables in the Editor and modify their values in the IPython Console" msgstr "" #: ../../videos/first-steps-with-spyder.rst:70 @@ -165,68 +122,27 @@ msgid "Get documentation in the Help pane in two different ways" msgstr "" #: ../../videos/first-steps-with-spyder.rst:84 -msgid "" -"Hello everyone! I'm Juanita, and in this video I will show you how to " -"start working with Spyder's four main panes. First, let's take a look at " -"the Editor, which you can use to open, edit and run files from your " -"computer. I will open a short \"Hello World\" program for this demo, " -"which you can `download here`_. Once you have it open in your Editor, you" -" can execute it by pressing the green run button. We can see the output " -"in the Python Console [Show IPython console] as well as the path of the " -"file that we are running and the working directory where this code was " -"run." +msgid "Hello everyone! I'm Juanita, and in this video I will show you how to start working with Spyder's four main panes. First, let's take a look at the Editor, which you can use to open, edit and run files from your computer. I will open a short \"Hello World\" program for this demo, which you can `download here`_. Once you have it open in your Editor, you can execute it by pressing the green run button. We can see the output in the Python Console [Show IPython console] as well as the path of the file that we are running and the working directory where this code was run." msgstr "" #: ../../videos/first-steps-with-spyder.rst:88 -msgid "" -"We can also run any Python code that is entered directly in the IPython " -"Console. For example, we can type ``print(\"Hello\")`` and see the " -"output. Or, we can try some math operations and see the results here too." -" Note that for implicitly printed output, there is a red indication that " -"differs from the output of the ``print()`` function." +msgid "We can also run any Python code that is entered directly in the IPython Console. For example, we can type ``print(\"Hello\")`` and see the output. Or, we can try some math operations and see the results here too. Note that for implicitly printed output, there is a red indication that differs from the output of the ``print()`` function." msgstr "" #: ../../videos/first-steps-with-spyder.rst:90 -msgid "" -"Now, let's start defining some variables. We can do this both from the " -"editor or from the Console. If I define a variable ``a = 10`` and then " -"run this code, I can see its value in the console just by typing its name" -" ``a``. However, you can also assign any variable in the IPython console " -"(``b = 20``) and its value will be stored too. In both cases, they can " -"also be seen in the Variable Explorer pane, which shows the name, type, " -"size and value of each of the objects previously defined. In this case, " -"we see variables ``a`` and ``b``, both of type int and with size 1. We " -"can also define a list ``l`` with ``l = [1, 2, 3]`` and see that the type" -" of the variable is list and the size is 3." +msgid "Now, let's start defining some variables. We can do this both from the editor or from the Console. If I define a variable ``a = 10`` and then run this code, I can see its value in the console just by typing its name ``a``. However, you can also assign any variable in the IPython console (``b = 20``) and its value will be stored too. In both cases, they can also be seen in the Variable Explorer pane, which shows the name, type, size and value of each of the objects previously defined. In this case, we see variables ``a`` and ``b``, both of type int and with size 1. We can also define a list ``l`` with ``l = [1, 2, 3]`` and see that the type of the variable is list and the size is 3." msgstr "" #: ../../videos/first-steps-with-spyder.rst:92 -msgid "" -"We can change the values of the variables in the Variable Explorer too by" -" double-clicking them and typing their new value. Now, we can check their" -" new value in the console. In the case of a more complex type like a " -"list, double-clicking it will open a viewer in which you can modify each " -"of its values separately, along with other more complex operations which " -"we'll demonstrate in a future video. We can remove a variable by right-" -"clicking it and selecting the option Remove. After doing this, we can " -"check in the IPython Console that the variable was actually deleted." +msgid "We can change the values of the variables in the Variable Explorer too by double-clicking them and typing their new value. Now, we can check their new value in the console. In the case of a more complex type like a list, double-clicking it will open a viewer in which you can modify each of its values separately, along with other more complex operations which we'll demonstrate in a future video. We can remove a variable by right-clicking it and selecting the option Remove. After doing this, we can check in the IPython Console that the variable was actually deleted." msgstr "" #: ../../videos/first-steps-with-spyder.rst:94 -msgid "" -"Finally, we are going to learn how to get help for objects in two " -"different ways. First, we can press :kbd:`Ctrl-I` (or :kbd:`Cmd-I` on " -"macOS) right after the name of an object written in the Editor or the " -"Console, for example ``numpy.array``. You can see that we obtain its " -"documentation in the Help pane if it is available. Second, if we change " -"the Source dropdown option to Console, we can type its name in the object" -" box in the Help pane. Now we can get help for Numpy arrays." +msgid "Finally, we are going to learn how to get help for objects in two different ways. First, we can press :kbd:`Ctrl-I` (or :kbd:`Cmd-I` on macOS) right after the name of an object written in the Editor or the Console, for example ``numpy.array``. You can see that we obtain its documentation in the Help pane if it is available. Second, if we change the Source dropdown option to Console, we can type its name in the object box in the Help pane. Now we can get help for Numpy arrays." msgstr "" #: ../../videos/first-steps-with-spyder.rst:96 -msgid "" -"You should now be ready to start using Spyder's four main panes. Check " -"out our next video to continue learning and as always, Happy Spydering!" +msgid "You should now be ready to start using Spyder's four main panes. Check out our next video to continue learning and as always, Happy Spydering!" msgstr "" #: ../../videos/first-steps-with-spyder.rst:102 @@ -234,9 +150,7 @@ msgid "Customization" msgstr "" #: ../../videos/first-steps-with-spyder.rst:104 -msgid "" -"Learn how to customize Spyder’s interface to match your workflow and " -"development style." +msgid "Learn how to customize Spyder’s interface to match your workflow and development style." msgstr "" #: ../../videos/first-steps-with-spyder.rst:106 @@ -256,73 +170,35 @@ msgid "Split, close and pop out Editor panels" msgstr "" #: ../../videos/first-steps-with-spyder.rst:123 -msgid "" -"Hello everyone, I'm Juanita! In this video, I will show you how to " -"customize Spyder to match your workflow and development style." +msgid "Hello everyone, I'm Juanita! In this video, I will show you how to customize Spyder to match your workflow and development style." msgstr "" #: ../../videos/first-steps-with-spyder.rst:125 -msgid "" -"First, we are going to learn how to change the font in the Editor, " -"IPython Console and Help panes. To do this, go to Preferences, select the" -" Appearance entry and scroll down to Fonts. You can change both the style" -" and the size of the font for both plain and rich text. You can see how " -"this affects the font in the Editor, Console and Help panes." +msgid "First, we are going to learn how to change the font in the Editor, IPython Console and Help panes. To do this, go to Preferences, select the Appearance entry and scroll down to Fonts. You can change both the style and the size of the font for both plain and rich text. You can see how this affects the font in the Editor, Console and Help panes." msgstr "" #: ../../videos/first-steps-with-spyder.rst:127 -msgid "" -"In this same dialog, you can easily change the syntax highlighting theme," -" for which you can see the preview at the right of the window. Note that " -"Spyder's interface theme changes to match the highlighting theme because " -"the Interface theme option is set to Automatic by default. However, you " -"can change the theme for the entire Spyder interface, choosing between " -"Light and Dark. After selecting this change, click Apply to restart " -"Spyder to apply the new theme." +msgid "In this same dialog, you can easily change the syntax highlighting theme, for which you can see the preview at the right of the window. Note that Spyder's interface theme changes to match the highlighting theme because the Interface theme option is set to Automatic by default. However, you can change the theme for the entire Spyder interface, choosing between Light and Dark. After selecting this change, click Apply to restart Spyder to apply the new theme." msgstr "" #: ../../videos/first-steps-with-spyder.rst:129 -msgid "" -"Beyond just Spyder's preferences, you can freely rearrange the panes in " -"Spyder's main window. To show or hide panes, go to Panes under the View " -"menu, and select which ones you want to see. For example, let's hide the " -"Files pane and show the Profiler pane. You can also close a pane from its" -" options menu, which will hide it from the main window." +msgid "Beyond just Spyder's preferences, you can freely rearrange the panes in Spyder's main window. To show or hide panes, go to Panes under the View menu, and select which ones you want to see. For example, let's hide the Files pane and show the Profiler pane. You can also close a pane from its options menu, which will hide it from the main window." msgstr "" #: ../../videos/first-steps-with-spyder.rst:131 -msgid "" -"By default, the panes and toolbars are locked so they can't be moved " -"accidentally. However, unchecking the option Lock panes and toolbars in " -"the View menu will allow you to move them freely anywhere on the window, " -"by dragging them from the top and dropping them at any position you like." -" You can also undock a pane, which will open a new window with it. You " -"can have as many separate windows as you have panes, if you choose. This " -"feature is very useful if you work with several monitors because you can " -"undock the Editor and move it to a different monitor, while working with " -"the rest of the panes in your main monitor." +msgid "By default, the panes and toolbars are locked so they can't be moved accidentally. However, unchecking the option Lock panes and toolbars in the View menu will allow you to move them freely anywhere on the window, by dragging them from the top and dropping them at any position you like. You can also undock a pane, which will open a new window with it. You can have as many separate windows as you have panes, if you choose. This feature is very useful if you work with several monitors because you can undock the Editor and move it to a different monitor, while working with the rest of the panes in your main monitor." msgstr "" #: ../../videos/first-steps-with-spyder.rst:133 -msgid "" -"Additionally, you can split the Editor pane vertically or horizontally in" -" as many copies as you want, and open one or more panels in separate " -"Spyder windows, complete with their own toolbar, outline and status bar." +msgid "Additionally, you can split the Editor pane vertically or horizontally in as many copies as you want, and open one or more panels in separate Spyder windows, complete with their own toolbar, outline and status bar." msgstr "" #: ../../videos/first-steps-with-spyder.rst:135 -msgid "" -"Finally, each pane can be customized further under its respective options" -" menu and Preferences panel." +msgid "Finally, each pane can be customized further under its respective options menu and Preferences panel." msgstr "" #: ../../videos/first-steps-with-spyder.rst:137 -msgid "" -"With all these options, you can customize Spyder to your heart's content." -" However, if you ever want to return to its default configuration, you " -"can always reset the window layout under Window Layouts in the View menu," -" or your entire Spyder configuration with the Reset to Default button in " -"the Preferences." +msgid "With all these options, you can customize Spyder to your heart's content. However, if you ever want to return to its default configuration, you can always reset the window layout under Window Layouts in the View menu, or your entire Spyder configuration with the Reset to Default button in the Preferences." msgstr "" #: ../../videos/first-steps-with-spyder.rst:139 @@ -330,7 +206,7 @@ msgid "Enjoy your customized version of Spyder, and Happy Spydering!" msgstr "" #: ../../videos/index.rst:3 -msgid "Intro Videos" +msgid "Tutorials" msgstr "" #: ../../videos/working-with-spyder.rst:3 @@ -338,9 +214,7 @@ msgid "Working with Spyder" msgstr "" #: ../../videos/working-with-spyder.rst:5 -msgid "" -"In this section, you will learn about Spyder's more advanced " -"functionality, and explore most of the panes." +msgid "In this section, you will learn about Spyder's more advanced functionality, and explore most of the panes." msgstr "" #: ../../videos/working-with-spyder.rst:11 @@ -348,9 +222,7 @@ msgid "Beyond the main panes" msgstr "" #: ../../videos/working-with-spyder.rst:13 -msgid "" -"Explore how to take advantage of Spyder’s functionality beyond just the " -"four core panes." +msgid "Explore how to take advantage of Spyder’s functionality beyond just the four core panes." msgstr "" #: ../../videos/working-with-spyder.rst:15 @@ -366,9 +238,7 @@ msgid "Quickly navigate within and between files with the Outline pane" msgstr "" #: ../../videos/working-with-spyder.rst:18 -msgid "" -"Search for text or regular expressions across your entire project with " -"the Find pane" +msgid "Search for text or regular expressions across your entire project with the Find pane" msgstr "" #: ../../videos/working-with-spyder.rst:19 @@ -376,121 +246,43 @@ msgid "Discover and explore structured documentation in the Online Help pane" msgstr "" #: ../../videos/working-with-spyder.rst:33 -msgid "" -"Hello everyone! I'm Juanita, and I am going to show you how to use some " -"of the remaining panes available in Spyder beyond just the four primary " -"ones." +msgid "Hello everyone! I'm Juanita, and I am going to show you how to use some of the remaining panes available in Spyder beyond just the four primary ones." msgstr "" #: ../../videos/working-with-spyder.rst:35 -msgid "" -"Let's start with the Plots pane, which is open by default when launching " -"Spyder. To see how it works, let's open a file that will generate a " -"couple plots from Matplotlib's documentation. You can view the generated " -"plots in the Plots pane and browse between them using the arrows, or " -"simply clicking them in the sidebar." +msgid "Let's start with the Plots pane, which is open by default when launching Spyder. To see how it works, let's open a file that will generate a couple plots from Matplotlib's documentation. You can view the generated plots in the Plots pane and browse between them using the arrows, or simply clicking them in the sidebar." msgstr "" #: ../../videos/working-with-spyder.rst:37 -msgid "" -"If you open the pane's options menu, you will see that Fit Plots to " -"Window is enabled by default. Disabling it will allow you to zoom the " -"plots in or out. You can also see that Mute inline plotting is enabled, " -"which prevents the same figures from also appearing in the IPython " -"Console. Note that every time that the code is run, new copies of the " -"plots are generated in the pane, but you can remove any you don't want to" -" keep around with the X button in the pane toolbar. Additionally, the " -"pane automatically updates to show the plots generated by each console as" -" you switch between them." +msgid "If you open the pane's options menu, you will see that Fit Plots to Window is enabled by default. Disabling it will allow you to zoom the plots in or out. You can also see that Mute inline plotting is enabled, which prevents the same figures from also appearing in the IPython Console. Note that every time that the code is run, new copies of the plots are generated in the pane, but you can remove any you don't want to keep around with the X button in the pane toolbar. Additionally, the pane automatically updates to show the plots generated by each console as you switch between them." msgstr "" #: ../../videos/working-with-spyder.rst:39 -msgid "" -"To use a plot in another document, click the Copy to Clipboard button and" -" paste it wherever you want, such as a word processor. Additionally, you " -"can save a plot as a PNG by clicking the save icon." +msgid "To use a plot in another document, click the Copy to Clipboard button and paste it wherever you want, such as a word processor. Additionally, you can save a plot as a PNG by clicking the save icon." msgstr "" #: ../../videos/working-with-spyder.rst:41 -msgid "" -"The Files pane, also open by default, lets you browse the contents of the" -" directories on your computer, open them in the Editor, and perform a " -"variety of other file operations. You can show or hide the size, kind and" -" date of the files in the pane's options menu. As you change the top-" -"level folder you're viewing in the pane, Spyder's working directory shown" -" in the top right of the main toolbar will update, which will also be " -"synchronized with the currently active console. Double-clicking a text " -"file will open it in the Editor, and copying one or more files will allow" -" you to paste them as automatically-formatted absolute or relative paths." -" Right-clicking any item will offer an array of additional options for " -"interacting with it." +msgid "The Files pane, also open by default, lets you browse the contents of the directories on your computer, open them in the Editor, and perform a variety of other file operations. You can show or hide the size, kind and date of the files in the pane's options menu. As you change the top-level folder you're viewing in the pane, Spyder's working directory shown in the top right of the main toolbar will update, which will also be synchronized with the currently active console. Double-clicking a text file will open it in the Editor, and copying one or more files will allow you to paste them as automatically-formatted absolute or relative paths. Right-clicking any item will offer an array of additional options for interacting with it." msgstr "" #: ../../videos/working-with-spyder.rst:43 -msgid "" -"You can also open a file in the system default external application, or " -"set up a custom file association in the File Associations tab of the " -"Files preferences pane. For example, we can add the ``.csv`` extension " -"and associate it with LibreOffice Calc under associated applications. Now" -" every time you click a file with this extension, it opens externally " -"with this program." +msgid "You can also open a file in the system default external application, or set up a custom file association in the File Associations tab of the Files preferences pane. For example, we can add the ``.csv`` extension and associate it with LibreOffice Calc under associated applications. Now every time you click a file with this extension, it opens externally with this program." msgstr "" #: ../../videos/working-with-spyder.rst:45 -msgid "" -"Now, let's see how to use the Outline pane to navigate within a file. " -"First, we have to open the pane under Panes in the View menu, since it " -"isn't visible by default. As you can see, it shows you all the classes, " -"methods and functions that are currently defined, and allows you to move " -"between them with just a click. For a very large file like this one, it " -"is very useful to switch between classes easily instead of scrolling " -"through the four-thousand-plus lines of code. You can also browse the " -"methods of a class by expanding it using the arrows, or the buttons in " -"the Outline pane's toolbar. The Outline continuously updates to highlight" -" the function, method or class corresponding to the cursor position in " -"your code, so you can easily keep track of what object you are working " -"on. Finally, by going to the pane options menu and activating Show all " -"files, you can easily switch between the scripts and modules you have " -"open, which is particularly important for navigating larger projects." +msgid "Now, let's see how to use the Outline pane to navigate within a file. First, we have to open the pane under Panes in the View menu, since it isn't visible by default. As you can see, it shows you all the classes, methods and functions that are currently defined, and allows you to move between them with just a click. For a very large file like this one, it is very useful to switch between classes easily instead of scrolling through the four-thousand-plus lines of code. You can also browse the methods of a class by expanding it using the arrows, or the buttons in the Outline pane's toolbar. The Outline continuously updates to highlight the function, method or class corresponding to the cursor position in your code, so you can easily keep track of what object you are working on. Finally, by going to the pane options menu and activating Show all files, you can easily switch between the scripts and modules you have open, which is particularly important for navigating larger projects." msgstr "" #: ../../videos/working-with-spyder.rst:47 -msgid "" -"The Files pane is another useful tool for particularly larger projects. " -"Like the Outline pane, it can be opened under Panes in the View menu. " -"This allows you to view and navigate through all occurrences of text or " -"regular expressions in any file in the working directory, project or " -"another custom directory. We see, for example, in the ``mainwindow.py`` " -"file we import the ``is_dark_font_color`` function. If we want to quickly" -" find the file where it was defined, we can write this string in the " -"search bar. With this search, we get 7 matches from 3 different files. " -"When we click on any of these matches, the file is opened automatically " -"in the Editor, right where this string appears." +msgid "The Files pane is another useful tool for particularly larger projects. Like the Outline pane, it can be opened under Panes in the View menu. This allows you to view and navigate through all occurrences of text or regular expressions in any file in the working directory, project or another custom directory. We see, for example, in the ``mainwindow.py`` file we import the ``is_dark_font_color`` function. If we want to quickly find the file where it was defined, we can write this string in the search bar. With this search, we get 7 matches from 3 different files. When we click on any of these matches, the file is opened automatically in the Editor, right where this string appears." msgstr "" #: ../../videos/working-with-spyder.rst:49 -msgid "" -"Finally, we'll learn how to browse documentation using the Online Help " -"pane. Once you open it, again under Panes in the View menu, you will see " -"an index of modules from which documentation is available, including both" -" those in the Python standard library and any third-party packages that " -"may be installed in Spyder's environment. For example, we can find help " -"for Numpy, Pandas and Matplotlib, which are all installed if you've " -"downloaded Spyder with Anaconda. You can browse the contents in the " -"built-in web browser provided by the pane, and click the hyperlinks " -"within to navigate to different pages. You can also enter the name of the" -" item you'd like documentation on in the Get field or in the space over " -"the pane's toolbar, to load its information directly. If you're not sure " -"of the object's name, use the Search field to view a list of results " -"applicable to any keyword." +msgid "Finally, we'll learn how to browse documentation using the Online Help pane. Once you open it, again under Panes in the View menu, you will see an index of modules from which documentation is available, including both those in the Python standard library and any third-party packages that may be installed in Spyder's environment. For example, we can find help for Numpy, Pandas and Matplotlib, which are all installed if you've downloaded Spyder with Anaconda. You can browse the contents in the built-in web browser provided by the pane, and click the hyperlinks within to navigate to different pages. You can also enter the name of the item you'd like documentation on in the Get field or in the space over the pane's toolbar, to load its information directly. If you're not sure of the object's name, use the Search field to view a list of results applicable to any keyword." msgstr "" #: ../../videos/working-with-spyder.rst:51 -msgid "" -"Now that you're familiar with a wider array of Spyder's panes and " -"features, you can accomplish a variety of common programming tasks with " -"ease. Stay tuned for our our next videos to further add to your " -"scientific toolbox, and as always, Happy Spydering!" +msgid "Now that you're familiar with a wider array of Spyder's panes and features, you can accomplish a variety of common programming tasks with ease. Stay tuned for our our next videos to further add to your scientific toolbox, and as always, Happy Spydering!" msgstr "" #: ../../videos/working-with-spyder.rst:57 @@ -502,9 +294,7 @@ msgid "Learn how to improve the quality of your programs using code analysis." msgstr "" #: ../../videos/working-with-spyder.rst:61 -msgid "" -"Open and use Code Analysis to evaluate the quality and style of Python " -"files" +msgid "Open and use Code Analysis to evaluate the quality and style of Python files" msgstr "" #: ../../videos/working-with-spyder.rst:62 @@ -520,127 +310,71 @@ msgid "Turn off messages on a line, in a file or globally" msgstr "" #: ../../videos/working-with-spyder.rst:78 -msgid "" -"Hello everyone! I'm Juanita, and in this video we will learn how to " -"improve your code quality using the Code Analysis pane. To display it, we" -" can click its name under Panes in the View menu." +msgid "Hello everyone! I'm Juanita, and in this video we will learn how to improve your code quality using the Code Analysis pane. To display it, we can click its name under Panes in the View menu." msgstr "" #: ../../videos/working-with-spyder.rst:80 -msgid "" -"This pane detects style issues, bad practices, potential bugs and other " -"quality problems in your code, without having to execute it. There are " -"three ways of running code analysis:" +msgid "This pane detects style issues, bad practices, potential bugs and other quality problems in your code, without having to execute it. There are three ways of running code analysis:" msgstr "" #: ../../videos/working-with-spyder.rst:82 -msgid "" -"To analyze a file that is open in the Editor, we can press the " -"configurable shortcut, :kbd:`F8` by default, or select Source --> Run " -"code analysis from the menu bar." +msgid "To analyze a file that is open in the Editor, we can press the configurable shortcut, :kbd:`F8` by default, or select Source --> Run code analysis from the menu bar." msgstr "" #: ../../videos/working-with-spyder.rst:84 -msgid "" -"We can also select a file to analyze by browsing for it using the file " -"button next to the path box. This will start the analysis automatically." +msgid "We can also select a file to analyze by browsing for it using the file button next to the path box. This will start the analysis automatically." msgstr "" #: ../../videos/working-with-spyder.rst:86 -msgid "" -"The third way is to manually enter the path of a file we'd like to check " -"in the path entry box in the pane's toolbar, and click the Analyze button" -" in the pane." +msgid "The third way is to manually enter the path of a file we'd like to check in the path entry box in the pane's toolbar, and click the Analyze button in the pane." msgstr "" #: ../../videos/working-with-spyder.rst:88 -msgid "" -"Based on these results, the code analysis shows an overall score of " -"4.34/10, which allows us to track improvements in our code quality. We " -"can also expand or collapse one or all the sections in the pane to be " -"able to see the Pylint errors, warnings and messages identifying the " -"issues with our code." +msgid "Based on these results, the code analysis shows an overall score of 4.34/10, which allows us to track improvements in our code quality. We can also expand or collapse one or all the sections in the pane to be able to see the Pylint errors, warnings and messages identifying the issues with our code." msgstr "" #: ../../videos/working-with-spyder.rst:90 -msgid "" -"For example, the results tell us that there is a warning on line 20. To " -"go directly to this line in the Editor, just click the message. Here, the" -" code analysis says there is a ``bad-whitespace`` issue. To understand " -"what this means, open the Pylint documentation. On the `Pylint docs " -"page`_ , click on Pylint features and search for the code of the message." +msgid "For example, the results tell us that there is a warning on line 20. To go directly to this line in the Editor, just click the message. Here, the code analysis says there is a ``bad-whitespace`` issue. To understand what this means, open the Pylint documentation. On the `Pylint docs page`_ , click on Pylint features and search for the code of the message." msgstr "" #: ../../videos/working-with-spyder.rst:94 -msgid "" -"We can see that the docs say that we used the wrong number of spaces " -"around an operator." +msgid "We can see that the docs say that we used the wrong number of spaces around an operator." msgstr "" #: ../../videos/working-with-spyder.rst:102 -msgid "" -"We can fix the error by adding one space before and after the operator in" -" this variable assignment. If we run the analysis again, we can see the " -"error isn't shown any more on this line." +msgid "We can fix the error by adding one space before and after the operator in this variable assignment. If we run the analysis again, we can see the error isn't shown any more on this line." msgstr "" #: ../../videos/working-with-spyder.rst:104 -msgid "" -"We can click the dropdown arrow in the filename field to view the list of" -" previous analyses. Clicking one of them will show us the results." +msgid "We can click the dropdown arrow in the filename field to view the list of previous analyses. Clicking one of them will show us the results." msgstr "" #: ../../videos/working-with-spyder.rst:106 -msgid "" -"Sometimes, it is useful to turn certain messages off. We can do that in " -"three different ways." +msgid "Sometimes, it is useful to turn certain messages off. We can do that in three different ways." msgstr "" #: ../../videos/working-with-spyder.rst:108 -msgid "" -"We might want to silence warnings on only one line; for example, this " -"\"unused\" import that is still necessary for the code execution. For " -"this, type ``# pylint: disable=unused-import`` as a comment at the end of" -" the line. Running the analysis again will show us that the error is no " -"longer visible." +msgid "We might want to silence warnings on only one line; for example, this \"unused\" import that is still necessary for the code execution. For this, type ``# pylint: disable=unused-import`` as a comment at the end of the line. Running the analysis again will show us that the error is no longer visible." msgstr "" #: ../../videos/working-with-spyder.rst:110 -msgid "" -"If we want to silence a message in the whole file, we can do it by " -"writing the disable command at the beginning of the file. For example, we" -" can disable the ``invalid-name`` warning that appears several times in " -"this file. If we run the analysis again, all of these warnings are gone." +msgid "If we want to silence a message in the whole file, we can do it by writing the disable command at the beginning of the file. For example, we can disable the ``invalid-name`` warning that appears several times in this file. If we run the analysis again, all of these warnings are gone." msgstr "" #: ../../videos/working-with-spyder.rst:112 -msgid "" -"Finally, we can suppress specific messages for all files by editing the " -"``.pylintrc`` configuration file in your user folder. If it doesn't " -"exist, we can generate it by opening our terminal, or the Anaconda Prompt" -" if you're using Windows, and running ``pylint --generate-rc > " -".pylintrc`` in our user directory." +msgid "Finally, we can suppress specific messages for all files by editing the ``.pylintrc`` configuration file in your user folder. If it doesn't exist, we can generate it by opening our terminal, or the Anaconda Prompt if you're using Windows, and running ``pylint --generate-rc > .pylintrc`` in our user directory." msgstr "" #: ../../videos/working-with-spyder.rst:114 -msgid "" -"Now, we can go to the ``MESSAGE CONTROL`` section in this file and add " -"the corresponding Pylint message name, for example ``no-name-in-module``." -" If we run the analysis one more time, we see that the ``no-name-in-" -"module`` warnings don't appear anymore." +msgid "Now, we can go to the ``MESSAGE CONTROL`` section in this file and add the corresponding Pylint message name, for example ``no-name-in-module``. If we run the analysis one more time, we see that the ``no-name-in-module`` warnings don't appear anymore." msgstr "" #: ../../videos/working-with-spyder.rst:116 -msgid "" -"We can see that the score of our file increased to 7.63/10, a big " -"improvement over the previous 4.34." +msgid "We can see that the score of our file increased to 7.63/10, a big improvement over the previous 4.34." msgstr "" #: ../../videos/working-with-spyder.rst:118 -msgid "" -"Now that we've learned how to improve the quality of our code, you are " -"ready to write cleaner and more correct programs using Spyder. Stay tuned" -" for our next videos and as always, Happy Spydering!" +msgid "Now that we've learned how to improve the quality of our code, you are ready to write cleaner and more correct programs using Spyder. Stay tuned for our next videos and as always, Happy Spydering!" msgstr "" #: ../../videos/working-with-spyder.rst:124 @@ -668,108 +402,53 @@ msgid "Use the information to speed up the run time of your code" msgstr "" #: ../../videos/working-with-spyder.rst:145 -msgid "" -"Hello everyone! I'm Juanita, and in this video we will learn how to " -"optimize your code using the profiler. To display it, click its name " -"under Panes in the View menu." +msgid "Hello everyone! I'm Juanita, and in this video we will learn how to optimize your code using the profiler. To display it, click its name under Panes in the View menu." msgstr "" #: ../../videos/working-with-spyder.rst:147 -msgid "" -"The Profiler will determine the run time and number of calls for every " -"function and method used in a file. There are three ways of profiling a " -"file:" +msgid "The Profiler will determine the run time and number of calls for every function and method used in a file. There are three ways of profiling a file:" msgstr "" #: ../../videos/working-with-spyder.rst:149 -msgid "" -"We can browse for a file using the open button to the right of the " -"Profiler's path box, which will run profiling over it automatically." +msgid "We can browse for a file using the open button to the right of the Profiler's path box, which will run profiling over it automatically." msgstr "" #: ../../videos/working-with-spyder.rst:151 -msgid "" -"We can also manually enter the path in the pane's path box, and then run " -"the analysis on the file by pressing the Profile button." +msgid "We can also manually enter the path in the pane's path box, and then run the analysis on the file by pressing the Profile button." msgstr "" #: ../../videos/working-with-spyder.rst:153 -msgid "" -"If we want to run the profiler for the file that is currently open in the" -" Editor, we can click Run --> Profile... in the menu bar, or use the " -"configurable shortcut :kbd:`F10`." +msgid "If we want to run the profiler for the file that is currently open in the Editor, we can click Run --> Profile... in the menu bar, or use the configurable shortcut :kbd:`F10`." msgstr "" #: ../../videos/working-with-spyder.rst:155 -msgid "" -"We see that the results in the pane show us the different functions and " -"methods in our file, with each sub-function listed hierarchically under " -"the item that called them. The columns show the total time taken by each " -"function and everything it called, while the local time includes only the" -" time spent in that particular function." +msgid "We see that the results in the pane show us the different functions and methods in our file, with each sub-function listed hierarchically under the item that called them. The columns show the total time taken by each function and everything it called, while the local time includes only the time spent in that particular function." msgstr "" #: ../../videos/working-with-spyder.rst:157 -msgid "" -"For example, the function ``values`` in this file calls a function " -"``internal_values`` values took a total of 482 us to run, with 338 us of " -"that spent executing internal_values inside of it. Therefore, the total " -"time for values is 482 us, but its local time is only 144 us as the rest " -"was spent inside ``internal_values``." +msgid "For example, the function ``values`` in this file calls a function ``internal_values`` values took a total of 482 us to run, with 338 us of that spent executing internal_values inside of it. Therefore, the total time for values is 482 us, but its local time is only 144 us as the rest was spent inside ``internal_values``." msgstr "" #: ../../videos/working-with-spyder.rst:159 -msgid "" -"The Calls column displays the total number of times that function was " -"called at that level. Finally, the numbers in the Diff columns for each " -"of the three appear if a comparison is loaded, and indicate the change in" -" runtime between the two measurements." +msgid "The Calls column displays the total number of times that function was called at that level. Finally, the numbers in the Diff columns for each of the three appear if a comparison is loaded, and indicate the change in runtime between the two measurements." msgstr "" #: ../../videos/working-with-spyder.rst:161 -msgid "" -"By double-clicking an item in the Profiler, we will be taken to the file " -"and line in the Editor where it was called. If this function was not " -"called in one of your open scripts, clicking it will open the file that " -"contains it. We can click the down arrow button in the filename field to " -"recall paths of previously profiled files." +msgid "By double-clicking an item in the Profiler, we will be taken to the file and line in the Editor where it was called. If this function was not called in one of your open scripts, clicking it will open the file that contains it. We can click the down arrow button in the filename field to recall paths of previously profiled files." msgstr "" #: ../../videos/working-with-spyder.rst:163 -msgid "" -"Now that we know how to interpret the results of our profiling, let's " -"optimize our code by finding the functions that take the longest time and" -" making them faster. In this case, ``to_datetime`` takes 39 seconds to " -"run. The reason for this is Pandas has to parse the non-standard " -"timestamp format and is not told to try to use a faster parser than the " -"default." +msgid "Now that we know how to interpret the results of our profiling, let's optimize our code by finding the functions that take the longest time and making them faster. In this case, ``to_datetime`` takes 39 seconds to run. The reason for this is Pandas has to parse the non-standard timestamp format and is not told to try to use a faster parser than the default." msgstr "" #: ../../videos/working-with-spyder.rst:165 -#, python-format -msgid "" -"We can reduce the time this function takes and compare it with the one " -"before. For this, first we have to save the data as a ``.Result`` file " -"with the save button in the pane. Now we have to figure out how to " -"optimize the function, so let's search for it. We see that we can speed " -"up this function by `manually specifying a datetime format`_. So, we add " -"the appropriate argument, ``format=\"%Y-%m-%d %H:%M:%S.%f %z\"``, to our " -"function call." +msgid "We can reduce the time this function takes and compare it with the one before. For this, first we have to save the data as a ``.Result`` file with the save button in the pane. Now we have to figure out how to optimize the function, so let's search for it. We see that we can speed up this function by `manually specifying a datetime format`_. So, we add the appropriate argument, ``format=\"%Y-%m-%d %H:%M:%S.%f %z\"``, to our function call." msgstr "" #: ../../videos/working-with-spyder.rst:169 -msgid "" -"Now, we run the profiling again to see how our script's performance has " -"improved. If we want to see how much we lowered the time, we can load our" -" previous result and take a look at the diff columns. Notice the " -"difference is green because the time was reduced by three times, taking " -"only 13 seconds instead of 39. Our code is now 26 seconds faster!" +msgid "Now, we run the profiling again to see how our script's performance has improved. If we want to see how much we lowered the time, we can load our previous result and take a look at the diff columns. Notice the difference is green because the time was reduced by three times, taking only 13 seconds instead of 39. Our code is now 26 seconds faster!" msgstr "" #: ../../videos/working-with-spyder.rst:171 -msgid "" -"Now that you've learned how to analyze the execution time of your code, " -"you are ready to write more efficient programs with Spyder's help. Stay " -"tuned for our next videos and as always, Happy Spydering!" +msgid "Now that you've learned how to analyze the execution time of your code, you are ready to write more efficient programs with Spyder's help. Stay tuned for our next videos and as always, Happy Spydering!" msgstr "" - diff --git a/doc/locales/pot/workshops.pot b/doc/locales/pot/workshops.pot index b093526b..967c9bc2 100644 --- a/doc/locales/pot/workshops.pot +++ b/doc/locales/pot/workshops.pot @@ -1,19 +1,19 @@ # SOME DESCRIPTIVE TITLE. # Copyright (C) 2009-2024 Spyder Doc Contributors; MIT License # This file is distributed under the same license as the Spyder package. -# FIRST AUTHOR , 2024. +# FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Spyder 5\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2024-01-29 08:54-0600\n" +"POT-Creation-Date: 2024-09-06 20:38-0500\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" -"Language-Team: en \n" +"Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=utf-8\n" +"Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #: ../../workshops/financial.rst:3 @@ -21,47 +21,30 @@ msgid "Financial Data Analysis with Spyder" msgstr "" #: ../../workshops/financial.rst:5 -msgid "" -"By the end of this workshop participants will be able to use Spyder " -"effectively for applying some normative financial theories and models to" -" assemble a portfolio of assets in a way that maximizes the expected " -"return for a given level of risk. In this way, statistically-based tools " -"are used to construct investment portfolios." +msgid "By the end of this workshop participants will be able to use Spyder effectively for applying some normative financial theories and models to assemble a portfolio of assets in a way that maximizes the expected return for a given level of risk. In this way, statistically-based tools are used to construct investment portfolios." msgstr "" -#: ../../workshops/financial.rst:11 ../../workshops/plugin-development.rst:15 +#: ../../workshops/financial.rst:11 +#: ../../workshops/plugin-development.rst:15 #: ../../workshops/scientific-computing.rst:11 msgid "Prerequisites" msgstr "" #: ../../workshops/financial.rst:13 -msgid "" -"To follow this workshop we recommend that you have a intermediate " -"knowledge of Python. You can visit `The Python Tutorial`_ to learn the " -"basics of this programming language or to refresh your knowledge of " -"Python." +msgid "To follow this workshop we recommend that you have a intermediate knowledge of Python. You can visit `The Python Tutorial`_ to learn the basics of this programming language or to refresh your knowledge of Python." msgstr "" #: ../../workshops/financial.rst:17 -msgid "" -"You will also need to have `Anaconda " -"`_ (or `Miniconda " -"`_) and Spyder installed." -" More information about Spyder installation in :doc:`installation " -"guide<../installation>`." +msgid "You will also need to have `Anaconda `_ (or `Miniconda `_) and Spyder installed. More information about Spyder installation in :doc:`installation guide<../installation>`." msgstr "" -#: ../../workshops/financial.rst:21 ../../workshops/scientific-computing.rst:17 -msgid "" -"Spyder now offers :ref:`install-standalone` for Windows and macOS, making" -" it easier to get up and running with the application without having to " -"download Anaconda or manually install it in your existing environment. " -"While we still support Anaconda, we recommend this install method on " -"those platforms to avoid most problems with package conflicts and other " -"issues." +#: ../../workshops/financial.rst:21 +#: ../../workshops/scientific-computing.rst:17 +msgid "Spyder now offers :ref:`install-standalone` for Windows and macOS, making it easier to get up and running with the application without having to download Anaconda or manually install it in your existing environment. While we still support Anaconda, we recommend this install method on those platforms to avoid most problems with package conflicts and other issues." msgstr "" -#: ../../workshops/financial.rst:25 ../../workshops/plugin-development.rst:24 +#: ../../workshops/financial.rst:25 +#: ../../workshops/plugin-development.rst:24 #: ../../workshops/scientific-computing.rst:20 msgid "It is also desirable to have the following prior knowledge:" msgstr "" @@ -78,46 +61,40 @@ msgstr "" msgid "Some knowledge of Financial Econometrics is desirable" msgstr "" -#: ../../workshops/financial.rst:34 ../../workshops/scientific-computing.rst:34 +#: ../../workshops/financial.rst:34 +#: ../../workshops/scientific-computing.rst:34 msgid "Learning goals" msgstr "" -#: ../../workshops/financial.rst:36 ../../workshops/scientific-computing.rst:36 +#: ../../workshops/financial.rst:36 +#: ../../workshops/scientific-computing.rst:36 msgid "After completing this workshop, you should be able to:" msgstr "" #: ../../workshops/financial.rst:38 -msgid "" -"Apply elementary statistical analysis to stock and cryptocurrency " -"portfolios to measure their performance" +msgid "Apply elementary statistical analysis to stock and cryptocurrency portfolios to measure their performance" msgstr "" #: ../../workshops/financial.rst:39 -msgid "" -"Understand the advantages of programming with an IDE, such as inspecting " -"variables using the Variable Explorer and interacting with plots " -"leveraging the Plots Pane." +msgid "Understand the advantages of programming with an IDE, such as inspecting variables using the Variable Explorer and interacting with plots leveraging the Plots Pane." msgstr "" -#: ../../workshops/financial.rst:44 ../../workshops/scientific-computing.rst:45 +#: ../../workshops/financial.rst:44 +#: ../../workshops/scientific-computing.rst:45 msgid "Learner profile" msgstr "" #: ../../workshops/financial.rst:46 -msgid "" -"This workshop is intended for people interested in finance who want to " -"take their first steps in Financial Analysis using Python and Spyder." +msgid "This workshop is intended for people interested in finance who want to take their first steps in Financial Analysis using Python and Spyder." msgstr "" -#: ../../workshops/financial.rst:52 ../../workshops/scientific-computing.rst:53 +#: ../../workshops/financial.rst:52 +#: ../../workshops/scientific-computing.rst:53 msgid "Intro" msgstr "" #: ../../workshops/financial.rst:54 -msgid "" -"In this workshop we will obtain financial data in real-time from `Yahoo! " -"Finance`_ API and explore financial portfolios using Econometrics and " -"computational tools." +msgid "In this workshop we will obtain financial data in real-time from `Yahoo! Finance`_ API and explore financial portfolios using Econometrics and computational tools." msgstr "" #: ../../workshops/financial.rst:58 @@ -125,24 +102,15 @@ msgid "Why use Python for financial analysis?" msgstr "" #: ../../workshops/financial.rst:60 -msgid "" -"Real-time analysis of historical and current financial data is essential " -"for those investing in financial instruments. Python has a number of " -"features that make it ideal for financial tasks:" +msgid "Real-time analysis of historical and current financial data is essential for those investing in financial instruments. Python has a number of features that make it ideal for financial tasks:" msgstr "" #: ../../workshops/financial.rst:62 -msgid "" -"It is easy to learn for anyone, whether they have previous programming " -"experience or not" +msgid "It is easy to learn for anyone, whether they have previous programming experience or not" msgstr "" #: ../../workshops/financial.rst:63 -msgid "" -"It has a variety of specialized mathematical and statistical libraries " -"(`SciPy `_, `NumPy `_, `Pandas " -"`_) that are commonly used for financial " -"analysis" +msgid "It has a variety of specialized mathematical and statistical libraries (`SciPy `_, `NumPy `_, `Pandas `_) that are commonly used for financial analysis" msgstr "" #: ../../workshops/financial.rst:64 @@ -150,22 +118,16 @@ msgid "It can be connected to APIs for loading financial data in real time" msgstr "" #: ../../workshops/financial.rst:65 -msgid "" -"It is the programming language with the most resources for machine " -"learning (supervised learning, unsupervised learning, reinforcement " -"learning), which is one of the most useful tools for Econometrics " -"nowadays" +msgid "It is the programming language with the most resources for machine learning (supervised learning, unsupervised learning, reinforcement learning), which is one of the most useful tools for Econometrics nowadays" msgstr "" -#: ../../workshops/financial.rst:66 ../../workshops/scientific-computing.rst:68 +#: ../../workshops/financial.rst:66 +#: ../../workshops/scientific-computing.rst:68 msgid "It has excellent libraries for plotting" msgstr "" #: ../../workshops/financial.rst:67 -msgid "" -"You can use resources such as `Google Colab " -"`_ or `Binder `_" -" to do your analysis in the cloud." +msgid "You can use resources such as `Google Colab `_ or `Binder `_ to do your analysis in the cloud." msgstr "" #: ../../workshops/financial.rst:71 @@ -173,23 +135,16 @@ msgid "Why should I use an IDE?" msgstr "" #: ../../workshops/financial.rst:73 -msgid "" -"Although you can use Python without an IDE (Integrated Development " -"Environment), you will work much better with one. Spyder is a Scientific " -"Integrated Development Environment written in Python, and designed by and" -" for scientists, engineers, and data analysts. Spyder's capabilities and " -"its integration with Python make it perfect for financial analysis." +msgid "Although you can use Python without an IDE (Integrated Development Environment), you will work much better with one. Spyder is a Scientific Integrated Development Environment written in Python, and designed by and for scientists, engineers, and data analysts. Spyder's capabilities and its integration with Python make it perfect for financial analysis." msgstr "" #: ../../workshops/financial.rst:77 msgid "Introduction to financial analysis with Spyder" msgstr "" -#: ../../workshops/financial.rst:79 ../../workshops/scientific-computing.rst:96 -msgid "" -"If you're not familiar with Spyder, we recommend you start with our " -":doc:`Quickstart<../quickstart>`. But if you want a summary, here's a " -"quick overview." +#: ../../workshops/financial.rst:79 +#: ../../workshops/scientific-computing.rst:96 +msgid "If you're not familiar with Spyder, we recommend you start with our :doc:`Quickstart<../quickstart>`. But if you want a summary, here's a quick overview." msgstr "" #: ../../workshops/financial.rst:83 @@ -203,12 +158,7 @@ msgstr "" #: ../../workshops/financial.rst:89 #: ../../workshops/scientific-computing.rst:106 -msgid "" -"The :doc:`Editor<../panes/editor>` is the place where you write your code" -" and save it as a file (script). It allows you to easily persist your " -"work. This is where you write the code you want to keep from the data " -"analysis you do in IPython Console. **Here you will also be able to read," -" edit and run the code from this workshop**." +msgid "The :doc:`Editor<../panes/editor>` is the place where you write your code and save it as a file (script). It allows you to easily persist your work. This is where you write the code you want to keep from the data analysis you do in IPython Console. **Here you will also be able to read, edit and run the code from this workshop**." msgstr "" #: ../../workshops/financial.rst:93 @@ -218,18 +168,12 @@ msgstr "" #: ../../workshops/financial.rst:95 #: ../../workshops/scientific-computing.rst:112 -msgid "" -"The :doc:`IPython Console<../panes/ipythonconsole>` is the Spyder's " -"component where you write chunks of code that you want to experiment " -"with. **In this workshop, we are going to give you pieces of code that " -"you can copy and run in this console**." +msgid "The :doc:`IPython Console<../panes/ipythonconsole>` is the Spyder's component where you write chunks of code that you want to experiment with. **In this workshop, we are going to give you pieces of code that you can copy and run in this console**." msgstr "" #: ../../workshops/financial.rst:97 #: ../../workshops/scientific-computing.rst:114 -msgid "" -"In essence, the IPython Console allows you to execute commands and " -"interact with data using Python." +msgid "In essence, the IPython Console allows you to execute commands and interact with data using Python." msgstr "" #: ../../workshops/financial.rst:101 @@ -239,18 +183,11 @@ msgstr "" #: ../../workshops/financial.rst:103 #: ../../workshops/scientific-computing.rst:120 -msgid "" -"The :doc:`Variable Explorer<../panes/variableexplorer>` is one of " -"Spyder's best features. It allows you to interactively browse and manage " -"the objects generated in the code of the currently selected " -":doc:`../panes/ipythonconsole` session." +msgid "The :doc:`Variable Explorer<../panes/variableexplorer>` is one of Spyder's best features. It allows you to interactively browse and manage the objects generated in the code of the currently selected :doc:`../panes/ipythonconsole` session." msgstr "" #: ../../workshops/financial.rst:105 -msgid "" -"The Variable Explorer is one of the most frequently used components in " -"this workshop. **This is the pane where we will observe the data and most" -" of the results of the analysis, except for the plots**." +msgid "The Variable Explorer is one of the most frequently used components in this workshop. **This is the pane where we will observe the data and most of the results of the analysis, except for the plots**." msgstr "" #: ../../workshops/financial.rst:109 @@ -259,12 +196,7 @@ msgid "Plots pane" msgstr "" #: ../../workshops/financial.rst:111 -msgid "" -"The :doc:`Plots pane <../panes/plots>` shows all the static graphs and " -"images created in your IPython Console session. **All plots generated by " -"the code will appear in this component**. This pane also allows you to " -"save each graphic in a local file or copy it to the clipboard to share it" -" with other people." +msgid "The :doc:`Plots pane <../panes/plots>` shows all the static graphs and images created in your IPython Console session. **All plots generated by the code will appear in this component**. This pane also allows you to save each graphic in a local file or copy it to the clipboard to share it with other people." msgstr "" #: ../../workshops/financial.rst:117 @@ -274,10 +206,7 @@ msgstr "" #: ../../workshops/financial.rst:119 #: ../../workshops/scientific-computing.rst:142 -msgid "" -"Before starting, you must have installed some packages and libraries " -"needed to run the code. We recommend you to install these requirements in" -" a virtual environment. Here we explain step by step how to do it." +msgid "Before starting, you must have installed some packages and libraries needed to run the code. We recommend you to install these requirements in a virtual environment. Here we explain step by step how to do it." msgstr "" #: ../../workshops/financial.rst:123 @@ -286,9 +215,7 @@ msgstr "" #: ../../workshops/financial.rst:125 #: ../../workshops/scientific-computing.rst:148 -msgid "" -"If you would like to have Spyder in a dedicated environment to update it " -"separately from your other packages and avoid any conflicts, you can." +msgid "If you would like to have Spyder in a dedicated environment to update it separately from your other packages and avoid any conflicts, you can." msgstr "" #: ../../workshops/financial.rst:127 @@ -297,10 +224,7 @@ msgid "You can set up your environment in two different ways." msgstr "" #: ../../workshops/financial.rst:131 -msgid "" -"We recommend creating the virtual environment with Anaconda (or " -"Miniconda) as it integrates seamlessly with Spyder. You can find " -"installation instructions in `Anaconda documentation`_." +msgid "We recommend creating the virtual environment with Anaconda (or Miniconda) as it integrates seamlessly with Spyder. You can find installation instructions in `Anaconda documentation`_." msgstr "" #: ../../workshops/financial.rst:137 @@ -308,23 +232,15 @@ msgid "With commands" msgstr "" #: ../../workshops/financial.rst:139 -msgid "" -"Just run the following command in your Anaconda Prompt (Windows) or " -"terminal (other platforms), to create a new environment called " -"``financial-analysis``:" +msgid "Just run the following command in your Anaconda Prompt (Windows) or terminal (other platforms), to create a new environment called ``financial-analysis``:" msgstr "" #: ../../workshops/financial.rst:145 -msgid "" -"To install Spyder's optional dependencies as well for full functionality," -" use the following command:" +msgid "To install Spyder's optional dependencies as well for full functionality, use the following command:" msgstr "" #: ../../workshops/financial.rst:156 -msgid "" -"Spyder now offers :ref:`install-standalone` for Windows and macOS, making" -" it easier to get up and running with the application without having to " -"download Anaconda or manually install it in your existing environment." +msgid "Spyder now offers :ref:`install-standalone` for Windows and macOS, making it easier to get up and running with the application without having to download Anaconda or manually install it in your existing environment." msgstr "" #: ../../workshops/financial.rst:160 @@ -332,21 +248,15 @@ msgid "Download the datasets" msgstr "" #: ../../workshops/financial.rst:162 -msgid "" -"Although during the workshop we will explain how to use some APIs to " -"download up-to-date data, you can also download the datasets in csv " -"format from `this link " -"`_." +msgid "Although during the workshop we will explain how to use some APIs to download up-to-date data, you can also download the datasets in csv format from `this link `_." msgstr "" #: ../../workshops/financial.rst:164 -msgid "" -"To follow this workshop you do not need to create a new directory. " -"However, if you have downloaded the data and want to use it instead of " -"the APIs, you must set the directory that has the downloaded data as the " -"working directory. In order to do this, check that the working directory " -"is correct. You should see in the upper right corner the path to the " -"directory where you have the downloaded data. Something like this:" +msgid "To follow this workshop you do not need to create a new directory. However, if you have downloaded the data and want to use it instead of the APIs, you must set the directory that has the downloaded data as the working directory. In order to do this, check that the working directory is correct. You should see in the upper right corner the path to the directory where you have the downloaded data. Something like this:" +msgstr "" + +#: ../../workshops/financial.rst:166 +msgid "Spyder's Working Directory plugin showing the working directory downloaded-data-dir" msgstr "" #: ../../workshops/financial.rst:171 @@ -354,11 +264,11 @@ msgid "Setting up the virtual environment in Spyder" msgstr "" #: ../../workshops/financial.rst:173 -msgid "" -"Let's check that the virtual environment we created is enabled in Spyder." -" Go to :guilabel:`Preferences > Python interpreter`, and use the dropdown" -" below :guilabel:`Use the following Python interpreter` to choose your " -"virtual environment. You should see something like this:" +msgid "Let's check that the virtual environment we created is enabled in Spyder. Go to :guilabel:`Preferences > Python interpreter`, and use the dropdown below :guilabel:`Use the following Python interpreter` to choose your virtual environment. You should see something like this:" +msgstr "" + +#: ../../workshops/financial.rst:175 +msgid "Screenshot on how to set up environment in Spyder's Preferences" msgstr "" #: ../../workshops/financial.rst:178 @@ -372,12 +282,7 @@ msgid "Download the code" msgstr "" #: ../../workshops/financial.rst:184 -msgid "" -"Although the workshop is designed for you to write the code in the " -"IPython Console, we have created a file that you can download " -":download:`here `. This script provides all the " -"code you will write in this workshop, and you can use it as a guide if " -"you get lost." +msgid "Although the workshop is designed for you to write the code in the IPython Console, we have created a file that you can download :download:`here `. This script provides all the code you will write in this workshop, and you can use it as a guide if you get lost." msgstr "" #: ../../workshops/financial.rst:190 @@ -385,28 +290,25 @@ msgid "Obtain financial data" msgstr "" #: ../../workshops/financial.rst:192 -msgid "" -"When it comes to finance, being up to date is very important. So we are " -"going to use a Python library that allows us to get updated historical " -"Stock Market records from `Yahoo! Finance`_ API. In this way, we will be " -"able to download data in the period of time we are interested in " -"analyzing." +msgid "When it comes to finance, being up to date is very important. So we are going to use a Python library that allows us to get updated historical Stock Market records from `Yahoo! Finance`_ API. In this way, we will be able to download data in the period of time we are interested in analyzing." msgstr "" #: ../../workshops/financial.rst:197 #: ../../workshops/scientific-computing.rst:261 -msgid "" -"Remember to type and run all code for this workshop in the \"IPython " -"Console\" at the bottom right of Spyder." +msgid "Remember to type and run all code for this workshop in the \"IPython Console\" at the bottom right of Spyder." +msgstr "" + +#: ../../workshops/financial.rst:199 +msgid "Screenshot IPython Console location in Spyder IDE" msgstr "" #: ../../workshops/financial.rst:202 -msgid "" -"You can also write your code in the Editor (the pane that occupies the " -"entire left side of Spyder). If you use the Editor, you can run the code " -"by selecting it and pressing the :guilabel:`Run selection or current " -"line` button in the :guilabel:`Run toolbar` or by pressing the :kbd:`F9` " -"key." +msgid "You can also write your code in the Editor (the pane that occupies the entire left side of Spyder). If you use the Editor, you can run the code by selecting it and pressing the :guilabel:`Run selection or current line` button in the :guilabel:`Run toolbar` or by pressing the :kbd:`F9` key." +msgstr "" + +#: ../../workshops/financial.rst:204 +#: ../../workshops/scientific-computing.rst:268 +msgid "Editor location in Spyder IDE" msgstr "" #: ../../workshops/financial.rst:207 @@ -415,23 +317,15 @@ msgid "To get started, import the libraries." msgstr "" #: ../../workshops/financial.rst:222 -msgid "" -"The first group of imports is for basic operations. The second " -"(``Historic_Crypto`` and ``yfinance``) imports the libraries that we will" -" use to download financial data." +msgid "The first group of imports is for basic operations. The second (``Historic_Crypto`` and ``yfinance``) imports the libraries that we will use to download financial data." msgstr "" #: ../../workshops/financial.rst:224 -msgid "" -"Let's start exploring libraries with an example. We are going to get " -"financial information about Netflix with one line of code:" +msgid "Let's start exploring libraries with an example. We are going to get financial information about Netflix with one line of code:" msgstr "" #: ../../workshops/financial.rst:230 -msgid "" -"We have used the ``Ticker`` class of the ``yfinance`` library to create a" -" ``netflix`` object. This object contains attributes and methods that we " -"can query to obtain various types of information." +msgid "We have used the ``Ticker`` class of the ``yfinance`` library to create a ``netflix`` object. This object contains attributes and methods that we can query to obtain various types of information." msgstr "" #: ../../workshops/financial.rst:234 @@ -439,51 +333,47 @@ msgid "General stock information" msgstr "" #: ../../workshops/financial.rst:236 -msgid "" -"If you want to know which methods and attributes you can query, you can " -"do so with the built-in ``help()`` function." +msgid "If you want to know which methods and attributes you can query, you can do so with the built-in ``help()`` function." msgstr "" #: ../../workshops/financial.rst:238 -msgid "" -"You can also type the name of the object (``netflix``) in the console, " -"then type a period and hit the Tab key once. IPython suggestions will " -"then appear to help you navigate the object:" +msgid "You can also type the name of the object (``netflix``) in the console, then type a period and hit the Tab key once. IPython suggestions will then appear to help you navigate the object:" +msgstr "" + +#: ../../workshops/financial.rst:240 +msgid "IPython Console auto-suggestions" msgstr "" #: ../../workshops/financial.rst:243 -msgid "" -"For example, we can obtain general information with the ``info`` property" -" of the object." +msgid "For example, we can obtain general information with the ``info`` property of the object." msgstr "" #: ../../workshops/financial.rst:249 -msgid "" -"We can observe the result in the Variable Explorer, in the " -"``netflix_info`` variable." +msgid "We can observe the result in the Variable Explorer, in the ``netflix_info`` variable." +msgstr "" + +#: ../../workshops/financial.rst:251 +msgid "First variable in Variable Explorer" msgstr "" #: ../../workshops/financial.rst:254 -msgid "" -"If we double-click on it, a new window with detailed information will be " -"displayed." +msgid "If we double-click on it, a new window with detailed information will be displayed." +msgstr "" + +#: ../../workshops/financial.rst:256 +msgid "Python dict example in Variable Explorer" msgstr "" #: ../../workshops/financial.rst:259 -msgid "" -"In that window we can see a Python dictionary in which each key has a " -"value assigned to it. Each type of value is represented by a distinctive " -"color. For example, we see that Netflix is an Entertainment industry, the" -" summary of the business type, among other indicators. The Variable " -"Explorer is a very convenient way to view these types of results. We can " -"compare it to viewing them in the IPython Console with the ``pprint`` " -"function:" +msgid "In that window we can see a Python dictionary in which each key has a value assigned to it. Each type of value is represented by a distinctive color. For example, we see that Netflix is an Entertainment industry, the summary of the business type, among other indicators. The Variable Explorer is a very convenient way to view these types of results. We can compare it to viewing them in the IPython Console with the ``pprint`` function:" +msgstr "" + +#: ../../workshops/financial.rst:265 +msgid "netflix_info output in IPython Console" msgstr "" #: ../../workshops/financial.rst:268 -msgid "" -"Although ``pprint`` displays all the information, it is easier to view it" -" in the Variable Explorer." +msgid "Although ``pprint`` displays all the information, it is easier to view it in the Variable Explorer." msgstr "" #: ../../workshops/financial.rst:272 @@ -491,24 +381,19 @@ msgid "Historical stock data" msgstr "" #: ../../workshops/financial.rst:274 -msgid "" -"We can download in a dataset the history of a stock with the following " -"line of code:" +msgid "We can download in a dataset the history of a stock with the following line of code:" msgstr "" #: ../../workshops/financial.rst:280 -msgid "" -"We can see a summary and more details of this dataset in the Variable " -"Explorer. It appears as a DataFrame object, with 7 columns and thousands " -"of rows. If we double-click on it we will see the historical records of " -"Netflix stock organized by ascending dates." +msgid "We can see a summary and more details of this dataset in the Variable Explorer. It appears as a DataFrame object, with 7 columns and thousands of rows. If we double-click on it we will see the historical records of Netflix stock organized by ascending dates." +msgstr "" + +#: ../../workshops/financial.rst:282 +msgid "Netflix historical operations" msgstr "" #: ../../workshops/financial.rst:285 -msgid "" -"Throughout this workshop we will use this historical information to " -"compare, with various normative financial theories, different types of " -"financial portfolios." +msgid "Throughout this workshop we will use this historical information to compare, with various normative financial theories, different types of financial portfolios." msgstr "" #: ../../workshops/financial.rst:291 @@ -516,22 +401,11 @@ msgid "First portfolio" msgstr "" #: ../../workshops/financial.rst:293 -msgid "" -"Let's build our first stock investment portfolio! Say we are interested " -"in investing in technology, and we want to know what performance can be " -"obtained by putting money into some of the \"heavyweights\" in this " -"industry." +msgid "Let's build our first stock investment portfolio! Say we are interested in investing in technology, and we want to know what performance can be obtained by putting money into some of the \"heavyweights\" in this industry." msgstr "" #: ../../workshops/financial.rst:295 -msgid "" -"To measure the performance of our first portfolio we are going to use a " -"classic theory in the world of finance: `mean-variance portfolio (MVP) " -"theory`_. This model assumes that investors only care about expected " -"returns and the variance of such returns. The analysis is based entirely " -"on statistical measures based on a time series of share prices, such as " -"periodic mean returns and the variances of those returns with the same " -"periodicity." +msgid "To measure the performance of our first portfolio we are going to use a classic theory in the world of finance: `mean-variance portfolio (MVP) theory`_. This model assumes that investors only care about expected returns and the variance of such returns. The analysis is based entirely on statistical measures based on a time series of share prices, such as periodic mean returns and the variances of those returns with the same periodicity." msgstr "" #: ../../workshops/financial.rst:301 @@ -539,72 +413,51 @@ msgid "Prepare portfolio data" msgstr "" #: ../../workshops/financial.rst:303 -msgid "" -"Before we start, let's run some lines of code to style the plots. These " -"lines are optional, but we recommend that you run them so that the " -"graphics look like the screenshots we present in this workshop." +msgid "Before we start, let's run some lines of code to style the plots. These lines are optional, but we recommend that you run them so that the graphics look like the screenshots we present in this workshop." msgstr "" #: ../../workshops/financial.rst:312 -msgid "" -"Suppose we want to measure the performance of a portfolio consisting of " -"Google, Apple, Microsoft, Netflix and Amazon stocks. Let's call this set " -"``SYMBOLS_1``." +msgid "Suppose we want to measure the performance of a portfolio consisting of Google, Apple, Microsoft, Netflix and Amazon stocks. Let's call this set ``SYMBOLS_1``." msgstr "" #: ../../workshops/financial.rst:320 -msgid "" -"If you search for ``SYMBOLS_1`` in Variable Explorer you will not find " -"it: Python interprets this element not as a variable, but as a " -"**constant**. This is because the name is written with uppercase letters " -"(no letter is lowercase). By default, the Variable Explorer doesn't show " -"this, but actually you can change the settings in the " -":guilabel:`Preferences` to be able to see these constants." +msgid "If you search for ``SYMBOLS_1`` in Variable Explorer you will not find it: Python interprets this element not as a variable, but as a **constant**. This is because the name is written with uppercase letters (no letter is lowercase). By default, the Variable Explorer doesn't show this, but actually you can change the settings in the :guilabel:`Preferences` to be able to see these constants." msgstr "" #: ../../workshops/financial.rst:322 -msgid "" -"We are going to download the historical data for this portfolio. To do " -"this, we are going to use the ``yfinance`` ``download()`` function, which" -" takes as its first argument a string with the symbols (``SYMBOLS_1``) " -"defined above. The rest of the arguments are the start date " -"(``start=\"2012-01-01\"``), the end date (``end=\"2021-01-01\"``) and how" -" the data will be grouped (``group_by=\"Ticker\"``)." +msgid "We are going to download the historical data for this portfolio. To do this, we are going to use the ``yfinance`` ``download()`` function, which takes as its first argument a string with the symbols (``SYMBOLS_1``) defined above. The rest of the arguments are the start date (``start=\"2012-01-01\"``), the end date (``end=\"2021-01-01\"``) and how the data will be grouped (``group_by=\"Ticker\"``)." msgstr "" #: ../../workshops/financial.rst:328 -msgid "" -"The last argument (``group_by=\"Ticker\"``) groups the information mainly" -" by stock. Otherwise, the primary grouping is done by the type of " -"information (e.g., opening price, closing price, volume traded) of the " -"transactions. In the following image you can see the differences (above " -"is the default organization and below is the grouping by \"Ticker\")." +msgid "The last argument (``group_by=\"Ticker\"``) groups the information mainly by stock. Otherwise, the primary grouping is done by the type of information (e.g., opening price, closing price, volume traded) of the transactions. In the following image you can see the differences (above is the default organization and below is the grouping by \"Ticker\")." +msgstr "" + +#: ../../workshops/financial.rst:330 +msgid "Data grouped by Ticker" msgstr "" #: ../../workshops/financial.rst:334 -msgid "" -"The historical data has been downloaded as a Pandas DataFrame. We can " -"explore this data in the variable ``data_1`` in the Variable Explorer." +msgid "The historical data has been downloaded as a Pandas DataFrame. We can explore this data in the variable ``data_1`` in the Variable Explorer." +msgstr "" + +#: ../../workshops/financial.rst:336 +msgid "Portfolio 1 historical data" msgstr "" #: ../../workshops/financial.rst:339 -msgid "" -"Let's change the formatting of the data a bit so that the symbols appear " -"as the column names, and the Ticker moves from columns to rows. We will " -"do this with the ``stack()`` operation of the DataFrame." +msgid "Let's change the formatting of the data a bit so that the symbols appear as the column names, and the Ticker moves from columns to rows. We will do this with the ``stack()`` operation of the DataFrame." +msgstr "" + +#: ../../workshops/financial.rst:345 +msgid "Portfolio 1 historical data stacked by Ticker" msgstr "" #: ../../workshops/financial.rst:348 -msgid "" -"From the Ticker we are only interested in the daily closing price. So we " -"will leave only the values for ``\"Close\"`` and eliminate the Ticker " -"column afterwards." +msgid "From the Ticker we are only interested in the daily closing price. So we will leave only the values for ``\"Close\"`` and eliminate the Ticker column afterwards." msgstr "" #: ../../workshops/financial.rst:354 -msgid "" -"You will notice that there is a new DataFrame in the Variable Explorer " -"called ``close_data_1`` with 2,265 rows and 5 columns." +msgid "You will notice that there is a new DataFrame in the Variable Explorer called ``close_data_1`` with 2,265 rows and 5 columns." msgstr "" #: ../../workshops/financial.rst:358 @@ -612,92 +465,55 @@ msgid "A first glance at the portfolio" msgstr "" #: ../../workshops/financial.rst:360 -msgid "" -"We want to see how our portfolio would have performed if we had invested " -"in it from 2012 to early 2021. How could we obtain this measurement? " -"Let's look at the monthly closing prices of each stock. To do this we " -"will do an automatic resample of the data. And then we will calculate the" -" change in relative frequencies (percentages)." +msgid "We want to see how our portfolio would have performed if we had invested in it from 2012 to early 2021. How could we obtain this measurement? Let's look at the monthly closing prices of each stock. To do this we will do an automatic resample of the data. And then we will calculate the change in relative frequencies (percentages)." msgstr "" #: ../../workshops/financial.rst:362 -msgid "" -"The resampling will be performed with the ``resample(\"M\")`` method and " -"the calculation of percentages with the ``pct_change()`` method. The " -"result will be stored in the ``monthly_data_1`` variable." +msgid "The resampling will be performed with the ``resample(\"M\")`` method and the calculation of percentages with the ``pct_change()`` method. The result will be stored in the ``monthly_data_1`` variable." msgstr "" #: ../../workshops/financial.rst:368 -msgid "" -"Since each stock is a column, we can use the ``mean()`` method on the " -"DataFrame to see the results." +msgid "Since each stock is a column, we can use the ``mean()`` method on the DataFrame to see the results." msgstr "" #: ../../workshops/financial.rst:383 -msgid "" -"Remember that this closing information represents the relative growth of " -"each stock, not its closing price in any currency." +msgid "Remember that this closing information represents the relative growth of each stock, not its closing price in any currency." msgstr "" #: ../../workshops/financial.rst:385 -msgid "" -"As we can see, all the results are positive, so this portfolio has been " -"profitable over the years. In relative terms, the biggest gains would " -"come from Netflix (0.4 percent). These percentages show an average of the" -" monthly variation of the stock price. But how stable have that prices " -"been? To find this out, we can calculate the standard deviation of stock " -"price growth:" +msgid "As we can see, all the results are positive, so this portfolio has been profitable over the years. In relative terms, the biggest gains would come from Netflix (0.4 percent). These percentages show an average of the monthly variation of the stock price. But how stable have that prices been? To find this out, we can calculate the standard deviation of stock price growth:" msgstr "" #: ../../workshops/financial.rst:398 -msgid "" -"The highest volatility is found in Netflix (0.1454), which indicates that" -" its price, despite being the fastest growing, has also had a lot of " -"variation during these years. The most stable price, on the other hand, " -"has been Microsoft's (0.0583)." +msgid "The highest volatility is found in Netflix (0.1454), which indicates that its price, despite being the fastest growing, has also had a lot of variation during these years. The most stable price, on the other hand, has been Microsoft's (0.0583)." msgstr "" #: ../../workshops/financial.rst:400 -msgid "" -"A good way to observe both growth and variability is to draw a time-" -"series plot. To scale the values, we are going to divide the relative " -"frequency of the closing price of the actions by the initial value it has" -" in the dataframe ``close_data_1`` (these initial values can be found " -"with ``close_data_1.iloc[0])``). The plot is drawn with the ``plot()`` " -"method of the Pandas DataFrame (to which we pass as arguments the size of" -" the plot and the plot title)." +msgid "A good way to observe both growth and variability is to draw a time-series plot. To scale the values, we are going to divide the relative frequency of the closing price of the actions by the initial value it has in the dataframe ``close_data_1`` (these initial values can be found with ``close_data_1.iloc[0])``). The plot is drawn with the ``plot()`` method of the Pandas DataFrame (to which we pass as arguments the size of the plot and the plot title)." +msgstr "" + +#: ../../workshops/financial.rst:406 +msgid "Portfolio 1 daily stock price" msgstr "" #: ../../workshops/financial.rst:411 -msgid "" -"You will be able to see the graph in the Plots pane. On the left, you " -"will see the plot in detail. On the right, a stack will be created with " -"all the plots that are generated both in the Console and by running the " -"code directly in the Editor. You can copy, delete or save the plot to " -"disk by clicking on it with the right mouse button or trackpad." +msgid "You will be able to see the graph in the Plots pane. On the left, you will see the plot in detail. On the right, a stack will be created with all the plots that are generated both in the Console and by running the code directly in the Editor. You can copy, delete or save the plot to disk by clicking on it with the right mouse button or trackpad." msgstr "" #: ../../workshops/financial.rst:413 -msgid "" -"The above time-series plot clearly shows the growth of all stocks, " -"particularly Netflix. The high volatility discussed above can also be " -"seen. For example, it can be seen from the plots that, due to high " -"volatility, investing in Netflix in the years 2014 and 2019 left " -"virtually no profit (if shares were bought at the beginning of the year " -"and sold right at the end)." +msgid "The above time-series plot clearly shows the growth of all stocks, particularly Netflix. The high volatility discussed above can also be seen. For example, it can be seen from the plots that, due to high volatility, investing in Netflix in the years 2014 and 2019 left virtually no profit (if shares were bought at the beginning of the year and sold right at the end)." msgstr "" #: ../../workshops/financial.rst:415 -msgid "" -"We can also plot with the ``plot()`` method the DataFrame we already have" -" with the monthly data. To do this, we will add 1 to all the values and " -"calculate the accumulated product with the ``cumprod()`` method:" +msgid "We can also plot with the ``plot()`` method the DataFrame we already have with the monthly data. To do this, we will add 1 to all the values and calculate the accumulated product with the ``cumprod()`` method:" +msgstr "" + +#: ../../workshops/financial.rst:421 +msgid "Portfolio 1 monthly stock price" msgstr "" #: ../../workshops/financial.rst:424 -msgid "" -"This plot of the monthly data is \"smoother\" than the plot of the daily " -"data." +msgid "This plot of the monthly data is \"smoother\" than the plot of the daily data." msgstr "" #: ../../workshops/financial.rst:428 @@ -705,67 +521,35 @@ msgid "Returns and volatility" msgstr "" #: ../../workshops/financial.rst:430 -msgid "" -"Remember that in the *mean-variance portfolio theory* what matters are " -"the expected returns and variances. To calculate these returns, we will " -"divide the price of the stock on one day by the price of the same stock " -"on the previous day. We will do this by dividing the ``close_data_1`` " -"DataFrame by a version of itself in which we shift each record one date " -"backwards (``shift(1)``). For example, if on the date 2012-01-03 a stock " -"was valued at 1, and on the next day (2012-01-02), it was valued at 2, " -"then in our shifted dataset, on the day 2012-01-03 the stock would be " -"worth 1. In this way, we would divide 1 by 2. And so on with all the " -"values of all the shares. We will also normalize the results by passing " -"them to a logarithmic scale with ``np.log()``." +msgid "Remember that in the *mean-variance portfolio theory* what matters are the expected returns and variances. To calculate these returns, we will divide the price of the stock on one day by the price of the same stock on the previous day. We will do this by dividing the ``close_data_1`` DataFrame by a version of itself in which we shift each record one date backwards (``shift(1)``). For example, if on the date 2012-01-03 a stock was valued at 1, and on the next day (2012-01-02), it was valued at 2, then in our shifted dataset, on the day 2012-01-03 the stock would be worth 1. In this way, we would divide 1 by 2. And so on with all the values of all the shares. We will also normalize the results by passing them to a logarithmic scale with ``np.log()``." msgstr "" #: ../../workshops/financial.rst:434 -msgid "" -"Trend lines are more easily drawn in logarithmic scale because they tend " -"to fit better to the minimums. In addition, the logarithmic scale gives a" -" more realistic view of price movements." +msgid "Trend lines are more easily drawn in logarithmic scale because they tend to fit better to the minimums. In addition, the logarithmic scale gives a more realistic view of price movements." msgstr "" #: ../../workshops/financial.rst:440 -msgid "" -"In the variable ``rets_1`` you can see the resulting DataFrame. If you " -"double-click on the variable name in the Variable Explorer, you will see " -"that there are positive values (the share price increased) and negative " -"values (the price decreased at the time of closing)." +msgid "In the variable ``rets_1`` you can see the resulting DataFrame. If you double-click on the variable name in the Variable Explorer, you will see that there are positive values (the share price increased) and negative values (the price decreased at the time of closing)." +msgstr "" + +#: ../../workshops/financial.rst:442 +msgid "Portfolio 1 daily returns" msgstr "" #: ../../workshops/financial.rst:445 -msgid "" -"In addition to the returns of each stock, we will need the specific " -"weight of each stock in the portfolio, i.e., how many shares of each " -"company are in the portfolio. In this workshop we will assume that there " -"is one share of each company and, therefore, the weights will be " -"distributed equally." +msgid "In addition to the returns of each stock, we will need the specific weight of each stock in the portfolio, i.e., how many shares of each company are in the portfolio. In this workshop we will assume that there is one share of each company and, therefore, the weights will be distributed equally." msgstr "" #: ../../workshops/financial.rst:449 -msgid "" -"A stock is a financial security that represents that you own a part of a " -"company (whatever the size of this part). A share, on the other hand, is " -"the smallest unit of denomination of a stock. A stock is composed of one " -"or several shares." +msgid "A stock is a financial security that represents that you own a part of a company (whatever the size of this part). A share, on the other hand, is the smallest unit of denomination of a stock. A stock is composed of one or several shares." msgstr "" #: ../../workshops/financial.rst:451 -msgid "" -"This weight will be a vector (Python list) composed of the relative " -"weight (between 0 and 1) of each stock in the portfolio. The sum of these" -" weights has to be 1. Since we will assume that each stock is a single " -"share, the distribution will be equal: ``[0.2, 0.2, 0.2, 0.2, 0.2]``." +msgid "This weight will be a vector (Python list) composed of the relative weight (between 0 and 1) of each stock in the portfolio. The sum of these weights has to be 1. Since we will assume that each stock is a single share, the distribution will be equal: ``[0.2, 0.2, 0.2, 0.2, 0.2]``." msgstr "" #: ../../workshops/financial.rst:457 -msgid "" -"With this information we can calculate the expected return of this " -"portfolio. The math is simple: this is given by the dot product of the " -"portfolio weights vector and the vector of expected returns. This result " -"must be multiplied by the number of days for which the return is to be " -"calculated (a year has approximately 252 stock price closings)." +msgid "With this information we can calculate the expected return of this portfolio. The math is simple: this is given by the dot product of the portfolio weights vector and the vector of expected returns. This result must be multiplied by the number of days for which the return is to be calculated (a year has approximately 252 stock price closings)." msgstr "" #: ../../workshops/financial.rst:459 @@ -773,21 +557,11 @@ msgid "Let's put all this into a function:" msgstr "" #: ../../workshops/financial.rst:466 -msgid "" -"Let's look at the expected return of this portfolio if we hold it for one" -" year:" +msgid "Let's look at the expected return of this portfolio if we hold it for one year:" msgstr "" #: ../../workshops/financial.rst:474 -#, python-format -msgid "" -"An expected gain of almost 30% in one year. Not bad, right? But don't " -"forget the other side of this coin: volatility. This calculation is a bit" -" more complex. First, the dot product of the annualized covariance of the" -" returns (this is multiplied by the number of trading days in a year) and" -" the weights is calculated. Then the dot product of the weights and the " -"previous result is obtained. Finally, the square root of this result is " -"extracted. Let's implement this into a function as well." +msgid "An expected gain of almost 30% in one year. Not bad, right? But don't forget the other side of this coin: volatility. This calculation is a bit more complex. First, the dot product of the annualized covariance of the returns (this is multiplied by the number of trading days in a year) and the weights is calculated. Then the dot product of the weights and the previous result is obtained. Finally, the square root of this result is extracted. Let's implement this into a function as well." msgstr "" #: ../../workshops/financial.rst:481 @@ -795,9 +569,7 @@ msgid "Let's see how our portfolio performs with respect to its volatility:" msgstr "" #: ../../workshops/financial.rst:489 -msgid "" -"If high return is desirable, high volatility is undesirable. The risk of " -"this portfolio is relatively large." +msgid "If high return is desirable, high volatility is undesirable. The risk of this portfolio is relatively large." msgstr "" #: ../../workshops/financial.rst:493 @@ -805,14 +577,7 @@ msgid "Sharpe ratio" msgstr "" #: ../../workshops/financial.rst:495 -msgid "" -"The `Sharpe`_ ratio or index is a measure of portfolio performance. It " -"relates the portfolio's return to its volatility, comparing the " -"expected/realized return with the expected/realized risk. It is " -"calculated as the difference between the actual investment returns and " -"the expected return in a zero-risk situation, divided by the volatility " -"of the investment. **It provides a model of the additional amount of " -"returns received for each additional unit of risk**." +msgid "The `Sharpe`_ ratio or index is a measure of portfolio performance. It relates the portfolio's return to its volatility, comparing the expected/realized return with the expected/realized risk. It is calculated as the difference between the actual investment returns and the expected return in a zero-risk situation, divided by the volatility of the investment. **It provides a model of the additional amount of returns received for each additional unit of risk**." msgstr "" #: ../../workshops/financial.rst:499 @@ -824,33 +589,19 @@ msgid "And let's apply this to our portfolio." msgstr "" #: ../../workshops/financial.rst:516 -msgid "" -"The Sharpe ratio measure is best understood in context: when comparing " -"two or more portfolios, the one with the higher Sharpe ratio provides " -"more profit for the same amount of risk." +msgid "The Sharpe ratio measure is best understood in context: when comparing two or more portfolios, the one with the higher Sharpe ratio provides more profit for the same amount of risk." msgstr "" #: ../../workshops/financial.rst:518 -msgid "" -"We can also use a `Monte Carlo " -"`_ simulation to " -"randomize the weights of each stock in the portfolio so that we can see " -"the range over which the Sharpe ratio can vary. In this way we can plot " -"some scenarios that together will give us a good insight of the " -"relationship between expected returns and expected volatility." +msgid "We can also use a `Monte Carlo `_ simulation to randomize the weights of each stock in the portfolio so that we can see the range over which the Sharpe ratio can vary. In this way we can plot some scenarios that together will give us a good insight of the relationship between expected returns and expected volatility." msgstr "" #: ../../workshops/financial.rst:520 -msgid "" -"We are going to do this with a function that we will explain step by step" -" in the `monte_carlo_sharpe function explained`_ section." +msgid "We are going to do this with a function that we will explain step by step in the `monte_carlo_sharpe function explained`_ section." msgstr "" #: ../../workshops/financial.rst:538 -msgid "" -"You do not need to type the following code in the IPython Console. If you" -" write the function above it will be enough. It is just a code " -"presentation to explain what is inside the function." +msgid "You do not need to type the following code in the IPython Console. If you write the function above it will be enough. It is just a code presentation to explain what is inside the function." msgstr "" #: ../../workshops/financial.rst:542 @@ -858,24 +609,15 @@ msgid "``monte_carlo_sharpe`` function explained" msgstr "" #: ../../workshops/financial.rst:544 -msgid "" -"Let's now break the function down to understand what is happening. First," -" we create a numpy array of length 1,000 and width of the number of " -"shares in the portfolio. Each row of the array has random weights that " -"always add up to 1:" +msgid "Let's now break the function down to understand what is happening. First, we create a numpy array of length 1,000 and width of the number of shares in the portfolio. Each row of the array has random weights that always add up to 1:" msgstr "" #: ../../workshops/financial.rst:552 -msgid "" -"The next section calculates the volatility and returns for the new random" -" weights using a list comprehension. The resulting list is transformed " -"back into a numpy array:" +msgid "The next section calculates the volatility and returns for the new random weights using a list comprehension. The resulting list is transformed back into a numpy array:" msgstr "" #: ../../workshops/financial.rst:559 -msgid "" -"Finally, we obtain the Sharpe ratio by dividing the index 1 " -"(volatilities) by the index 0 (returns) of the numpy array:" +msgid "Finally, we obtain the Sharpe ratio by dividing the index 1 (volatilities) by the index 0 (returns) of the numpy array:" msgstr "" #: ../../workshops/financial.rst:567 @@ -883,10 +625,7 @@ msgid "Using the ``monte_carlo_sharpe`` function" msgstr "" #: ../../workshops/financial.rst:569 -msgid "" -"We use the function to get the simulated returns and volatility of " -"portfolio 1 (``port_1_vr``) and the related Sharpe ratios " -"(``port_1_sr``)." +msgid "We use the function to get the simulated returns and volatility of portfolio 1 (``port_1_vr``) and the related Sharpe ratios (``port_1_sr``)." msgstr "" #: ../../workshops/financial.rst:571 @@ -894,33 +633,27 @@ msgid "Enter the following code in the console." msgstr "" #: ../../workshops/financial.rst:579 -msgid "" -"Remember that the weights are initialized randomly, so each time you run " -"this code you will get different results." +msgid "Remember that the weights are initialized randomly, so each time you run this code you will get different results." msgstr "" #: ../../workshops/financial.rst:581 -msgid "" -"With this we obtain two arrays with 1,000 simulated cases for our " -"portfolio. But the best way to explore this is with a plot." +msgid "With this we obtain two arrays with 1,000 simulated cases for our portfolio. But the best way to explore this is with a plot." msgstr "" #: ../../workshops/financial.rst:593 msgid "You should see in the Plots pane something like this:" msgstr "" +#: ../../workshops/financial.rst:595 +msgid "Portfolio 1 Monte Carlo Sharpe simulation scatter plot" +msgstr "" + #: ../../workshops/financial.rst:598 -msgid "" -"A roughly linear relationship can be observed between returns and " -"volatility: the higher the volatility, the higher the gains. And the " -"Sharpe ratio shows an important amount of variability (it is noticeable " -"in the \"width\" of the line drawn)." +msgid "A roughly linear relationship can be observed between returns and volatility: the higher the volatility, the higher the gains. And the Sharpe ratio shows an important amount of variability (it is noticeable in the \"width\" of the line drawn)." msgstr "" #: ../../workshops/financial.rst:600 -msgid "" -"This seems to be a good portfolio because it has a good performance with " -"a not very large variance." +msgid "This seems to be a good portfolio because it has a good performance with a not very large variance." msgstr "" #: ../../workshops/financial.rst:604 @@ -928,10 +661,7 @@ msgid "Optimal portfolio weights" msgstr "" #: ../../workshops/financial.rst:606 -msgid "" -"Can we use the data obtained to calculate the optimal weights for the " -"portfolio by year? Of course we can. Let's start by delimiting the " -"previous years as variables." +msgid "Can we use the data obtained to calculate the optimal weights for the portfolio by year? Of course we can. Let's start by delimiting the previous years as variables." msgstr "" #: ../../workshops/financial.rst:612 @@ -939,55 +669,27 @@ msgid "We will now write a function to calculate these optimal weights." msgstr "" #: ../../workshops/financial.rst:629 -msgid "" -"Let's describe this function in broad strokes. ``bounds`` indicates the " -"maximum and minimum weights for each stock in the portfolio. The lowest " -"weight will be 0 and the highest weight will be 1 for each stock in the " -"portfolio. ``constraints`` is a function that ensures that the sum of the" -" weights of all actions always adds up to 1. Then a loop is initialized " -"that will segment the data for each year. In the variable ``_rets`` the " -"returns for the specified year are obtained. In ``_opt_w`` the " -"``portfolio_shape()`` function is used to calculate the weights that " -"maximize the Sharpe ratio. This is done with the ``minimize()`` function " -"of SciPy (which takes as arguments the ``portfolio_shape`` function, the " -"actual weights of our stocks in the portfolio, and the ``bounds`` and the" -" ``constraints`` variables). Notice the ``-`` sign before " -"``portfolio_sharpe``? It's because ``minimize()`` aims to find the " -"minimum value of a function relative to a parameter, but we are " -"interested in the maximum, so we make the result of ``portfolio_sharpe`` " -"a negative one." +msgid "Let's describe this function in broad strokes. ``bounds`` indicates the maximum and minimum weights for each stock in the portfolio. The lowest weight will be 0 and the highest weight will be 1 for each stock in the portfolio. ``constraints`` is a function that ensures that the sum of the weights of all actions always adds up to 1. Then a loop is initialized that will segment the data for each year. In the variable ``_rets`` the returns for the specified year are obtained. In ``_opt_w`` the ``portfolio_shape()`` function is used to calculate the weights that maximize the Sharpe ratio. This is done with the ``minimize()`` function of SciPy (which takes as arguments the ``portfolio_shape`` function, the actual weights of our stocks in the portfolio, and the ``bounds`` and the ``constraints`` variables). Notice the ``-`` sign before ``portfolio_sharpe``? It's because ``minimize()`` aims to find the minimum value of a function relative to a parameter, but we are interested in the maximum, so we make the result of ``portfolio_sharpe`` a negative one." msgstr "" #: ../../workshops/financial.rst:631 -msgid "" -"We will use the function we just defined to calculate the optimal weights" -" for each year, and we are going to save the result in a Pandas DataFrame" -" to take advantage of the Variable Explorer display options." +msgid "We will use the function we just defined to calculate the optimal weights for each year, and we are going to save the result in a Pandas DataFrame to take advantage of the Variable Explorer display options." msgstr "" #: ../../workshops/financial.rst:639 -msgid "" -"Double click on the ``port_1_ow`` variable in the Variable Explorer. In " -"the table, you can specify the number of decimal places to display, by " -"clicking the format button at the bottom left of the pane, as you can see" -" in the following image:" +msgid "Double click on the ``port_1_ow`` variable in the Variable Explorer. In the table, you can specify the number of decimal places to display, by clicking the format button at the bottom left of the pane, as you can see in the following image:" +msgstr "" + +#: ../../workshops/financial.rst:641 +msgid "Portfolio 1 optimal weights by year" msgstr "" #: ../../workshops/financial.rst:644 -msgid "" -"We set the number of decimal places to 4 and uncheck the **Column " -"min/max** checkbox to better appreciate the contrasts in the row values " -"(years)." +msgid "We set the number of decimal places to 4 and uncheck the **Column min/max** checkbox to better appreciate the contrasts in the row values (years)." msgstr "" #: ../../workshops/financial.rst:646 -msgid "" -"You can see, for example, how 2015 was a particularly good year for " -"investing in Amazon and Netflix, while 2014 was the year of Apple. " -"Despite Netflix's rapid growth over the years, its high volatility means " -"that its Sharpe Ratio is not very remarkable in any year, especially (as " -"we said above) in 2014 and 2019. In the same respect, Apple and Microsoft" -" seem to be safer bets in the return/volatility ratio." +msgid "You can see, for example, how 2015 was a particularly good year for investing in Amazon and Netflix, while 2014 was the year of Apple. Despite Netflix's rapid growth over the years, its high volatility means that its Sharpe Ratio is not very remarkable in any year, especially (as we said above) in 2014 and 2019. In the same respect, Apple and Microsoft seem to be safer bets in the return/volatility ratio." msgstr "" #: ../../workshops/financial.rst:650 @@ -995,54 +697,35 @@ msgid "Comparison of expected and realized returns" msgstr "" #: ../../workshops/financial.rst:652 -msgid "" -"Finally, we will use the optimal weights to calculate the expected " -"returns and compare them with the actual returns." +msgid "Finally, we will use the optimal weights to calculate the expected returns and compare them with the actual returns." msgstr "" #: ../../workshops/financial.rst:668 -msgid "" -"In this function we compare year to year realized returns with " -"theoretically expected returns. This is done by estimating:" +msgid "In this function we compare year to year realized returns with theoretically expected returns. This is done by estimating:" msgstr "" #: ../../workshops/financial.rst:670 -msgid "" -"The returns from applying the optimal weights of the previous year's " -"stocks to the data for that same year (``expected_pr``)." +msgid "The returns from applying the optimal weights of the previous year's stocks to the data for that same year (``expected_pr``)." msgstr "" #: ../../workshops/financial.rst:671 -msgid "" -"The returns from applying the optimal weights of the previous year's " -"stocks to the following year's data (``realized_pr``)." +msgid "The returns from applying the optimal weights of the previous year's stocks to the following year's data (``realized_pr``)." msgstr "" #: ../../workshops/financial.rst:673 -msgid "" -"We are going to apply this function to the data in portfolio 1 and store " -"the results in a DataFrame that we can review in the Variable Explorer." +msgid "We are going to apply this function to the data in portfolio 1 and store the results in a DataFrame that we can review in the Variable Explorer." msgstr "" #: ../../workshops/financial.rst:680 -msgid "" -"The expected column shows the predicted values if the optimal portfolio " -"composition had been used. The realized column, on the other hand, shows " -"the actual profits that would have been obtained with those weights. It " -"can be seen that there are notable differences in some years. Let's look " -"at this in a plot." +msgid "The expected column shows the predicted values if the optimal portfolio composition had been used. The realized column, on the other hand, shows the actual profits that would have been obtained with those weights. It can be seen that there are notable differences in some years. Let's look at this in a plot." +msgstr "" + +#: ../../workshops/financial.rst:686 +msgid "Portfolio 1 expected and realized returns comparison" msgstr "" #: ../../workshops/financial.rst:689 -msgid "" -"The most notable differences are seen in 2014 and 2016. In those years, " -"the previous year's optimal portfolio weights (in blue in the above plot)" -" are a lousy indicator of the following year's stock performance (in " -"red). In 2013, our model estimated that Google and Netflix were excellent" -" investments. But by 2014 their share price did not grow if we compare " -"the price at the beginning and at the end of that year. And something " -"similar happened in 2016, in which Amazon's growing trend of the previous" -" year diminished, and the value of Microsoft and Apple shares grew." +msgid "The most notable differences are seen in 2014 and 2016. In those years, the previous year's optimal portfolio weights (in blue in the above plot) are a lousy indicator of the following year's stock performance (in red). In 2013, our model estimated that Google and Netflix were excellent investments. But by 2014 their share price did not grow if we compare the price at the beginning and at the end of that year. And something similar happened in 2016, in which Amazon's growing trend of the previous year diminished, and the value of Microsoft and Apple shares grew." msgstr "" #: ../../workshops/financial.rst:691 @@ -1050,23 +733,15 @@ msgid "Let's summarize these numbers." msgstr "" #: ../../workshops/financial.rst:701 -msgid "" -"Our optimal weight model offered us a profit of around 40%, but the " -"profit we would have obtained, due to real market fluctuations, would " -"have been almost 20%. Not bad, but the mean-variance portfolio model we " -"have applied for annual calculations is not very accurate, is it?" +msgid "Our optimal weight model offered us a profit of around 40%, but the profit we would have obtained, due to real market fluctuations, would have been almost 20%. Not bad, but the mean-variance portfolio model we have applied for annual calculations is not very accurate, is it?" msgstr "" #: ../../workshops/financial.rst:703 -msgid "" -"And this result is less encouraging if we calculate the correlations " -"between expected and realized profits." +msgid "And this result is less encouraging if we calculate the correlations between expected and realized profits." msgstr "" #: ../../workshops/financial.rst:713 -msgid "" -"As we can see, the correlations are negative, which warns us that we " -"should be cautious when using this type of modeling." +msgid "As we can see, the correlations are negative, which warns us that we should be cautious when using this type of modeling." msgstr "" #: ../../workshops/financial.rst:719 @@ -1074,11 +749,7 @@ msgid "Second portfolio" msgstr "" #: ../../workshops/financial.rst:721 -msgid "" -"We are now going to apply all the previous code with a portfolio of a " -"different nature. Let's assume that instead of technology companies, we " -"are now interested in pharmaceuticals. We will build a portfolio with " -"stocks of Pfizer, Astra Zeneca, Johnson & Johnson." +msgid "We are now going to apply all the previous code with a portfolio of a different nature. Let's assume that instead of technology companies, we are now interested in pharmaceuticals. We will build a portfolio with stocks of Pfizer, Astra Zeneca, Johnson & Johnson." msgstr "" #: ../../workshops/financial.rst:725 @@ -1090,12 +761,7 @@ msgid "Let's download the data and format it." msgstr "" #: ../../workshops/financial.rst:740 -msgid "" -"If you do not want to use the yfinance API, you can download the " -"``close_data_2.csv`` file containing the closing information for this " -"portfolio. Copy this file to your working directory. Load the data with " -"the following instruction: ``>>> close_data_2 = " -"pd.read_csv(\"close_data_2.csv\")``." +msgid "If you do not want to use the yfinance API, you can download the ``close_data_2.csv`` file containing the closing information for this portfolio. Copy this file to your working directory. Load the data with the following instruction: ``>>> close_data_2 = pd.read_csv(\"close_data_2.csv\")``." msgstr "" #: ../../workshops/financial.rst:744 @@ -1103,18 +769,11 @@ msgid "Mean and standard deviation" msgstr "" #: ../../workshops/financial.rst:746 -msgid "" -"We are going to put the data in a monthly format and observe the mean and" -" standard deviation." +msgid "We are going to put the data in a monthly format and observe the mean and standard deviation." msgstr "" #: ../../workshops/financial.rst:768 -msgid "" -"As in portfolio 1, all means are positive. But its largest value (that of" -" JNJ) barely reaches 1% per month, which is slower growth than that of " -"portfolio 1. The variation is also smaller compared to that of the " -"previous portfolio (here the largest deviation is 0.06) which makes it a " -"lower risk investment." +msgid "As in portfolio 1, all means are positive. But its largest value (that of JNJ) barely reaches 1% per month, which is slower growth than that of portfolio 1. The variation is also smaller compared to that of the previous portfolio (here the largest deviation is 0.06) which makes it a lower risk investment." msgstr "" #: ../../workshops/financial.rst:772 @@ -1125,11 +784,16 @@ msgstr "" msgid "Let's better visualize the above with a couple of charts." msgstr "" +#: ../../workshops/financial.rst:785 +msgid "Portfolio 2 daily stock price" +msgstr "" + +#: ../../workshops/financial.rst:788 +msgid "Portfolio 2 monthly stock price" +msgstr "" + #: ../../workshops/financial.rst:791 -msgid "" -"These two plots show a steady growth over the years, but also a high " -"variability in each year. This seems to be a good portfolio only if taken" -" as a long-term investment." +msgid "These two plots show a steady growth over the years, but also a high variability in each year. This seems to be a good portfolio only if taken as a long-term investment." msgstr "" #: ../../workshops/financial.rst:795 @@ -1137,32 +801,23 @@ msgid "Returns, volatility and Sharpe ratio" msgstr "" #: ../../workshops/financial.rst:797 -msgid "" -"To confirm what was said in the previous section, let's calculate " -"returns, volatility and Sharpe ratio." +msgid "To confirm what was said in the previous section, let's calculate returns, volatility and Sharpe ratio." msgstr "" #: ../../workshops/financial.rst:811 -msgid "" -"The return of this portfolio is significantly lower than that of the " -"previous portfolio (0.0809 < 0.2859). Its volatility (0.1637 < 0.2370) is" -" also lower, but to a lesser extent. This is reflected in a lower Sharpe " -"ratio as well (0.4940 < 1.2062). This means, within the mean-variance " -"theory approach, that the first portfolio is a better investment than the" -" second one." +msgid "The return of this portfolio is significantly lower than that of the previous portfolio (0.0809 < 0.2859). Its volatility (0.1637 < 0.2370) is also lower, but to a lesser extent. This is reflected in a lower Sharpe ratio as well (0.4940 < 1.2062). This means, within the mean-variance theory approach, that the first portfolio is a better investment than the second one." msgstr "" #: ../../workshops/financial.rst:813 -msgid "" -"The different behavior is clearly observed if we apply a Monte Carlo " -"simulation and visualize it with a graph:" +msgid "The different behavior is clearly observed if we apply a Monte Carlo simulation and visualize it with a graph:" +msgstr "" + +#: ../../workshops/financial.rst:827 +msgid "Portfolio 2 Monte Carlo Sharpe simulation scatter plot" msgstr "" #: ../../workshops/financial.rst:830 -msgid "" -"High volatility does not correspond in most cases with high returns. In " -"fact, there are scenarios in the simulation in which higher expected " -"returns are related to lower expected volatility." +msgid "High volatility does not correspond in most cases with high returns. In fact, there are scenarios in the simulation in which higher expected returns are related to lower expected volatility." msgstr "" #: ../../workshops/financial.rst:834 @@ -1170,44 +825,35 @@ msgid "Optimal pharmaceutical stock weights" msgstr "" #: ../../workshops/financial.rst:836 -msgid "" -"Let us now see what are the optimal weights for each stock using the " -"``optimal_weights`` function." +msgid "Let us now see what are the optimal weights for each stock using the ``optimal_weights`` function." +msgstr "" + +#: ../../workshops/financial.rst:846 +msgid "Portfolio 2 optimal weights by year" msgstr "" #: ../../workshops/financial.rst:849 -msgid "" -"In addition, we can use these optimal weights to plot the expected and " -"realized returns of this portfolio for each year." +msgid "In addition, we can use these optimal weights to plot the expected and realized returns of this portfolio for each year." +msgstr "" + +#: ../../workshops/financial.rst:858 +msgid "Portfolio 2 expected and realized returns comparison" msgstr "" #: ../../workshops/financial.rst:861 -msgid "" -"Due to the high volatility of this portfolio, our model has not been able" -" to adequately forecast expected returns in several of the years. Higher " -"than expected returns would have been realized in 2013 and 2017, but in " -"2015 and 2018 using the model would have generated losses." +msgid "Due to the high volatility of this portfolio, our model has not been able to adequately forecast expected returns in several of the years. Higher than expected returns would have been realized in 2013 and 2017, but in 2015 and 2018 using the model would have generated losses." msgstr "" #: ../../workshops/financial.rst:863 -msgid "" -"Finally, let us look at the differences between the expected and realized" -" means, and the linear correlation between the data." +msgid "Finally, let us look at the differences between the expected and realized means, and the linear correlation between the data." msgstr "" #: ../../workshops/financial.rst:881 -msgid "" -"As we can see, the model with optimal weights predicted a return close to" -" 15% per year, but the realized return would have barely reached 6%. And " -"the negative correlations show, as with portfolio 1, that there does not " -"seem to be any correspondence between these values." +msgid "As we can see, the model with optimal weights predicted a return close to 15% per year, but the realized return would have barely reached 6%. And the negative correlations show, as with portfolio 1, that there does not seem to be any correspondence between these values." msgstr "" #: ../../workshops/financial.rst:883 -msgid "" -"The comparison is then favorable for portfolio 1. But what if we compare " -"portfolio 1 with a \"higher risk\" investment such as cryptocurrencies? " -"Let's discuss it below." +msgid "The comparison is then favorable for portfolio 1. But what if we compare portfolio 1 with a \"higher risk\" investment such as cryptocurrencies? Let's discuss it below." msgstr "" #: ../../workshops/financial.rst:889 @@ -1219,20 +865,11 @@ msgid "Download cryptocurrencies data" msgstr "" #: ../../workshops/financial.rst:894 -msgid "" -"Our third portfolio will consist of three cryptocurrencies: bitcoin " -"(BTC), ethereum (ETH) and litecoin (LTC). To access historical data, we " -"are going to use a library called **Historic-Crypto**." +msgid "Our third portfolio will consist of three cryptocurrencies: bitcoin (BTC), ethereum (ETH) and litecoin (LTC). To access historical data, we are going to use a library called **Historic-Crypto**." msgstr "" #: ../../workshops/financial.rst:898 -msgid "" -"If you want to make use of the data without the Historic-Crypto library, " -"you can `download the dataset " -"`_" -" \"crypto_hist.csv\" in your working directory, and load it in memory " -"with the instruction ``crypto_hist = pd.read_csv(\"crypto_hist.csv\")``, " -"and skip to section `Monthly data`_." +msgid "If you want to make use of the data without the Historic-Crypto library, you can `download the dataset `_ \"crypto_hist.csv\" in your working directory, and load it in memory with the instruction ``crypto_hist = pd.read_csv(\"crypto_hist.csv\")``, and skip to section `Monthly data`_." msgstr "" #: ../../workshops/financial.rst:900 @@ -1240,26 +877,15 @@ msgid "Import the libraries:" msgstr "" #: ../../workshops/financial.rst:907 -msgid "" -"We are going to use the ``Cryptocurrencies`` class to obtain a list of " -"available cryptocurrencies." +msgid "We are going to use the ``Cryptocurrencies`` class to obtain a list of available cryptocurrencies." msgstr "" #: ../../workshops/financial.rst:915 -msgid "" -"If you want more information about the use of this library you can make a" -" quick query using the Spyder Help panel (type in the console " -"``Cryptocurrencies`` and use :kbd:`Ctrl-I` or :kbd:`Cmd-I` to display " -"it). Or you can read the documentation in their `official repository " -"`_" +msgid "If you want more information about the use of this library you can make a quick query using the Spyder Help panel (type in the console ``Cryptocurrencies`` and use :kbd:`Ctrl-I` or :kbd:`Cmd-I` to display it). Or you can read the documentation in their `official repository `_" msgstr "" #: ../../workshops/financial.rst:917 -msgid "" -"A new variable has appeared in the Variable Explorer: ``crypto_list``. It" -" is a Pandas DataFrame that has a basic description of the types of " -"cryptocurrency transactions. For example, we can look up which token is " -"the token for ethereum transactions in US dollars." +msgid "A new variable has appeared in the Variable Explorer: ``crypto_list``. It is a Pandas DataFrame that has a basic description of the types of cryptocurrency transactions. For example, we can look up which token is the token for ethereum transactions in US dollars." msgstr "" #: ../../workshops/financial.rst:923 @@ -1267,32 +893,19 @@ msgid "In this case, we are interested in the symbol with ID 171: ETH-USD." msgstr "" #: ../../workshops/financial.rst:925 -msgid "" -"We can use the HistoricalData class of Historic-Crypto to download the " -"history of transactions done in the cryptocurrencies of our portfolio, in" -" US dollars." +msgid "We can use the HistoricalData class of Historic-Crypto to download the history of transactions done in the cryptocurrencies of our portfolio, in US dollars." msgstr "" #: ../../workshops/financial.rst:946 -msgid "" -"Let's merge the resulting dataframes to have all the data in a single " -"table." +msgid "Let's merge the resulting dataframes to have all the data in a single table." msgstr "" #: ../../workshops/financial.rst:953 -msgid "" -"We will not present the procedures and code in this section, but only the" -" results of the analysis. You can follow the steps in the previous " -"sections to recreate these results." +msgid "We will not present the procedures and code in this section, but only the results of the analysis. You can follow the steps in the previous sections to recreate these results." msgstr "" #: ../../workshops/financial.rst:957 -msgid "" -"Use all this section on portfolio 3 to check your understanding of the " -"concepts and code we have presented until now. If you have any questions," -" you can consult the :download:`code ` code that " -"accompanies this workshop. But we encourage you to try as much as " -"possible to solve the code on your own." +msgid "Use all this section on portfolio 3 to check your understanding of the concepts and code we have presented until now. If you have any questions, you can consult the :download:`code ` code that accompanies this workshop. But we encourage you to try as much as possible to solve the code on your own." msgstr "" #: ../../workshops/financial.rst:961 @@ -1303,10 +916,12 @@ msgstr "" msgid "Let's take a look at the monthly history of cryptocurrency price growth." msgstr "" +#: ../../workshops/financial.rst:965 +msgid "Portfolio 3 daily stock price" +msgstr "" + #: ../../workshops/financial.rst:968 -msgid "" -"We can note that the scale here is much larger. And the proportion of ETH" -" growth over the other two coins is quite remarkable." +msgid "We can note that the scale here is much larger. And the proportion of ETH growth over the other two coins is quite remarkable." msgstr "" #: ../../workshops/financial.rst:972 @@ -1330,12 +945,7 @@ msgid "Sharpe: 0.8176" msgstr "" #: ../../workshops/financial.rst:980 -msgid "" -"These numbers are higher than those obtained for portfolios 1 and 2, " -"except for the Sharpe ratio. This is a very volatile portfolio (in fact " -"three times more volatile than that of the technology companies), and " -"that makes it ultimately not as profitable as portfolio 1. The returns " -"are higher (almost double) but the risk may not compensate for it." +msgid "These numbers are higher than those obtained for portfolios 1 and 2, except for the Sharpe ratio. This is a very volatile portfolio (in fact three times more volatile than that of the technology companies), and that makes it ultimately not as profitable as portfolio 1. The returns are higher (almost double) but the risk may not compensate for it." msgstr "" #: ../../workshops/financial.rst:984 @@ -1343,57 +953,43 @@ msgid "Monte carlo simulation" msgstr "" #: ../../workshops/financial.rst:986 -msgid "" -"The Monte Carlo simulation also shows the non-linear correlation between " -"risk and returns (as you can see, sometimes high risk involves only " -"modest profits):" +msgid "The Monte Carlo simulation also shows the non-linear correlation between risk and returns (as you can see, sometimes high risk involves only modest profits):" +msgstr "" + +#: ../../workshops/financial.rst:988 +msgid "Portfolio 3 Monte Carlo Sharpe simulation scatter plot" msgstr "" #: ../../workshops/financial.rst:991 -msgid "" -"As can be seen, there are points (bottom right) that show a very high " -"volatility and yet have a very low expected return. In this sense, " -"portfolio 1 represents a safer investment because the higher risk is " -"consistently offset by higher returns." +msgid "As can be seen, there are points (bottom right) that show a very high volatility and yet have a very low expected return. In this sense, portfolio 1 represents a safer investment because the higher risk is consistently offset by higher returns." msgstr "" #: ../../workshops/financial.rst:995 msgid "Optimal cryptocurrency weights" msgstr "" +#: ../../workshops/financial.rst:997 +msgid "Portfolio 3 optimal weights by year" +msgstr "" + #: ../../workshops/financial.rst:1000 -msgid "" -"The optimal portfolio weights, if calculated annually, suggest that our " -"portfolio should have been quite polarized in some years: the " -"recommendation is to have bought only bitcoins before the start of 2016 " -"and 2019, and only ethereum in 2018. Starting 2017 and 2020, on the other" -" hand, our weights recommended a more balanced investment between bitcoin" -" and ethereum. Litecoin is not recommended by our model." +msgid "The optimal portfolio weights, if calculated annually, suggest that our portfolio should have been quite polarized in some years: the recommendation is to have bought only bitcoins before the start of 2016 and 2019, and only ethereum in 2018. Starting 2017 and 2020, on the other hand, our weights recommended a more balanced investment between bitcoin and ethereum. Litecoin is not recommended by our model." msgstr "" #: ../../workshops/financial.rst:1004 msgid "Expected and realized returns" msgstr "" +#: ../../workshops/financial.rst:1006 +msgid "Portfolio 3 expected and realized returns comparison" +msgstr "" + #: ../../workshops/financial.rst:1009 -msgid "" -"In this graph we can see that in 2017 and 2020 the earnings obtained " -"would have exceeded the expected earnings (with our calculated weights). " -"In 2019 our model predicted a sharp drop in the portfolio, but in reality" -" the portfolio did not make either annualized gains or losses that year. " -"In contrast, in 2018, our model would have brought us heavy losses, as " -"the value of cryptocurrencies declined sharply that year." +msgid "In this graph we can see that in 2017 and 2020 the earnings obtained would have exceeded the expected earnings (with our calculated weights). In 2019 our model predicted a sharp drop in the portfolio, but in reality the portfolio did not make either annualized gains or losses that year. In contrast, in 2018, our model would have brought us heavy losses, as the value of cryptocurrencies declined sharply that year." msgstr "" #: ../../workshops/financial.rst:1011 -msgid "" -"The mean expected return for our portfolio is 0.6972, which is higher " -"than the realized return of 0.4181 that we would have obtained. Having " -"invested in this portfolio over the long term (from 2016 to the present) " -"would have been a very good deal. Due to the high variability, investing " -"in the short term would have been very risky. In terms of gross profits, " -"the realized returns of this portfolio were more than double those of " -"portfolio 1 (0.4181 > 0.1997)." +msgid "The mean expected return for our portfolio is 0.6972, which is higher than the realized return of 0.4181 that we would have obtained. Having invested in this portfolio over the long term (from 2016 to the present) would have been a very good deal. Due to the high variability, investing in the short term would have been very risky. In terms of gross profits, the realized returns of this portfolio were more than double those of portfolio 1 (0.4181 > 0.1997)." msgstr "" #: ../../workshops/financial.rst:1017 @@ -1403,18 +999,11 @@ msgid "Final words" msgstr "" #: ../../workshops/financial.rst:1019 -msgid "" -"The mean-variance portfolio (MVP) theory is one of the many tools " -"available to financial analysis. In recent years, machine learning " -"algorithms have even been used to predict the behavior of stock prices " -"more accurately than can be achieved with any standard financial theory." +msgid "The mean-variance portfolio (MVP) theory is one of the many tools available to financial analysis. In recent years, machine learning algorithms have even been used to predict the behavior of stock prices more accurately than can be achieved with any standard financial theory." msgstr "" #: ../../workshops/financial.rst:1021 -msgid "" -"The examples given during this workshop are not intended to serve as " -"guidelines for you to invest your money. It is only a first step towards " -"learning financial analysis using Python and a scientific IDE." +msgid "The examples given during this workshop are not intended to serve as guidelines for you to invest your money. It is only a first step towards learning financial analysis using Python and a scientific IDE." msgstr "" #: ../../workshops/financial.rst:1023 @@ -1472,25 +1061,17 @@ msgid "Obtain the optimal weights of the stocks in a portfolio." msgstr "" #: ../../workshops/financial.rst:1037 -msgid "" -"With the skills learned here, you will be able to approach more complex " -"topics of financial analysis such as those you will find in the " -"references in the next section." +msgid "With the skills learned here, you will be able to approach more complex topics of financial analysis such as those you will find in the references in the next section." msgstr "" #: ../../workshops/financial.rst:1039 #: ../../workshops/scientific-computing.rst:774 -msgid "" -"Thank you for reaching the end of this workshop! We hope you found it " -"helpful and informative." +msgid "Thank you for reaching the end of this workshop! We hope you found it helpful and informative." msgstr "" #: ../../workshops/financial.rst:1041 #: ../../workshops/plugin-development.rst:1422 -msgid "" -"If you are interested in an introduction to scientific computing with " -"Spyder, you can visit the workshop :doc:`Scientific Computing and " -"Visualization with Spyder <../workshops/scientific-computing>`." +msgid "If you are interested in an introduction to scientific computing with Spyder, you can visit the workshop :doc:`Scientific Computing and Visualization with Spyder <../workshops/scientific-computing>`." msgstr "" #: ../../workshops/financial.rst:1045 @@ -1500,11 +1081,7 @@ msgid "Homework" msgstr "" #: ../../workshops/financial.rst:1047 -msgid "" -"If you want to check what you have learned, we suggest you try to obtain " -"the results presented for the third portfolio. If you have any questions," -" you can consult the code that accompanies this workshop in our " -"repository." +msgid "If you want to check what you have learned, we suggest you try to obtain the results presented for the third portfolio. If you have any questions, you can consult the code that accompanies this workshop in our repository." msgstr "" #: ../../workshops/financial.rst:1053 @@ -1514,9 +1091,7 @@ msgid "Further reading" msgstr "" #: ../../workshops/financial.rst:1055 -msgid "" -"Much of the math used to apply MVP was the mathematics outlined in Yves " -"Hilpisch's excellent book, which we recommend to you:" +msgid "Much of the math used to apply MVP was the mathematics outlined in Yves Hilpisch's excellent book, which we recommend to you:" msgstr "" #: ../../workshops/financial.rst:1057 @@ -1524,9 +1099,7 @@ msgid "Yves Hilpisch, Y. (2020). *Artificial Intelligence in Finance*. O'Reilly. msgstr "" #: ../../workshops/financial.rst:1059 -msgid "" -"A classic that has been with us for decades and is one of Warren " -"Buffett's favorites:" +msgid "A classic that has been with us for decades and is one of Warren Buffett's favorites:" msgstr "" #: ../../workshops/financial.rst:1061 @@ -1534,9 +1107,7 @@ msgid "Graham, B. (1949). *The Intelligent Investor*. HarperCollins." msgstr "" #: ../../workshops/financial.rst:1063 -msgid "" -"Another good resource for financial analysis with Python is the following" -" book by James Ma Weiming:" +msgid "Another good resource for financial analysis with Python is the following book by James Ma Weiming:" msgstr "" #: ../../workshops/financial.rst:1065 @@ -1552,53 +1123,33 @@ msgid "Plugin Development with Spyder" msgstr "" #: ../../workshops/plugin-development.rst:5 -msgid "" -"This workshop reviews the features and possibilities of the API offered " -"by `Spyder`_ 5—the recently released version of our favorite IDE for " -"scientific Python—for plugin development and to extend its functionality." +msgid "This workshop reviews the features and possibilities of the API offered by `Spyder`_ 5—the recently released version of our favorite IDE for scientific Python—for plugin development and to extend its functionality." msgstr "" #: ../../workshops/plugin-development.rst:7 -msgid "" -"As a practical exercise, we will develop a simple plugin that " -"incorporates a configurable pomodoro timer in the status bar and some " -"toolbar buttons to interact with it." +msgid "As a practical exercise, we will develop a simple plugin that incorporates a configurable pomodoro timer in the status bar and some toolbar buttons to interact with it." msgstr "" #: ../../workshops/plugin-development.rst:17 #: ../../workshops/scientific-computing.rst:13 -msgid "" -"You will need to have Spyder installed. Visit our :doc:`installation " -"guide<../installation>` for more information." +msgid "You will need to have Spyder installed. Visit our :doc:`installation guide<../installation>` for more information." msgstr "" #: ../../workshops/plugin-development.rst:21 -msgid "" -"Spyder now offers :ref:`install-standalone` for Windows and macOS, making" -" it easier to get up and running with the application without having to " -"download Anaconda or manually install it in your existing environment. " -"However, readers of this workshop should install Spyder using Anaconda or" -" Miniconda, as standalone installers currently do not allow to add extra " -"packages like the plugin we are going to develop in this workshop." +msgid "Spyder now offers :ref:`install-standalone` for Windows and macOS, making it easier to get up and running with the application without having to download Anaconda or manually install it in your existing environment. However, readers of this workshop should install Spyder using Anaconda or Miniconda, as standalone installers currently do not allow to add extra packages like the plugin we are going to develop in this workshop." msgstr "" #: ../../workshops/plugin-development.rst:26 #: ../../workshops/scientific-computing.rst:22 -msgid "" -"Basic level of Python. You can visit `The Python Tutorial`_ to learn the " -"basics of this programming language." +msgid "Basic level of Python. You can visit `The Python Tutorial`_ to learn the basics of this programming language." msgstr "" #: ../../workshops/plugin-development.rst:27 -msgid "" -"Know the basics of Qt application development using Python, either with " -"`PyQT`_ or `PySide`_." +msgid "Know the basics of Qt application development using Python, either with `PyQT`_ or `PySide`_." msgstr "" #: ../../workshops/plugin-development.rst:29 -msgid "" -"To quickly get started in desktop application development with Qt and " -"Python here is a set of open access resources:" +msgid "To quickly get started in desktop application development with Qt and Python here is a set of open access resources:" msgstr "" #: ../../workshops/plugin-development.rst:31 @@ -1626,9 +1177,7 @@ msgid "By the end of this workshop participants will know:" msgstr "" #: ../../workshops/plugin-development.rst:50 -msgid "" -"The basics to develop plugins for Spyder, and get a general idea of its " -"inner workings." +msgid "The basics to develop plugins for Spyder, and get a general idea of its inner workings." msgstr "" #: ../../workshops/plugin-development.rst:51 @@ -1636,15 +1185,11 @@ msgid "What types of plugins can be developed with Spyder." msgstr "" #: ../../workshops/plugin-development.rst:52 -msgid "" -"The structure of a plugin and the functionality of each component and how" -" it connects to Spyder to extend its features." +msgid "The structure of a plugin and the functionality of each component and how it connects to Spyder to extend its features." msgstr "" #: ../../workshops/plugin-development.rst:53 -msgid "" -"How to package and publish our plugin so that it can be easily installed " -"and used by others." +msgid "How to package and publish our plugin so that it can be easily installed and used by others." msgstr "" #: ../../workshops/plugin-development.rst:59 @@ -1652,64 +1197,47 @@ msgid "Spyder for developers" msgstr "" #: ../../workshops/plugin-development.rst:61 -msgid "" -"The best place to find information about contributing to Spyder or " -"developing for Spyder is its Github repository, in particular the " -"`contribution guide`_." +msgid "The best place to find information about contributing to Spyder or developing for Spyder is its Github repository, in particular the `contribution guide`_." +msgstr "" + +#: ../../workshops/plugin-development.rst:63 +msgid "Spyder IDE components." msgstr "" #: ../../workshops/plugin-development.rst:66 -msgid "" -"The core of **Spyder** is `Spyder-IDE`_ , a desktop application developed" -" in *Qt*, which requires for its operation two packages with it is " -"closely related (and without which it cannot work): *spyder-kernels* and " -"*python-lsp-server*." +msgid "The core of **Spyder** is `Spyder-IDE`_ , a desktop application developed in *Qt*, which requires for its operation two packages with it is closely related (and without which it cannot work): *spyder-kernels* and *python-lsp-server*." msgstr "" #: ../../workshops/plugin-development.rst:68 -msgid "" -"`Qt`_ is an open source multiplatform widget toolkit for creating native " -"graphical user interfaces. Qt is a very complete development framework " -"that offers utilities for building applications, and has extensions for " -"Networking, Bluetooth, Charts, 3D rendering, Navigation (as GPS), among " -"others." +msgid "`Qt`_ is an open source multiplatform widget toolkit for creating native graphical user interfaces. Qt is a very complete development framework that offers utilities for building applications, and has extensions for Networking, Bluetooth, Charts, 3D rendering, Navigation (as GPS), among others." msgstr "" #: ../../workshops/plugin-development.rst:70 -msgid "" -"Spyder uses `qtpy`_ which is an abstraction layer that allows you to work" -" with Qt from Python regardless of whether you use either of the two " -"reference libraries: PyQt or PySide." +msgid "Spyder uses `qtpy`_ which is an abstraction layer that allows you to work with Qt from Python regardless of whether you use either of the two reference libraries: PyQt or PySide." msgstr "" #: ../../workshops/plugin-development.rst:72 -msgid "" -"`spyder-kernels`_ provide Jupyter kernels to Spyder, for use within its " -"consoles." +msgid "`spyder-kernels`_ provide Jupyter kernels to Spyder, for use within its consoles." msgstr "" #: ../../workshops/plugin-development.rst:76 -msgid "" -"Spyder is currently developed in such a way that most of its features are" -" implemented as plugins." +msgid "Spyder is currently developed in such a way that most of its features are implemented as plugins." msgstr "" #: ../../workshops/plugin-development.rst:89 msgid "Types of plugins we can develop in Spyder" msgstr "" +#: ../../workshops/plugin-development.rst:92 +msgid "Types of Spyder plugins." +msgstr "" + #: ../../workshops/plugin-development.rst:97 -msgid "" -"A plugin is a component that adds functionality to an application, it can" -" be a graphical component, for example, to display maps, or a non-" -"graphical one that adds additional syntax coloring schemes." +msgid "A plugin is a component that adds functionality to an application, it can be a graphical component, for example, to display maps, or a non-graphical one that adds additional syntax coloring schemes." msgstr "" #: ../../workshops/plugin-development.rst:99 -msgid "" -"Formally, plugins are instances of Qt classes that modify the behavior of" -" Spyder. Aside from a few fundamental components, most of Spyder's " -"functionality arises from the interaction of plugins of two types:" +msgid "Formally, plugins are instances of Qt classes that modify the behavior of Spyder. Aside from a few fundamental components, most of Spyder's functionality arises from the interaction of plugins of two types:" msgstr "" #: ../../workshops/plugin-development.rst:104 @@ -1717,10 +1245,7 @@ msgid "SpyderDockablePlugin" msgstr "" #: ../../workshops/plugin-development.rst:106 -msgid "" -"It is a plugin that works as a `QDockWidget`_, this is a Qt class that " -"provides a graphical control that can be docked inside a `QMainWindow`_ " -"or floated as a top-level window on the desktop." +msgid "It is a plugin that works as a `QDockWidget`_, this is a Qt class that provides a graphical control that can be docked inside a `QMainWindow`_ or floated as a top-level window on the desktop." msgstr "" #: ../../workshops/plugin-development.rst:113 @@ -1728,54 +1253,43 @@ msgid "SpyderPluginV2" msgstr "" #: ../../workshops/plugin-development.rst:115 -msgid "" -"``SpyderPluginV2`` is a plugin that does not create a new dock widget on " -"Spyder's main window. In fact, ``SpyderPluginV2`` is the parent class of " -"``SpyderDockablePlugin``." +msgid "``SpyderPluginV2`` is a plugin that does not create a new dock widget on Spyder's main window. In fact, ``SpyderPluginV2`` is the parent class of ``SpyderDockablePlugin``." msgstr "" #: ../../workshops/plugin-development.rst:120 msgid "Discovering Spyder plugins" msgstr "" +#: ../../workshops/plugin-development.rst:120 +msgid "``SpyderDockablePlugin``" +msgstr "" + #: ../../workshops/plugin-development.rst:124 -msgid "" -"If we look at the Spyder interface, we can find a number of different " -"panes on the right side (with the default layout), such as *Help*, " -"*Variable Explorer*, *Plots*, *Files* and *History*." +msgid "If we look at the Spyder interface, we can find a number of different panes on the right side (with the default layout), such as *Help*, *Variable Explorer*, *Plots*, *Files* and *History*." msgstr "" #: ../../workshops/plugin-development.rst:126 -msgid "" -"Each of these panes is a ``SpyderDockablePlugin`` that offers an *Undock*" -" option by clicking the hamburger menu button in the upper right corner." +msgid "Each of these panes is a ``SpyderDockablePlugin`` that offers an *Undock* option by clicking the hamburger menu button in the upper right corner." msgstr "" #: ../../workshops/plugin-development.rst:128 -msgid "" -"These plugins can also be hidden or shown via their entry in the *View > " -"Panes* menu, or using its corresponding keyboard shortcut displayed " -"there." +msgid "These plugins can also be hidden or shown via their entry in the *View > Panes* menu, or using its corresponding keyboard shortcut displayed there." +msgstr "" + +#: ../../workshops/plugin-development.rst:120 +msgid "``SpyderPluginV2``" msgstr "" #: ../../workshops/plugin-development.rst:132 -msgid "" -"High-level interface elements that do not offer an undocking option are " -"basically instances of ``SpyderPluginV2``. These are typically used to " -"handle more abstract functionality." +msgid "High-level interface elements that do not offer an undocking option are basically instances of ``SpyderPluginV2``. These are typically used to handle more abstract functionality." msgstr "" #: ../../workshops/plugin-development.rst:134 -msgid "" -"Examples of this are the *appearance* and *layout* plugins that manage " -"Spyder's code color schemes and window layouts respectively." +msgid "Examples of this are the *appearance* and *layout* plugins that manage Spyder's code color schemes and window layouts respectively." msgstr "" #: ../../workshops/plugin-development.rst:136 -msgid "" -"Other examples of this type of plugins are the *main menu* and keyboard " -"*shortcuts*. Some graphical elements, such as the main toolbar and the " -"status bar are also instances of the ``SpyderPluginV2`` class." +msgid "Other examples of this type of plugins are the *main menu* and keyboard *shortcuts*. Some graphical elements, such as the main toolbar and the status bar are also instances of the ``SpyderPluginV2`` class." msgstr "" #: ../../workshops/plugin-development.rst:142 @@ -1783,23 +1297,19 @@ msgid "What will we do?" msgstr "" #: ../../workshops/plugin-development.rst:144 -msgid "" -"Our practical work will consist in the implementation of the Pomodoro " -"technique for time management in the Spyder interface." +msgid "Our practical work will consist in the implementation of the Pomodoro technique for time management in the Spyder interface." +msgstr "" + +#: ../../workshops/plugin-development.rst:146 +msgid "Description of the pomodoro technique." msgstr "" #: ../../workshops/plugin-development.rst:151 -msgid "" -"The `Pomodoro Technique`_, designed by Francesco Cirillo, is a time " -"management practice used to increase your focus and productivity when " -"trying to complete assignments or meet deadlines. Choosing to use a " -"Pomodoro Timer can help to give a task your full, undivided attention." +msgid "The `Pomodoro Technique`_, designed by Francesco Cirillo, is a time management practice used to increase your focus and productivity when trying to complete assignments or meet deadlines. Choosing to use a Pomodoro Timer can help to give a task your full, undivided attention." msgstr "" #: ../../workshops/plugin-development.rst:154 -msgid "" -"The typical process of the Pomodoro Technique consists of the following " -"six steps:" +msgid "The typical process of the Pomodoro Technique consists of the following six steps:" msgstr "" #: ../../workshops/plugin-development.rst:157 @@ -1815,22 +1325,15 @@ msgid "Work only on that task until the timer ends." msgstr "" #: ../../workshops/plugin-development.rst:160 -msgid "" -"When the timer rings, put a checkmark on a piece of paper, this is called" -" \"a pomodoro\"." +msgid "When the timer rings, put a checkmark on a piece of paper, this is called \"a pomodoro\"." msgstr "" #: ../../workshops/plugin-development.rst:161 -msgid "" -"If you have less than 3 checkmarks take a short break (by default, 5 " -"minutes), and return to step 2." +msgid "If you have less than 3 checkmarks take a short break (by default, 5 minutes), and return to step 2." msgstr "" #: ../../workshops/plugin-development.rst:162 -msgid "" -"When you have completed four Pomodoro cycles, you deserve a longer break " -"(our default is 15 minutes). Checkmarks are reset to zero, go back to " -"step 1." +msgid "When you have completed four Pomodoro cycles, you deserve a longer break (our default is 15 minutes). Checkmarks are reset to zero, go back to step 1." msgstr "" #: ../../workshops/plugin-development.rst:168 @@ -1838,39 +1341,31 @@ msgid "Steps" msgstr "" #: ../../workshops/plugin-development.rst:170 -msgid "" -"These are the general steps that we will be following throughout this " -"workshop:" +msgid "These are the general steps that we will be following throughout this workshop:" msgstr "" #: ../../workshops/plugin-development.rst:172 -msgid "" -"Select the most suitable plugin type and create its initial structure " -"using `cookiecutter`_." +msgid "Select the most suitable plugin type and create its initial structure using `cookiecutter`_." msgstr "" #: ../../workshops/plugin-development.rst:173 -msgid "" -"Install the plugin in development mode in the virtual environment from " -"which we run Spyder." +msgid "Install the plugin in development mode in the virtual environment from which we run Spyder." msgstr "" #: ../../workshops/plugin-development.rst:174 -msgid "" -"Implement the functionality of our plugin using the Spyder classes and " -"following the guidelines indicated in the plugin structure." +msgid "Implement the functionality of our plugin using the Spyder classes and following the guidelines indicated in the plugin structure." msgstr "" #: ../../workshops/plugin-development.rst:175 -msgid "" -"Build a configuration page for our plugin, which would appear in Tools > " -"Preferences." +msgid "Build a configuration page for our plugin, which would appear in Tools > Preferences." msgstr "" +#: ../../workshops/plugin-development.rst:177 #: ../../workshops/plugin-development.rst:180 msgid "Location of Spyder Pomodoro Timer widgets in Spyder." msgstr "" +#: ../../workshops/plugin-development.rst:182 #: ../../workshops/plugin-development.rst:185 msgid "Spyder Pomodoro Timer in the preferences window." msgstr "" @@ -1892,23 +1387,15 @@ msgid "Status bar widget: to display the time for the current pomodoro interval. msgstr "" #: ../../workshops/plugin-development.rst:196 -msgid "" -"State: we have three activity states: *pomodoro*, *short-break* and " -"*long-break*. We can show a message (with `QMessageBox`_) to tell users " -"that the time to take a break has arrived." +msgid "State: we have three activity states: *pomodoro*, *short-break* and *long-break*. We can show a message (with `QMessageBox`_) to tell users that the time to take a break has arrived." msgstr "" #: ../../workshops/plugin-development.rst:197 -msgid "" -"Interactions: the user could use Start, Stop and Reset buttons to handle " -"the Pomodoro Timer. This can be implemented adding `QAction`_ instances " -"in a menu on the toolbar." +msgid "Interactions: the user could use Start, Stop and Reset buttons to handle the Pomodoro Timer. This can be implemented adding `QAction`_ instances in a menu on the toolbar." msgstr "" #: ../../workshops/plugin-development.rst:199 -msgid "" -"Tasks Logger - Counter: We need a variable to count the number of " -"pomodoros completed." +msgid "Tasks Logger - Counter: We need a variable to count the number of pomodoros completed." msgstr "" #: ../../workshops/plugin-development.rst:202 @@ -1916,18 +1403,11 @@ msgid "Notifications" msgstr "" #: ../../workshops/plugin-development.rst:204 -msgid "" -"Dialog: Each time a pomodoro or break interval is completed, a message " -"should appear to prompt the user to start working on a task or take a " -"break." +msgid "Dialog: Each time a pomodoro or break interval is completed, a message should appear to prompt the user to start working on a task or take a break." msgstr "" #: ../../workshops/plugin-development.rst:206 -msgid "" -"When working on a plugin for any system, we must check the data " -"structures and functions available in that system that can facilitate our" -" development. This involves spending considerable time understanding its " -"inner workings." +msgid "When working on a plugin for any system, we must check the data structures and functions available in that system that can facilitate our development. This involves spending considerable time understanding its inner workings." msgstr "" #: ../../workshops/plugin-development.rst:219 @@ -1935,18 +1415,15 @@ msgid "Set up a development environment" msgstr "" #: ../../workshops/plugin-development.rst:221 -msgid "" -"In principle, we could use any Spyder installed within a `conda " -"environment`_ according to the instructions given in the `installation " -"guide`_." +msgid "In principle, we could use any Spyder installed within a `conda environment`_ according to the instructions given in the `installation guide`_." msgstr "" #: ../../workshops/plugin-development.rst:223 -msgid "" -"However, if you use a working environment that has other dependencies and" -" you want to keep your plugin development independent of them, it is " -"recommended to create a new environment which only has Spyder with the " -"minimum dependencies needed for your plugin." +msgid "However, if you use a working environment that has other dependencies and you want to keep your plugin development independent of them, it is recommended to create a new environment which only has Spyder with the minimum dependencies needed for your plugin." +msgstr "" + +#: ../../workshops/plugin-development.rst:225 +msgid "Spyder development environment." msgstr "" #: ../../workshops/plugin-development.rst:228 @@ -1954,30 +1431,19 @@ msgid "We can install it in the following way:" msgstr "" #: ../../workshops/plugin-development.rst:240 -msgid "" -"`Anaconda Individual Edition`_ is a Python distribution for data science " -"and machine learning to be used in a single machine." +msgid "`Anaconda Individual Edition`_ is a Python distribution for data science and machine learning to be used in a single machine." msgstr "" #: ../../workshops/plugin-development.rst:241 -msgid "" -"`Conda`_ is an Anaconda tool that manages virtual environments and their " -"packages." +msgid "`Conda`_ is an Anaconda tool that manages virtual environments and their packages." msgstr "" #: ../../workshops/plugin-development.rst:242 -msgid "" -"Conda can work with *channels* that allow the use of packages that are " -"not part of the official distribution. The most important channel is " -"`conda-forge`_, where a more extensive and updated list of packages than " -"those offered by Anaconda Individual Edition are maintained." +msgid "Conda can work with *channels* that allow the use of packages that are not part of the official distribution. The most important channel is `conda-forge`_, where a more extensive and updated list of packages than those offered by Anaconda Individual Edition are maintained." msgstr "" #: ../../workshops/plugin-development.rst:243 -msgid "" -"Finally, `mamba`_, is an optimized implementation of conda's package " -"management features, that resolves dependencies and installs packages " -"much faster than conda." +msgid "Finally, `mamba`_, is an optimized implementation of conda's package management features, that resolves dependencies and installs packages much faster than conda." msgstr "" #: ../../workshops/plugin-development.rst:256 @@ -1985,11 +1451,11 @@ msgid "Create a repository" msgstr "" #: ../../workshops/plugin-development.rst:258 -msgid "" -"Now that we have our local virtual environment, it is good practice to " -"manage our source code with a version control system, and the most widely" -" used web service for this purpose is currently Github. Here you can " -"find, for example, the Spyder and Python repositories." +msgid "Now that we have our local virtual environment, it is good practice to manage our source code with a version control system, and the most widely used web service for this purpose is currently Github. Here you can find, for example, the Spyder and Python repositories." +msgstr "" + +#: ../../workshops/plugin-development.rst:260 +msgid "Git and Github repository concepts." msgstr "" #: ../../workshops/plugin-development.rst:263 @@ -2001,16 +1467,11 @@ msgid "Log in to your Github account." msgstr "" #: ../../workshops/plugin-development.rst:266 -msgid "" -"Click on the \"New repository\" option in the \"+\" menu at the top right" -" next to your profile picture." +msgid "Click on the \"New repository\" option in the \"+\" menu at the top right next to your profile picture." msgstr "" #: ../../workshops/plugin-development.rst:267 -msgid "" -"A dialog will appear where you can insert the repository name and some " -"basic options, e.g. to initialize the repository with a README or license" -" files." +msgid "A dialog will appear where you can insert the repository name and some basic options, e.g. to initialize the repository with a README or license files." msgstr "" #: ../../workshops/plugin-development.rst:268 @@ -2018,24 +1479,15 @@ msgid "Click the “Create repository” button." msgstr "" #: ../../workshops/plugin-development.rst:269 -msgid "" -"In the main window of the recently created repository, click on the green" -" \"Code\" button an copy the clone link." +msgid "In the main window of the recently created repository, click on the green \"Code\" button an copy the clone link." msgstr "" #: ../../workshops/plugin-development.rst:270 -msgid "" -"In your local command line run ``$ git clone [repo-link]``. You must have" -" git installed and configured on your computer. If you don't have " -"experience using git we recommend The Carpentries workshop `Version " -"control with git`_." +msgid "In your local command line run ``$ git clone [repo-link]``. You must have git installed and configured on your computer. If you don't have experience using git we recommend The Carpentries workshop `Version control with git`_." msgstr "" #: ../../workshops/plugin-development.rst:272 -msgid "" -"A detailed description of `repository creation`_ could be found in the " -"official Github documentation, and a `hello world`_ tutorial with basic " -"git operations from the Github interface." +msgid "A detailed description of `repository creation`_ could be found in the official Github documentation, and a `hello world`_ tutorial with basic git operations from the Github interface." msgstr "" #: ../../workshops/plugin-development.rst:282 @@ -2043,24 +1495,19 @@ msgid "Let's get started" msgstr "" #: ../../workshops/plugin-development.rst:284 -msgid "" -"We already have a git repository and a virtual environment where Spyder 5" -" is installed." +msgid "We already have a git repository and a virtual environment where Spyder 5 is installed." msgstr "" #: ../../workshops/plugin-development.rst:286 -msgid "" -"Let's activate our environment and go into the local folder of our " -"repository." +msgid "Let's activate our environment and go into the local folder of our repository." msgstr "" #: ../../workshops/plugin-development.rst:293 -msgid "" -"Then we need to use ``cookiecutter`` to create the initial structure of " -"our plugin. `cookiecutter`_ is a tool made in Python specifically " -"designed to create project templates. We have developed one of these " -"templates to generate the basic structure of a plugin, it can be found " -"at: https://github.com/spyder-ide/spyder5-plugin-cookiecutter" +msgid "Then we need to use ``cookiecutter`` to create the initial structure of our plugin. `cookiecutter`_ is a tool made in Python specifically designed to create project templates. We have developed one of these templates to generate the basic structure of a plugin, it can be found at: https://github.com/spyder-ide/spyder5-plugin-cookiecutter" +msgstr "" + +#: ../../workshops/plugin-development.rst:298 +msgid "Folder structure of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:301 @@ -2072,9 +1519,7 @@ msgid "The plugin structure" msgstr "" #: ../../workshops/plugin-development.rst:334 -msgid "" -"After ``cookicutter`` finishes its job, you'll get the following tree " -"structure in your repository" +msgid "After ``cookicutter`` finishes its job, you'll get the following tree structure in your repository" msgstr "" #: ../../workshops/plugin-development.rst:356 @@ -2086,19 +1531,11 @@ msgid "The Makefile, which has several useful commands:" msgstr "" #: ../../workshops/plugin-development.rst:375 -msgid "" -"``setup.py``, which helps you to install, package and distribute your " -"plugin with ``setuptools``, the standard for distributing Python Modules." -" On this file the ``entry_points`` parameter of ``setup`` is quite " -"important, as it is the one that allows Spyder to identify this package " -"as a plugin, and to know how to access its functionalities." +msgid "``setup.py``, which helps you to install, package and distribute your plugin with ``setuptools``, the standard for distributing Python Modules. On this file the ``entry_points`` parameter of ``setup`` is quite important, as it is the one that allows Spyder to identify this package as a plugin, and to know how to access its functionalities." msgstr "" #: ../../workshops/plugin-development.rst:380 -msgid "" -"The ``spyder-pomodoro-timer`` folder has the name you introduced when " -"running ``cookiecutter``. Inside this you'll see a folder called " -"``spyder``, where we will place the code of our plugin." +msgid "The ``spyder-pomodoro-timer`` folder has the name you introduced when running ``cookiecutter``. Inside this you'll see a folder called ``spyder``, where we will place the code of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:382 @@ -2106,56 +1543,31 @@ msgid "In the ``spyder`` directory you'll find the following files:" msgstr "" #: ../../workshops/plugin-development.rst:384 -msgid "" -"``api.py``: where the functionality of the plugin is exposed to the rest " -"of Spyder. That would allow additional functionality to be added from " -"other plugins." +msgid "``api.py``: where the functionality of the plugin is exposed to the rest of Spyder. That would allow additional functionality to be added from other plugins." msgstr "" #: ../../workshops/plugin-development.rst:386 -msgid "" -"``plugin.py``: is the core of the plugin. Depending on the type of plugin" -" we created, here you'll see an instance of ``SpyderDockablePlugin`` or " -"``SpyderPluginV2``." +msgid "``plugin.py``: is the core of the plugin. Depending on the type of plugin we created, here you'll see an instance of ``SpyderDockablePlugin`` or ``SpyderPluginV2``." msgstr "" #: ../../workshops/plugin-development.rst:388 -msgid "" -"If it is a ``SpyderPluginV2`` you should set a constant class named " -"``CONTAINER_CLASS`` with an instance of ``PluginMainContainer``." +msgid "If it is a ``SpyderPluginV2`` you should set a constant class named ``CONTAINER_CLASS`` with an instance of ``PluginMainContainer``." msgstr "" #: ../../workshops/plugin-development.rst:389 -msgid "" -"If it is a ``SpyderDockablePlugin`` you should set a constant class named" -" ``WIDGET_CLASS`` with an instance of ``PluginMainWidget``." +msgid "If it is a ``SpyderDockablePlugin`` you should set a constant class named ``WIDGET_CLASS`` with an instance of ``PluginMainWidget``." msgstr "" #: ../../workshops/plugin-development.rst:391 -msgid "" -"``container.py``: only used for ``SpyderPluginV2`` plugins. This file " -"contains an instance of ``PluginMainContainer`` that holds a reference to" -" all graphical elements (or widgets) that the plugin is going to add to " -"the interface. This is necessary because Qt requires widgets to be " -"children of other widgets before using them (otherwise they appear as " -"floating windows). Since ``SpyderPluginV2`` is not a widget, we need a " -"data structure (i.e. the container) that is a widget for that." +msgid "``container.py``: only used for ``SpyderPluginV2`` plugins. This file contains an instance of ``PluginMainContainer`` that holds a reference to all graphical elements (or widgets) that the plugin is going to add to the interface. This is necessary because Qt requires widgets to be children of other widgets before using them (otherwise they appear as floating windows). Since ``SpyderPluginV2`` is not a widget, we need a data structure (i.e. the container) that is a widget for that." msgstr "" #: ../../workshops/plugin-development.rst:393 -msgid "" -"``widgets.py``: in this file we will add the graphical components of our " -"plugin. If it is of type ``SpyderPluginV2`` and it does not have widgets," -" then it is not necessary. We can also place here the instance of " -"``PluginMainWidget`` necessary for ``SpyderDockablePlugin``, if we are " -"developing that kind of plugin." +msgid "``widgets.py``: in this file we will add the graphical components of our plugin. If it is of type ``SpyderPluginV2`` and it does not have widgets, then it is not necessary. We can also place here the instance of ``PluginMainWidget`` necessary for ``SpyderDockablePlugin``, if we are developing that kind of plugin." msgstr "" #: ../../workshops/plugin-development.rst:396 -msgid "" -"``confpage.py``: this is where you specify the configuration page that " -"will be displayed in ``Preferences``, so that the user can adjust the " -"options of our plugin." +msgid "``confpage.py``: this is where you specify the configuration page that will be displayed in ``Preferences``, so that the user can adjust the options of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:402 @@ -2163,10 +1575,7 @@ msgid "Building our first plugin" msgstr "" #: ../../workshops/plugin-development.rst:404 -msgid "" -"From now on we will be building the plugin step by step. In the `spyder " -"pomodoro timer repository`_ you will find the final version of the code " -"for you to take a look at it, in case we are missing any detail." +msgid "From now on we will be building the plugin step by step. In the `spyder pomodoro timer repository`_ you will find the final version of the code for you to take a look at it, in case we are missing any detail." msgstr "" #: ../../workshops/plugin-development.rst:409 @@ -2175,57 +1584,35 @@ msgid "Widgets" msgstr "" #: ../../workshops/plugin-development.rst:411 -msgid "" -"The best way to start building our plugin is by implementing its " -"graphical components first in ``widgets.py``" +msgid "The best way to start building our plugin is by implementing its graphical components first in ``widgets.py``" msgstr "" #: ../../workshops/plugin-development.rst:413 -msgid "" -"Let's call the initial version, without any editing ``INITIAL``. In " -"`INITIAL`_, widgets.py is as follows:" +msgid "Let's call the initial version, without any editing ``INITIAL``. In `INITIAL`_, widgets.py is as follows:" msgstr "" #: ../../workshops/plugin-development.rst:431 -msgid "" -"The preset imports are a guide to what we will need in our plugin. The " -"``on_conf_change`` decorator will allow us to propagate the changes in " -"configuration. ``get_translation`` helps us to generate translation " -"strings for the plugin and ``SpyderWidgetMixin`` adds to any widget the " -"attributes and methods needed to integrate it with Spyder (icon, style, " -"translation, actions and extra options)." +msgid "The preset imports are a guide to what we will need in our plugin. The ``on_conf_change`` decorator will allow us to propagate the changes in configuration. ``get_translation`` helps us to generate translation strings for the plugin and ``SpyderWidgetMixin`` adds to any widget the attributes and methods needed to integrate it with Spyder (icon, style, translation, actions and extra options)." msgstr "" #: ../../workshops/plugin-development.rst:433 -msgid "" -"When taking a look at the Spyder ``api`` module, we can find that in " -"Spyder there are two types of predefined components for the status bar:" +msgid "When taking a look at the Spyder ``api`` module, we can find that in Spyder there are two types of predefined components for the status bar:" msgstr "" #: ../../workshops/plugin-development.rst:435 -msgid "" -"``StatusBarWidget``, a class derived from ``QWidget`` and " -"``SpyderWidgetMixin``, which contains an icon, a label and a spinner (to " -"show the plugin loading)." +msgid "``StatusBarWidget``, a class derived from ``QWidget`` and ``SpyderWidgetMixin``, which contains an icon, a label and a spinner (to show the plugin loading)." msgstr "" #: ../../workshops/plugin-development.rst:436 -msgid "" -"``BaseTimerStatus``, a class derived from ``StatusBarWidget`` with an " -"internal ``QTimer`` to periodically update its content." +msgid "``BaseTimerStatus``, a class derived from ``StatusBarWidget`` with an internal ``QTimer`` to periodically update its content." msgstr "" #: ../../workshops/plugin-development.rst:440 -msgid "" -"Below, we will be indicating links in github with the diffs between the " -"tags, this as an aid to check the progressive changes that will be made " -"in the code." +msgid "Below, we will be indicating links in github with the diffs between the tags, this as an aid to check the progressive changes that will be made in the code." msgstr "" #: ../../workshops/plugin-development.rst:442 -msgid "" -"The first version that we are going to reach after the first editions " -"will be called ``HELLO WORLD``." +msgid "The first version that we are going to reach after the first editions will be called ``HELLO WORLD``." msgstr "" #: ../../workshops/plugin-development.rst:444 @@ -2233,9 +1620,7 @@ msgid "`INITIAL -> HELLO WORLD widgets.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:448 -msgid "" -"Since we want a widget that shows the pomodoro countdown and is " -"periodically updated, we will use a ``BaseTimerStatus`` instance." +msgid "Since we want a widget that shows the pomodoro countdown and is periodically updated, we will use a ``BaseTimerStatus`` instance." msgstr "" #: ../../workshops/plugin-development.rst:450 @@ -2255,34 +1640,27 @@ msgid "With that, we can write our first widget like this" msgstr "" #: ../../workshops/plugin-development.rst:493 -msgid "" -"Spyder needs ``ID`` to be defined for ``BaseTimerStatus``. Its " -"constructor calls the parent class constructor and initializes the label " -"with ``value``." +msgid "Spyder needs ``ID`` to be defined for ``BaseTimerStatus``. Its constructor calls the parent class constructor and initializes the label with ``value``." msgstr "" #: ../../workshops/plugin-development.rst:495 -msgid "" -"We add a tooltip to verify the presence of our widget. Since Spyder uses " -"``qtawesome`` (another of our projects that eases the incorporation of " -"iconic fonts into PyQt applications), we can select an appropriate icon " -"by running the ``qta-browser`` command on a terminal." +msgid "We add a tooltip to verify the presence of our widget. Since Spyder uses ``qtawesome`` (another of our projects that eases the incorporation of iconic fonts into PyQt applications), we can select an appropriate icon by running the ``qta-browser`` command on a terminal." msgstr "" #: ../../workshops/plugin-development.rst:501 msgid "From here we can select and copy the name of the icon of our preference." msgstr "" +#: ../../workshops/plugin-development.rst:503 +msgid "qta browser dialog" +msgstr "" + #: ../../workshops/plugin-development.rst:506 -msgid "" -"To finish the implementation of our widget, we need to add the following " -"method:" +msgid "To finish the implementation of our widget, we need to add the following method:" msgstr "" #: ../../workshops/plugin-development.rst:516 -msgid "" -"``BaseTimerStatus`` requires this method to be implemented to update its " -"content every time it is requested by the internal timer." +msgid "``BaseTimerStatus`` requires this method to be implemented to update its content every time it is requested by the internal timer." msgstr "" #: ../../workshops/plugin-development.rst:520 @@ -2290,12 +1668,7 @@ msgid "The container" msgstr "" #: ../../workshops/plugin-development.rst:522 -msgid "" -"The next step in the development of our plugin is to create an instance " -"of the widget we wrote above, so we can add it to Spyder's status bar. " -"For that, we need to use a container. Due to Qt specifics, we need an " -"instance of ``QWidget`` (the container) to be the parent of all other " -"widgets part of our plugin (as mentioned above)." +msgid "The next step in the development of our plugin is to create an instance of the widget we wrote above, so we can add it to Spyder's status bar. For that, we need to use a container. Due to Qt specifics, we need an instance of ``QWidget`` (the container) to be the parent of all other widgets part of our plugin (as mentioned above)." msgstr "" #: ../../workshops/plugin-development.rst:524 @@ -2307,15 +1680,11 @@ msgid "`INITIAL -> HELLO WORLD container.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:551 -msgid "" -"In this case ``SpyderPomodoroTimerContainer`` is already defined, and we " -"must implement the ``setup`` and ``update_actions`` methods." +msgid "In this case ``SpyderPomodoroTimerContainer`` is already defined, and we must implement the ``setup`` and ``update_actions`` methods." msgstr "" #: ../../workshops/plugin-development.rst:553 -msgid "" -"Now we are going to add the widget created earlier to the container. To " -"do so, first we need to import the widget." +msgid "Now we are going to add the widget created earlier to the container. To do so, first we need to import the widget." msgstr "" #: ../../workshops/plugin-development.rst:560 @@ -2327,10 +1696,7 @@ msgid "Plugin" msgstr "" #: ../../workshops/plugin-development.rst:572 -msgid "" -"Finally, we define our plugin so that it is registered within Spyder. The" -" `INITIAL`_ version (i.e. the one created by cookiecutter) for " -"``plugin.py`` is:" +msgid "Finally, we define our plugin so that it is registered within Spyder. The `INITIAL`_ version (i.e. the one created by cookiecutter) for ``plugin.py`` is:" msgstr "" #: ../../workshops/plugin-development.rst:575 @@ -2346,10 +1712,7 @@ msgid "`INITIAL -> HELLO WORLD plugin.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:637 -msgid "" -"First, we need to declare the dependencies of our plugin, by defining the" -" ``REQUIRES`` class constant. Since we're going to add a status bar " -"widget, we require the ``StatusBar`` plugin, as shown below." +msgid "First, we need to declare the dependencies of our plugin, by defining the ``REQUIRES`` class constant. Since we're going to add a status bar widget, we require the ``StatusBar`` plugin, as shown below." msgstr "" #: ../../workshops/plugin-development.rst:643 @@ -2367,9 +1730,7 @@ msgid "by" msgstr "" #: ../../workshops/plugin-development.rst:676 -msgid "" -"Due to recent changes to the Spyder API, we need to add to the spyder " -"imports" +msgid "Due to recent changes to the Spyder API, we need to add to the spyder imports" msgstr "" #: ../../workshops/plugin-development.rst:683 @@ -2377,9 +1738,7 @@ msgid "And add the following after the ``on_initialize`` method:" msgstr "" #: ../../workshops/plugin-development.rst:693 -msgid "" -"With these changes, Spyder will be aware of the presence of our plugin, " -"and that this plugin adds a new widget to the status bar." +msgid "With these changes, Spyder will be aware of the presence of our plugin, and that this plugin adds a new widget to the status bar." msgstr "" #: ../../workshops/plugin-development.rst:695 @@ -2387,21 +1746,19 @@ msgid "Finally, we add the following method to our plugin:" msgstr "" #: ../../workshops/plugin-development.rst:704 -msgid "" -"In this way, ``SpyderPomodoroTimer`` can access ``pomodoro_timer_status``" -" of ``SpyderPomodoroTimerContainer`` as if it were its own property." +msgid "In this way, ``SpyderPomodoroTimer`` can access ``pomodoro_timer_status`` of ``SpyderPomodoroTimerContainer`` as if it were its own property." msgstr "" #: ../../workshops/plugin-development.rst:706 msgid "In summary, we did the following:" msgstr "" +#: ../../workshops/plugin-development.rst:708 +msgid "Basic structure of Pomodoro Timer Spyder plugin." +msgstr "" + #: ../../workshops/plugin-development.rst:711 -msgid "" -"We created a widget, then we added it to the container, which is " -"registered in the plugin through the ``CONTAINER_CLASS`` constant. In the" -" plugin, we accessed the instance of that widget and added it to the " -"status bar." +msgid "We created a widget, then we added it to the container, which is registered in the plugin through the ``CONTAINER_CLASS`` constant. In the plugin, we accessed the instance of that widget and added it to the status bar." msgstr "" #: ../../workshops/plugin-development.rst:717 @@ -2413,9 +1770,7 @@ msgid "Now it is time to see how our plugin looks in the Spyder interface." msgstr "" #: ../../workshops/plugin-development.rst:721 -msgid "" -"**From the root folder of our plugin**, we activate the environment where" -" Spyder is installed, and run:" +msgid "**From the root folder of our plugin**, we activate the environment where Spyder is installed, and run:" msgstr "" #: ../../workshops/plugin-development.rst:729 @@ -2423,16 +1778,15 @@ msgid "Now we can see two outputs. The first one is shown in the command line:" msgstr "" #: ../../workshops/plugin-development.rst:736 -msgid "" -"And in Spyder you'll see our plugin in the status bar with the tooltip " -"\"I am the Pomodoro tooltip\"." +msgid "And in Spyder you'll see our plugin in the status bar with the tooltip \"I am the Pomodoro tooltip\"." +msgstr "" + +#: ../../workshops/plugin-development.rst:738 +msgid "First version of our plugin" msgstr "" #: ../../workshops/plugin-development.rst:741 -msgid "" -"Keep in mind that every time we make a change to our code, it is " -"necessary to restart Spyder so that the plugin is reloaded and we can " -"check the changes." +msgid "Keep in mind that every time we make a change to our code, it is necessary to restart Spyder so that the plugin is reloaded and we can check the changes." msgstr "" #: ../../workshops/plugin-development.rst:747 @@ -2440,12 +1794,7 @@ msgid "Enhancing our plugin" msgstr "" #: ../../workshops/plugin-development.rst:749 -msgid "" -"From now on we are going to go into details of how things are implemented" -" in Qt. So in case you have any doubts, the Qt documentation will be your" -" best guide. We created an annex to this workshop that quickly explains " -"way the fundamental concepts of Qt for those in a hurry: :ref:`qt-" -"fundamentals`" +msgid "From now on we are going to go into details of how things are implemented in Qt. So in case you have any doubts, the Qt documentation will be your best guide. We created an annex to this workshop that quickly explains way the fundamental concepts of Qt for those in a hurry: :ref:`qt-fundamentals`" msgstr "" #: ../../workshops/plugin-development.rst:754 @@ -2453,23 +1802,15 @@ msgid "Timer updates" msgstr "" #: ../../workshops/plugin-development.rst:756 -msgid "" -"The first problem with our plugin is that its pomodoro timer is not being" -" updated. To activate it we can use the ``QTimer`` in " -"``PomodoroTimerStatus``, which is present because it's an instance of " -"``BaseTimerStatus``." +msgid "The first problem with our plugin is that its pomodoro timer is not being updated. To activate it we can use the ``QTimer`` in ``PomodoroTimerStatus``, which is present because it's an instance of ``BaseTimerStatus``." msgstr "" #: ../../workshops/plugin-development.rst:758 -msgid "" -"The second version where the value in the status bar is updated is called" -" ``TIMER``." +msgid "The second version where the value in the status bar is updated is called ``TIMER``." msgstr "" #: ../../workshops/plugin-development.rst:760 -msgid "" -"Let's go back to ``widgets.py`` and add this constant below the import " -"lines (line 22)." +msgid "Let's go back to ``widgets.py`` and add this constant below the import lines (line 22)." msgstr "" #: ../../workshops/plugin-development.rst:762 @@ -2477,9 +1818,7 @@ msgid "`HELLO WORLD -> TIMER widgets.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:774 -msgid "" -"``POMODORO_DEFAULT`` is to set the pomodoro time limit in milliseconds, " -"and ``INTERVAL`` to the timer update rate." +msgid "``POMODORO_DEFAULT`` is to set the pomodoro time limit in milliseconds, and ``INTERVAL`` to the timer update rate." msgstr "" #: ../../workshops/plugin-development.rst:776 @@ -2487,22 +1826,11 @@ msgid "Now, in the ``__init__`` method of ``PomodoroTimerStatus`` we need to add msgstr "" #: ../../workshops/plugin-development.rst:788 -msgid "" -"Up to this point, we created a default value (``POMODORO_DEFAULT``) for " -"the timer duration during pomodoros; we added it to the " -"``pomodoro_limit`` attribute to be able to configure it; and with that " -"value we initialized the ``countdown`` attribute that will be modified " -"over time. As for the update interval of the timer, we set it to to the " -"value of ``INTERVAL``, which corresponds to 1 second (one thousand " -"milliseconds)." +msgid "Up to this point, we created a default value (``POMODORO_DEFAULT``) for the timer duration during pomodoros; we added it to the ``pomodoro_limit`` attribute to be able to configure it; and with that value we initialized the ``countdown`` attribute that will be modified over time. As for the update interval of the timer, we set it to to the value of ``INTERVAL``, which corresponds to 1 second (one thousand milliseconds)." msgstr "" #: ../../workshops/plugin-development.rst:791 -msgid "" -"The function of ``self.timer`` is to update our timer periodically. This " -"is done through the method ``timeout.connect()``, to which we pass as " -"parameter the reference to the ``update_timer`` function that will " -"perform the required adjustments." +msgid "The function of ``self.timer`` is to update our timer periodically. This is done through the method ``timeout.connect()``, to which we pass as parameter the reference to the ``update_timer`` function that will perform the required adjustments." msgstr "" #: ../../workshops/plugin-development.rst:793 @@ -2510,26 +1838,23 @@ msgid "Now let's implement ``update_timer`` at the end of the file:" msgstr "" #: ../../workshops/plugin-development.rst:813 -msgid "" -"Here we rely on the ``display_time`` method that converts the current " -"``countdown`` value, which is measured in milliseconds, into a human-" -"readable format. And ``update_timer`` simply keeps updating the countdown" -" until it reaches zero." +msgid "Here we rely on the ``display_time`` method that converts the current ``countdown`` value, which is measured in milliseconds, into a human-readable format. And ``update_timer`` simply keeps updating the countdown until it reaches zero." msgstr "" #: ../../workshops/plugin-development.rst:815 msgid "If we run Spyder again we will find that our timer has come to life." msgstr "" +#: ../../workshops/plugin-development.rst:817 +msgid "Timer countdown working." +msgstr "" + #: ../../workshops/plugin-development.rst:824 msgid "Timer controls" msgstr "" #: ../../workshops/plugin-development.rst:826 -msgid "" -"Now we need a way to control our timer. We can achieve this by adding " -"some buttons to Spyder's toolbar, which will be useful to learn how to " -"work with toolbars, menus and actions in Spyder." +msgid "Now we need a way to control our timer. We can achieve this by adding some buttons to Spyder's toolbar, which will be useful to learn how to work with toolbars, menus and actions in Spyder." msgstr "" #: ../../workshops/plugin-development.rst:830 @@ -2537,9 +1862,7 @@ msgid "PomodoroTimerToolbar" msgstr "" #: ../../workshops/plugin-development.rst:832 -msgid "" -"The next version where actions are added to the toolbar is called " -"``ACTIONS``." +msgid "The next version where actions are added to the toolbar is called ``ACTIONS``." msgstr "" #: ../../workshops/plugin-development.rst:834 @@ -2547,37 +1870,23 @@ msgid "`TIMER -> ACTIONS widgets.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:838 -msgid "" -"Let's go back to ``widgets.py`` and import the Spyder application toolbar" -" class:" +msgid "Let's go back to ``widgets.py`` and import the Spyder application toolbar class:" msgstr "" #: ../../workshops/plugin-development.rst:844 -msgid "" -"And create an instance of it by adding the following code before the " -"definition of ``PomodoroTimerStatus``:" +msgid "And create an instance of it by adding the following code before the definition of ``PomodoroTimerStatus``:" msgstr "" #: ../../workshops/plugin-development.rst:853 -msgid "" -"As you can see, this statement is very simple. It only needs to declare " -"an ``ID``, that serves to identify our toolabr among the rest." +msgid "As you can see, this statement is very simple. It only needs to declare an ``ID``, that serves to identify our toolabr among the rest." msgstr "" #: ../../workshops/plugin-development.rst:855 -msgid "" -"It is possible to include other Qt widgets in our toolbar, but in this " -"case it's better to use the appropriate Spyder methods for that in order " -"to maintain their relationship with the rest of the application. In other" -" words, as long as the widget you need exists in ``spyder.api.widgets``, " -"use it!" +msgid "It is possible to include other Qt widgets in our toolbar, but in this case it's better to use the appropriate Spyder methods for that in order to maintain their relationship with the rest of the application. In other words, as long as the widget you need exists in ``spyder.api.widgets``, use it!" msgstr "" #: ../../workshops/plugin-development.rst:858 -msgid "" -"Next, we need to declare a boolean variable in our status widget to " -"indicate if the countdown is paused or not. For that, let's add the " -"following inside the ``__init__`` method of ``PomodoroTimerStatus``:" +msgid "Next, we need to declare a boolean variable in our status widget to indicate if the countdown is paused or not. For that, let's add the following inside the ``__init__`` method of ``PomodoroTimerStatus``:" msgstr "" #: ../../workshops/plugin-development.rst:864 @@ -2589,12 +1898,7 @@ msgid "Create the Pomodoro Toolbar" msgstr "" #: ../../workshops/plugin-development.rst:882 -msgid "" -"Now we are going to create a new section in our toolbar and associate " -"some functionality to it by means of actions. This particular information" -" is recommended to be included in the ``api.py`` file because this way we" -" can offer endpoints to the rest of Spyder and new plugins for tweaking " -"the behavior of our plugin." +msgid "Now we are going to create a new section in our toolbar and associate some functionality to it by means of actions. This particular information is recommended to be included in the ``api.py`` file because this way we can offer endpoints to the rest of Spyder and new plugins for tweaking the behavior of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:884 @@ -2606,19 +1910,11 @@ msgid "Let's add the following to the end of ``api.py``:" msgstr "" #: ../../workshops/plugin-development.rst:904 -msgid "" -"With these we are telling the rest of Spyder, and our own plugin, that we" -" are going to have a new toolbar section called \"pomodoro_timer\". This " -"section will consist of a button containing a menu (with a single section" -" \"main_section\") and actions identified as \"start_timer\", " -"\"pause_timer\" and \"stop_timer\", to start, pause and stop (resetting) " -"our timer, respectively." +msgid "With these we are telling the rest of Spyder, and our own plugin, that we are going to have a new toolbar section called \"pomodoro_timer\". This section will consist of a button containing a menu (with a single section \"main_section\") and actions identified as \"start_timer\", \"pause_timer\" and \"stop_timer\", to start, pause and stop (resetting) our timer, respectively." msgstr "" #: ../../workshops/plugin-development.rst:906 -msgid "" -"Note that these are simple class definitions with class constants, to " -"ease the encapsulation and exchange of this information in a simple way." +msgid "Note that these are simple class definitions with class constants, to ease the encapsulation and exchange of this information in a simple way." msgstr "" #: ../../workshops/plugin-development.rst:909 @@ -2630,25 +1926,15 @@ msgid "`TIMER -> ACTIONS container.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:915 -msgid "" -"Now let's go to ``container.py``, where we are going to implement the " -"behavior of our new toolbar and its actions. In this case, we are not " -"going to specify the internal behavior of our plugin, but the " -"relationship between its widgets and other areas of Spyder, so it is more" -" convenient to do it in the container." +msgid "Now let's go to ``container.py``, where we are going to implement the behavior of our new toolbar and its actions. In this case, we are not going to specify the internal behavior of our plugin, but the relationship between its widgets and other areas of Spyder, so it is more convenient to do it in the container." msgstr "" #: ../../workshops/plugin-development.rst:918 -msgid "" -"As we did with ``PomodoroTimerStatus``, we are going to use ``qtawesome``" -" icons for our actions. For this purpose, let's add at the beginning of " -"our imports:" +msgid "As we did with ``PomodoroTimerStatus``, we are going to use ``qtawesome`` icons for our actions. For this purpose, let's add at the beginning of our imports:" msgstr "" #: ../../workshops/plugin-development.rst:926 -msgid "" -"We also imported ``QToolButton`` because it will be used to set the " -"button that we will add in our toolbar." +msgid "We also imported ``QToolButton`` because it will be used to set the button that we will add in our toolbar." msgstr "" #: ../../workshops/plugin-development.rst:928 @@ -2656,39 +1942,27 @@ msgid "At the end of the Spyder imports we also need:" msgstr "" #: ../../workshops/plugin-development.rst:934 -msgid "" -"Now, let's include ``PomodoroTimerToolbar`` and the actions and sections " -"we just declared in ``api.py`` in our local imports:" +msgid "Now, let's include ``PomodoroTimerToolbar`` and the actions and sections we just declared in ``api.py`` in our local imports:" msgstr "" #: ../../workshops/plugin-development.rst:948 -msgid "" -"Next, we need to do following things in the ``setup`` method of " -"``SpyderPomodoroTimerContainer``." +msgid "Next, we need to do following things in the ``setup`` method of ``SpyderPomodoroTimerContainer``." msgstr "" #: ../../workshops/plugin-development.rst:950 -msgid "" -"The first one is to create an instance of the toolbar class we declared " -"earlier:" +msgid "The first one is to create an instance of the toolbar class we declared earlier:" msgstr "" #: ../../workshops/plugin-development.rst:957 -msgid "" -"The second one is to create the actions corresponding to Start, Pause and" -" Stop our pomodoro timer:" +msgid "The second one is to create the actions corresponding to Start, Pause and Stop our pomodoro timer:" msgstr "" #: ../../workshops/plugin-development.rst:986 -msgid "" -"The third one is to create the menu that will contain our actions and add" -" them to it." +msgid "The third one is to create the menu that will contain our actions and add them to it." msgstr "" #: ../../workshops/plugin-development.rst:1004 -msgid "" -"The fourth one is to create a button that will contain the menu and " -"configure it as ``PopupMode``, so that it is displayed when clicked." +msgid "The fourth one is to create a button that will contain the menu and configure it as ``PopupMode``, so that it is displayed when clicked." msgstr "" #: ../../workshops/plugin-development.rst:1017 @@ -2696,24 +1970,15 @@ msgid "And finally, the fifth one is to add the button to our toolbar:" msgstr "" #: ../../workshops/plugin-development.rst:1028 -msgid "" -"When creating the actions, we indicate by means of the ``triggered`` " -"parameter the methods to be executed when they are activated, i.e. when " -"the corresponding buttons on the toolbar are clicked." +msgid "When creating the actions, we indicate by means of the ``triggered`` parameter the methods to be executed when they are activated, i.e. when the corresponding buttons on the toolbar are clicked." msgstr "" #: ../../workshops/plugin-development.rst:1030 -msgid "" -"We can insert these methods at the end of the " -"``SpyderPomodoroTimerContainer`` declaration, in the section that our " -"cookiecutter template indicates as ``# --- Public API``." +msgid "We can insert these methods at the end of the ``SpyderPomodoroTimerContainer`` declaration, in the section that our cookiecutter template indicates as ``# --- Public API``." msgstr "" #: ../../workshops/plugin-development.rst:1050 -msgid "" -"These methods simply manipulate the ``pause`` field of " -"``pomodoro_timer_status``, and in the case of ``stop_pomodoro_timer`` the" -" countdown is restarted." +msgid "These methods simply manipulate the ``pause`` field of ``pomodoro_timer_status``, and in the case of ``stop_pomodoro_timer`` the countdown is restarted." msgstr "" #: ../../workshops/plugin-development.rst:1053 @@ -2725,9 +1990,7 @@ msgid "`TIMER -> ACTIONS plugin.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1059 -msgid "" -"A final mandatory step is to go to ``plugin.py`` and register this new " -"toolbar component." +msgid "A final mandatory step is to go to ``plugin.py`` and register this new toolbar component." msgstr "" #: ../../workshops/plugin-development.rst:1061 @@ -2735,9 +1998,7 @@ msgid "To do this, add ``Plugins.Toolbar`` to the plugin requirements:" msgstr "" #: ../../workshops/plugin-development.rst:1067 -msgid "" -"And use this plugin's API to add the toolbar we have created in the " -"container to Spyder's toolbar." +msgid "And use this plugin's API to add the toolbar we have created in the container to Spyder's toolbar." msgstr "" #: ../../workshops/plugin-development.rst:1078 @@ -2745,27 +2006,31 @@ msgid "Review the changes" msgstr "" #: ../../workshops/plugin-development.rst:1080 -msgid "" -"The first thing we can notice is that we already have the corresponding " -"buttons in the toolbar." +msgid "The first thing we can notice is that we already have the corresponding buttons in the toolbar." +msgstr "" + +#: ../../workshops/plugin-development.rst:1082 +msgid "Pomodoro timer toolbar buttons" msgstr "" #: ../../workshops/plugin-development.rst:1085 -msgid "" -"The strings that were entered as the ``tip`` parameter in the creation of" -" the actions are shown here as the buttons' tooltips." +msgid "The strings that were entered as the ``tip`` parameter in the creation of the actions are shown here as the buttons' tooltips." msgstr "" #: ../../workshops/plugin-development.rst:1087 -msgid "" -"Also, if we check the menu \"View > Toolbars\", we find that there is a " -"new entry there corresponding to our toolbar." +msgid "Also, if we check the menu \"View > Toolbars\", we find that there is a new entry there corresponding to our toolbar." +msgstr "" + +#: ../../workshops/plugin-development.rst:1089 +msgid "View > Toolbars menu with \"Pomodoro Timer Toolbar\" option." msgstr "" #: ../../workshops/plugin-development.rst:1093 -msgid "" -"Finally, let's check how the new Pomodoro Timer control buttons in the " -"toolbar interact with the component in the status bar." +msgid "Finally, let's check how the new Pomodoro Timer control buttons in the toolbar interact with the component in the status bar." +msgstr "" + +#: ../../workshops/plugin-development.rst:1095 +msgid "Interaction between the Pomodoro Timer toolbar and its status bar." msgstr "" #: ../../workshops/plugin-development.rst:1102 @@ -2773,9 +2038,7 @@ msgid "Add a Configuration Page" msgstr "" #: ../../workshops/plugin-development.rst:1104 -msgid "" -"Another feature of Spyder plugins is that they can have configurable " -"options that appear in Spyder's Preferences window." +msgid "Another feature of Spyder plugins is that they can have configurable options that appear in Spyder's Preferences window." msgstr "" #: ../../workshops/plugin-development.rst:1107 @@ -2783,16 +2046,11 @@ msgid "Configuration defaults" msgstr "" #: ../../workshops/plugin-development.rst:1109 -msgid "" -"The final version in which we add a configurable parameter will be called" -" ``CONFPAGE``." +msgid "The final version in which we add a configurable parameter will be called ``CONFPAGE``." msgstr "" #: ../../workshops/plugin-development.rst:1111 -msgid "" -"The first step is to define what options we want to offer to our users. " -"For this we must create a new file, which we can call ``conf.py``. In " -"this file we will write the following:" +msgid "The first step is to define what options we want to offer to our users. For this we must create a new file, which we can call ``conf.py``. In this file we will write the following:" msgstr "" #: ../../workshops/plugin-development.rst:1113 @@ -2800,26 +2058,15 @@ msgid "`ACTIONS -> CONFPAGE config.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1138 -msgid "" -"We must highlight the declaration of ``CONF_SECTION``, which is the " -"internal name of the section in Preferences corresponding to our plugin; " -"and the dictionary keys associated with ``CONF_DEFAULTS``. In this case, " -"we are indicating that ``pomodoro_limit`` is a configurable parameter " -"within the ``spyder_pomodoro_timer`` section." +msgid "We must highlight the declaration of ``CONF_SECTION``, which is the internal name of the section in Preferences corresponding to our plugin; and the dictionary keys associated with ``CONF_DEFAULTS``. In this case, we are indicating that ``pomodoro_limit`` is a configurable parameter within the ``spyder_pomodoro_timer`` section." msgstr "" #: ../../workshops/plugin-development.rst:1140 -msgid "" -"At the end of this file it is necessary to set another important " -"constant, ``CONF_VERSION``, which must be updated when adding, removing " -"or renaming configurable parameters in successive versions of the plugin." +msgid "At the end of this file it is necessary to set another important constant, ``CONF_VERSION``, which must be updated when adding, removing or renaming configurable parameters in successive versions of the plugin." msgstr "" #: ../../workshops/plugin-development.rst:1153 -msgid "" -"Note that we are moving the definition of ``POMODORO_DEFAULT`` from " -"``widgets.py`` to ``conf.py``, since we now have a dedicated place for " -"default configuration values." +msgid "Note that we are moving the definition of ``POMODORO_DEFAULT`` from ``widgets.py`` to ``conf.py``, since we now have a dedicated place for default configuration values." msgstr "" #: ../../workshops/plugin-development.rst:1156 @@ -2827,10 +2074,7 @@ msgid "Configuration page" msgstr "" #: ../../workshops/plugin-development.rst:1158 -msgid "" -"Now, we need to build the page that will appear in the Preferences " -"window. For this, we edit the ``confpage.py`` file generated by " -"cokkiecutter as follows:" +msgid "Now, we need to build the page that will appear in the Preferences window. For this, we edit the ``confpage.py`` file generated by cokkiecutter as follows:" msgstr "" #: ../../workshops/plugin-development.rst:1160 @@ -2838,20 +2082,11 @@ msgid "`ACTIONS -> CONFPAGE confpage.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1206 -msgid "" -"This mostly corresponds to the regular code for user interfaces based on " -"Qt widgets. In this case, our options section corresponds to a " -"``QGroupBox``, where the parameters are organized vertically using a " -"``QVBoxLayout``, and each parameter corresponds to a ``QGridLayout`` " -"where labels and inputs are distributed (in this case a ``QSpinBox``)." +msgid "This mostly corresponds to the regular code for user interfaces based on Qt widgets. In this case, our options section corresponds to a ``QGroupBox``, where the parameters are organized vertically using a ``QVBoxLayout``, and each parameter corresponds to a ``QGridLayout`` where labels and inputs are distributed (in this case a ``QSpinBox``)." msgstr "" #: ../../workshops/plugin-development.rst:1208 -msgid "" -"Configuration pages in Spyder provide some helper methods to facilitate " -"this work. For instance, ``create_spinbox`` allows to instantiate and " -"initialize in a single step the widgets corresponding prefix an suffix " -"labels together with the spinbox." +msgid "Configuration pages in Spyder provide some helper methods to facilitate this work. For instance, ``create_spinbox`` allows to instantiate and initialize in a single step the widgets corresponding prefix an suffix labels together with the spinbox." msgstr "" #: ../../workshops/plugin-development.rst:1211 @@ -2859,9 +2094,7 @@ msgid "Propagate configuration changes" msgstr "" #: ../../workshops/plugin-development.rst:1213 -msgid "" -"Since we moved all the configuration information to ``conf.py``, now we " -"have to import it from there into ``widgets.py``." +msgid "Since we moved all the configuration information to ``conf.py``, now we have to import it from there into ``widgets.py``." msgstr "" #: ../../workshops/plugin-development.rst:1215 @@ -2869,19 +2102,11 @@ msgid "`ACTIONS -> CONFPAGE widgets.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1228 -msgid "" -"Now we can access the configuration options from anywhere in our plugin " -"using the ``get_conf`` method. In this case we use it to access the value" -" of ``pomodoro_limit`` from the configuration instead of the constant " -"``POMODORO_DEFAULT``." +msgid "Now we can access the configuration options from anywhere in our plugin using the ``get_conf`` method. In this case we use it to access the value of ``pomodoro_limit`` from the configuration instead of the constant ``POMODORO_DEFAULT``." msgstr "" #: ../../workshops/plugin-development.rst:1236 -msgid "" -"Now we can add a method that updates our configurable parameter " -"``pomodoro_limit``. The ``@on_conf_change`` decorator is the one in " -"charge of capturing the signal that is generated when applying the change" -" of a specific option." +msgid "Now we can add a method that updates our configurable parameter ``pomodoro_limit``. The ``@on_conf_change`` decorator is the one in charge of capturing the signal that is generated when applying the change of a specific option." msgstr "" #: ../../workshops/plugin-development.rst:1247 @@ -2889,9 +2114,7 @@ msgid "Registering preferences" msgstr "" #: ../../workshops/plugin-development.rst:1249 -msgid "" -"Finally, it is necessary to activate the use of preferences in " -"``plugin.py``, by requiring the Preferences plugin" +msgid "Finally, it is necessary to activate the use of preferences in ``plugin.py``, by requiring the Preferences plugin" msgstr "" #: ../../workshops/plugin-development.rst:1251 @@ -2899,18 +2122,15 @@ msgid "`ACTIONS -> CONFPAGE plugin.py diff`_" msgstr "" #: ../../workshops/plugin-development.rst:1262 -msgid "" -"and registering our plugin in a method with the decorator " -"``@on_plugin_available``." +msgid "and registering our plugin in a method with the decorator ``@on_plugin_available``." msgstr "" #: ../../workshops/plugin-development.rst:1271 -msgid "" -"Now we can access the Preferences window either from the toolbar or from " -"the \"Tools > Preferences\" menu. There we will find a section called " -"*Spyder Pomodoro Timer* and inside it is the *Pomodoro timer limit* " -"parameter. If we change that value, we will see how the corresponding " -"label in the status bar changes." +msgid "Now we can access the Preferences window either from the toolbar or from the \"Tools > Preferences\" menu. There we will find a section called *Spyder Pomodoro Timer* and inside it is the *Pomodoro timer limit* parameter. If we change that value, we will see how the corresponding label in the status bar changes." +msgstr "" + +#: ../../workshops/plugin-development.rst:1273 +msgid "Pomodoro Timer toolbar configuration page." msgstr "" #: ../../workshops/plugin-development.rst:1276 @@ -2922,18 +2142,15 @@ msgid "Publishing your plugin" msgstr "" #: ../../workshops/plugin-development.rst:1284 -msgid "" -"Since the recommended way to install Spyder is through conda, the obvious" -" choice would be to publish our plugin through a channel like conda-" -"forge, but this is a task that is beyond the scope of this workshop due " -"to its complexity." +msgid "Since the recommended way to install Spyder is through conda, the obvious choice would be to publish our plugin through a channel like conda-forge, but this is a task that is beyond the scope of this workshop due to its complexity." msgstr "" #: ../../workshops/plugin-development.rst:1286 -msgid "" -"However, the tools used to publish packages in conda are usually based on" -" the packages published in PyPI. So let's see how to publish our plugin " -"there." +msgid "However, the tools used to publish packages in conda are usually based on the packages published in PyPI. So let's see how to publish our plugin there." +msgstr "" + +#: ../../workshops/plugin-development.rst:1288 +msgid "Publish your plugin in PyPI." msgstr "" #: ../../workshops/plugin-development.rst:1293 @@ -2941,25 +2158,15 @@ msgid "PyPI and TestPyPI" msgstr "" #: ../../workshops/plugin-development.rst:1295 -msgid "" -"The first thing we have to do is to create an account on the `PyPI`_ and " -"`TestPyPI`_ websites. Although our package will be finally published in " -"PyPI, it is advisable to use TestPyPI to test that our package can be " -"published properly without generating additional load to the PyPI servers" -" or affecting their logs." +msgid "The first thing we have to do is to create an account on the `PyPI`_ and `TestPyPI`_ websites. Although our package will be finally published in PyPI, it is advisable to use TestPyPI to test that our package can be published properly without generating additional load to the PyPI servers or affecting their logs." msgstr "" #: ../../workshops/plugin-development.rst:1297 -msgid "" -"Next, we need edit the ``setup.py`` file at the root of our project with " -"our own data. Fortunately, cookiecutter created one for us." +msgid "Next, we need edit the ``setup.py`` file at the root of our project with our own data. Fortunately, cookiecutter created one for us." msgstr "" #: ../../workshops/plugin-development.rst:1299 -msgid "" -"To upload our package to PyPI we have to use a tool called `Twine`_ that " -"makes this task much easier. And we can install it in our conda " -"environment using:" +msgid "To upload our package to PyPI we have to use a tool called `Twine`_ that makes this task much easier. And we can install it in our conda environment using:" msgstr "" #: ../../workshops/plugin-development.rst:1306 @@ -2967,29 +2174,19 @@ msgid "Build and check the package" msgstr "" #: ../../workshops/plugin-development.rst:1308 -msgid "" -"Before publishing our plugin we must package it. To do it we must write " -"the following from the root folder of our project (where ``setup.py`` is " -"placed):" +msgid "Before publishing our plugin we must package it. To do it we must write the following from the root folder of our project (where ``setup.py`` is placed):" msgstr "" #: ../../workshops/plugin-development.rst:1314 -msgid "" -"After that we will see that the following files are generated in the " -"``dist`` folder:" +msgid "After that we will see that the following files are generated in the ``dist`` folder:" msgstr "" #: ../../workshops/plugin-development.rst:1323 -msgid "" -"On Linux and macOS we can check that the newly built distribution " -"packages contain the expected files by inspecting the contents of the " -"``tar`` file:" +msgid "On Linux and macOS we can check that the newly built distribution packages contain the expected files by inspecting the contents of the ``tar`` file:" msgstr "" #: ../../workshops/plugin-development.rst:1329 -msgid "" -"You can also use ``twine`` to run a check on the created files in " -"``dist``:" +msgid "You can also use ``twine`` to run a check on the created files in ``dist``:" msgstr "" #: ../../workshops/plugin-development.rst:1338 @@ -2997,52 +2194,31 @@ msgid "Upload to PyPI" msgstr "" #: ../../workshops/plugin-development.rst:1340 -msgid "" -"Now we can use twine to upload the distribution packages we have built. " -"First, we will upload them to TestPyPI to make sure everything works:" +msgid "Now we can use twine to upload the distribution packages we have built. First, we will upload them to TestPyPI to make sure everything works:" msgstr "" #: ../../workshops/plugin-development.rst:1346 -msgid "" -"This command will prompt you for the username and password with which you" -" registered in TestPyPI." +msgid "This command will prompt you for the username and password with which you registered in TestPyPI." msgstr "" #: ../../workshops/plugin-development.rst:1348 -msgid "" -"If we open https://test.pypi.org/project/spyder-pomodoro-timer/ in the " -"browser we will be able to see the package we have just published." +msgid "If we open https://test.pypi.org/project/spyder-pomodoro-timer/ in the browser we will be able to see the package we have just published." msgstr "" #: ../../workshops/plugin-development.rst:1350 -msgid "" -"There we'll see that some details are missing, like the package " -"description, and that our package is marked as ``Development Status " -"5-Stable``." +msgid "There we'll see that some details are missing, like the package description, and that our package is marked as ``Development Status 5-Stable``." msgstr "" #: ../../workshops/plugin-development.rst:1352 -msgid "" -"To fix the first one, we can follow the instructions in `Making a PyPI-" -"friendly README`_. Since we already have a README file, we simply add the" -" following lines to the beginning of our ``setup.py`` file:" +msgid "To fix the first one, we can follow the instructions in `Making a PyPI-friendly README`_. Since we already have a README file, we simply add the following lines to the beginning of our ``setup.py`` file:" msgstr "" #: ../../workshops/plugin-development.rst:1368 -msgid "" -"We can also change the classifiers of our package using the following " -"site as a guide: https://pypi.org/classifiers. Here we can simply copy " -"the classifiers we consider appropriate and then paste them into our " -"code. Specifically in ``setup.py``, within the list that enters as the " -"``classifier`` argument in the call to function ``setup``." +msgid "We can also change the classifiers of our package using the following site as a guide: https://pypi.org/classifiers. Here we can simply copy the classifiers we consider appropriate and then paste them into our code. Specifically in ``setup.py``, within the list that enters as the ``classifier`` argument in the call to function ``setup``." msgstr "" #: ../../workshops/plugin-development.rst:1371 -msgid "" -"With these changes, and by bumping our plugin's version in the " -"``__init__.py`` file inside the ``spyder_pomodoro_timer`` folder, we can " -"repeat the cycle of building a new version of our package, loading it " -"into TestPyPI for checking, and finally loading it into PyPI by using:" +msgid "With these changes, and by bumping our plugin's version in the ``__init__.py`` file inside the ``spyder_pomodoro_timer`` folder, we can repeat the cycle of building a new version of our package, loading it into TestPyPI for checking, and finally loading it into PyPI by using:" msgstr "" #: ../../workshops/plugin-development.rst:1377 @@ -3050,36 +2226,19 @@ msgid "And check the result in https://pypi.org/project/spyder-pomodoro-timer/" msgstr "" #: ../../workshops/plugin-development.rst:1379 -msgid "" -"Once this is done, anyone can install our plugin in their environments " -"simply by running:" +msgid "Once this is done, anyone can install our plugin in their environments simply by running:" msgstr "" #: ../../workshops/plugin-development.rst:1396 -msgid "" -"The possibility of making a tool extensible through plugins, extensions " -"or addons, as they are usually called, is a fundamental feature that " -"allows taking advantage of the talent of third-party developers to " -"respond to needs and enhancements that are beyond the scope of the " -"application's core development team." +msgid "The possibility of making a tool extensible through plugins, extensions or addons, as they are usually called, is a fundamental feature that allows taking advantage of the talent of third-party developers to respond to needs and enhancements that are beyond the scope of the application's core development team." msgstr "" #: ../../workshops/plugin-development.rst:1398 -msgid "" -"Similarly, a plugin-based system makes the application much easier to " -"maintain. Eventually, the ability to enable and disable plugins makes it " -"more adaptable to different use cases. For instance, at present it would " -"be inconceivable to think of a web browser that does not have extensions " -"to block advertising or organize links, even if those features don't come" -" by default on them." +msgid "Similarly, a plugin-based system makes the application much easier to maintain. Eventually, the ability to enable and disable plugins makes it more adaptable to different use cases. For instance, at present it would be inconceivable to think of a web browser that does not have extensions to block advertising or organize links, even if those features don't come by default on them." msgstr "" #: ../../workshops/plugin-development.rst:1400 -msgid "" -"In Spyder we have put special interest in consolidating an API that " -"allows the development of plugins in a consistent way. The main focus of " -"the development effort between versions 4 and 5 was in this direction and" -" we are at a key moment where we expect to capitalize on all this work." +msgid "In Spyder we have put special interest in consolidating an API that allows the development of plugins in a consistent way. The main focus of the development effort between versions 4 and 5 was in this direction and we are at a key moment where we expect to capitalize on all this work." msgstr "" #: ../../workshops/plugin-development.rst:1404 @@ -3123,15 +2282,11 @@ msgid "Add a menu with actions in the toolbar." msgstr "" #: ../../workshops/plugin-development.rst:1414 -msgid "" -"Add configuration options to our plugin and display them appear in the " -"Preferences window." +msgid "Add configuration options to our plugin and display them appear in the Preferences window." msgstr "" #: ../../workshops/plugin-development.rst:1415 -msgid "" -"Edit the description and classifiers of the installable package of our " -"plugin." +msgid "Edit the description and classifiers of the installable package of our plugin." msgstr "" #: ../../workshops/plugin-development.rst:1416 @@ -3139,45 +2294,28 @@ msgid "Publish our plugin to TestPyPI and PyPI." msgstr "" #: ../../workshops/plugin-development.rst:1418 -msgid "" -"With these skills we hope to ease the way for you to develop your own " -"Spyder plugins." +msgid "With these skills we hope to ease the way for you to develop your own Spyder plugins." msgstr "" #: ../../workshops/plugin-development.rst:1420 -msgid "" -"If you have ideas for plugin development feel free to contact us through " -"the `Spyder-IDE`_ Github organization space." +msgid "If you have ideas for plugin development feel free to contact us through the `Spyder-IDE`_ Github organization space." msgstr "" #: ../../workshops/plugin-development.rst:1424 #: ../../workshops/scientific-computing.rst:776 -msgid "" -"If you are interested in an introduction to financial analysis with " -"Spyder, you can visit the workshop :doc:`Financial Data Analysis with " -"Spyder<../workshops/financial>`." +msgid "If you are interested in an introduction to financial analysis with Spyder, you can visit the workshop :doc:`Financial Data Analysis with Spyder<../workshops/financial>`." msgstr "" #: ../../workshops/plugin-development.rst:1431 -msgid "" -"As you may have noticed, there were some features left to implement such " -"as notifications when pomodoros are completed. Try to implement them and " -"do not hesitate to contact us if you have any doubts." +msgid "As you may have noticed, there were some features left to implement such as notifications when pomodoros are completed. Try to implement them and do not hesitate to contact us if you have any doubts." msgstr "" #: ../../workshops/plugin-development.rst:1438 -msgid "" -"In the `plugin-examples`_ repository you can find additional examples " -"that will surely be useful for you to further understand Spyder plugin " -"development." +msgid "In the `plugin-examples`_ repository you can find additional examples that will surely be useful for you to further understand Spyder plugin development." msgstr "" #: ../../workshops/plugin-development.rst:1440 -msgid "" -"A more in-depth review of the Spyder repository itself, especially its " -"simpler plugins, such as History, Plots or Working directory, may help " -"you understand it better. As well as a review of the various helper " -"functions, widgets and mixins present in ``spyder.api``." +msgid "A more in-depth review of the Spyder repository itself, especially its simpler plugins, such as History, Plots or Working directory, may help you understand it better. As well as a review of the various helper functions, widgets and mixins present in ``spyder.api``." msgstr "" #: ../../workshops/qt_fundamentals.rst:5 @@ -3185,12 +2323,7 @@ msgid "Qt Fundamentals" msgstr "" #: ../../workshops/qt_fundamentals.rst:9 -msgid "" -"**Qt** is a multiplatform widget toolkit for creating native graphical " -"user interfaces. Qt is also a very complete development framework that " -"offers utilities for building applications, and libraries of extensions " -"for Networking, Bluetooth, Charts, 3D rendering, Navigation (as GPS), " -"among others." +msgid "**Qt** is a multiplatform widget toolkit for creating native graphical user interfaces. Qt is also a very complete development framework that offers utilities for building applications, and libraries of extensions for Networking, Bluetooth, Charts, 3D rendering, Navigation (as GPS), among others." msgstr "" #: ../../workshops/qt_fundamentals.rst:14 @@ -3198,40 +2331,23 @@ msgid "Basic Qt Components" msgstr "" #: ../../workshops/qt_fundamentals.rst:16 -msgid "" -"As mentioned before, Spyder's plugin development consists of extending " -"the functionality of its Qt-based graphical interface." +msgid "As mentioned before, Spyder's plugin development consists of extending the functionality of its Qt-based graphical interface." msgstr "" #: ../../workshops/qt_fundamentals.rst:18 -msgid "" -"To develop a GUI we will add graphical elements of interaction known as " -"widgets, arrange them using layouts. Then, we interconnect those widgets " -"using customized procedures implemented as functions or methods, allowing" -" to trigger behavior from user interaction. In the following, we will " -"develop these ideas in more detail." +msgid "To develop a GUI we will add graphical elements of interaction known as widgets, arrange them using layouts. Then, we interconnect those widgets using customized procedures implemented as functions or methods, allowing to trigger behavior from user interaction. In the following, we will develop these ideas in more detail." msgstr "" #: ../../workshops/qt_fundamentals.rst:20 -msgid "" -"Each type of Qt component is a class starting with the letter ``Q`` " -"followed by a name related to its functionality." +msgid "Each type of Qt component is a class starting with the letter ``Q`` followed by a name related to its functionality." msgstr "" #: ../../workshops/qt_fundamentals.rst:22 -msgid "" -"The core component of Qt is the ``QApplication`` class. Every Qt " -"application needs a single instance of this class as the base, from where" -" the Qt *event loop* is controlled. Spyder itself is an instance of " -"``QApplication``, its starting point is in the following two lines of " -"code (spyder/spyder/app/mainwindow.py):" +msgid "The core component of Qt is the ``QApplication`` class. Every Qt application needs a single instance of this class as the base, from where the Qt *event loop* is controlled. Spyder itself is an instance of ``QApplication``, its starting point is in the following two lines of code (spyder/spyder/app/mainwindow.py):" msgstr "" #: ../../workshops/qt_fundamentals.rst:30 -msgid "" -"``QMainWindow`` is a pre-built widget that provides many standard window " -"features as toolbars, menus, a status bar, dockable widgets and more, " -"which serves as the basis for the application." +msgid "``QMainWindow`` is a pre-built widget that provides many standard window features as toolbars, menus, a status bar, dockable widgets and more, which serves as the basis for the application." msgstr "" #: ../../workshops/qt_fundamentals.rst:34 @@ -3239,31 +2355,15 @@ msgid "Signals & Slots" msgstr "" #: ../../workshops/qt_fundamentals.rst:36 -msgid "" -"**Signals** are notifications emitted by widgets when something happens. " -"That something could be different things, from pressing a button, to " -"changing text in an input box, to changing text in the window. Many " -"signals are initiated by user action, but this is not a rule." +msgid "**Signals** are notifications emitted by widgets when something happens. That something could be different things, from pressing a button, to changing text in an input box, to changing text in the window. Many signals are initiated by user action, but this is not a rule." msgstr "" #: ../../workshops/qt_fundamentals.rst:39 -msgid "" -"**Slots** are signal receivers. Functions or methods could be used as " -"slots, by connecting a signal to them. If a signal sends data, the " -"receiver callable will also receive it. Many Qt widgets also have their " -"own built-in slots, so the corresponding widgets are notified " -"automatically." +msgid "**Slots** are signal receivers. Functions or methods could be used as slots, by connecting a signal to them. If a signal sends data, the receiver callable will also receive it. Many Qt widgets also have their own built-in slots, so the corresponding widgets are notified automatically." msgstr "" #: ../../workshops/qt_fundamentals.rst:47 -msgid "" -"In computer science a *Widget* is a shortened form of “window gadget”. A " -"widget is an element of interaction, such as a button, or a container for" -" other widgets, as panels or tabs. The ``QWidget`` class is the " -"fundamental class for creating interfaces in Qt, it receives events from " -"the window system, and renders its representation on the screen. A widget" -" can provide a container for grouping other widgets, and if it is not " -"embedded in a parent widget, it becomes a window." +msgid "In computer science a *Widget* is a shortened form of “window gadget”. A widget is an element of interaction, such as a button, or a container for other widgets, as panels or tabs. The ``QWidget`` class is the fundamental class for creating interfaces in Qt, it receives events from the window system, and renders its representation on the screen. A widget can provide a container for grouping other widgets, and if it is not embedded in a parent widget, it becomes a window." msgstr "" #: ../../workshops/qt_fundamentals.rst:52 @@ -3271,14 +2371,7 @@ msgid "Layouts" msgstr "" #: ../../workshops/qt_fundamentals.rst:54 -msgid "" -"Interfaces are built by embedding widgets inside widgets, and since they " -"are visual components they are visually organized by means of *layouts*. " -"A layout indicates how the widgets fill their container, either as " -"columns, rows, cells in a matrix or stacked so that only one is visible " -"at a time. Those are the 4 basic layouts available in Qt: " -"``QHBoxLayout``, ``QVBoxLayout``, ``QGridLayout``, and " -"``QStackedLayout``." +msgid "Interfaces are built by embedding widgets inside widgets, and since they are visual components they are visually organized by means of *layouts*. A layout indicates how the widgets fill their container, either as columns, rows, cells in a matrix or stacked so that only one is visible at a time. Those are the 4 basic layouts available in Qt: ``QHBoxLayout``, ``QVBoxLayout``, ``QGridLayout``, and ``QStackedLayout``." msgstr "" #: ../../workshops/qt_fundamentals.rst:61 @@ -3286,12 +2379,7 @@ msgid "Actions, Toolbars & Menus" msgstr "" #: ../../workshops/qt_fundamentals.rst:63 -msgid "" -"User interfaces of desktop applications usually use ``QToolbar`` and " -"``QMenu``. Since these are alternative ways to access the same " -"functionality, Qt provides ``QAction`` as a way to avoid duplication of " -"functions. Thus, each time a menu option or a toolbar button gives access" -" to the same function, they point to the same action." +msgid "User interfaces of desktop applications usually use ``QToolbar`` and ``QMenu``. Since these are alternative ways to access the same functionality, Qt provides ``QAction`` as a way to avoid duplication of functions. Thus, each time a menu option or a toolbar button gives access to the same function, they point to the same action." msgstr "" #: ../../workshops/qt_fundamentals.rst:67 @@ -3299,18 +2387,11 @@ msgid "Dialogs" msgstr "" #: ../../workshops/qt_fundamentals.rst:69 -msgid "" -"A *Dialog* is a GUI component that communicates with the user. Dialogs " -"are commonly used for functions that do not fit into the main interface. " -"In Qt, by design ``QDialog`` is a modal (or blocking) window that show in" -" front of the main Window until it is dismissed." +msgid "A *Dialog* is a GUI component that communicates with the user. Dialogs are commonly used for functions that do not fit into the main interface. In Qt, by design ``QDialog`` is a modal (or blocking) window that show in front of the main Window until it is dismissed." msgstr "" #: ../../workshops/qt_fundamentals.rst:72 -msgid "" -"Qt provides some *special dialogs* for the most common use-cases as *file" -" Open/Save*, *font selection*, *error messages*, *color choosing*, " -"*printing*, among others." +msgid "Qt provides some *special dialogs* for the most common use-cases as *file Open/Save*, *font selection*, *error messages*, *color choosing*, *printing*, among others." msgstr "" #: ../../workshops/qt_fundamentals.rst:76 @@ -3318,11 +2399,7 @@ msgid "Windows" msgstr "" #: ../../workshops/qt_fundamentals.rst:78 -msgid "" -"If an application requires additional windows that do not block the main " -"window, these are generated as non-parent ``QWidget`` instances. These " -"are used for tasks that happen in parallel over long-running processes " -"such as displaying graphs or document editing." +msgid "If an application requires additional windows that do not block the main window, these are generated as non-parent ``QWidget`` instances. These are used for tasks that happen in parallel over long-running processes such as displaying graphs or document editing." msgstr "" #: ../../workshops/qt_fundamentals.rst:83 @@ -3330,12 +2407,7 @@ msgid "Events" msgstr "" #: ../../workshops/qt_fundamentals.rst:85 -msgid "" -"An *Event* denote every interaction the user has with a Qt application. " -"There are several types of events designed to address different types of " -"interactions. In Qt they are represented by ``QEvent`` instances that " -"contain information about what prompted them, and are passed to specific " -"handlers that are responsible for triggering further actions." +msgid "An *Event* denote every interaction the user has with a Qt application. There are several types of events designed to address different types of interactions. In Qt they are represented by ``QEvent`` instances that contain information about what prompted them, and are passed to specific handlers that are responsible for triggering further actions." msgstr "" #: ../../workshops/scientific-computing.rst:3 @@ -3343,26 +2415,15 @@ msgid "Scientific Computing and Visualization with Spyder" msgstr "" #: ../../workshops/scientific-computing.rst:5 -msgid "" -"This workshop allows you to explore some of Spyder's features that make " -"Spyder an ideal IDE for using the scientific tools offered by Python. " -"Throughout the workshop, we will apply the scientific method to answer " -"some questions related to our preferences and cognitive abilities. By the" -" end of this workshop participants will be able to use Spyder to explore " -"data, analyze it with some statistical tools and plot the relationship " -"between variables." +msgid "This workshop allows you to explore some of Spyder's features that make Spyder an ideal IDE for using the scientific tools offered by Python. Throughout the workshop, we will apply the scientific method to answer some questions related to our preferences and cognitive abilities. By the end of this workshop participants will be able to use Spyder to explore data, analyze it with some statistical tools and plot the relationship between variables." msgstr "" #: ../../workshops/scientific-computing.rst:23 -msgid "" -"Some knowledge of Statistics (`hypothesis testing`_ , `ANOVA`_, " -"`p-value`_)" +msgid "Some knowledge of Statistics (`hypothesis testing`_ , `ANOVA`_, `p-value`_)" msgstr "" #: ../../workshops/scientific-computing.rst:38 -msgid "" -"Apply the scientific method to answer questions related to psychometric " -"variables" +msgid "Apply the scientific method to answer questions related to psychometric variables" msgstr "" #: ../../workshops/scientific-computing.rst:39 @@ -3370,16 +2431,11 @@ msgid "Understand how to use Spyder's built-in scientific computing tools" msgstr "" #: ../../workshops/scientific-computing.rst:47 -msgid "" -"This workshop is intended for people who want to learn how to answer " -"questions scientifically from a dataset. We have also designed it to " -"serve as a tutorial for learning how to use Spyder as a research tool." +msgid "This workshop is intended for people who want to learn how to answer questions scientifically from a dataset. We have also designed it to serve as a tutorial for learning how to use Spyder as a research tool." msgstr "" #: ../../workshops/scientific-computing.rst:55 -msgid "" -"In this workshop we will explore a data set and use it to answer some " -"questions using the scientific method." +msgid "In this workshop we will explore a data set and use it to answer some questions using the scientific method." msgstr "" #: ../../workshops/scientific-computing.rst:59 @@ -3387,10 +2443,7 @@ msgid "Why do scientific research with Python?" msgstr "" #: ../../workshops/scientific-computing.rst:61 -msgid "" -"Python is a mature programming language that has been chosen by much of " -"the scientific community to support the research process. There are a few" -" reasons for this:" +msgid "Python is a mature programming language that has been chosen by much of the scientific community to support the research process. There are a few reasons for this:" msgstr "" #: ../../workshops/scientific-computing.rst:63 @@ -3398,39 +2451,23 @@ msgid "It is versatile and easy to learn and use" msgstr "" #: ../../workshops/scientific-computing.rst:64 -msgid "" -"It allows for multiple ways to handle inputs and outputs. No matter what " -"format your data is in, in Python there is always a way to import it (and" -" export it in the format of your choice)" +msgid "It allows for multiple ways to handle inputs and outputs. No matter what format your data is in, in Python there is always a way to import it (and export it in the format of your choice)" msgstr "" #: ../../workshops/scientific-computing.rst:65 -msgid "" -"It is interpreted. You don't have to write code from start to finish to " -"see partial results. This makes it especially easy and fast to explore " -"data" +msgid "It is interpreted. You don't have to write code from start to finish to see partial results. This makes it especially easy and fast to explore data" msgstr "" #: ../../workshops/scientific-computing.rst:66 -msgid "" -"It has built-in support for scientific computing tasks: `SciPy " -"`_, `NumPy `_, `Pandas " -"`_, and a vast number of other libraries " -"created by and for scientists" +msgid "It has built-in support for scientific computing tasks: `SciPy `_, `NumPy `_, `Pandas `_, and a vast number of other libraries created by and for scientists" msgstr "" #: ../../workshops/scientific-computing.rst:67 -msgid "" -"It is the most widely used programming language for Machine Learning " -"(including Keras and TensorFlow)" +msgid "It is the most widely used programming language for Machine Learning (including Keras and TensorFlow)" msgstr "" #: ../../workshops/scientific-computing.rst:69 -msgid "" -"It can be integrated with `Jupyter Notebooks `_ and " -"implementations of these in the cloud (`Google Colab " -"`_ or `Binder " -"`_)" +msgid "It can be integrated with `Jupyter Notebooks `_ and implementations of these in the cloud (`Google Colab `_ or `Binder `_)" msgstr "" #: ../../workshops/scientific-computing.rst:73 @@ -3438,15 +2475,7 @@ msgid "How can Spyder help me in my scientific research?" msgstr "" #: ../../workshops/scientific-computing.rst:75 -msgid "" -"Spyder is a Scientific Integrated Development Environment written in " -"Python, and designed by and for scientists, engineers, and data analysts." -" It features a unique combination of the advanced editing, analysis, " -"debugging, and profiling functionality of a comprehensive development " -"tool with the data exploration, interactive execution, deep inspection, " -"and beautiful visualization capabilities of a scientific package. " -"Together with Python, it provides a very complete set of tools for " -"scientific computing." +msgid "Spyder is a Scientific Integrated Development Environment written in Python, and designed by and for scientists, engineers, and data analysts. It features a unique combination of the advanced editing, analysis, debugging, and profiling functionality of a comprehensive development tool with the data exploration, interactive execution, deep inspection, and beautiful visualization capabilities of a scientific package. Together with Python, it provides a very complete set of tools for scientific computing." msgstr "" #: ../../workshops/scientific-computing.rst:79 @@ -3454,11 +2483,7 @@ msgid "The basic steps of the scientific method" msgstr "" #: ../../workshops/scientific-computing.rst:81 -msgid "" -"The `scientific method " -"`_ is a set of good " -"practices used to achieve new knowledge in a valid way. Broadly speaking," -" the stages of the scientific method are as follows:" +msgid "The `scientific method `_ is a set of good practices used to achieve new knowledge in a valid way. Broadly speaking, the stages of the scientific method are as follows:" msgstr "" #: ../../workshops/scientific-computing.rst:83 @@ -3466,9 +2491,7 @@ msgid "Observation: first find something that needs an explanation" msgstr "" #: ../../workshops/scientific-computing.rst:84 -msgid "" -"Search/generate theory: say a thing or two about the state of the world " -"or how it works (an abstract thought about a phenomenon)" +msgid "Search/generate theory: say a thing or two about the state of the world or how it works (an abstract thought about a phenomenon)" msgstr "" #: ../../workshops/scientific-computing.rst:85 @@ -3476,9 +2499,7 @@ msgid "Hypothesis: identify variables and make predictions" msgstr "" #: ../../workshops/scientific-computing.rst:86 -msgid "" -"Testing/Experiment/More observation: measure relationship between " -"variables" +msgid "Testing/Experiment/More observation: measure relationship between variables" msgstr "" #: ../../workshops/scientific-computing.rst:87 @@ -3490,10 +2511,7 @@ msgid "Reporting: share new findings" msgstr "" #: ../../workshops/scientific-computing.rst:90 -msgid "" -"Throughout this workshop, we will be developing each of these steps in a " -"practical way. We will use Spyder as a research tool and psychometric " -"data from an online dating site to make it easy and fun." +msgid "Throughout this workshop, we will be developing each of these steps in a practical way. We will use Spyder as a research tool and psychometric data from an online dating site to make it easy and fun." msgstr "" #: ../../workshops/scientific-computing.rst:94 @@ -3501,25 +2519,15 @@ msgid "Introduction to scientific research with Spyder" msgstr "" #: ../../workshops/scientific-computing.rst:100 -msgid "" -"If you already have experience with Spyder, you can skip to `Preparation " -"work`_ section." +msgid "If you already have experience with Spyder, you can skip to `Preparation work`_ section." msgstr "" #: ../../workshops/scientific-computing.rst:122 -msgid "" -"The Variable Explorer is one of the most frequently used components in " -"this workshop. **This is the pane where we will observe the data and most" -" of the results of the scientific analysis, except for the plots**." +msgid "The Variable Explorer is one of the most frequently used components in this workshop. **This is the pane where we will observe the data and most of the results of the scientific analysis, except for the plots**." msgstr "" #: ../../workshops/scientific-computing.rst:128 -msgid "" -"The :doc:`Plots pane <../panes/plots>` shows all the static graphs and " -"images created in your IPython Console session. **All plots generated by " -"the code will appear in this component**. You will also be able to save " -"each graphic in a local file or copy it to the clipboard to share it with" -" other researchers." +msgid "The :doc:`Plots pane <../panes/plots>` shows all the static graphs and images created in your IPython Console session. **All plots generated by the code will appear in this component**. You will also be able to save each graphic in a local file or copy it to the clipboard to share it with other researchers." msgstr "" #: ../../workshops/scientific-computing.rst:132 @@ -3527,12 +2535,7 @@ msgid "Code Analysis (share a stylish code!)" msgstr "" #: ../../workshops/scientific-computing.rst:134 -msgid "" -"Wouldn't it be great to have a tool to be able to detect code errors, " -"stylistic problems, bad practices, inconsistencies and other issues? This" -" is precisely the task of the :doc:`Code Analysis<../panes/pylint>`. " -"Your code can run, but if you are going to share it with other " -"researchers it would be great if it is both readable and neat as well." +msgid "Wouldn't it be great to have a tool to be able to detect code errors, stylistic problems, bad practices, inconsistencies and other issues? This is precisely the task of the :doc:`Code Analysis<../panes/pylint>`. Your code can run, but if you are going to share it with other researchers it would be great if it is both readable and neat as well." msgstr "" #: ../../workshops/scientific-computing.rst:146 @@ -3540,12 +2543,7 @@ msgid "Setting up the Conda environment" msgstr "" #: ../../workshops/scientific-computing.rst:154 -msgid "" -"We recommend creating the virtual environment with `Anaconda " -"`_ (or `Miniconda " -"`_) as it integrates " -"seamlessly with Spyder. You can find installation instructions in " -"`Anaconda documentation`_." +msgid "We recommend creating the virtual environment with `Anaconda `_ (or `Miniconda `_) as it integrates seamlessly with Spyder. You can find installation instructions in `Anaconda documentation`_." msgstr "" #: ../../workshops/scientific-computing.rst:160 @@ -3553,25 +2551,15 @@ msgid "1. With commands" msgstr "" #: ../../workshops/scientific-computing.rst:162 -msgid "" -"Just run the following command in your Anaconda Prompt (Windows) or " -"terminal (other platforms), for a minimal install of Spyder into a new " -"environment called ``scientific-computing``:" +msgid "Just run the following command in your Anaconda Prompt (Windows) or terminal (other platforms), for a minimal install of Spyder into a new environment called ``scientific-computing``:" msgstr "" #: ../../workshops/scientific-computing.rst:168 -msgid "" -"To install Spyder's optional dependencies as well for full functionality," -" use the following command instead:" +msgid "To install Spyder's optional dependencies as well for full functionality, use the following command instead:" msgstr "" #: ../../workshops/scientific-computing.rst:176 -msgid "" -"Spyder now offers :ref:`install-standalone` for Windows and macOS, making" -" it easier to get up and running with the application without having to " -"download Anaconda or manually install it in your existing environment. If" -" you use the standalone installer, there is no need to install " -"``spyder=5`` with conda." +msgid "Spyder now offers :ref:`install-standalone` for Windows and macOS, making it easier to get up and running with the application without having to download Anaconda or manually install it in your existing environment. If you use the standalone installer, there is no need to install ``spyder=5`` with conda." msgstr "" #: ../../workshops/scientific-computing.rst:180 @@ -3579,11 +2567,7 @@ msgid "2. From an environment.yml file" msgstr "" #: ../../workshops/scientific-computing.rst:182 -msgid "" -"You can also install the virtual environment easily using the environment" -" file (``scientific-computing.yml``) that we share with you. Just run the" -" following command in the terminal (you must have the environment file in" -" the current directory):" +msgid "You can also install the virtual environment easily using the environment file (``scientific-computing.yml``) that we share with you. Just run the following command in the terminal (you must have the environment file in the current directory):" msgstr "" #: ../../workshops/scientific-computing.rst:190 @@ -3599,10 +2583,7 @@ msgid "Downloading the dataset" msgstr "" #: ../../workshops/scientific-computing.rst:202 -msgid "" -"We are going to work with a public dataset called OKCupid, collected by " -"Kirkegaard and Bjerrekaer. The dataset is composed of 68,371 records and " -"2,626 variables." +msgid "We are going to work with a public dataset called OKCupid, collected by Kirkegaard and Bjerrekaer. The dataset is composed of 68,371 records and 2,626 variables." msgstr "" #: ../../workshops/scientific-computing.rst:204 @@ -3614,11 +2595,7 @@ msgid "Setting up the working directory" msgstr "" #: ../../workshops/scientific-computing.rst:212 -msgid "" -"The virtual environment and the data file are now ready. The only thing " -"that remains is to create a directory to work in. In your operating " -"system, create a new directory with the name of your choice. Then copy " -"and unzip the dataset file there." +msgid "The virtual environment and the data file are now ready. The only thing that remains is to create a directory to work in. In your operating system, create a new directory with the name of your choice. Then copy and unzip the dataset file there." msgstr "" #: ../../workshops/scientific-computing.rst:214 @@ -3626,9 +2603,7 @@ msgid "Here is an example (on Linux or macOS):" msgstr "" #: ../../workshops/scientific-computing.rst:221 -msgid "" -"Keep in mind that in this new directory you must have the data file " -"unzipped." +msgid "Keep in mind that in this new directory you must have the data file unzipped." msgstr "" #: ../../workshops/scientific-computing.rst:223 @@ -3636,27 +2611,23 @@ msgid "Launch Spyder:" msgstr "" #: ../../workshops/scientific-computing.rst:229 -msgid "" -"Let's make sure Spyder is ready. First, check that the working directory " -"is correct. You should see in the upper right corner the path to the " -"directory where you have the dataset. Something like this:" +msgid "Let's make sure Spyder is ready. First, check that the working directory is correct. You should see in the upper right corner the path to the directory where you have the dataset. Something like this:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:231 +msgid "Spyder's Working Directory plugin showing the working directory of spyder-scientific" msgstr "" #: ../../workshops/scientific-computing.rst:234 -msgid "" -"Second, let's check that the virtual environment we created is enabled in" -" Spyder. Go to :guilabel:`Preferences` > :guilabel:`Python interpreter`, " -"and use the dropdown under :guilabel:`Use the following Python " -"interpreter` to select the path to your virtual environment. You should " -"see something like this:" +msgid "Second, let's check that the virtual environment we created is enabled in Spyder. Go to :guilabel:`Preferences` > :guilabel:`Python interpreter`, and use the dropdown under :guilabel:`Use the following Python interpreter` to select the path to your virtual environment. You should see something like this:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:236 +msgid "Set up environment in Spyder's Preferences" msgstr "" #: ../../workshops/scientific-computing.rst:245 -msgid "" -"Although the workshop is designed for you to write the code in the " -"IPython Console, we have created a file that you can :download:`download " -"`. This script provides all the code you will " -"write in this workshop, and you can use it as a guide if you get lost." +msgid "Although the workshop is designed for you to write the code in the IPython Console, we have created a file that you can :download:`download `. This script provides all the code you will write in this workshop, and you can use it as a guide if you get lost." msgstr "" #: ../../workshops/scientific-computing.rst:251 @@ -3664,41 +2635,27 @@ msgid "The dataset" msgstr "" #: ../../workshops/scientific-computing.rst:253 -msgid "" -"OKCupid is a dataset that gathers information obtained from the online " -"dating site OKCupid. It consists of 68,371 records collected " -"automatically employing a scraper that extracted public information." +msgid "OKCupid is a dataset that gathers information obtained from the online dating site OKCupid. It consists of 68,371 records collected automatically employing a scraper that extracted public information." msgstr "" #: ../../workshops/scientific-computing.rst:255 -msgid "" -"The dataset contains demographic data (e.g., gender, sexual orientation " -"and age). It also includes answers to general questions used by the " -"website's algorithm to calculate some personality indicators to help find" -" compatible matches." +msgid "The dataset contains demographic data (e.g., gender, sexual orientation and age). It also includes answers to general questions used by the website's algorithm to calculate some personality indicators to help find compatible matches." msgstr "" #: ../../workshops/scientific-computing.rst:257 -msgid "" -"If you want more information about how this dataset was collected and " -"what kind of information it contains you can get it in this paper: `The " -"OKCupid dataset`_." +msgid "If you want more information about how this dataset was collected and what kind of information it contains you can get it in this paper: `The OKCupid dataset`_." +msgstr "" + +#: ../../workshops/scientific-computing.rst:263 +msgid "IPython Console location in Spyder IDE" msgstr "" #: ../../workshops/scientific-computing.rst:266 -msgid "" -"You can also write your code or in the Editor (the pane that occupies the" -" entire left side of Spyder). If you use the Editor, you can run the code" -" by selecting it and pressing the :guilabel:`Run selection or current " -"line` button in the :guilabel:`Run toolbar` or by pressing the F9 button." +msgid "You can also write your code or in the Editor (the pane that occupies the entire left side of Spyder). If you use the Editor, you can run the code by selecting it and pressing the :guilabel:`Run selection or current line` button in the :guilabel:`Run toolbar` or by pressing the F9 button." msgstr "" #: ../../workshops/scientific-computing.rst:280 -msgid "" -"The data you downloaded earlier is in `parquet " -"`_ format. This format" -" is very convenient because it is smaller and faster than CSV or JSON " -"files." +msgid "The data you downloaded earlier is in `parquet `_ format. This format is very convenient because it is smaller and faster than CSV or JSON files." msgstr "" #: ../../workshops/scientific-computing.rst:282 @@ -3706,15 +2663,15 @@ msgid "Load data:" msgstr "" #: ../../workshops/scientific-computing.rst:288 -msgid "" -"You should now be able to see the data you have imported in the Variable " -"Explorer." +msgid "You should now be able to see the data you have imported in the Variable Explorer." +msgstr "" + +#: ../../workshops/scientific-computing.rst:290 +msgid "Dataset in the Variable Explorer" msgstr "" #: ../../workshops/scientific-computing.rst:293 -msgid "" -"You can see that the object is of type DataFrame and the number of rows " -"and columns of the object." +msgid "You can see that the object is of type DataFrame and the number of rows and columns of the object." msgstr "" #: ../../workshops/scientific-computing.rst:299 @@ -3726,122 +2683,95 @@ msgid "Age" msgstr "" #: ../../workshops/scientific-computing.rst:305 -msgid "" -"Now, let's explore one of the variables, in this case, the numeric " -"variable age (``d_age``)." +msgid "Now, let's explore one of the variables, in this case, the numeric variable age (``d_age``)." msgstr "" #: ../../workshops/scientific-computing.rst:309 -msgid "" -"In the OKCupid dataset, all demographic variables are prefixed with " -"\"d\\_\" and profile variables with \"p\\_\"." +msgid "In the OKCupid dataset, all demographic variables are prefixed with \"d\\_\" and profile variables with \"p\\_\"." +msgstr "" + +#: ../../workshops/scientific-computing.rst:315 +msgid "Console output for data.d_age.describe()" msgstr "" #: ../../workshops/scientific-computing.rst:318 -msgid "" -"What happened? We called the ``data`` object and used Python's dot " -"notation to pick the ``d_age`` column. This has a `Pandas Series " -"`_ type object. To this " -"object we pass the ``describe()`` method that shows a summary of some " -"indicators: count of values, mean, standard deviation, maximum value, " -"minimum value, among others. With these figures we can see that the " -"sample is mainly constituted of young people (the average is 31.65 years " -"old)." +msgid "What happened? We called the ``data`` object and used Python's dot notation to pick the ``d_age`` column. This has a `Pandas Series `_ type object. To this object we pass the ``describe()`` method that shows a summary of some indicators: count of values, mean, standard deviation, maximum value, minimum value, among others. With these figures we can see that the sample is mainly constituted of young people (the average is 31.65 years old)." msgstr "" #: ../../workshops/scientific-computing.rst:320 -msgid "" -"The return of a function, method or the attribute of an object can be " -"stored as a variable to have it at hand in the Variable Explorer:" +msgid "The return of a function, method or the attribute of an object can be stored as a variable to have it at hand in the Variable Explorer:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:327 +msgid "More variables in Variable Explorer" msgstr "" #: ../../workshops/scientific-computing.rst:330 -msgid "" -"The values are floats. The lowest age is 18.0 years and the highest is " -"100.0 years." +msgid "The values are floats. The lowest age is 18.0 years and the highest is 100.0 years." msgstr "" #: ../../workshops/scientific-computing.rst:334 -msgid "" -"Notice also that each type of variable has a different color to quickly " -"distinguish them." +msgid "Notice also that each type of variable has a different color to quickly distinguish them." msgstr "" #: ../../workshops/scientific-computing.rst:336 -msgid "" -"We already know the minimum and maximum age, and that the mean is around " -"32 years old. A good way to further explore this variable is to plot a " -"histogram, a type of graph that shows the frequency distributions. In " -"this way we can see if the groups of young people on the platform are " -"more numerous than the older ones." +msgid "We already know the minimum and maximum age, and that the mean is around 32 years old. A good way to further explore this variable is to plot a histogram, a type of graph that shows the frequency distributions. In this way we can see if the groups of young people on the platform are more numerous than the older ones." msgstr "" #: ../../workshops/scientific-computing.rst:338 -msgid "" -"We can plot a histogram directly from the dataframe. To do this we select" -" the variable (as we did with the ``.describe()``) and invoke the " -"``.plot.hist()`` method. In this method we will pass as arguments the " -"number of bins and the transparency of the plot (``alpha``)." +msgid "We can plot a histogram directly from the dataframe. To do this we select the variable (as we did with the ``.describe()``) and invoke the ``.plot.hist()`` method. In this method we will pass as arguments the number of bins and the transparency of the plot (``alpha``)." +msgstr "" + +#: ../../workshops/scientific-computing.rst:344 +msgid "Age histogram with Pandas" msgstr "" #: ../../workshops/scientific-computing.rst:348 -msgid "" -"Another way to generate a simple histogram in Spyder is to use a context " -"menu on an array in the Variable Explorer. But first we must store these " -"values in a list and call that variable ``age``." +msgid "Another way to generate a simple histogram in Spyder is to use a context menu on an array in the Variable Explorer. But first we must store these values in a list and call that variable ``age``." +msgstr "" + +#: ../../workshops/scientific-computing.rst:354 +msgid "Age histogram option from Variable Explorer" +msgstr "" + +#: ../../workshops/scientific-computing.rst:357 +msgid "Age histogram from Variable Explorer" msgstr "" #: ../../workshops/scientific-computing.rst:360 -msgid "" -"Frequency distributions come in different sizes and shapes. The shape of " -"a histogram reveals very interesting things about the data. A " -"symmetrical, bell-shaped histogram might indicate that the distribution " -"is normal (most of the scores are close to the center of the " -"distribution). In the age histogram, you can see that it has a \"tail\" " -"to the right (towards the older ages). Technically this is called " -"\"positively `skewed`_\". It is also noticeable that it is somewhat " -"pointy (positive `kurtosis`_ or leptokurtic). These two things could " -"suggest that age is not a random variable." +msgid "Frequency distributions come in different sizes and shapes. The shape of a histogram reveals very interesting things about the data. A symmetrical, bell-shaped histogram might indicate that the distribution is normal (most of the scores are close to the center of the distribution). In the age histogram, you can see that it has a \"tail\" to the right (towards the older ages). Technically this is called \"positively `skewed`_\". It is also noticeable that it is somewhat pointy (positive `kurtosis`_ or leptokurtic). These two things could suggest that age is not a random variable." msgstr "" #: ../../workshops/scientific-computing.rst:365 -msgid "" -"Although we can create the histogram directly from the dataframe, we are " -"going to use a Python library called Seaborn to do the same, because this" -" library will allow us to do more interesting things later." +msgid "Although we can create the histogram directly from the dataframe, we are going to use a Python library called Seaborn to do the same, because this library will allow us to do more interesting things later." msgstr "" #: ../../workshops/scientific-computing.rst:372 -msgid "" -"We call ``sns.histplot()`` with three arguments. The first one " -"(``data.d_age``) is a Pandas Series with the **quantitative** variable we" -" want to plot. The second (``kde=True``) adds a curve showing an ideal " -"model of the age distribution (using a method called *Kernel Density " -"Estimator*). And the third one (``bins=25``) indicates that we want 25 " -"bins in the graph." +msgid "We call ``sns.histplot()`` with three arguments. The first one (``data.d_age``) is a Pandas Series with the **quantitative** variable we want to plot. The second (``kde=True``) adds a curve showing an ideal model of the age distribution (using a method called *Kernel Density Estimator*). And the third one (``bins=25``) indicates that we want 25 bins in the graph." +msgstr "" + +#: ../../workshops/scientific-computing.rst:374 +msgid "Age histogram with Seaborn" msgstr "" #: ../../workshops/scientific-computing.rst:377 -msgid "" -"The second line (``plt.show()``) is intended to show all the figures not " -"displayed so far. If you have any doubts about how to utilize an object, " -"method or function, you can use the ``help()`` tool in the console. For " -"example:" +msgid "The second line (``plt.show()``) is intended to show all the figures not displayed so far. If you have any doubts about how to utilize an object, method or function, you can use the ``help()`` tool in the console. For example:" msgstr "" #: ../../workshops/scientific-computing.rst:383 -msgid "" -"Or you can also take advantage of the Help pane included in Spyder to get" -" on-screen help:" +msgid "Or you can also take advantage of the Help pane included in Spyder to get on-screen help:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:385 +msgid "plt.show() help in Spyder's Help pane" msgstr "" #: ../../workshops/scientific-computing.rst:388 -msgid "" -"With Seaborn, we can add a line representing the mean of the histogram. " -"To do this we will use the ``axvline()`` method and add a text with the " -"value of the mean where ``text()``, ``min_ylim`` and ``max_ylim`` are " -"used to mark the position of the text." +msgid "With Seaborn, we can add a line representing the mean of the histogram. To do this we will use the ``axvline()`` method and add a text with the value of the mean where ``text()``, ``min_ylim`` and ``max_ylim`` are used to mark the position of the text." +msgstr "" + +#: ../../workshops/scientific-computing.rst:400 +msgid "Age histogram with mean line" msgstr "" #: ../../workshops/scientific-computing.rst:405 @@ -3849,46 +2779,27 @@ msgid "Religion seriosity" msgstr "" #: ../../workshops/scientific-computing.rst:407 -msgid "" -"We know the extent of the dataframe and we have seen how to explore a " -"quantitative variable. Now let's move on to a qualitative variable. The " -"``columns`` attribute shows a list of column names in the dataframe. We " -"also know that demographic variables are prefixed with \"d\\_\", so we " -"can look for variable names that correspond to this prefix." +msgid "We know the extent of the dataframe and we have seen how to explore a quantitative variable. Now let's move on to a qualitative variable. The ``columns`` attribute shows a list of column names in the dataframe. We also know that demographic variables are prefixed with \"d\\_\", so we can look for variable names that correspond to this prefix." msgstr "" #: ../../workshops/scientific-computing.rst:413 -msgid "" -"In the Variable Explorer you will see a new variable ``demograph``. If " -"you double click on it you will see a list of the demographic variables " -"in the dataset. At the end of the list you will see a value " -"``d_religion_seriosity``. If you right click on it, several options will " -"appear on the screen. You can rename the column, delete it or insert a " -"new one. Let's click on :guilabel:`Copy` to copy the column name into " -"memory." +msgid "In the Variable Explorer you will see a new variable ``demograph``. If you double click on it you will see a list of the demographic variables in the dataset. At the end of the list you will see a value ``d_religion_seriosity``. If you right click on it, several options will appear on the screen. You can rename the column, delete it or insert a new one. Let's click on :guilabel:`Copy` to copy the column name into memory." msgstr "" #: ../../workshops/scientific-computing.rst:415 -msgid "" -"In the IPython Console, type ``data.`` and then copy the column name. " -"Type a period at the end (no spaces) and hit tab. You should see " -"something like the following:" +msgid "In the IPython Console, type ``data.`` and then copy the column name. Type a period at the end (no spaces) and hit tab. You should see something like the following:" +msgstr "" + +#: ../../workshops/scientific-computing.rst:417 +msgid "IPython Console auto-completion" msgstr "" #: ../../workshops/scientific-computing.rst:420 -msgid "" -"You can then see a list of all relevant methods and attributes of the " -"class. Right at the end you will see ``value_counts`` that could be used " -"to summarize the variable. It is a method so it must end in parentheses:" +msgid "You can then see a list of all relevant methods and attributes of the class. Right at the end you will see ``value_counts`` that could be used to summarize the variable. It is a method so it must end in parentheses:" msgstr "" #: ../../workshops/scientific-computing.rst:432 -msgid "" -"In addition to demographic and profile variables, the dataset includes " -"responses to questions on a variety of topics. These questions are coded " -"with a prefix \"q\" followed by an integer. The text of the questions is " -"stored in a file called :file:`question_data.csv` (which you can download" -" as part of the `OKCupid dataset`_)." +msgid "In addition to demographic and profile variables, the dataset includes responses to questions on a variety of topics. These questions are coded with a prefix \"q\" followed by an integer. The text of the questions is stored in a file called :file:`question_data.csv` (which you can download as part of the `OKCupid dataset`_)." msgstr "" #: ../../workshops/scientific-computing.rst:434 @@ -3896,15 +2807,11 @@ msgid "We can examine this file in the Variable Explorer:" msgstr "" #: ../../workshops/scientific-computing.rst:440 -msgid "" -"Double click on \"question_data\" in the Variable Explorer to display " -"each question aligned with its code (\"q\" + number)." +msgid "Double click on \"question_data\" in the Variable Explorer to display each question aligned with its code (\"q\" + number)." msgstr "" #: ../../workshops/scientific-computing.rst:442 -msgid "" -"Now that we have learned how to explore the data we can ask interesting " -"questions and try to answer them with the help of the dataset and Spyder." +msgid "Now that we have learned how to explore the data we can ask interesting questions and try to answer them with the help of the dataset and Spyder." msgstr "" #: ../../workshops/scientific-computing.rst:448 @@ -3912,63 +2819,31 @@ msgid "Think of a theory and write a hypothesis" msgstr "" #: ../../workshops/scientific-computing.rst:450 -msgid "" -"A theory is nothing more than an explanation of something. For example, " -"we could get involved in the eternal conflict between cats and dogs. I, " -"as a dog person, might have a theory (unscientific, of course) that those" -" who prefer to have the companionship of a dog are smarter people than " -"those who prefer a wicked (but lovable) kitty. To test the support of a " -"theory, one can make a prediction based on it and see how this prediction" -" behaves in an experiment or a concrete situation. We call this " -"prediction a hypothesis." +msgid "A theory is nothing more than an explanation of something. For example, we could get involved in the eternal conflict between cats and dogs. I, as a dog person, might have a theory (unscientific, of course) that those who prefer to have the companionship of a dog are smarter people than those who prefer a wicked (but lovable) kitty. To test the support of a theory, one can make a prediction based on it and see how this prediction behaves in an experiment or a concrete situation. We call this prediction a hypothesis." msgstr "" #: ../../workshops/scientific-computing.rst:452 -msgid "" -"A hypothesis is a statement that can be tested employing the scientific " -"method. They must be verifiable using empirical evidence or data. For " -"example, *green is the best color* is not a hypothesis since it cannot be" -" proven or disproven." +msgid "A hypothesis is a statement that can be tested employing the scientific method. They must be verifiable using empirical evidence or data. For example, *green is the best color* is not a hypothesis since it cannot be proven or disproven." msgstr "" #: ../../workshops/scientific-computing.rst:454 -msgid "" -"Concerning the above theory of a person's pet preferences, to explore it " -"we should find two variables to relate. The first variable would be " -"related to a **self-identification as a cat person or dog person**. The " -"second variable would be related to a person's **ability to solve " -"problems and situations**." +msgid "Concerning the above theory of a person's pet preferences, to explore it we should find two variables to relate. The first variable would be related to a **self-identification as a cat person or dog person**. The second variable would be related to a person's **ability to solve problems and situations**." msgstr "" #: ../../workshops/scientific-computing.rst:456 -msgid "" -"The OKCupid dataset has useful variables that we can use to investigate " -"this theory. For example, question **q997** (*Are you a cat person or a " -"dog person?* ) provides information about a person's pet preferences. The" -" second variable is slightly more difficult to come up with, as it is " -"somewhat more complex. Fortunately, the researchers who collected the " -"dataset have also selected 14 questions that can serve as a proxy for a " -"cognitive ability test. This selection of questions can be found in the " -"file :file:`test_items.csv` in the `OKCupid dataset`_." +msgid "The OKCupid dataset has useful variables that we can use to investigate this theory. For example, question **q997** (*Are you a cat person or a dog person?* ) provides information about a person's pet preferences. The second variable is slightly more difficult to come up with, as it is somewhat more complex. Fortunately, the researchers who collected the dataset have also selected 14 questions that can serve as a proxy for a cognitive ability test. This selection of questions can be found in the file :file:`test_items.csv` in the `OKCupid dataset`_." msgstr "" #: ../../workshops/scientific-computing.rst:462 -msgid "" -"So, let's try to see if there is any evidence in the OKCupid dataset to " -"support the following hypothesis:" +msgid "So, let's try to see if there is any evidence in the OKCupid dataset to support the following hypothesis:" msgstr "" #: ../../workshops/scientific-computing.rst:464 -msgid "" -"*People who prefer dogs to cats would score higher on tests of cognitive " -"ability*." +msgid "*People who prefer dogs to cats would score higher on tests of cognitive ability*." msgstr "" #: ../../workshops/scientific-computing.rst:468 -msgid "" -"SPOILER ALERT: If you are a cat person, and feel you should immediately " -"leave this workshop, I suggest you stay. If you're not a cat person, stay" -" too." +msgid "SPOILER ALERT: If you are a cat person, and feel you should immediately leave this workshop, I suggest you stay. If you're not a cat person, stay too." msgstr "" #: ../../workshops/scientific-computing.rst:474 @@ -3976,10 +2851,7 @@ msgid "Build the test" msgstr "" #: ../../workshops/scientific-computing.rst:476 -msgid "" -"We already know which questions will be part of the cognitive ability " -"test. Now we are going to process this data to obtain the scores for each" -" person." +msgid "We already know which questions will be part of the cognitive ability test. Now we are going to process this data to obtain the scores for each person." msgstr "" #: ../../workshops/scientific-computing.rst:478 @@ -3987,9 +2859,7 @@ msgid "First, we make a copy of the original dataset:" msgstr "" #: ../../workshops/scientific-computing.rst:484 -msgid "" -"Then, we find the correct answer to each test question (these answers are" -" in ``test_items``)." +msgid "Then, we find the correct answer to each test question (these answers are in ``test_items``)." msgstr "" #: ../../workshops/scientific-computing.rst:493 @@ -3997,56 +2867,27 @@ msgid "The correct answers have been stored in the ``test_items`` dataframe." msgstr "" #: ../../workshops/scientific-computing.rst:495 -msgid "" -"Next, we will indicate, in the ``ca_test`` dataframe, whether the person " -"answered correctly to each question selected in the cognitive ability " -"test. These answers will be entered as a boolean in new variables with " -"the prefix \"resp\\_\" followed by the corresponding question code. The " -"Boolean is calculated with the function ``lambda row: row[q] == a, " -"axis=1``." +msgid "Next, we will indicate, in the ``ca_test`` dataframe, whether the person answered correctly to each question selected in the cognitive ability test. These answers will be entered as a boolean in new variables with the prefix \"resp\\_\" followed by the corresponding question code. The Boolean is calculated with the function ``lambda row: row[q] == a, axis=1``." msgstr "" #: ../../workshops/scientific-computing.rst:510 -msgid "" -"Some ``test_items`` questions are not in the data but don't worry about " -"that. We use a ``try... except`` block to ignore these errors. Answering " -"these questions was optional, so many OkCupid site users did not answer " -"all of them. So we have removed from the records the users who did not " -"answer the 14 questions we have chosen for the cognitive ability test. " -"This reduced the sample size considerably. There are other ways to avoid " -"this reduction, but they are outside the scope of this workshop." +msgid "Some ``test_items`` questions are not in the data but don't worry about that. We use a ``try... except`` block to ignore these errors. Answering these questions was optional, so many OkCupid site users did not answer all of them. So we have removed from the records the users who did not answer the 14 questions we have chosen for the cognitive ability test. This reduced the sample size considerably. There are other ways to avoid this reduction, but they are outside the scope of this workshop." msgstr "" #: ../../workshops/scientific-computing.rst:512 -msgid "" -"We want to sum the correct answers for each person, but some integer " -"results were stored as strings, so let's fix that:" +msgid "We want to sum the correct answers for each person, but some integer results were stored as strings, so let's fix that:" msgstr "" #: ../../workshops/scientific-computing.rst:524 -msgid "" -"Now that we have the correct answer for each test question, let's add up " -"each correct answer for each person. There are 14 questions, so the " -"maximum score will also be 14:" +msgid "Now that we have the correct answer for each test question, let's add up each correct answer for each person. There are 14 questions, so the maximum score will also be 14:" msgstr "" #: ../../workshops/scientific-computing.rst:531 -msgid "" -"How do we add up these responses? Remember that each answer was stored as" -" a boolean (True or False) with the prefix \"resp\\_\". So we search in " -"the ``ca_test`` dataframe for the answers of each column starting with " -"\"resp\" (we use the regular expression ``regex=\"^resp\"`` and the " -"method ``filter``) and sum the True values of each row with " -"``sum(axis=1)``. Then we store these results in the \"cognitive_score\" " -"column of the ``ca_test`` dataset." +msgid "How do we add up these responses? Remember that each answer was stored as a boolean (True or False) with the prefix \"resp\\_\". So we search in the ``ca_test`` dataframe for the answers of each column starting with \"resp\" (we use the regular expression ``regex=\"^resp\"`` and the method ``filter``) and sum the True values of each row with ``sum(axis=1)``. Then we store these results in the \"cognitive_score\" column of the ``ca_test`` dataset." msgstr "" #: ../../workshops/scientific-computing.rst:533 -msgid "" -"You can see the results of these operations by typing in the IPython " -"Console ``ca_test.cognitive_score.describe()``. If you do so, in *count* " -"you will see that the new number of records has been reduced to 479 (the " -"rest of the 68,371 users did not answer all of these questions)." +msgid "You can see the results of these operations by typing in the IPython Console ``ca_test.cognitive_score.describe()``. If you do so, in *count* you will see that the new number of records has been reduced to 479 (the rest of the 68,371 users did not answer all of these questions)." msgstr "" #: ../../workshops/scientific-computing.rst:537 @@ -4057,20 +2898,16 @@ msgstr "" msgid "Let's draw a histogram of this variable to see the frequency distribution." msgstr "" +#: ../../workshops/scientific-computing.rst:546 +msgid "Cognitive test score histogram" +msgstr "" + #: ../../workshops/scientific-computing.rst:549 -msgid "" -"As you can see, in this case, the distribution is not symmetrical but has" -" a long \"tail\" on the left (negatively skewed). This means that most of" -" the users who answered all the questions did quite well and that only a " -"few users answered most of the questions in the wrong way." +msgid "As you can see, in this case, the distribution is not symmetrical but has a long \"tail\" on the left (negatively skewed). This means that most of the users who answered all the questions did quite well and that only a few users answered most of the questions in the wrong way." msgstr "" #: ../../workshops/scientific-computing.rst:553 -msgid "" -"The values we have calculated in this section were already in the data " -"(``data.CA_items``). However, we have chosen to obtain these results " -"again using code because it is a good way to learn how to use the tools " -"provided by Python and Pandas for data manipulation." +msgid "The values we have calculated in this section were already in the data (``data.CA_items``). However, we have chosen to obtain these results again using code because it is a good way to learn how to use the tools provided by Python and Pandas for data manipulation." msgstr "" #: ../../workshops/scientific-computing.rst:559 @@ -4078,65 +2915,35 @@ msgid "Relate variables" msgstr "" #: ../../workshops/scientific-computing.rst:561 -msgid "" -"Remember that the hypothesis relates two variables: which pet do you " -"prefer and cognitive ability. The measurement of pet preferences will be " -"made from question **q997** (categorical or qualitative variable) and " -"cognitive ability will be measured from the sum of the correct answers on" -" the test (quantitative interval variable). With this type of variable we" -" can make some box plots to see if there are differences between the " -"means." +msgid "Remember that the hypothesis relates two variables: which pet do you prefer and cognitive ability. The measurement of pet preferences will be made from question **q997** (categorical or qualitative variable) and cognitive ability will be measured from the sum of the correct answers on the test (quantitative interval variable). With this type of variable we can make some box plots to see if there are differences between the means." msgstr "" #: ../../workshops/scientific-computing.rst:563 -msgid "" -"But first, let's change the standard Seaborn palette, to get prettier " -"plots." +msgid "But first, let's change the standard Seaborn palette, to get prettier plots." msgstr "" #: ../../workshops/scientific-computing.rst:573 -msgid "" -"Seaborn allows you to choose from different styles of graphics and color " -"palettes. More information is available at " -"https://seaborn.pydata.org/tutorial/color_palettes.html" +msgid "Seaborn allows you to choose from different styles of graphics and color palettes. More information is available at https://seaborn.pydata.org/tutorial/color_palettes.html" msgstr "" #: ../../workshops/scientific-computing.rst:575 -msgid "" -"Now, we are going to create box plots to observe the relationship between" -" variables. To do this, we will use the ``catplot`` class of Seaborn. The" -" first argument will be the x-axis, which in this case will be the " -"qualitative variable (question **q997**). The second argument will be the" -" y-axis, where we will place the quantitative variable (cognitive score)." -" With the parameter ``kind`` we indicate that it is a box plot. The " -"parameters ``height`` and ``aspect`` regulate the appearance of the " -"graph. The last parameter, ``data``, indicates where the data comes from." +msgid "Now, we are going to create box plots to observe the relationship between variables. To do this, we will use the ``catplot`` class of Seaborn. The first argument will be the x-axis, which in this case will be the qualitative variable (question **q997**). The second argument will be the y-axis, where we will place the quantitative variable (cognitive score). With the parameter ``kind`` we indicate that it is a box plot. The parameters ``height`` and ``aspect`` regulate the appearance of the graph. The last parameter, ``data``, indicates where the data comes from." +msgstr "" + +#: ../../workshops/scientific-computing.rst:583 +msgid "Pet preferences and cognitive score relationship (boxplot)" msgstr "" #: ../../workshops/scientific-computing.rst:586 -#, python-format -msgid "" -"Box plots or box-whisker diagrams display, near the center of the box, " -"the **mean** of the data as a horizontal line. The lines bordering the " -"box represent **50% of the observations** (*interquartile range* ). " -"Outside the box, upwards and downwards, we find two whiskers: the lower " -"one represents the **mean of the values in the lower part of the " -"dataset**, and the upper one represents the **mean of the values in the " -"upper part of the dataset**. The points beyond the whiskers are " -"**outliers**." +msgid "Box plots or box-whisker diagrams display, near the center of the box, the **mean** of the data as a horizontal line. The lines bordering the box represent **50% of the observations** (*interquartile range* ). Outside the box, upwards and downwards, we find two whiskers: the lower one represents the **mean of the values in the lower part of the dataset**, and the upper one represents the **mean of the values in the upper part of the dataset**. The points beyond the whiskers are **outliers**." msgstr "" #: ../../workshops/scientific-computing.rst:590 -msgid "" -"An outlier is a value that is very different from the rest of the data " -"values. They must be taken into account because they can often create a " -"bias in the model we are trying to fit to the data." +msgid "An outlier is a value that is very different from the rest of the data values. They must be taken into account because they can often create a bias in the model we are trying to fit to the data." msgstr "" #: ../../workshops/scientific-computing.rst:592 -msgid "" -"The graph shows four boxes measuring cognitive ability for the following " -"groups:" +msgid "The graph shows four boxes measuring cognitive ability for the following groups:" msgstr "" #: ../../workshops/scientific-computing.rst:594 @@ -4156,41 +2963,23 @@ msgid "Those who like neither cats nor dogs." msgstr "" #: ../../workshops/scientific-computing.rst:599 -msgid "" -"The lowest mean is that of those who prefer dogs only, but by very " -"little. The box (and boundaries) representing dog lovers is also " -"\"wider,\" implying a larger variability in the individual test results " -"for this group. But this is not a very different dispersion from that of " -"those who prefer cats. All the means are within the limits of the other " -"boxes (interquartiles), which seems to indicate that, in fact, there are " -"not really important differences in the intelligence test scores for " -"these groups. This seems to undermine support for the initial hypothesis " -"we posed above." +msgid "The lowest mean is that of those who prefer dogs only, but by very little. The box (and boundaries) representing dog lovers is also \"wider,\" implying a larger variability in the individual test results for this group. But this is not a very different dispersion from that of those who prefer cats. All the means are within the limits of the other boxes (interquartiles), which seems to indicate that, in fact, there are not really important differences in the intelligence test scores for these groups. This seems to undermine support for the initial hypothesis we posed above." msgstr "" #: ../../workshops/scientific-computing.rst:603 -msgid "" -"If you want to see the figures, enter ``dog_or_cat = " -"ca_test.groupby(\"q997\")[\"cognitive_score\"].describe()`` in the " -"IPython Console and look at the results in the Variable Explorer. This " -"way you can see how many people prefer cats or dogs, and the means and " -"standard deviation of the cognitive ability test results for each group." +msgid "If you want to see the figures, enter ``dog_or_cat = ca_test.groupby(\"q997\")[\"cognitive_score\"].describe()`` in the IPython Console and look at the results in the Variable Explorer. This way you can see how many people prefer cats or dogs, and the means and standard deviation of the cognitive ability test results for each group." msgstr "" #: ../../workshops/scientific-computing.rst:605 -msgid "" -"To appreciate in context the real difference in the averages, let's " -"create some bar charts. We are now going to use Seaborn's barplot class. " -"On the x-axis we put again the qualitative variable (**q997**) and on the" -" y-axis the quantitative variable (cognitive_score). The data parameter " -"takes as argument the entire dataset." +msgid "To appreciate in context the real difference in the averages, let's create some bar charts. We are now going to use Seaborn's barplot class. On the x-axis we put again the qualitative variable (**q997**) and on the y-axis the quantitative variable (cognitive_score). The data parameter takes as argument the entire dataset." +msgstr "" + +#: ../../workshops/scientific-computing.rst:617 +msgid "Pet preferences and cognitive score mean representation (box graph)" msgstr "" #: ../../workshops/scientific-computing.rst:620 -msgid "" -"If the box plots indicated that the means did not show significant " -"differences (possibly due to chance), the bar plot confirms that these " -"differences are, in proportion, quite modest." +msgid "If the box plots indicated that the means did not show significant differences (possibly due to chance), the bar plot confirms that these differences are, in proportion, quite modest." msgstr "" #: ../../workshops/scientific-computing.rst:626 @@ -4198,36 +2987,19 @@ msgid "ANOVA test" msgstr "" #: ../../workshops/scientific-computing.rst:628 -msgid "" -"To make sure that the differences between the means are statistically " -"significant, we will perform an ANOVA (analysis of variance) because we " -"are going to compare the means of more than two groups." +msgid "To make sure that the differences between the means are statistically significant, we will perform an ANOVA (analysis of variance) because we are going to compare the means of more than two groups." msgstr "" #: ../../workshops/scientific-computing.rst:630 -msgid "" -"How does ANOVA work? This analysis tells us whether three or more means " -"are equal. If so, this would support the null hypothesis." +msgid "How does ANOVA work? This analysis tells us whether three or more means are equal. If so, this would support the null hypothesis." msgstr "" #: ../../workshops/scientific-computing.rst:634 -msgid "" -"The *null hypothesis* is an alternative prediction to the one we have " -"stated in our hypothesis. The null hypothesis simply states that the " -"observed differences in means are due to random variations that occur " -"when samples are collected." +msgid "The *null hypothesis* is an alternative prediction to the one we have stated in our hypothesis. The null hypothesis simply states that the observed differences in means are due to random variations that occur when samples are collected." msgstr "" #: ../../workshops/scientific-computing.rst:636 -msgid "" -"An ANOVA produces an *F-ratio* (also called F-statistic) that compares " -"the amount of systematic variation in the data (variation that can be " -"explained by the model or hypothesis) with the amount of unsystematic " -"variance (variation that cannot be explained by our hypothesis or model)." -" This means that F is the ratio of the model to its error. ANOVA also " -"produces a *p-value* that indicates the probability that the variation " -"can be attributed to the null hypothesis. The smaller the p-value, the " -"less likely it is that the observed variation is due to chance." +msgid "An ANOVA produces an *F-ratio* (also called F-statistic) that compares the amount of systematic variation in the data (variation that can be explained by the model or hypothesis) with the amount of unsystematic variance (variation that cannot be explained by our hypothesis or model). This means that F is the ratio of the model to its error. ANOVA also produces a *p-value* that indicates the probability that the variation can be attributed to the null hypothesis. The smaller the p-value, the less likely it is that the observed variation is due to chance." msgstr "" #: ../../workshops/scientific-computing.rst:640 @@ -4235,68 +3007,43 @@ msgid "Formatting the data" msgstr "" #: ../../workshops/scientific-computing.rst:642 -msgid "" -"To perform an ANOVA, let's start by pivoting the dataset with the " -"cognitive ability test results. The pet preferences values will now be " -"the column names, and each row will represent a person." +msgid "To perform an ANOVA, let's start by pivoting the dataset with the cognitive ability test results. The pet preferences values will now be the column names, and each row will represent a person." msgstr "" #: ../../workshops/scientific-computing.rst:646 -msgid "" -"To perform an ANOVA, certain requirements or assumptions must be met. For" -" example, the distributions of the residuals must be normal. This is not " -"the case here. There are more appropriate statistical tests for this " -"example, and the possibility of performing certain transformations on the" -" data in order to apply ANOVA in this case. However, we use ANOVA because" -" it is a fairly popular test, and because the purpose of this workshop is" -" to serve as an introduction to scientific computing with Spyder. We do " -"not intend here to obtain scientific results for publication." +msgid "To perform an ANOVA, certain requirements or assumptions must be met. For example, the distributions of the residuals must be normal. This is not the case here. There are more appropriate statistical tests for this example, and the possibility of performing certain transformations on the data in order to apply ANOVA in this case. However, we use ANOVA because it is a fairly popular test, and because the purpose of this workshop is to serve as an introduction to scientific computing with Spyder. We do not intend here to obtain scientific results for publication." msgstr "" #: ../../workshops/scientific-computing.rst:652 -msgid "" -"You will see that one of the columns includes the answers to the test " -"made by people who did not specify their preferences towards pets. Let's " -"delete that column." +msgid "You will see that one of the columns includes the answers to the test made by people who did not specify their preferences towards pets. Let's delete that column." +msgstr "" + +#: ../../workshops/scientific-computing.rst:658 +msgid "Pet preferences pivot table for ANOVA analysis." msgstr "" #: ../../workshops/scientific-computing.rst:661 -msgid "" -"Now let's rename the column names (for simplicity) and remove the records" -" that have missing values (with ``dropna``). The argument " -"``inplace=True`` allows you to directly modify a dataframe without having" -" to create a new one." +msgid "Now let's rename the column names (for simplicity) and remove the records that have missing values (with ``dropna``). The argument ``inplace=True`` allows you to directly modify a dataframe without having to create a new one." msgstr "" #: ../../workshops/scientific-computing.rst:671 -msgid "" -"In the variable ``dog_or_cat_col_names`` we have stored the names of the " -"values in order. This implies that: A = Both, B = Cats, C = Dogs, and D =" -" Neither." +msgid "In the variable ``dog_or_cat_col_names`` we have stored the names of the values in order. This implies that: A = Both, B = Cats, C = Dogs, and D = Neither." msgstr "" #: ../../workshops/scientific-computing.rst:673 -msgid "" -"To perform ANOVA, we are going to use a Python library called \"stats\", " -"in particular the ``f_oneway`` function. You can find more information " -"about this library by typing ``stats`` in the Help Pane or learn more " -"about the function by typing ``stats.f_oneway``." +msgid "To perform ANOVA, we are going to use a Python library called \"stats\", in particular the ``f_oneway`` function. You can find more information about this library by typing ``stats`` in the Help Pane or learn more about the function by typing ``stats.f_oneway``." +msgstr "" + +#: ../../workshops/scientific-computing.rst:675 +msgid "stats.f_oneway() help in Spyder's Help pane" msgstr "" #: ../../workshops/scientific-computing.rst:678 -msgid "" -"The help notes that this function requires an array-like with the " -"measurements for each group as an input (in our case, one sample for A, " -"one for B, one for C, and one for D). Since we have empty cells in each " -"column, let's remove them from each column (the ``f_oneway`` function " -"does not support missing values)." +msgid "The help notes that this function requires an array-like with the measurements for each group as an input (in our case, one sample for A, one for B, one for C, and one for D). Since we have empty cells in each column, let's remove them from each column (the ``f_oneway`` function does not support missing values)." msgstr "" #: ../../workshops/scientific-computing.rst:684 -msgid "" -"In the above line of code we are creating a list with 4 elements: the " -"test results of each column A, B, C, and D, without the missing values " -"(they are removed with ``dropna()``)." +msgid "In the above line of code we are creating a list with 4 elements: the test results of each column A, B, C, and D, without the missing values (they are removed with ``dropna()``)." msgstr "" #: ../../workshops/scientific-computing.rst:688 @@ -4304,56 +3051,27 @@ msgid "Run ANOVA" msgstr "" #: ../../workshops/scientific-computing.rst:690 -msgid "" -"Now, let's run ANOVA and store the output in two variables: ``f_value`` " -"and ``p_value``. Notice that since ``dog_or_cat_samples`` is a list, we " -"must pass the argument with an asterisk (``*dog_or_cat_samples``)." +msgid "Now, let's run ANOVA and store the output in two variables: ``f_value`` and ``p_value``. Notice that since ``dog_or_cat_samples`` is a list, we must pass the argument with an asterisk (``*dog_or_cat_samples``)." msgstr "" #: ../../workshops/scientific-computing.rst:696 -msgid "" -"With the help of ``stats.f_oneway`` in the Help Pane you can read a " -"description of the output of this function, some interesting notes about " -"the test, and some references that you can use to better understand the " -"nature of this analysis." +msgid "With the help of ``stats.f_oneway`` in the Help Pane you can read a description of the output of this function, some interesting notes about the test, and some references that you can use to better understand the nature of this analysis." msgstr "" #: ../../workshops/scientific-computing.rst:700 -msgid "" -"In the Help pane you will read that ANOVA requires certain assumptions to" -" be satisfied. In this workshop we have not checked those assumptions " -"because our goal is merely to show some Spyder functions that make the " -"research work easier. Thus, the results obtained in this example with " -"ANOVA should not be taken too rigorously." +msgid "In the Help pane you will read that ANOVA requires certain assumptions to be satisfied. In this workshop we have not checked those assumptions because our goal is merely to show some Spyder functions that make the research work easier. Thus, the results obtained in this example with ANOVA should not be taken too rigorously." msgstr "" #: ../../workshops/scientific-computing.rst:702 -msgid "" -"In the Variable Explorer you can find these two new variables: " -"``f_value`` and ``p_value``. ``p_value`` (0.6275) is well over 0.05, " -"which gives support to the null hypothesis (detracting support from our " -"hypothesis). To know if the F value obtained is greater than the " -"theoretically expected value, a **F critical value** must be calculated. " -"This can be estimated using the ``stats`` library, a significance level " -"(*q* ), and the degrees of freedom (*df* ) for the number of groups and " -"the number of observations:" +msgid "In the Variable Explorer you can find these two new variables: ``f_value`` and ``p_value``. ``p_value`` (0.6275) is well over 0.05, which gives support to the null hypothesis (detracting support from our hypothesis). To know if the F value obtained is greater than the theoretically expected value, a **F critical value** must be calculated. This can be estimated using the ``stats`` library, a significance level (*q* ), and the degrees of freedom (*df* ) for the number of groups and the number of observations:" msgstr "" #: ../../workshops/scientific-computing.rst:713 -msgid "" -"The value of ``f_critical`` (2.6241) is larger than that of ``f_value`` " -"(0.5813). This means that the variance between the means of these groups " -"is not significantly different. Since the *p* value indicates that we " -"cannot rule out random variations, then we have to discard our " -"hypothesis." +msgid "The value of ``f_critical`` (2.6241) is larger than that of ``f_value`` (0.5813). This means that the variance between the means of these groups is not significantly different. Since the *p* value indicates that we cannot rule out random variations, then we have to discard our hypothesis." msgstr "" #: ../../workshops/scientific-computing.rst:715 -msgid "" -"What is the conclusion of all this? There seems to be little or no " -"evidence in our data to think that there is indeed a correlation between " -"a person's pet preferences and his or her ability to solve practical or " -"abstract problems. Cat and dog owners, rejoice!" +msgid "What is the conclusion of all this? There seems to be little or no evidence in our data to think that there is indeed a correlation between a person's pet preferences and his or her ability to solve practical or abstract problems. Cat and dog owners, rejoice!" msgstr "" #: ../../workshops/scientific-computing.rst:721 @@ -4361,11 +3079,7 @@ msgid "Report and share" msgstr "" #: ../../workshops/scientific-computing.rst:723 -msgid "" -"In science, sharing results, good and bad, is critical. Today, in " -"scientific computing, it is also crucial to share data, and the code used" -" to process and analyze it. To help with this, we will use Spyder's Code " -"Analysis." +msgid "In science, sharing results, good and bad, is critical. Today, in scientific computing, it is also crucial to share data, and the code used to process and analyze it. To help with this, we will use Spyder's Code Analysis." msgstr "" #: ../../workshops/scientific-computing.rst:727 @@ -4373,18 +3087,15 @@ msgid "Code Analysis" msgstr "" #: ../../workshops/scientific-computing.rst:729 -msgid "" -"When you share code, you want it to be readable, clean, and not overly " -"complex. The Code Analysis component can help us detect these issues and " -"even bugs that can affect the performance of our code." +msgid "When you share code, you want it to be readable, clean, and not overly complex. The Code Analysis component can help us detect these issues and even bugs that can affect the performance of our code." msgstr "" #: ../../workshops/scientific-computing.rst:731 -msgid "" -"To see an example, you can open the :download:`scientific-computing-" -"astro.py ` file and run the " -":guilabel:`Code Analysis` (open the file in the pane and click on the " -"green triangular button in the upper right corner)." +msgid "To see an example, you can open the :download:`scientific-computing-astro.py ` file and run the :guilabel:`Code Analysis` (open the file in the pane and click on the green triangular button in the upper right corner)." +msgstr "" + +#: ../../workshops/scientific-computing.rst:733 +msgid "Code Analysis pane Example for astrological sign and cognitive ability" msgstr "" #: ../../workshops/scientific-computing.rst:736 @@ -4408,39 +3119,23 @@ msgid "Error: probable bugs in the code" msgstr "" #: ../../workshops/scientific-computing.rst:743 -msgid "" -"Each of these categories indicates the type of alert and the line on " -"which the potential issue occurs. For example, it tells us that line 129 " -"is too long, or that we imported numpy but did not use it at all in the " -"code." +msgid "Each of these categories indicates the type of alert and the line on which the potential issue occurs. For example, it tells us that line 129 is too long, or that we imported numpy but did not use it at all in the code." msgstr "" #: ../../workshops/scientific-computing.rst:745 -msgid "" -"These suggestions can contribute to sharing clean code. We recommend " -"using this panel to polish your code before publishing it." +msgid "These suggestions can contribute to sharing clean code. We recommend using this panel to polish your code before publishing it." msgstr "" #: ../../workshops/scientific-computing.rst:753 -msgid "" -"In this workshop we have taken the first steps to use Spyder for " -"scientific computing. We have seen how from a question or doubt a " -"hypothesis is raised. This question can also emerge from the exploration " -"of some data, which can be done by calculating some measures (such as " -"mean, median, standard deviation) or by drawing some plots." +msgid "In this workshop we have taken the first steps to use Spyder for scientific computing. We have seen how from a question or doubt a hypothesis is raised. This question can also emerge from the exploration of some data, which can be done by calculating some measures (such as mean, median, standard deviation) or by drawing some plots." msgstr "" #: ../../workshops/scientific-computing.rst:755 -msgid "" -"Often, in order to answer the question, we must process some data (for " -"example, for the construction of a cognitive ability test)." +msgid "Often, in order to answer the question, we must process some data (for example, for the construction of a cognitive ability test)." msgstr "" #: ../../workshops/scientific-computing.rst:757 -msgid "" -"Finally, we try to establish a relationship between variables with some " -"statistical tests. The results of these tests will support or not our " -"initial hypothesis." +msgid "Finally, we try to establish a relationship between variables with some statistical tests. The results of these tests will support or not our initial hypothesis." msgstr "" #: ../../workshops/scientific-computing.rst:762 @@ -4468,32 +3163,19 @@ msgid "Improve code readability with Code Analysis." msgstr "" #: ../../workshops/scientific-computing.rst:772 -msgid "" -"Spyder has many features that can help you do data analysis. You can find" -" more information in our `official documentation `_." +msgid "Spyder has many features that can help you do data analysis. You can find more information in our `official documentation `_." msgstr "" #: ../../workshops/scientific-computing.rst:782 -msgid "" -"If you want to check what you have learned, we suggest you analyze the " -"data to try to answer the following question: *Do the different zodiac " -"signs influence the results of a cognitive ability test?,* you can check " -"the Python script :download:`scientific-computing-astro.py ` if you have any doubts." +msgid "If you want to check what you have learned, we suggest you analyze the data to try to answer the following question: *Do the different zodiac signs influence the results of a cognitive ability test?,* you can check the Python script :download:`scientific-computing-astro.py ` if you have any doubts." msgstr "" #: ../../workshops/scientific-computing.rst:790 -msgid "" -"For a description of the dataset used, see the following `paper " -"`__:" +msgid "For a description of the dataset used, see the following `paper `__:" msgstr "" #: ../../workshops/scientific-computing.rst:792 -msgid "" -"Kirkegaard, E. O. W., & Bjerrekær, J. D. (2016). *The OKCupid dataset: A " -"very large public dataset of dating site users*. Open Differential " -"Psychology. doi:10.26775/odp.2016.11.03*" +msgid "Kirkegaard, E. O. W., & Bjerrekær, J. D. (2016). *The OKCupid dataset: A very large public dataset of dating site users*. Open Differential Psychology. doi:10.26775/odp.2016.11.03*" msgstr "" #: ../../workshops/scientific-computing.rst:794 @@ -4501,8 +3183,5 @@ msgid "A very fun book for learning statistics with R is the following:" msgstr "" #: ../../workshops/scientific-computing.rst:796 -msgid "" -"Field, A., Miles, J., & Field, Z. (2012). *Discovering statistics using " -"R*. SAGE Publications." +msgid "Field, A., Miles, J., & Field, Z. (2012). *Discovering statistics using R*. SAGE Publications." msgstr "" -