go to post Raj Singh · Nov 18 Yes! Our default stance -- barring security or other concerns -- is to make these bug reports public after we moderate. We didn't think about needing the submitter to opt-in to public status because I assumed that would be expected. @Dmitry Maslennikov I hear you that an important audience for this is the open source developer who isn't a formally licensed InterSystems customer.
go to post Raj Singh · Nov 17 Remember we are not trying to replace the official way of handling customer bug reports, which is still via the WRC. We are simply expanding our ability to listen to users, with a way for developers who aren't operating under formal licenses -- mainly during hackathons or contests -- to get us information about problems they may be seeing.
go to post Raj Singh · Oct 10 Agreed. I think I now understand you don't need to know how to authenticate a user. Do you want to (after initial authentication) pass those authentication credentials to another app?
go to post Raj Singh · Aug 25 This might help: https://community.intersystems.com/post/vscode-and-csp-what-did-i-miss#c...
go to post Raj Singh · Aug 20 @Ronaldo Nascimento what kind of connection? DBAPI? Can you share a code sample?
go to post Raj Singh · Aug 19 Thanks for the question, @André Dienes Friedrich. The simple answer is no, there is no set expiration time. We like to keep deprecated features around as long as a good number of users are depending upon them in production. Some reasons why a feature would be removed are: keeping the deprecated library conflicts with important features of the replacement; it becomes too burdensome to support the deprecated one; or the deprecated one becomes a risk in terms of security or data integrity. That hasn't happened yet with the libraries you mention.
go to post Raj Singh · Jul 6 Hi @Justin Millette. It isn't possible to support multiple in-process Python virtual environments simultaneously. This is because a Python virtual environment is defined at the operating system level, not the application level. A virtual environment consists of a specific Python executable and a set of associated libraries running within an OS-level process. Since IRIS itself is an OS-level process, it can only host a single Python interpreter when running Python code in-process. Supporting multiple virtual environments in this context would require multiple OS processes, which would negate the benefits of embedded execution. If you really need virtual environments, use normal client-side Python.
go to post Raj Singh · Jul 3 Sounds like it's more accurate to say you want to exclude web applications that ship with IRIS, not only those that are of type "System." Using the security.applications table @David Hockenbroch mentioned, I'd exclude those from namespaces InterSystems uses for product, e.g.: SELECT name,namespace,resource,type FROM security.applications WHERE NameSpace not in ('%SYS','HSSYS','HSLIB','HSCUSTOM')
go to post Raj Singh · Jun 9 Hi Nezla. It sounds like you want to do Python-only development. In that case, you'll want to write a Flask app or similar. Search this site for Flask and you'll find many articles, such as this one: https://community.intersystems.com/post/simplest-template-rest-crud-inte....
go to post Raj Singh · May 22 Let me comment separately on the venv question. Remember, you could choose to run your flask app in a separate container and use Docker compose to orchestrate the containers. That will give you all the normal venv options. If, however, you choose to run your flask app embedded in IRIS (running using embedded Python), you are running in-process with IRIS, and that process can't load and unload Python virtual environments while maintaining the benefits of running in embedded mode, so therefore the implication for containerization is that yes you do have to create a new base image when you want to add a package, but that's the tradeoff.
go to post Raj Singh · May 21 Have you seen https://github.com/grongierisc/iris-flask-template? This agrees with a lot of what you found out, but might be a little simpler. The only thing I changed for my work is my pip3 install command in Dockerfile adds a --target as recommended by @Dmitry Maslennikov: RUN pip3 install -r requirements.txt --target /usr/irissys/mgr/python
go to post Raj Singh · Mar 13 pip install sqlalchemy-iris[intersystems] returns: zsh: no matches found: sqlalchemy-iris[intersystems] Could this be because I'm on an M2 Mac?