poetry | Chinese modern poetry corpus collation , 3489 poets | Dataset library

I'd love to initialize a poetry-generated project without going through the interactive shell for versions and dependencies etc.

However, a few attempts of fiddling around with the command line options all failed.

Such as

I have a python 3.6 code-base which needs to be installed in the environment's site-packages directory in order to be called and used. After moving it to docker, I decided that I should set up a shared volume between the docker container and the host machine in order to avoid copying and installing the code on the container and having to rebuild every time I made a change to the code and wanted to run it. In order to achieve this, I had to change a lot of the import statements from relative to absolute. Here is the structure of the application:

I am trying to use SQLAlchemy 1.4 beta with Poetry. It is released on PyPi.

Poetry does not recognise the beta package in pyproject.toml:

While making a small thingy in javascript, I found that I could make comments /like these/

Because stack overflow's code doesn't color them, here's an image:

I haven't found anything about them, and I think they may have an extremely specific name and usage, because in no answer regarding comments I was able to find mentions of it.

For more specifity, I was using google's App Script, but because their documentation doesn't say anything about single slash comments, I doubt it is related to said IDE.

Also, I say it is a comment because when putting it in the middle of my code it acts like one, but the fact it's affected by the return shows it isn't really a comment, and leaves me even more clueless.

Any input or clue to continue searching would be greatly appreciated!

Edit: Indeed it wasn't a comment, it is instead a weird unused expression, that JS understood as a comment in the specific situation it was in.
Also I'd like to point out the speed of the answerer; I refreshed the page to fix a typo and it was already answered in clear detail, thanks!

Edit 2: Now knowing that it is an expression, I can see that a few of the things I found when looking for them, indeed mentioned them, for example this answer briefly noted that /[///]/ is an expression, but I confused the meaning of expression as "normal code" instead of the object meant for matching string patterns.

I am adding sections to our website and all but one of them are working the way I want: i.e. no margin between sections.

I'm not able to get this one page's sections to have no margin between sections; they have extra space beneath. I have went over the code with a fine tooth comb and cannot find the error.

I am first including the code of a sample page that works correctly:

I'm testing poetry and I was wondering if it is possible to install prebuilt packages from conda-forge, as cartopy without relying on conda (so keeping a 100% poetry process). I googled this a bit but the only way I found is to install poetry within a conda venv using pip and then installing from conda-forge using conda and then tweaking poetry files to make it aware of the conda venv so that the TOML is written properly.

Packages like cartopy are a pain to install if not from a prebuilt version, if possible I'd change my conda stack to poetry stack if something like poetry add [?conda-forge?] cartopy works

Thanks.

Poetry install:

mypy 0.812 allows the following useful type hint:

I have a python package where the dependencies is specified in a poetry.lock file for development and testing. I then build and publish the package, which gets installed on the production docker image. But here is the problem: the published package has its dependency specified in the tool.poetry.dependencies section of pyproject.toml, which could be different from poetry.lock. So it's possible that the production env ends up with dependencies different from testing env.

I can think of several ways to achieve consistency, but none of them seems that good to me:

1. Use the same set versions in pyproject.toml as in poetry.lock. This will guarantee the published package has the same dependencies as dev/test. But what's even the point of keeping a poetry.lock file at this point, since pyproject.toml can be used for poetry install as well if there is no poetry.lock file. I think this works, but then I don't understand why even have poetry.lock in the first place.

2. In the production docker image, checkout the poetry.lock file from package repo and run poetry install before installing the package itself. But this will increase the docker image size, introduce unnecessary config if the repo is private, and overall doesn't seem natural.

I'm pretty new to this part of Python so maybe one of these is the "standard" workflow. Or maybe I'm just completely missing something. Thanks for answering!