Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finalize port to Python 3 / Gtk 3 #1022

Open
wants to merge 157 commits into
base: master
Choose a base branch
from
Open

Conversation

cydanil
Copy link
Contributor

@cydanil cydanil commented Jun 16, 2021

Description

This PR brings further fixes, which makes Gourmet operate almost as well as the Python 2 version.

It fixes:

  • Issues with saving new recipes;
  • Rating to text in recipe browser;
  • Path generation in recipe browser;
  • Alphabetical ordering of recipes in browser;
  • KeyEditor plugin;
  • Pin dependencies versions;
  • Switching windows with the 'Go' menu;
  • Index error when updating ingredient key;
  • String slicing in MasterCook importer;

It introduces:

  • AppImage support;
  • Integrating i18n into the build process
  • Removing dependency on argcomplete;
  • Copying recipes to clipboard from Ctrl-C and context menu.

Downloads are available here !

Thanks!
Cyril :)

closes #1014
closes #1017
closes #1016
closes #1012
closes #1011
closes #996
closes #994
closes #962
closes #955

gnarlyquack and others added 30 commits October 29, 2020 13:38
Let's ensure topic branches are in a usable state before pull requests
are made
Use setuptools.find_packages to avoid manually maintaining the package
list.

This restores __init__.py to the gourmet/exporters directory so it can
be discovered.

This also eliminates a bug in the previous crawl_plugins function that
erroneously discovered __pycache__ and other non-source directories.
We probably don't want to include tests when building non-source
distributions, and non-development installs may not have the
dependencies installed to run them anyway.
This can cause installation to fail if we end up trying to import a
dependency that isn't (yet) installed.
Generally the project root will be our current working directory, which
Python automatically includes in its system path. Since gourmet is no
longer in the project root, we must now explicitly install it to run it,
which helps ensure we have a working, installable distribution.
We can now just "graft" the src directory, which means any additional
package data will be automatically included.
Gourmet can now be installed in one step and plugin-specific
dependencies can be optionally installed using 'extras_require'.

setuptools is removed as a requirement since this provides the build
system and must already be installed for anything to work.
A development install can now be installed in one step using
'development.in'. This installs gourmet in "editable" mode as well as
additional development dependencies.

'development.txt' is renamed to 'development.in' to support pinning of
dependencies (using, e.g., pip-tools). Unfortunately, this only works
for local installs since gourmet is a "local" package and results in a
non-portable, absolute file path being generated in 'development.txt'.
Consequently, 'development.txt' is added to .gitignore, and build
environments can just use 'development.in' directly.

wheel is removed as a development dependency since it must already be
installed in order for pip to build wheels when installing dependencies.
But do allow them to be manually triggered.

This reverts commit 65ffca7.
Fixes imports from ica.se, nytimes, and allrecipes.
* Set images to None in database upon deletion
* Remove deprecated to_unicode helper function
This copies the FAQ and LICENSE into the package so they are available
as a resource.
This option and setting appear to been removed since at least commit
648a40f in October 2008.
All package data is now maintained within the gourmet package itself, so
no need to look for plugins in a build directory.
@cydanil cydanil changed the title Fix most Python3 port issues Finalize port to Python 3 / Gtk 3 Jul 1, 2021
@fbobraga
Copy link
Contributor

How to install on raspberry pi?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment