Search the Community
Showing results for tags 'packaging'.
-
Hi! I've put together a workflow to interact with Obsidian. It relies heavily on some Python libraries like NLTK and Gensim, and I've done my best to package them, following advice from @deanishe found elsewhere on this forum. However, I get an error when I try to run it on a different computer: ``` import regex._regex as _regex "ModuleNotFoundError:" No module named ‘regex._regex’ ``` For what I've gathered, that may have something to do with the fact that Regex (required by NLTK) comes with a precompiled binary that may not play well with the other system or its python interpreter. All my scripts have a shebang pointing to `/usr/bin/python3` and I'm comfortable with it as a minimum requirement, but is there any hope of properly packaging Regex with the workflow?
-
I've created a handful for workflows that we use at my office and I would love to have an easy way to batch export and update the metadata so that i can share them with people. Right now when i make a change export the workflow to disk and email it to people. It would be great if there was some way to automate this or script this out. so i could just run alfred -package workflow_name outputFile and then upload the workflows to an internal server or something like that. It this possible or just wishful thinking? Thanks
- 3 replies
-
- automation
- scripting
-
(and 2 more)
Tagged with:
-
There are currently several methods for packaging workflows, all with advantages and disadvantages of course. For example: deanishe uses a script similar to: https://gist.github.com/deanishe/b16f018119ef3fe951af documents the export function within Alfred itself: https://alfredworkflow.readthedocs.org/en/latest/tutorial_2.html#sharing-your-workflow shawnrice appears to use a shell script: https://github.com/shawnrice/packal-updater/blob/master/alfred.bundler.sh Wolph (me) uses a Makefile: https://github.com/WoLpH/alfred-converter/blob/master/Makefile It seems to me that there is a better solution though. The setuptools package is widely used within the Python community to compile, build and deploy packages to the PyPI servers but it can do more. The Sphinx-PyPI-upload-2 package for example (https://github.com/WoLpH/sphinx-pypi-upload) makes it possible to upload Sphinx documentation to the PyPI servers which can be built using the commands from Sphinx itself. With that regard I propose a new solution for packaging Alfred workflows: Use entry_points to create a bdist_alfred command similar to bdist_wheel (https://wheel.readthedocs.org/) Create a upload_packal command similar to upload_sphinx (https://github.com/WoLpH/sphinx-pypi-upload/blob/master/setup.py#L32-L36) Create a standard for specifying Alfred entry points through the setup.py
- 11 replies
-
- setuptools
- packaging
-
(and 2 more)
Tagged with: