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

BF(PY3): workaround for python3.4 on debian returning obnoxious SC_ARG_MAX #3165

Merged
merged 1 commit into from Feb 14, 2019

Conversation

@yarikoptic
Copy link
Member

@yarikoptic yarikoptic commented Feb 14, 2019

it returns 2**62 number when running the package build.

Closes #3150

…G_MAX

it returns 2**62 number when running the package build.

Closes datalad#3150
kyleam
kyleam approved these changes Feb 14, 2019
@kyleam kyleam merged commit 9c6f6ab into datalad:master Feb 14, 2019
2 of 3 checks passed
@yarikoptic yarikoptic deleted the bf-python34-long branch Feb 15, 2019
@yarikoptic yarikoptic added this to the Release 0.11.3 milestone Feb 15, 2019
yarikoptic added a commit that referenced this issue Apr 6, 2019
 ## 0.11.3 (Feb 19, 2019) -- read-me-gently

 Just a few of important fixes and minor enhancements.

 ### Fixes

 - The logic for setting the maximum command line length now works
   around Python 3.4 returning an unreasonably high value for
   `SC_ARG_MAX` on Debian systems. ([#3165])

 - DataLad commands that are conceptually "read-only", such as
   `datalad ls -L`, can fail when the caller lacks write permissions
   because git-annex tries merging remote git-annex branches to update
   information about availability. DataLad now disables
   `annex.merge-annex-branches` in some common "read-only" scenarios to
   avoid these failures. ([#3164])

 ### Enhancements and new features

 - Accessing an "unbound" dataset method now automatically imports the
   necessary module rather than requiring an explicit import from the
   Python caller. For example, calling `Dataset.add` no longer needs to
   be preceded by `from datalad.distribution.add import Add` or an
   import of `datalad.api`. ([#3156])

 - Configuring the new variable `datalad.ssh.identityfile` instructs
   DataLad to pass a value to the `-i` option of `ssh`. ([#3149])
   ([#3168])

* tag '0.11.3': (35 commits)
  ENH: Finalized changelog entry for 0.11.3
  [DATALAD RUNCMD] CHANGELOG: Re-linkify 0.11.3 entries
  CHANGELOG: Mention #3168
  ENH: sshconnector: Get identity file with datalad.cfg.get()
  [DATALAD RUNCMD] CHANGELOG: Linkify 0.11.3 entries
  CHANGELOG: Add entries for 0.11.3
  BF/RF(TST): skip test if actual sudo chown call fails
  BF(TMP): declare check_datasets_datalad_org failing on windows
  BF(TST): replace not relevant trailing .pull test with .repo_info
  BF(BK): for some reason an exception on repo_info invocation isn't raised while on travis
  TST: test_ro_operations  via sudo (when possible)
  BF: allow to disallow git-annex branch merges for repo_info and use that in ls
  BF(unicode): use assure_unicode while formatting an exception
  BF(PY3): workaround for python3.4 on debian returning obnoxious SC_ARG_MAX
  BF: revert change for repo_info about not merging remote git-annex
  BF: set annex.merge-annex-branches=false for invocations not requiring updated remote information
  ENH: ssh: Support configuring an identity file
  ENH: SSHConnection: Support custom identity files
  ENH: ssh: Add identity_file parameter to get_connection_hash()
  TST+BF: sshconnector: Fix stale socket path construction
  ...
yarikoptic added a commit that referenced this issue Apr 6, 2019
 ## 0.11.3 (Feb 19, 2019) -- read-me-gently

 Just a few of important fixes and minor enhancements.

 ### Fixes

 - The logic for setting the maximum command line length now works
   around Python 3.4 returning an unreasonably high value for
   `SC_ARG_MAX` on Debian systems. ([#3165])

 - DataLad commands that are conceptually "read-only", such as
   `datalad ls -L`, can fail when the caller lacks write permissions
   because git-annex tries merging remote git-annex branches to update
   information about availability. DataLad now disables
   `annex.merge-annex-branches` in some common "read-only" scenarios to
   avoid these failures. ([#3164])

 ### Enhancements and new features

 - Accessing an "unbound" dataset method now automatically imports the
   necessary module rather than requiring an explicit import from the
   Python caller. For example, calling `Dataset.add` no longer needs to
   be preceded by `from datalad.distribution.add import Add` or an
   import of `datalad.api`. ([#3156])

 - Configuring the new variable `datalad.ssh.identityfile` instructs
   DataLad to pass a value to the `-i` option of `ssh`. ([#3149])
   ([#3168])

* tag '0.11.3':
  BF(TST): skip if windows OR root; catch any exception
yarikoptic added a commit that referenced this issue Apr 6, 2019
 ## 0.11.3 (Feb 19, 2019) -- read-me-gently

 Just a few of important fixes and minor enhancements.

 ### Fixes

 - The logic for setting the maximum command line length now works
   around Python 3.4 returning an unreasonably high value for
   `SC_ARG_MAX` on Debian systems. ([#3165])

 - DataLad commands that are conceptually "read-only", such as
   `datalad ls -L`, can fail when the caller lacks write permissions
   because git-annex tries merging remote git-annex branches to update
   information about availability. DataLad now disables
   `annex.merge-annex-branches` in some common "read-only" scenarios to
   avoid these failures. ([#3164])

 ### Enhancements and new features

 - Accessing an "unbound" dataset method now automatically imports the
   necessary module rather than requiring an explicit import from the
   Python caller. For example, calling `Dataset.add` no longer needs to
   be preceded by `from datalad.distribution.add import Add` or an
   import of `datalad.api`. ([#3156])

 - Configuring the new variable `datalad.ssh.identityfile` instructs
   DataLad to pass a value to the `-i` option of `ssh`. ([#3149])
   ([#3168])

* tag '0.11.3':
  Boost version to 0.11.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants