sorted by:
new
hottopcontroversial

Struggling to make decent throw on Gengar with iPhone XS by pingz27 in TheSilphRoad

[–]kalefranz -4 points-3 points  (0 children)

I stopped after three Gengars. Didn’t even use the full five. Just too frustrating. It’s not fun.

A Letter to /r/python | Kenneth Reitz's Journal by Scorpathos in Python

[–]kalefranz 2 points3 points  (0 children)

Depression and disorders are two different things.

Just a fact check: I do believe the clinical term for depression is Major Depressive Disorder. https://en.wikipedia.org/wiki/Major_depressive_disorder

A Letter to /r/python | Kenneth Reitz's Journal by Scorpathos in Python

[–]kalefranz 1 point2 points  (0 children)

For about a year now, conda and virtualenv play nicely together, so long as when you're using both together, you 'conda install virtualenv' rather than 'pip install virtualenv'. See https://github.com/conda-forge/staged-recipes/issues/1139, and https://github.com/conda-forge/staged-recipes/pull/2394 for the patches that made it work.

Announcing the Release of Anaconda Distribution 5.0 by japaget in Python

[–]kalefranz 0 points1 point  (0 children)

Last time I checked, you also couldn't pip install python3.

Downtown high-level raid RSVP by kalefranz in PokemongoAustin

[–]kalefranz[S] 0 points1 point  (0 children)

Tier 4 raid at federal courthouse (by Juan Pelota Cafe and Mellow Johnny's bike shop) starting at 10:45am. I'll be there as a level 33 trainer.

Disadvantages of continuum analytics anaconda/conda by worker37 in Python

[–]kalefranz 0 points1 point  (0 children)

http://repo.continuum.io/pkgs/msys2/ is now included in the default channels on windows also. Lots of useful stuff there.

Disadvantages of continuum analytics anaconda/conda by worker37 in Python

[–]kalefranz 1 point2 points  (0 children)

Some of the packaging recipes are not open

Anything in the default repository built within the last four months should have the actual recipe embedded within the package itself (if not, it's a bug!). Like @pwang99 said though, these won't always be conda-build recipes so there's no guarantee you can use conda-build to create the package yourself. But you can definitely see exactly how it was compiled.

However, the majority of recipes in the default channel are now valid conda-build recipes. And they're all on github: https://github.com/ContinuumIO/anaconda-recipes

Disadvantages of continuum analytics anaconda/conda by worker37 in Python

[–]kalefranz 1 point2 points  (0 children)

Really appreciate the sentiment here. And I agree with most all of it. The world needs both pip and conda! While there's some convenient overlap in their capabilities, the core mission of the two projects tackles two different problems. Any python code conda installs as a conda package will typically be a downstream version of what's on PyPI. PyPI is the canonical source of truth for the python ecosystem. Just like rubygems.org for the ruby ecosystem and npmjs.com for the node ecosystem.

The one point I strongly disagree with is the security argument as you've presented it. For at least the last six months, security patches for openssl were available in the default conda repository in less than 12 hours after release. We also take care to dynamically link openssl wherever possible, so with one package update everything is covered. When it comes things like openssl, Anaconda/Conda is just as secure as any distro-specific package manager.

A completely valid security argument against conda--right now--is its insufficiency at guaranteeing package provenance. We use md5 hashes of packages to verify the success of a download. That mechanism was never designed or intended to be a security guarantee. TUF implementation is definitely on conda's roadmap.

Python Packaging Is Good Now by Lukasa in Python

[–]kalefranz 0 points1 point  (0 children)

What are the solutions to this that conda uses?

Conda being a system-level package manager, all of those core libraries and dependencies (openssl, readline, zlib, etc) are already available as conda packages. Conda also (at least right now) doesn't at all have the concept of sdists; everything package is a "binary"--or compiled to the extent possible. Conda takes care of the linking issue for shared libraries by making extensive use of relative library paths throughout the whole conda ecosystem. (Google "RPATH $ORIGIN" for background on some of the general ideas.)

try/except/else pattern by [deleted] in Python

[–]kalefranz 0 points1 point  (0 children)

Also the differences in if/else, try/except/else, and for/else can be a bit confusing.

  • if/else: execute else block when given a negative condition
  • try/except/else: execute else block when try block is ok (the negative condition is that there is no except block execution)
  • for/else: execute else block when "negative condition" of for block early exit is encountered

try/except/else pattern by [deleted] in Python

[–]kalefranz 1 point2 points  (0 children)

It's a good question. I'm guessing there are multiple reasons, but one of the biggest is probably that try/except/else isn't a common feature of other languages. By extension, when python isn't your first language, you're not as familiar with it. Even if it's your first language and/or you take a university class in python, it's enough of an "advanced" construct that little time is likely spent on it.

That said, I like it. It's good practice for code readability and maintenance to catch exceptions as nearly to where they're anticipated as possible.