how to parse yml in xlrelease without tampering inbuilt jython jar for adding pyyaml module? - xlrelease

how to parse yml in xlrelease without tampering inbuilt jython jar for adding pyyaml module?
I tried exploring all inbuilt modules in embedded jython jar. I couldnt find anything to parse yaml

Related

How can I Deploy a Django App as a .war file or in any other packaged way?

I have a Django Project for which I am trying to find a way to deploy as a .war file.
My objective is
to not reveal the source code during deployment
to De-Couple Django App from Database and deploy as a .war file. This will help me to update the app without re-initializing database.
As Jython is not supported for Python3, is there an alternative?
I also tried to create an exe through PyIntsaller but it acts as a malicious executable.

Is there any GCP managed service is available to store python whl files and use them in requirements.txt

I have one enterprise application built using python flask. There are several individual modules are there which I converted then to whl files and referring them in other modules inside requirements.txt.
Is there any GCP service available to store these whl files other than GCS so that I can directly refer them inside requirements.txt
There is an alpha feature in artifact registry that creates a private pipy for you. You should be able to store your wheel file and to get them, with pip, when you need it (and if you have the permission for).
I'm not a python expert and I didn't tested it, but the promise is here. I will be happy if you provide me feedbacks on this feature!

How can I use non-Python dependencies for my Django Zappa project?

I'm using a Python package called natto-py which requires a non-python Japanese tokeniser called MeCab.
Is it possible to use this for my Zappa project? How can MeCab be installed on Lambda (since pip does not work)?
Django 1.10 & Python 3.5
Just drop the binary in the same directory as your zappa project and zappa will zip it up and ship it to Lambda.
Since you are compiling your own binary, I would strongly recommend using a local docker environment for zappa to more closely match the AWS Lambda environment.
Also if your binary is big and will make your Lambda package bigger than 50MB then be sure to use the slim_handler option.

Installing new package in Weka API

Can someone explain to me the steps for including new package in Weka API using the package manager. I am able to install new packages to Weka using the GUI. I am confused how to do so in the API. How do I get the .jar file, which will support the newly added package? I want the weka.jar file to support libsvm.

Installing binary package on heroku

I want to deploy a binary package on heroku for use by my application
I am using the new Cedar stack, the official documentation states that it is recommended to use the vulcan tool for building binaries for heroku
So , i just did that, and the result was a tar.gz file containing a mini linux file system
Now what? how to deploy that binary package to heroku?
all the available documentation refer to using vulcan with buildpacks to create new applications
but, i want to deploy this binary package to an existing application
The question is , How can i do that?
should i put it in my git repo and upload it? if so, where should i put it? and how to unpack it and deploy it correctly on heroku to be available and correctly configured?
thanks
Joe
You need to incorporate that compiled output into a buildpack. See https://devcenter.heroku.com/articles/buildpack-binaries
Start with the buildpack for the language you're working in -- ruby / python / node. You'll probably just unpack the tarball into the a subdirectory of the vendor directory in the buildpack. Push your forked buildpack up to github and then point heroku to the buildpack.