Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wiki: Python discussion and Python and Plone development #13244

Closed
garbas opened this issue Feb 21, 2016 · 8 comments
Closed

wiki: Python discussion and Python and Plone development #13244

garbas opened this issue Feb 21, 2016 · 8 comments

Comments

@garbas
Copy link
Member

garbas commented Feb 21, 2016

https://nixos.org/wiki/Python_discussion
https://nixos.org/wiki/Python
https://nixos.org/wiki/Plone_development

ping @domenkozar @datakurre @cillianderoiste could you check that all info from above wiki pages is in nixpkgs manual.

@garbas garbas added this to the Move the wiki! milestone Feb 21, 2016
@FRidh
Copy link
Member

FRidh commented Feb 21, 2016

I'm updating Python docs in #13320

@datakurre
Copy link
Contributor

@FRidh Thanks. I was not aware of python-on-nix docs. Would've definitely helped earlier.

@garbas I'd just drop "Plone development" chapter for now, and replace it later with more generic "Buildout" development later.

@garbas, @cillianderoiste What should we do with various zc_buildout versions vs. zc_buildout_nix? Should zc_buildout_nix behavior be made the default? (And maybe an option to turn it off at will.) zc_buildout_nix is patched to always prefer packages from the current nix environment and made possible to e.g. properly build Plone in Nix until namespace packages broke with buildout due to wheels.

@datakurre
Copy link
Contributor

@garbas Here's the buildout namespace issue, which I mentioned: #12141

@FRidh
Copy link
Member

FRidh commented Jun 23, 2018

@Profpatsch if you close an issue, please motivate way.

@datakurre
Copy link
Contributor

I wonder, how many there are using buildout-based development with nix? @cillianderoiste? I have a team using nix with buildout but the current version of pythonPackages.zc_buildout_nix should just work.

@cillianderoiste I do have one more patch locally for my team for zc_buildout_nix:

    postInstall = ''                                                            
      sed -i "s|import sys|import sys\nimport os\nsys.executable = os.path.join(sys.prefix, 'bin', os.path.basename(sys.executable))|" $out/bin/buildout
      cat $out/bin/buildout                                                     
    '';

It fixes zc.buildout-generated scripts to have python interpreter with zc.buildout available. Of course, it does not prevent garbage collection of those envs. Maybe I should propose that as a patch for zc_buildout_nix...

@Profpatsch Profpatsch reopened this Jun 23, 2018
@Profpatsch
Copy link
Member

@FRidh I batch-closed all wiki issues, after consultation with garbas. Feel free to reopen anything that is still relevant (or worked on).

Actually, I probably should shoot a mail to the discourse as well.

@Profpatsch
Copy link
Member

Discourse thread

@FRidh
Copy link
Member

FRidh commented Mar 3, 2019

Nothing actionable here I think, so closing.

@FRidh FRidh closed this as completed Mar 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants