| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
- Convert the `importlib.metadata` subsection into a Tip.
- Remove the 'Summary' subsection header.
|
|
|
| |
Co-authored-by: Anderson Bravalheri <andersonbravalheri+github@gmail.com>
|
|
|
|
|
|
| |
Have checked that the snippets continue to work with this space
included. The space improves readability, hence this is probably a good
addition.
|
|
|
|
|
| |
Some extra indentation was causing the code block to be interpreted as a
code block within a blockquote.
|
|
|
|
|
|
| |
A few lines have been added in each of the sections on Console Scripts,
GUI scripts and Entry Points for Plugins. A line has also been added at
the end of the Syntax section to further make things clear.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Matter is courtesy of @abravalheri.
Have removed the `.ini` syntax highlighting of the code blocks so that
the syntax does not appear specific to `setup.cfg` but more
general-purpose.
Have also moved this section down to the end of the document so that
users can refer to it after having a basic understanding of how each of
console scripts, GUI scripts, and entry points work.
|
|
|
|
|
| |
Since it is deprecated and relevant details have already been covered in
a separate Dependencies Management page.
|
|
|
|
|
| |
Explains why quoting around `timmins.display` is required. Might be
helpful for beginners.
|
|
|
|
|
|
| |
Indentation was 8 spaces. Should be 4 spaces for consistency with other
`setup.cfg` snippets.
Also fixed up tab/spaces glitches in other places.
|
| |
|
|
|
|
|
| |
Had incorrectly used `timmins_plugin_fancy` instead of
`timmins-plugin-fancy` in several places.
|
|
|
|
|
| |
Had used `=` for separating key and value pair in dictionary, should
have `:` instead.
|
| |
|
| |
|
|
|
|
|
|
|
| |
- Old example was on loading entry points corresponding to console
scripts.
- Everything in that example has probably been included in the newer
example.
|
|
|
|
|
|
| |
- Defining multiple EPs under the same group
- Loading an EP by its name
- Loading all EPs in a given group
|
| |
|
|
|
|
| |
In the Advertising Behaviour section.
|
|
|
|
|
|
|
|
| |
- Indicated that for Python versions lower than 3.8, the backport
should be used.
- Indicated that the only change that needs to be made while using the
backport, is to replace `importlib.metadata` with
`importlib_metadata`.
|
|
|
|
| |
Snippet borrowed from Python Packaging user guide
|
| |
|
|
|
|
| |
Fixes warning emitted during `tox -e docs`
|
| |
|
|
|
|
|
| |
`PySimpleGUI` must be added to package dependencies in order to run the example in the GUI scripts section.
Co-authored-by: Anderson Bravalheri <andersonbravalheri+github@gmail.com>
|
|
|
| |
Co-authored-by: Anderson Bravalheri <andersonbravalheri+github@gmail.com>
|
|
|
|
|
|
| |
Changed the wording of the console scripts example, so that it is more
clear why `__main__.py` is required and why console scripts are a better
alternative.
|
|
|
|
|
|
| |
Added two lines to make this clear to users. Also added that any parsing
of user input can take place within the body of the function using
regular command-line parsing utilities.
|
|
|
|
|
|
|
|
|
|
| |
Removed a line stating that installers like Pip create wrapper scripts
around the function, and replaced it with a longer note at the end of
the GUI scripts section. This note includes a sample wrapper script
taken from the Python Packaging user guide. I think this longer note
along with an actual example of how the wrapper script might look like
will make it more clear to the user how console/GUI scripts work behind
the scenes.
|
|
|
|
|
|
| |
This note has been taken from the Python Packaging user guide. I think
it will be of interest to users who want to understand what is the
difference between `console_scripts` and `gui_scripts`.
|
|
|
|
|
|
|
|
|
|
| |
- Made separate section for `gui_scripts`
- Added an example `hello_world()` function that can be invoked using
a GUI script entry point
- Added `setup.cfg`, `setup.py` and `pyproject.toml` configuration
snippets
- Added that running `hello-world` in the terminal will open up a GUI
window.
|
|
|
|
|
|
| |
- Added output of the command `python -m timmins`.
- Added input and output when a console script is set up, i.e. when
`hello-world` is run on the terminal.
|
|
|
|
|
|
|
| |
- I think there is no need to include name, version, `packages`, etc.
They haven't been included in the equivalent `setup.cfg` snippet as
well as in other snippets in the documentation.
- Fixed up indentation by changing tabs to 4 spaces.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Using `src` layout for consistency with other examples in the
documentation.
- Using a tree diagram.
- Showing a `setup.py` file in the diagram with a comment indicating
that `setup.cfg` or `pyproject.toml` can also be used, again for
consistency with other examples in the documentation.
- Root directory is kept as `project_root_directory` to indicate that
any name can be used.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Fix a difference between the name of function definition and calling.
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|