[{"_1":2,"_154":-5,"_155":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_124":-5,"_125":11,"_126":17,"_127":11,"_128":-5,"_129":11,"_130":-5,"_131":132},"canonicalUrl","https://hub.docker.com/r/cbinckly/djextpkg-nginx/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","cbinckly","reponame","djextpkg-nginx","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-09-10T22:27:37.673384Z","description","","is_private","last_updated","2019-12-19T20:08:53.030128Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",1348,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n\n \n \n \n \n Python Package Manager for Orchid Extender - README\n \n \n \n\n\n

The Python Package Manager for Orchid Extender

The Python Package Manager for Orchid Extender unlocks the full potential of Python for customizing Sage 300. It enables quick and easy management of the embedded Python installation used by Extender and supports installation of most of the 195,000 packages from the Python Packaging Index or any custom package from a version control system (VCS) repository.

What is the problem?

Extender uses an embedded Python installation that does not include the usual executables or run in a standards compliant shell. This makes it difficult to leverage Python's package ecosystem when using Extender to customize Sage 300.

How does it work?

The Python Package Manager for Orchid Extender makes it easy to install, uninstall, and retrieve the information for packages. It works by temporarily creating a fully functioning Python environment and using pip, the standard Python package manager, to manage the Extender Python installation.

How do I get a copy?

You can download the latest version. To use it the package manager you'll need a license. Request a seven day trial.

How do I install it?

The module must be installed and run as a Windows Administrator. Open the Sage desktop and navigate to Extender -> Setup. Open the Modules screen.

In the modules screen, click Import and select the VIEXTPKG.2665093.vi file. Once the import is complete, close the Modules screen.

From the Extender -> Setup menu, open the Custom Table Editor. In the Custom Table Editor, select the Python Package Manager Configuration table and click Load. Input your Client ID and click Add to save the entry.

That's it, you're all ready to go.

How do I run it?

A new icon for the Python Package Manager is created in the Extender -> Setup menu when the module is installed.

The Python Package Manager can also be run by opening the Scripts screen from the Extender -> Setup menu, highlighting PackageManager.2665093 in the grid, and clicking Run.

How do I use it?

The Package Manager creates a temporary Python environment on start up, which can take a minute or two. The first time you open the screen you may also be notified that pip is out of date and will be upgraded.

Once the Package Manager screen opens, you have a couple of choices.

Install a New Package

Install a new package by filling in the Package Name and clicking 'Install'. The Python Package Manager automatically resolves and installs all required package dependencies.

You can also provide a VCS URI to any repository pip can install from. See VCS Support for more information.

Once the package installation completes an alert pops up with the result.

Manage an Existing Package

When the Package Manager starts, it takes an inventory of all the packages installed. Any of these packages can be upgraded or uninstalled: simply select the package from the Installed Packages drop down and click 'Upgrade' or 'Uninstall'.

Once the action is complete an alert provides the result.

What can I use it for?

Installing and removing packages! This alone unlocks lots of new opportunities for Extender.

Leverage libraries

Need to parse an excel file, do calculations with Julian Dates, access a database or web service like AWS? Maybe a little AI to perform dynamic validations?

Simply install a package from the Python Package Index and save yourself from recreating the wheel.

Create your own

Create and publish your own libraries to keep DRY and maximize code re-use. Package code that you use frequently across scripts and re-use the code from your package to save time, improve maintainability, and deliver highly readable code focused on your customer's business logic.

This approach makes backporting bug-fixes to existing customers simple. Simply fix the code, publish a new version of the package, and upgrade the Package in one click using the Python Package Manager for Extender! No need to redistribute new module files.

Have a look at a new workflow for developing and deploying Extender scripts leveraging the Python Package Manager for Extender.

VCS Support

Pip can install directly from a Version Control System. Supported systems include git, subversion, mercurial, and bazaar. This makes development and testing of packages much easier: install the package directly from the code repository in editable mode and upgrades will use the latest commit.

The Package Manager depends on pip, and can do all the things that pip can, so check out pip's docs on working with VCS for supported schemes and syntax.

Note that to download packages using a VCS the binaries or supporting libraries for the VCS must be installed seperately. At present, the SSH transport protocol is not supported.

Debugging and Viewing the Log

Some packages cannot be installed. In particular, those that require custom extensions be compiled in place are not supported.

To figure out why a particular action failed, or just to see a transcript of the package actions performed, use the 'View Log' button. This will open the logs for the last two operations in the default viewer for text (.txt) files.

Help!

If ever things aren't working as expected, a package you need won't install, or you accidentally uninstall pip (please, never do this), drop us a line and we will help to get you running.

\n\n\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",40402804,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},"content_type","creator",5841846,"full_size",9421846,"id",68542029,"images",[97],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},"architecture","amd64","digest","sha256:324c6706971d88daa1d3a238e9da055785667d52ec208aedec576d856a040e8e","features","last_pulled","2026-09-21T19:38:20.730197154Z","last_pushed","2019-12-19T20:08:53Z","os","linux","os_features","os_version","size","variant","2019-12-19T20:08:52.759605Z","last_updater","last_updater_username","media_type","latest","repository",7681025,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":135,"_142":143,"_131":152,"_153":11},{"_36":136,"_38":137,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":138,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":139,"_75":11,"_76":141,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":140},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_144":60,"_145":-5,"_146":-5,"_147":148},"count","next","previous","results",[149],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":150,"_46":113,"_114":90,"_115":29,"_116":52,"_53":117,"_118":119,"_120":104,"_121":113,"_122":62,"_123":17},[151],{"_98":99,"_100":101,"_102":44,"_103":104,"_105":106,"_107":108,"_109":44,"_110":-5,"_111":92,"_59":62,"_112":-5},[],"canDeleteTags","actionData","errors"]

cbinckly/djextpkg-nginx

Tags for cbinckly/djextpkg-nginx